OData meeting #41, Thursday, 13 Jun 2013, 0900 - 1800 PT and Friday, 14 Jun 2013, 0900 - 1600 PT

Note: For explanations of conventions and other formal aspects common to OData TC meeting minutes which are used in this document please cf. “Formal Aspects of Meeting Minutes”.

Meeting chaired by Barbara Hartel

Day One

1 Roll call

1.1 Members Present:

    Anila Kumar GVN (CA Technologies)
    Barbara Hartel (SAP AG)
    Dale Moberg (Axway Software)
    Edmond Bourne (BlackBerry)
    Gerald Krause (SAP AG)
    Hubert Heijkers (IBM)
    John Willson (Individual)
    Ken Baclawski (Northeastern University)
    Martin Zurmuehl (SAP AG)
    Matthew Borges (SAP AG) a.k.a. Matt
    Michael Pizzo (Microsoft) a.k.a. Mike
    Ralf Handl (SAP AG)
    Shishir Pardikar (Citrix Systems)
    Stefan Drees (Individual)
    Susan Malaika (IBM)

Quorum achieved. Details cf. normative attendance sheet for this meeting.

2 Approval of Agenda

Agenda approved as published.

3 Approval of Minutes from Previous Meeting(s)

3.1 Approval of Minutes of 2013–06–06 Meeting#40

Meeting minutes approved with no objections.

4 Review of Issues List (IL) and Progress

Notes:

4.1 Issues in Applied state

Stefan:

I move to close the issues ODATA–102, ODATA–126, ODATA–152, ODATA–153, ODATA–165, ODATA–290, ODATA–295, ODATA–346, ODATA–351, ODATA–364, ODATA–365, ODATA–366, ODATA–367, ODATA–368, ODATA–369, ODATA–370, ODATA–371, ODATA–373, ODATA–375, ODATA–376, ODATA–378, ODATA–380, ODATA–382, ODATA–383, ODATA–384, ODATA–385, ODATA–388, ODATA–389, ODATA–390, ODATA–392, ODATA–393, ODATA–394, ODATA–395, ODATA–396, ODATA–397, ODATA–398, ODATA–399, ODATA–400, ODATA–401, ODATA–402, ODATA–403, ODATA–404, ODATA–406, ODATA–407, ODATA–408, ODATA–409, ODATA–411, ODATA–412, ODATA–414, ODATA–417, ODATA–418, ODATA–420, ODATA–421, ODATA–422, and ODATA–429 as applied. Martin seconds.

No further discussion. No objections. The motion passes.

4.1.1 ODATA–102

ODATA–102:
“Representing Actions/Functions Bound to Multiple Entities” [components: OData JSON Format, OData ATOM Format] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–102:
“Representing Actions/Functions Bound to Multiple Entities” [components: OData JSON Format, OData ATOM Format] is Closed with no objections.

4.1.2 ODATA–126

ODATA–126:
“Metadata as an OData service” [components: OData Protocol, OData CSDL, OData URL Conventions] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–126:
“Metadata as an OData service” [components: OData Protocol, OData CSDL, OData URL Conventions] is Closed with no objections.

4.1.3 ODATA–152

ODATA–152:
“JSON: Add examples for all request and response types using a consistent sample OData service” [component: OData JSON Format] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–152:
“JSON: Add examples for all request and response types using a consistent sample OData service” [component: OData JSON Format] is Closed with no objections.

4.1.4 ODATA–153

ODATA–153:
“Atom: Add examples for all request and response types using a consistent sample OData service” [component: OData ATOM Format] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–153:
“Atom: Add examples for all request and response types using a consistent sample OData service” [component: OData ATOM Format] is Closed with no objections.

4.1.5 ODATA–165

ODATA–165:
“Support Cross-joins” [components: OData URL Conventions, OData ABNF Construction Rules] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–165:
“Support Cross-joins” [components: OData URL Conventions, OData ABNF Construction Rules] is Closed with no objections.

4.1.6 ODATA–290

ODATA–290:
“Check the use of SHOULD vs. MUST in Protocol spec” [component: OData Protocol] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–290:
“Check the use of SHOULD vs. MUST in Protocol spec” [component: OData Protocol] is Closed with no objections.

4.1.7 ODATA–295

ODATA–295:
“Services should be able to ‘advertise’ what form of change tracking they support” [component: OData Protocol] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–295:
“Services should be able to ‘advertise’ what form of change tracking they support” [component: OData Protocol] is Closed with no objections.

4.1.8 ODATA–346

ODATA–346:
“Order of child elements of MUST be preserved” [components: OData CSDL, OData ATOM Format, OData Protocol, OData JSON Format] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–346:
“Order of child elements of MUST be preserved” [components: OData CSDL, OData ATOM Format, OData Protocol, OData JSON Format] is Closed with no objections.

4.1.9 ODATA–351

