OData meeting #42, Thursday, 20 Jun 2013, 0800 - 0900 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

1 Roll call

1.1 Members Present:

    Barbara Hartel (SAP AG)
    Dale Moberg (Axway Software)
    Diane Downie (Citrix Systems)
    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
    Patrick Durusau (Individual)
    Ralf Handl (SAP AG)
    Robert Richards (Mashery)
    Stefan Drees (Individual)
    Susan Malaika (IBM)
    Ted Jones (Red Hat)

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–13/14 Meeting#41 F2F

Meeting minutes approved with no objections.

4 Review of Action Items (AI) and Progress

Context:

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

4.1 Action items due by 2013–06–20 (end of day)

None.

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

None.

5 Review of Issues List (IL) and Progress

Notes:

5.1 Issues in Applied state

Ralf:

I move to close ODATA–166, ODATA–289, ODATA–294, ODATA–314, ODATA–316, ODATA–317, ODATA–381, ODATA–386, ODATA–413, ODATA–416, ODATA–419, ODATA–423, ODATA–425, ODATA–426, ODATA–427, ODATA–428, ODATA–430, ODATA–431, ODATA–433, ODATA–434, ODATA–435, ODATA–436, ODATA–437, ODATA–438, ODATA–439, ODATA–440, ODATA–442, ODATA–443, ODATA–444, ODATA–446, ODATA–447, ODATA–448, ODATA–449, ODATA–450, ODATA–451, ODATA–452, ODATA–453, ODATA–454, and ODATA–455 as applied. Hubert seconds.

No further discussion. No objections. The motion passes.

5.1.1 ODATA–166

ODATA–166:
“Inconsistent lifted operators for $filter” [component: OData URL Conventions] is Applied.

Note:

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

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

5.1.2 ODATA–289

ODATA–289:
“Callback for notification after async invocation of Create, Update, Delete and Service Operations” [components: Vocabularies, OData Protocol] is Applied.

Note:

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

ODATA–289:
“Callback for notification after async invocation of Create, Update, Delete and Service Operations” [components: Vocabularies, OData Protocol] is Closed with no objections.

5.1.3 ODATA–294

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

Note:

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

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

5.1.4 ODATA–314

ODATA–314:
“Please clarify the meaning of filter functions applied to DateTimeOffset values” [components: OData URL Conventions, OData Protocol] is Applied.

Note:

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

ODATA–314:
“Please clarify the meaning of filter functions applied to DateTimeOffset values” [components: OData URL Conventions, OData Protocol] is Closed with no objections.

5.1.5 ODATA–316

ODATA–316:
“Services select a default set of properties in absence of $select” [component: OData Protocol] is Applied.

Note:

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

ODATA–316:
“Services select a default set of properties in absence of $select” [component: OData Protocol] is Closed with no objections.

5.1.6 ODATA–317

ODATA–317:
“Allow multiple reads in the same transaction” [component: OData Protocol] is Applied.

Note:

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

ODATA–317:
“Allow multiple reads in the same transaction” [component: OData Protocol] is Closed with no objections.

5.1.7 ODATA–381

ODATA–381:
“Hanging paragraphs - all current csprd01 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 [5.1])

ODATA–381:
“Hanging paragraphs - all current csprd01 documents” [components: OData CSDL, OData ATOM Format, OData Protocol, OData JSON Format, OData URL Conventions] is Closed with no objections.

5.1.8 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.

Patrick:

I move ODATA–386 to resolved. Mike seconds.

No further discussion. No objections. The motion passes.

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 Resolved.

Note:

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

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 Closed with no objections.

5.1.9 ODATA–413

ODATA–413:
“Replace conformance clauses in URL and CSDL with references to Protocol” [components: OData URL Conventions, OData CSDL] is Applied.

Note:

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

ODATA–413:
“Replace conformance clauses in URL and CSDL with references to Protocol” [components: OData URL Conventions, OData CSDL] is Closed with no objections.

5.1.10 ODATA–416

ODATA–416:
“Non-normative text in conformance 13.1 of part 1” [component: OData Protocol] is Applied.

Note:

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

ODATA–416:
“Non-normative text in conformance 13.1 of part 1” [component: OData Protocol] is Closed with no objections.

5.1.11 ODATA–419

ODATA–419:
“Specify ETag handling more precisely” [component: OData Protocol] is Applied.

Note:

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

ODATA–419:
“Specify ETag handling more precisely” [component: OData Protocol] is Closed with no objections.

5.1.12 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 Applied.

Note:

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

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

5.1.13 ODATA–425

ODATA–425:
“Clarify rules around parameter overloads and return types” [components: OData CSDL, OData ABNF Construction Rules, OData URL Conventions, OData Protocol] is Applied.

Note:

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

ODATA–425:
“Clarify rules around parameter overloads and return types” [components: OData CSDL, OData ABNF Construction Rules, OData URL Conventions, OData Protocol] is Closed with no objections.

5.1.14 ODATA–426

ODATA–426:
“Metadata URL for nested objects can be relative to metadata URL of enclosing object” [component: OData JSON Format] is Applied.

Note:

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

ODATA–426:
“Metadata URL for nested objects can be relative to metadata URL of enclosing object” [component: OData JSON Format] is Closed with no objections.

5.1.15 ODATA–427

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

Note:

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

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

5.1.16 ODATA–428

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

Note:

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

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

5.1.17 ODATA–430

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

Note:

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

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

5.1.18 ODATA–431

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

Note:

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

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

5.1.19 ODATA–433

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

Note:

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

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

5.1.20 ODATA–434

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

Note:

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

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

5.1.21 ODATA–435

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

Note:

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

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

5.1.22 ODATA–436

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

Note:

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

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

5.1.23 ODATA–437

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

Note:

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

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