ODATA–351:
“Define ID, ReadLink and EditLink in Part 1: Protocol, define representation in Atom and JSON” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–351:
“Define ID, ReadLink and EditLink in Part 1: Protocol, define representation in Atom and JSON” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Closed with no objections.

4.1.10 ODATA–364

ODATA–364:
“Explicitly state that the restriction that a property MUST NOT have the same name as its containing type only applies to directly declared properties” [component: OData CSDL] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–364:
“Explicitly state that the restriction that a property MUST NOT have the same name as its containing type only applies to directly declared properties” [component: OData CSDL] is Closed with no objections.

4.1.11 ODATA–365

ODATA–365:
“Rename edm:AssertType to edm:Cast and clarify behavior of edm:Cast and cast()” [components: OData URL Conventions, OData CSDL] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–365:
“Rename edm:AssertType to edm:Cast and clarify behavior of edm:Cast and cast()” [components: OData URL Conventions, OData CSDL] is Closed with no objections.

4.1.12 ODATA–366

ODATA–366:
“Clarify whether server-generated properties can be omitted in POST, even if they are not nullable” [component: OData Protocol] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–366:
“Clarify whether server-generated properties can be omitted in POST, even if they are not nullable” [component: OData Protocol] is Closed with no objections.

4.1.13 ODATA–367

ODATA–367:
“Explicitly state that server MAY expand results beyond what’s requested with $expand” [component: OData Protocol] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–367:
“Explicitly state that server MAY expand results beyond what’s requested with $expand” [component: OData Protocol] is Closed with no objections.

4.1.14 ODATA–368

ODATA–368:
“Deep insert: if server responds with 201 Created it MUST respond with at least the expansion depth of the insert operation” [component: OData Protocol] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–368:
“Deep insert: if server responds with 201 Created it MUST respond with at least the expansion depth of the insert operation” [component: OData Protocol] is Closed with no objections.

4.1.15 ODATA–369

ODATA–369:
“POST to navigation link with binding information leading to a different ‘parent’ is invalid” [component: OData Protocol] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–369:
“POST to navigation link with binding information leading to a different ‘parent’ is invalid” [component: OData Protocol] is Closed with no objections.

4.1.16 ODATA–370

ODATA–370:
“Disallow Nullable facet for collection-valued properties” [component: OData CSDL] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–370:
“Disallow Nullable facet for collection-valued properties” [component: OData CSDL] is Closed with no objections.

4.1.17 ODATA–371

ODATA–371:
“Clearly describe behavior of PUT for structural and navigation properties” [component: OData Protocol] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–371:
“Clearly describe behavior of PUT for structural and navigation properties” [component: OData Protocol] is Closed with no objections.

4.1.18 ODATA–373

ODATA–373:
“Add boolean expressions that can be used in <edm:If>” [component: OData CSDL] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–373:
“Add boolean expressions that can be used in <edm:If>” [component: OData CSDL] is Closed with no objections.

4.1.19 ODATA–375

ODATA–375:
“Allow querying collections of complex type instances similar to querying collections of entities” [component: OData URL Conventions] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–375:
“Allow querying collections of complex type instances similar to querying collections of entities” [component: OData URL Conventions] is Closed with no objections.

4.1.20 ODATA–376

ODATA–376:
“Navigation link representation for navigation properties of complex type instances” [component: OData JSON Format] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–376:
“Navigation link representation for navigation properties of complex type instances” [component: OData JSON Format] is Closed with no objections.

4.1.21 ODATA–378

ODATA–378:
“Support relative IRIs for ids in JSON” [components: OData JSON Format, OData ATOM Format] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–378:
“Support relative IRIs for ids in JSON” [components: OData JSON Format, OData ATOM Format] is Closed with no objections.

4.1.22 ODATA–380

ODATA–380:
“Insert a section in protocol (and similar in JSON and ATOM) named ‘Security Considerations’ (before ‘Conformance’)” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–380:
“Insert a section in protocol (and similar in JSON and ATOM) named ‘Security Considerations’ (before ‘Conformance’)” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Closed with no objections.

4.1.23 ODATA–382

ODATA–382:
“Conformance clauses need to refer to sections defining aspects of conformance and do so uniformly” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–382:
“Conformance clauses need to refer to sections defining aspects of conformance and do so uniformly” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Closed with no objections.

4.1.24 ODATA–383

ODATA–383:
“Number all examples in all documents” [components: OData CSDL, OData ATOM Format, OData Protocol, OData JSON Format, OData URL Conventions] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–383:
“Number all examples in all documents” [components: OData CSDL, OData ATOM Format, OData Protocol, OData JSON Format, OData URL Conventions] is Closed with no objections.

4.1.25 ODATA–384

ODATA–384:
“Normative text needs to be typographically distinct from examples” [components: OData CSDL, OData ATOM Format, OData Protocol, OData JSON Format, OData URL Conventions] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–384:
“Normative text needs to be typographically distinct from examples” [components: OData CSDL, OData ATOM Format, OData Protocol, OData JSON Format, OData URL Conventions] is Closed with no objections.

4.1.26 ODATA–385

ODATA–385:
“Overview wording suggestion” [component: OData Protocol] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–385:
“Overview wording suggestion” [component: OData Protocol] is Closed with no objections.

4.1.27 ODATA–388

ODATA–388:
“Remove ‘when’ from OData-specific items in delta responses” [components: OData JSON Format, OData ATOM Format] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–388:
“Remove ‘when’ from OData-specific items in delta responses” [components: OData JSON Format, OData ATOM Format] is Closed with no objections.

4.1.28 ODATA–389

ODATA–389:
“JSON: use odata.kind values ‘Entity’ and ‘deletedEntity’, Atom: use metadata:link and metadata:deleted-link” [components: OData JSON Format, OData ATOM Format] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–389:
“JSON: use odata.kind values ‘Entity’ and ‘deletedEntity’, Atom: use metadata:link and metadata:deleted-link” [components: OData JSON Format, OData ATOM Format] is Closed with no objections.

4.1.29 ODATA–390

ODATA–390:
“Additional description of use of GeoJSON in OData JSON.” [component: OData JSON Format] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–390:
“Additional description of use of GeoJSON in OData JSON.” [component: OData JSON Format] is Closed with no objections.

4.1.30 ODATA–392

ODATA–392:
“Expanded Navigation Properties should be implicitly added to $select” [component: OData URL Conventions] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–392:
“Expanded Navigation Properties should be implicitly added to $select” [component: OData URL Conventions] is Closed with no objections.

4.1.31 ODATA–393

ODATA–393:
“Allow querying collections of primitive type instances similar to other collections” [components: OData URL Conventions, OData ABNF Construction Rules] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–393:
“Allow querying collections of primitive type instances similar to other collections” [components: OData URL Conventions, OData ABNF Construction Rules] is Closed with no objections.

4.1.32 ODATA–394

ODATA–394:
“Introduce path segment /$all for search on service and entity container level” [components: OData URL Conventions, OData ABNF Construction Rules] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–394:
“Introduce path segment /$all for search on service and entity container level” [components: OData URL Conventions, OData ABNF Construction Rules] is Closed with no objections.

4.1.33 ODATA–395

ODATA–395:
“Simplify rule for implicit values of enumeration members” [component: OData CSDL] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–395:
“Simplify rule for implicit values of enumeration members” [component: OData CSDL] is Closed with no objections.

4.1.34 ODATA–396

ODATA–396:
“Partner attribute of edm:NavigationProperty is a property path, not a SimpleIdentifier” [component: OData CSDL] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–396:
“Partner attribute of edm:NavigationProperty is a property path, not a SimpleIdentifier” [component: OData CSDL] is Closed with no objections.

4.1.35 ODATA–397

ODATA–397:
“Lazy loading of Annotations: Add optional Attribute ‘TargetNamespace’ to edmx:IncludeAnnotations element” [component: OData CSDL] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–397:
“Lazy loading of Annotations: Add optional Attribute ‘TargetNamespace’ to edmx:IncludeAnnotations element” [component: OData CSDL] is Closed with no objections.

4.1.36 ODATA–398

ODATA–398:
“Define canonical function as a path segment that allows retrieving an entity by its id” [components: OData Protocol, OData ABNF Construction Rules, OData URL Conventions] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–398:
“Define canonical function as a path segment that allows retrieving an entity by its id” [components: OData Protocol, OData ABNF Construction Rules, OData URL Conventions] is Closed with no objections.

4.1.37 ODATA–399

ODATA–399:
“Describe expected life cycle management of next-links inside 11.2.4.7 Server-Driven Paging” [component: OData Protocol] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–399:
“Describe expected life cycle management of next-links inside 11.2.4.7 Server-Driven Paging” [component: OData Protocol] is Closed with no objections.

4.1.38 ODATA–400

ODATA–400:
“Allow JSON values also in common expressions, not only in parameter aliases” [components: OData URL Conventions, OData ABNF Construction Rules] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–400:
“Allow JSON values also in common expressions, not only in parameter aliases” [components: OData URL Conventions, OData ABNF Construction Rules] is Closed with no objections.

4.1.39 ODATA–401

ODATA–401:
“Replace ‘substringof’ canonical function with ‘contains’” [components: OData Protocol, OData ABNF Construction Rules, OData URL Conventions] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–401:
“Replace ‘substringof’ canonical function with ‘contains’” [components: OData Protocol, OData ABNF Construction Rules, OData URL Conventions] is Closed with no objections.

4.1.40 ODATA–402

ODATA–402:
“Require services to support $expand on navigation properties” [component: OData Protocol] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–402:
“Require services to support $expand on navigation properties” [component: OData Protocol] is Closed with no objections.

4.1.41 ODATA–403