5.1.24 ODATA–438

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

Note:

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

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

5.1.25 ODATA–439

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

Note:

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

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

5.1.26 ODATA–440

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

Note:

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

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

5.1.27 ODATA–442

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

Note:

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

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

5.1.28 ODATA–443

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

Note:

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

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

5.1.29 ODATA–444

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

Note:

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

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

5.1.30 ODATA–446

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 Applied.

Note:

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

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 Closed with no objections.

5.1.31 ODATA–447

ODATA–447:
Rename Metadata URL to Context" [component: OData ATOM Format] is Applied.

Note:

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

ODATA–447:
Rename Metadata URL to Context" [component: OData ATOM Format] is Closed with no objections.

5.1.32 ODATA–448

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

Note:

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

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

5.1.33 ODATA–449

ODATA–449:
“Clarify restrictions for action/function overloads, rename IsBindable to IsBound” [components: OData ATOM Format, OData ABNF Construction Rules, OData JSON Format, OData CSDL, OData URL Conventions, OData Protocol] is Applied.

Note:

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

ODATA–449:
“Clarify restrictions for action/function overloads, rename IsBindable to IsBound” [components: OData ATOM Format, OData ABNF Construction Rules, OData JSON Format, OData CSDL, OData URL Conventions, OData Protocol] is Closed with no objections.

5.1.34 ODATA–450

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

Note:

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

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

5.1.35 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] is Applied.

Note:

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

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 Closed with no objections.

5.1.36 ODATA–452

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

Note:

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

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

5.1.37 ODATA–453

ODATA–453:
“deal with KEY function” [component: OData ABNF Construction Rules] is Open.

Discussion:

Ralf:

I move to resolve ODATA–453 as proposed, covering contained entities. Mike seconds.

No further discussion. No objections. The motion passes.

ODATA–453:
“deal with KEY function” [component: OData ABNF Construction Rules] is Resolved as noted in the motion with no objections.

Note:

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

ODATA–453:
“deal with KEY function” [component: OData ABNF Construction Rules] is Closed with no objections.

5.1.38 ODATA–454

ODATA–454:
“Need a way to specify a property is unavailable” [components: OData JSON Format, OData ATOM Format, Vocabularies] is New.

Discussion:

Mike:

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

No further discussion. No objections. The motion passes.

ODATA–454:
“Need a way to specify a property is unavailable” [components: OData JSON Format, OData ATOM Format, Vocabularies] is Resolved with no objections.

Note:

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

ODATA–454:
“Need a way to specify a property is unavailable” [components: OData JSON Format, OData ATOM Format, Vocabularies] is Closed with no objections.

5.1.39 ODATA–455

ODATA–455:
“Make EntityContainer a Singleton in MetadataService” [component: OData CSDL] is New.

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–455:
“Make EntityContainer a Singleton in MetadataService” [component: OData CSDL] is Resolved.

Note:

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

ODATA–455:
“Make EntityContainer a Singleton in MetadataService” [component: OData CSDL] is Closed with no objections.

5.2 Issues in Proposed state

5.2.1 ODATA–456

ODATA–456:
“Don’t require client to specify odata.trackchanges preference on each page” [component: OData Protocol] is Open.

Hubert:

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

No further discussion. No objections. The motion passes.

ODATA–456:
“Don’t require client to specify odata.trackchanges preference on each page” [component: OData Protocol] is Resolved with no objections.

5.2.2 ODATA–457

ODATA–457:
“Require hash (#) on odata.type” [components: OData ATOM Format, OData ABNF Construction Rules, OData Extension for JSON Data] is Open.

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–457:
“Require hash (#) on odata.type” [components: OData ATOM Format, OData ABNF Construction Rules, OData Extension for JSON Data] is Resolved with no objections.

5.2.3 ODATA–458

ODATA–458:
“odata.isolation should be a header rather than an expectation” [component: OData Protocol] is Open.

Martin:

I move to resolve ODATA–458 as proposed. Matt seconds.

No further discussion. No objections. The motion passes.

ODATA–458:
“odata.isolation should be a header rather than an expectation” [component: OData Protocol] is Resolved with no objections.

5.2.4 ODATA–459

ODATA–459:
“State consequences of using IRIs that are not URLs” [components: OData Protocol, OData JSON Format] is Open.

Discussion:

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–459:
“State consequences of using IRIs that are not URLs” [components: OData Protocol, OData JSON Format] is Resolved with no objections.

Discussion (cont.):

Mike:

I move that for version 4.0, we define that the client must be prepared to accept any IRI but that services must use URIs in version 4.0 since we have no lossless representation of an IRI in the entity-id header. John seconds.

No further discussion. No objections. The motion passes.

ODATA–459:
“State consequences of using IRIs that are not URLs” [components: OData Protocol, OData JSON Format] is Resolved as noted in the motion with no objections.

5.2.5 ODATA–460

ODATA–460:
“Add terms to capability vocabulary” [components: Vocabularies, OData Protocol] is Open.

Discussion:

Hubert:

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

No further discussion. No objections. The motion passes.

ODATA–460:
“Add terms to capability vocabulary” [components: Vocabularies, OData Protocol] is Resolved with no objections.

5.2.6 ODATA–441

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

Mike:

I move we accept the alternate proposal in ODATA–441; that the cast segment is added to the edit/read link by convention if the type of the instance is a derived type of the expected type. Hubert 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 as noted in the motion with no objections.

6 Next Meetings

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

Note:

Extraordinary meeting to approve CSD02.

Discussion:

7 AOB

None.

Meeting adjourned on 1022 PT

List of Open Action Items Before the Meeting

Retrieval time stamp: 2013-06-20 07:00 +02:00.

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

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 5. 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:

None.

JIRA Issues:

Timeline Reference

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