ODATA–403:
“Mechanism to advertise conformance level of OData services” [component: OData Protocol] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–403:
“Mechanism to advertise conformance level of OData services” [component: OData Protocol] is Closed with no objections.

4.1.42 ODATA–404

ODATA–404:
“Make Capabilities vocabulary a part of OData 4.0” [component: Vocabularies] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–404:
“Make Capabilities vocabulary a part of OData 4.0” [component: Vocabularies] is Closed with no objections.

4.1.43 ODATA–406

ODATA–406:
“Attribute ContainsTarget (public comment c201305e00009)” [components: OData URL Conventions, OData CSDL] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–406:
“Attribute ContainsTarget (public comment c201305e00009)” [components: OData URL Conventions, OData CSDL] is Closed with no objections.

4.1.44 ODATA–407

ODATA–407:
“Navigation Properties in Complex Types (public comment c201305e00012)” [component: OData ATOM Format] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–407:
“Navigation Properties in Complex Types (public comment c201305e00012)” [component: OData ATOM Format] is Closed with no objections.

4.1.45 ODATA–408

ODATA–408:
“11.2.3 OData services MAY/SHOULD/MUST expose their data model” [component: OData Protocol] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–408:
“11.2.3 OData services MAY/SHOULD/MUST expose their data model” [component: OData Protocol] is Closed with no objections.

4.1.46 ODATA–409

ODATA–409:
“11.3.3.1 conflicts with conformance for intermediate and advanced OData” [component: OData Protocol] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–409:
“11.3.3.1 conflicts with conformance for intermediate and advanced OData” [component: OData Protocol] is Closed with no objections.

4.1.47 ODATA–411

ODATA–411:
“Reconsider placement and semantics of OnDelete element” [component: OData CSDL] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–411:
“Reconsider placement and semantics of OnDelete element” [component: OData CSDL] is Closed with no objections.

4.1.48 ODATA–412

ODATA–412:
“Consistent representation of empty values” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–412:
“Consistent representation of empty values” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Closed with no objections.

4.1.49 ODATA–414

ODATA–414:
“Fix syntax for deleting links to support containment” [components: OData Protocol, OData ABNF Construction Rules, OData URL Conventions] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–414:
“Fix syntax for deleting links to support containment” [components: OData Protocol, OData ABNF Construction Rules, OData URL Conventions] is Closed with no objections.

4.1.50 ODATA–417

ODATA–417:
“Define content negotiation and default format for paths ending in /$value, /$count, /$metadata and /$batch” [components: OData JSON Format, OData ATOM Format, OData URL Conventions] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–417:
“Define content negotiation and default format for paths ending in /$value, /$count, /$metadata and /$batch” [components: OData JSON Format, OData ATOM Format, OData URL Conventions] is Closed with no objections.

4.1.51 ODATA–418

ODATA–418:
“EntitySet attribute or NavigationPropertyBinding child elements for Named Entities (edm:Entity)” [component: OData CSDL] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–418:
“EntitySet attribute or NavigationPropertyBinding child elements for Named Entities (edm:Entity)” [component: OData CSDL] is Closed with no objections.

4.1.52 ODATA–420

ODATA–420:
“Response codes 404 and 405: MUST instead of SHOULD” [component: OData Protocol] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–420:
“Response codes 404 and 405: MUST instead of SHOULD” [component: OData Protocol] is Closed with no objections.

4.1.53 ODATA–421

ODATA–421:
“Remove odata.kind from JSON and add metadata URL templates for link, deletedLink, and deletedEntity” [components: OData Protocol, OData JSON Format] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–421:
“Remove odata.kind from JSON and add metadata URL templates for link, deletedLink, and deletedEntity” [components: OData Protocol, OData JSON Format] is Closed with no objections.

4.1.54 ODATA–422

ODATA–422:
“Add metadata URL to representations of entity references, define format for collections of references” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–422:
“Add metadata URL to representations of entity references, define format for collections of references” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Closed with no objections.

4.1.55 ODATA–429

ODATA–429:
“Add Boolean property RequiresFilter to Capabilities.FilterRestrictionsType” [component: Vocabularies] is Applied.

Note:

Issue state has been progressed by grouping motion (cf. section [4.1])

ODATA–429:
“Add Boolean property RequiresFilter to Capabilities.FilterRestrictionsType” [component: Vocabularies] is Closed with no objections.

4.2 Issues in Proposed state

4.2.1 ODATA–166

ODATA–166:
“Inconsistent lifted operators for $filter” [component: OData Protocol] is Open.

Matt:

I move to resolve ODATA–166 as proposed. Hubert seconds.

No further discussion. No objections. The motion passes.

ODATA–166:
“Inconsistent lifted operators for $filter” [component: OData Protocol] is Resolved with no objections.

4.2.2 ODATA–294

ODATA–294:
“Clarifications needed for Filter System Query Option: Operators and Functions” [component: OData URL Conventions] is Open.

Ralf:

I move to resolve ODATA–294 as proposed. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–294:
“Clarifications needed for Filter System Query Option: Operators and Functions” [component: OData URL Conventions] is Resolved with no objections.

4.2.3 ODATA–317

ODATA–317:
“Allow multiple reads in the same transaction” [component: OData Batch Processing Format] is Open.

Discussion:

Hubert:

I move to resolve OData–317 as proposed. Matt seconds.

No further discussion. No objections. The motion passes.

ODATA–317:
“Allow multiple reads in the same transaction” [component: OData Batch Processing Format] is Resolved with no objections.

4.2.4 ODATA–415

ODATA–415:
“Use of ‘MUST,’ ‘MAY,’ ‘SHOULD,’ etc in Part 3 CSDL definitions” [component: OData CSDL] is Open.

Ralf:

I move to close ODATA–415 without further action. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–415:
“Use of ‘MUST,’ ‘MAY,’ ‘SHOULD,’ etc in Part 3 CSDL definitions” [component: OData CSDL] is Closed with no objections.

4.2.5 ODATA–423

ODATA–423:
“Rename edm:Entity to edm:Singleton” [components: OData CSDL, OData ATOM Format, OData Protocol, OData JSON Format, OData URL Conventions] is Open.

Ralf:

I move to resolve ODATA–423 as proposed. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–423:
“Rename edm:Entity to edm:Singleton” [components: OData CSDL, OData ATOM Format, OData Protocol, OData JSON Format, OData URL Conventions] is Resolved with no objections.

4.2.6 ODATA–291

ODATA–291:
“Consider adding a mechanism for idempotence with POST” [component: Unknown] is New.

Ralf:

I move to resolve ODATA–291 as proposed by creating a committee note. Mike seconds.

No further discussion. No objections. The motion passes.

ODATA–291:
“Consider adding a mechanism for idempotence with POST” [component: Unknown] is Resolved with no objections.

4.2.7 ODATA–333

ODATA–333:
“Visualize high level EDM overview through means of small diagrams to aid the reader on understanding base terms” [component: OData Protocol] is New.

Ralf:

I move to close ODATA–333 without further action. Ed seconds.

No further discussion. No objections. The motion passes.

ODATA–333:
“Visualize high level EDM overview through means of small diagrams to aid the reader on understanding base terms” [component: OData Protocol] is Closed with no objections.

4.2.8 ODATA–427

ODATA–427:
“Consider Providing More Information For Changed Links In a Delta Response” [component: OData Protocol] is New.

Matt:

I move to resolve ODATA–427 as proposed. Mike seconds.

No further discussion. No objections. The motion passes.

ODATA–427:
“Consider Providing More Information For Changed Links In a Delta Response” [component: OData Protocol] is Resolved with no objections.

4.2.9 ODATA–428

ODATA–428:
“Introduce dynamic expression AnnotationPath and accompanying abstract type Edm.AnnotationPath” [component: OData CSDL] is New.

Ralf:

I move to resolve ODATA–428 as proposed. Mike seconds.

No further discussion. No objections. The motion passes.

ODATA–428:
“Introduce dynamic expression AnnotationPath and accompanying abstract type Edm.AnnotationPath” [component: OData CSDL] is Resolved with no objections.

4.2.10 ODATA–430

ODATA–430:
“Add term Core.ResourcePath to describe unconventional resource paths in CSDL” [components: OData URL Conventions, OData CSDL, Vocabularies] is New.

Discussion:

Mike:

I move we accept ODATA–430 as proposed. Ralf seconds.

No further discussion. No objections. The motion passes.

ODATA–430:
“Add term Core.ResourcePath to describe unconventional resource paths in CSDL” [components: OData URL Conventions, OData CSDL, Vocabularies] is Resolved with no objections.

4.2.11 ODATA–431

ODATA–431:
“Add $expand=, $expand=/$ref, $expand=*($levels=…) for expanding all navigation properties” [component: OData URL Conventions] is New.

Discussion:

Hubert:

I move to resolve ODATA–431 as per the updated proposal. Mike seconds.

No further discussion. No objections. The motion passes.

ODATA–431:
“Add $expand=, $expand=/$ref, $expand=*($levels=…) for expanding all navigation properties” [component: OData URL Conventions] is Resolved as noted in the motion with no objections.

4.2.12 ODATA–432

ODATA–432:
“Define meaning of odata.associationLink on entity level” [component: OData Extension for JSON Data] is New.

Ralf:

I move to defer ODATA–432 to V5.0. Mike seconds.

No further discussion. No objections. The motion passes.

ODATA–432:
“Define meaning of odata.associationLink on entity level” [component: OData Extension for JSON Data] is Deferred with no objections.

4.2.13 ODATA–433

ODATA–433:
“Rollback requirement that services support $expand” [component: OData Protocol] is New.

Mike:

I move we resolve ODATA–433 as proposed. Shishir seconds.

No further discussion. No objections. The motion passes.

ODATA–433:
“Rollback requirement that services support $expand” [component: OData Protocol] is Resolved with no objections.

4.2.14 ODATA–434

ODATA–434:
“Introduce path segment for cross-joins on entity-container level” [components: OData URL Conventions, OData ABNF Construction Rules] is New.

Ralf:

I move to resolve ODATA–434 as proposed. Hubert seconds.

No further discussion. No objections. The motion passes.

ODATA–434:
“Introduce path segment for cross-joins on entity-container level” [components: OData URL Conventions, OData ABNF Construction Rules] is Resolved with no objections.

4.2.15 ODATA–435

ODATA–435:
“Simplify URL syntax and CSDL by restricting services to exactly one entity container” [components: OData CSDL, OData ABNF Construction Rules, OData URL Conventions] is New.

Mike:

I move we resolve ODATA–435 as proposed. John seconds.

No further discussion. No objections. The motion passes.

ODATA–435:
“Simplify URL syntax and CSDL by restricting services to exactly one entity container” [components: OData CSDL, OData ABNF Construction Rules, OData URL Conventions] is Resolved with no objections.

4.2.16 ODATA–436

ODATA–436:
“Allow annotating edm:Annotation element, disallow annotating edm:Collection element” [component: OData CSDL] is New.

Ralf:

I move we resolve ODATA–436 as proposed. Stefan seconds.

No further discussion. No objections. The motion passes.

ODATA–436:
“Allow annotating edm:Annotation element, disallow annotating edm:Collection element” [component: OData CSDL] is Resolved with no objections.

4.2.17 ODATA–437

ODATA–437:
“Describe path syntax for edm:Annotations/@Target ” [component: OData CSDL] is New.

Discussion:

Ralf:

I move we resolve ODATA–437 as proposed with the addition that in applying the proposal we list the elements that can be annotated instead of stating the negative list. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–437:
“Describe path syntax for edm:Annotations/@Target ” [component: OData CSDL] is Resolved as noted in the motion with no objections.

4.2.18 ODATA–438

ODATA–438:
“Rename edm:Url to edm:UrlExpression” [component: OData CSDL] is New.

Discussion:

Stefan:

I move we resolve ODATA–438 as proposed. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–438:
“Rename edm:Url to edm:UrlRef” [component: OData CSDL] is Resolved with no objections.

4.2.19 ODATA–439

ODATA–439:
“Complete Metadata URL patterns” [components: OData Protocol, OData ABNF Construction Rules] is New.

Discussion:

Ralf:

I move we resolve ODATA–439 as proposed. Hubert seconds.

No further discussion. No objections. The motion passes.

ODATA–439:
“Complete Metadata URL patterns” [components: OData Protocol, OData ABNF Construction Rules] is Resolved with no objections.

4.2.20 ODATA–440

ODATA–440:
“Specify response for function or action that returns a single null value” [component: OData Protocol] is New.

No discussion. No objections.

ODATA–440:
“Specify response for function or action that returns a single null value” [component: OData Protocol] is Open with no objections.

Processing continued on day two:

Ralf:

I move to resolve ODATA–440 as proposed. Hubert seconds.

No further discussion. No objections. The motion passes.

ODATA–440:
“Specify response for function or action that returns a single null value” [component: OData Protocol] is Resolved with no objections.

4.2.21 ODATA–441

ODATA–441:
“Specify canonical form of entity-id” [components: OData URL Conventions, OData Protocol] is New.

Discussion:

Mike:

I move we resolve ODATA–441 as proposed. Ralf seconds.

No further discussion. No objections. The motion passes.

ODATA–441:
“Specify canonical form of entity-id” [components: OData URL Conventions, OData Protocol] is Resolved with no objections.

4.2.22 ODATA–442

ODATA–442:
“Adapt metadata service” [component: OData CSDL] is New.

Discussion:

No further discussion. No objections.

ODATA–442:
“Adapt metadata service” [component: OData CSDL] is Open with no objections.

Discussion(cont. on day two):

Ralf:

I move to resolve ODATA–442 as proposed. Hubert seconds.

No further discussion. No objections. The motion passes.

ODATA–442:
“Adapt metadata service” [component: OData CSDL] is Resolved with no objections.

4.2.23 ODATA–443

ODATA–443:
“Last page of delta response MUST contain a delta link” [component: OData Protocol] is New.

Discussion:

Stefan:

I move that we resolve ODATA–443 as proposed. Mike seconds.

No further discussion. No objections. The motion passes.

ODATA–443:
“Last page of delta response MUST contain a delta link” [component: OData Protocol] is Resolved with no objections.

4.2.24 ODATA–444

ODATA–444:
“Representation of entity references” [components: OData JSON Format, OData ATOM Format, OData Protocol] is New.

Hubert:

I move to resolve ODATA–444 as proposed. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–444:
“Representation of entity references” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Resolved with no objections.

4.2.25 ODATA–445

ODATA–445:
“odata.type relative to odata.type in surrounding entities” [component: OData JSON Format] is New.

Mike:

I move we resolve odata–445 as proposed. Stefan seconds.

No further discussion. No objections. The motion passes.

ODATA–445:
“odata.type relative to odata.type in surrounding entities” [component: OData JSON Format] is Resolved with no objections.

4.2.26 ODATA–446

ODATA–446:
“Rename Named Stream to Stream Entity” [components: OData ATOM Format, OData ABNF Construction Rules, OData JSON Format, OData CSDL, OData URL Conventions, OData Protocol, Vocabularies] is New.

Discussion:

No further discussion. No objections.

ODATA–446:
“Rename Named Stream to Stream Property” [components: OData ATOM Format, OData ABNF Construction Rules, OData JSON Format, OData CSDL, OData URL Conventions, OData Protocol, Vocabularies] is Resolved with no objections.

4.2.27 ODATA–447

ODATA–447:
“Rename Metadata URL to Context and make it structured information” [components: OData ATOM Format, OData ABNF Construction Rules, OData JSON Format, OData CSDL, OData URL Conventions, OData Protocol] is New.

Discussion:

No further discussion. No objections.

ODATA–447:
“Rename Metadata URL to Context and make it structured information” [components: OData ATOM Format, OData ABNF Construction Rules, OData JSON Format, OData CSDL, OData URL Conventions, OData Protocol] is Open with no objections.

Processing continued on day two:

Hubert:

I move to resolve ODATA–447 as proposed. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–447:
“Rename Metadata URL to Context and make it structured information” [components: OData ATOM Format, OData ABNF Construction Rules, OData JSON Format, OData CSDL, OData URL Conventions, OData Protocol] is Resolved with no objections.

4.2.28 ODATA–289

ODATA–289:
“Callback for notification after async invocation of Create, Update, Delete and Service Operations” [component: OData URL Conventions] is Open.

Discussion:

No further discussion. No objections.

ODATA–289:
“Callback for notification after async invocation of Create, Update, Delete and Service Operations” [component: OData URL Conventions] is Open with no objections.

Processing continued on day two:

Discussion:

Hubert:

I move to resolve ODATA–289 as proposed. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–289:
“Callback for notification after async invocation of Create, Update, Delete and Service Operations” [component: OData URL Conventions] is Resolved with no objections.
4.2.28.1 End of Issue Processing

Note:

meeting has been paused and was continued 2013–06–14 at 0900 PT

Day Two

5 Approval of Agenda for day two

Agenda for day two approved as published.

6 Next Steps CSD02

Context:

We prepare towards approving CSD02 in next Meeting on 2013–06–20 by Call during 0800–1000 PT

Discussion:

7 Review of Issues List (IL) and Progress

Notes:

7.1 Remaining issues

7.1.1 ODATA–386

ODATA–386:
“odata-v4.0-csprd01-part1-protocol, 3 Data Model, appears to be an unnumbered list of definitions, with annotations defined in a separate subsection - suggest new format, etc.” [component: OData Protocol] is Open.

Discussion:

No further discussion. No objections.

ODATA–386:
“odata-v4.0-csprd01-part1-protocol, 3 Data Model, appears to be an unnumbered list of definitions, with annotations defined in a separate subsection - suggest new format, etc.” [component: OData Protocol] is Open with no objections.

7.1.2 ODATA–448

ODATA–448:
“Add Nullable facet to edm:ReturnType” [component: OData CSDL] is New.

Ralf:

I move to resolve ODATA–448 as proposed. Hubert seconds.

No further discussion. No objections. The motion passes.

ODATA–448:
“Add Nullable facet to edm:ReturnType” [component: OData CSDL] is Resolved with no objections.

7.1.3 ODATA–449

ODATA–449:
“Remove IsBindable attribute from edm:Function” [components: OData ATOM Format, OData ABNF Construction Rules, OData JSON Format, OData CSDL, OData URL Conventions, OData Protocol] is New.

Discussion:

No further discussion. No objections.

ODATA–449:
“Remove IsBindable attribute from edm:Function” [components: OData ATOM Format, OData ABNF Construction Rules, OData JSON Format, OData CSDL, OData URL Conventions, OData Protocol] is Open with no objections.

Processing continued during day two:

Discussion (cont.):

Stefan:

I move to resolve ODATA–449 as proposed. Ralf seconds.

No further discussion. No objections. The motion passes.

ODATA–449:
“Remove IsBindable attribute from edm:Function” [components: OData ATOM Format, OData ABNF Construction Rules, OData JSON Format, OData CSDL, OData URL Conventions, OData Protocol] is Resolved with no objections.

7.1.4 ODATA–450

ODATA–450:
“ordering of association link , navigation link, expanded nav prop” [components: OData ATOM Format, OData JSON Format] is New.

Mike:

I move we approve ODATA_450 as proposed. Hubert seconds.

No further discussion. No objections. The motion passes.

ODATA–450:
“ordering of association link , navigation link, expanded nav prop” [components: OData ATOM Format, OData JSON Format] is Resolved with no objections.

7.1.5 ODATA–452

ODATA–452:
“Services should be allowed to filter changes based on selected fields” [component: OData Protocol] is New.

Mike:

I move we accept ODATA–452 as proposed. Matt seconds.

No further discussion. No objections. The motion passes.

ODATA–452:
“Services should be allowed to filter changes based on selected fields” [component: OData Protocol] is Resolved with no objections.

7.1.6 c201306e00012

Context:

We received the public Comment #20130600012 on 2013–06–14 with title “feedback/discussion now that public comment period is over”. To prepare processing a corresponding JIRA issue ODATA–451 has been created with summary “Provide section that clearly indicates what system query options are allowed on the various combinations of URL type and HTTP method (public comment c201306e00012)” [component: Unknown].

Original mail text was:

Where can I send comments about or have discussion regarding the OData v4 spec now that the public comment period is over? I would like to know if the $select and $expand system query options are allowed on insert entity requests to limit or expand the data that is returned (when it is requested via a PREFER header that data be returned). A section that clearly indicates what system query options are allowed on the various combinations of URL type and HTTP method would be helpful (unless it exists already and I just missed it).

7.1.6.1 ODATA–451
ODATA–451:
“Provide section that clearly indicates what system query options are allowed on the various combinations of URL type and HTTP method (public comment c201306e00012)” [component: OData URL Conventions] New.

Ralf:

I move to resolve ODATA–451 as proposed. Mike seconds.

No further discussion. No objections.

ODATA–451:
“Provide section that clearly indicates what system query options are allowed on the various combinations of URL type and HTTP method (public comment c201306e00012)” [component: OData URL Conventions] is Resolved with no objections.

8 Review of Action Items (AI) and Progress

Context:

See the “List of Open Action Items Before the Meeting” section in the appendix.

8.1 Action items due by 2013–06–14 (end of day)

8.1.1 AI#0019

AI#0019
“Prepare Working Draft 01 (WD01) version of OData Extension for XML Data” [owner: Stefan Drees] is Ongoing (Note: Due 2013–06–14)

Discussion:

AI#0019
“Prepare Working Draft 01 (WD01) version of OData Extension for XML Data” [owner: Stefan Drees] is Ongoing (Note: Due 2013–07–31)

8.1.2 AI#0020

AI#0020
“Prepare Working Draft 01 (WD01) version of OData Extension for JSON Data” [owner: Susan Malaika] is Ongoing

Note:

Discussion points relevant to AI#0020 are noted in section 8.1.1 where the discussion is documented.

AI#0020
“Prepare Working Draft 01 (WD01) version of OData Extension for JSON Data” [owner: Susan Malaika] is Ongoing (Note: Due 2013–07–31)

8.2 Action items NOT due by 2013–06–14 (end of day) but MAY be ready for closure

None.

8.2.1 AI#0018

AI#0018
“Prepare Working Draft 01 (WD01) version of OData Extension for Temporal Data” [owner: Hubert Heijkers] is Ongoing

Note:

Set as due date for AI#0018 the end of July as with AI0019 and AI0020. For details cf. 8.1.1 where the discussion is documented.

AI#0018
“Prepare Working Draft 01 (WD01) version of OData Extension for Temporal Data” [owner: Hubert Heijkers] is Ongoing (Note: Due 2013–07–31)

9 Next Meetings

9.1 Weekly Meeting on 2013–06–20 by Call during 0800–0900 PT

Agreed (cf. section 6 and pleases note the duration of one hour).

9.2 Meeting on 2013–06–24 by Call during 1230–1330 PT

Agreed (cf. section 6).

10 AOB

None.

Meeting adjourned on 1800 PT

List of Open Action Items Before the Meeting

Retrieval time stamp: 2013-06-13 14:00 +02:00.

AI#0018
“Prepare Working Draft 01 (WD01) version of OData Extension for Temporal Data” [owner: Hubert Heijkers] is Ongoing
AI#0019
“Prepare Working Draft 01 (WD01) version of OData Extension for XML Data” [owner: Stefan Drees] is Ongoing (Note: Due 2013–06–14)
AI#0020
“Prepare Working Draft 01 (WD01) version of OData Extension for JSON Data” [owner: Susan Malaika] is Ongoing (Note: Due 2013–06–14)

Note: The actual action item processing is documented in section 4 and subsections thereof.

Index of Issues Processed During the Meeting

Note: The actual issue processing is documented in sections 4 and 7. The below index has two main parts: First come the public comments (if any), second the JIRA issues. Each list of issues is sorted by ascending issue number. Noted are the ID, the summary and the reference to the relevant subsection where the issue progression has been documented:

Public Comments:

JIRA Issues:

Timeline Reference

Note: Please cf. the current revision of the TC timeline.