OData meeting #38, Thursday, 23 MAY 2013, 0800 - 1000 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 and Ram Jeyaraman

Acting chair: Barbara Hartel

1 Roll call

1.1 Members Present:

    Barbara Hartel (SAP AG)
    Dale Moberg (Axway Software)
    Edmond Bourne (BlackBerry)
    Gerald Krause (SAP AG)
    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
    Nuno Linhares (SDL)
    Patrick Durusau (Individual)
    Ralf Handl (SAP AG)
    Ram Jeyaraman (Microsoft)
    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

Stefan asks to deal with the 3 comments from today All are fine with that. Agenda approved as published and amended.

3 Approval of Minutes from Previous Meeting(s)

3.1 Approval of Minutes of 2013–05–16 Meeting#37

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–05–23 (end of day)

None.

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

None.

5 Review of Issues List (IL) and Progress

Notes:

5.1 Public Review Issues

Discussion:

5.1.1 c201305e00008

Context:

We received the public Comment #20130500008 on 2013–05–23 with title “Deep Updates”. To prepare processing a corresponding JIRA issue ODATA–405 has been created with summary “Deep Updates (public comment c201305e00008)” [component: OData ATOM Format].

5.1.1.1 ODATA–405
ODATA–405:
“Deep Updates (public comment c201305e00008)” [component: OData ATOM Format] is New.

Discussion:

No further discussion. No objections.

ODATA–405:
“Deep Updates (public comment c201305e00008)” [component: OData ATOM Format] is Open with no objections.

5.1.2 c201305e00009

Context:

We received the public Comment #20130500009 on 2013–05–23 with title “Attribute ContainsTarget”. To prepare processing a corresponding JIRA issue ODATA–406 has been created with summary “Attribute ContainsTarget (public comment c201305e00009)” [component: OData CSDL].

5.1.2.1 ODATA–406
ODATA–406:
“Attribute ContainsTarget (public comment c201305e00009)” [component: OData CSDL] is New.

Discussion:

No further discussion. No objections.

ODATA–406:
“Attribute ContainsTarget (public comment c201305e00009)” [component: OData CSDL] is Open with no objections.

Mike:

I move we approve ODATA–406 as proposed. Ralf seconds.

No further discussion. No objections. The motion passes.

ODATA–406:
“Attribute ContainsTarget (public comment c201305e00009)” [component: OData CSDL] is Resolved with no objections.

5.1.3 c201305e00012

Context:

We received the public Comment #20130500012 on 2013–05–23 with title “Navigation Properties in Complex Types”. To prepare processing a corresponding JIRA issue ODATA–407 has been created with summary “Navigation Properties in Complex Types (public comment c201305e00012)” [component: OData CSDL].

5.1.3.1 ODATA–407
ODATA–407:
“Navigation Properties in Complex Types (public comment c201305e00012)” [component: OData CSDL] is New.

Discussion:

No further discussion. No objections.

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

Discussion (cont.):

No further discussion. No objections.

5.2 Issues in Proposed state (carried over from May 16, 2013)

5.2.1 ODATA–391

ODATA–391:
“Add query function isdefined(PropertyPath) to determine whether an instance has a property of that name” [components: OData URL Conventions, OData Extension for Data Aggregation] is Open.

Discussion:

Mike:

I move we accept ODATA–391 as amended to apply only to the aggregation extension and not to open properties. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–391:
“Add query function isdefined(PropertyPath) to determine whether an instance has a property of that name” [components: OData URL Conventions, OData Extension for Data Aggregation] is Resolved as noted in the motion with no objections.

5.2.2 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 New.

Discussion:

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

Discussion:

Ralf:

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

No further discussion. No objections. The motion passes.

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

5.2.3 ODATA–395

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

Discussion:

Ralf:

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

No further discussion. No objections. The motion passes.

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

5.3 Editorial issues (carried over from May 16, 2013)

5.3.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 New.

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.

5.3.2 ODATA–385

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

Discussion:

Mike:

I move we accept ODATA–385 as amended in the proposal. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–385:
“Overview wording suggestion” [component: OData Protocol] is Resolved as noted in the motion with no objections.

5.3.3 ODATA–384

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

Discussion:

No further discussion. No objections. The motion passes.

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

5.3.4 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 New.

Discussion:

No further discussion. No objections.

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

Note:

Patrick will deliver an evaluation if and where example reference ambiguities might arise to support reolution of this issue.

5.3.5 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 New.

Discussion:

Patrick:

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

No further discussion. No objections. The motion passes.

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

5.3.6 ODATA–381

ODATA–381:
“Hanging paragraphs - all current csprd01 documents” [components: OData CSDL, OData ATOM Format, OData Extension for JSON Data] is New.

Discussion:

No further discussion. No objections.

ODATA–381:
“Hanging paragraphs - all current csprd01 documents” [components: OData CSDL, OData ATOM Format, OData Extension for JSON Data] is Open with no objections.

Note:

Patrick will deliver an evaluation if and where conflicting ambiguous refrences might arise to support reolution of this issue.

5.4 Issues in Proposed state (may need deeper discussion) (carried over from May 9, 2013)

5.4.1 OData Protocol

5.4.1.1 ODATA–262
ODATA–262:
“Specify how OData services can be protected against cross-site request forgery (CSRF or XSRF)” [component: OData Protocol] is Open.

Discussion:

No further discussion. No objections.

ODATA–262:
“Specify how OData services can be protected against cross-site request forgery (CSRF or XSRF)” [component: OData Protocol] is Open with no objections.

5.4.2 OData Protocol, OData URL Conventions

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

Discussion:

No further discussion. No objections.

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

5.4.3 OData CSDL, OData Protocol, OData URL Conventions

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

Ralf:

I move to resolve ODATA–126 as proposed. Stefan seconds.

No further discussion. No objections. The motion passes.

ODATA–126:
“Metadata as an OData service” [components: OData Protocol, OData CSDL, OData URL Conventions] is Resolved with no objections.
5.4.3.2 ODATA–295
ODATA–295:
“Services should be able to ‘advertise’ what form of change tracking they support” [components: OData Protocol, OData CSDL] is New.

Discussion:

Mike:

I move we accept ODATA–295 as proposed. Stefan seconds.

No further discussion. No objections. The motion passes.

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

5.4.4 OData JSON Format

5.4.4.1 ODATA–316
ODATA–316:
“Allow omitting properties with null or default values from responses” [component: OData JSON Format] is Open.

Discusssion:

ODATA–316:
“Allow omitting properties with null or default values from responses” [component: OData JSON Format] is Open with no objections.

5.5 Issues in Proposed State since May 16, 2013

5.5.1 OData ABNF Construction Rules, OData Protocol, OData URL Conventions

5.5.1.1 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 New.

Mike:

I move we accept ODATA–398 as proposed. Stefan seconds.

No further discussion. No objections. The motion passes.

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 Resolved with no objections.
5.5.1.2 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 New. Discussion:

Mike:

I move we accept ODATA–400 as proposed. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–400:
“Allow JSON values also in common expressions, not only in parameter aliases” [components: OData URL Conventions, OData ABNF Construction Rules] is Resolved with no objections.
5.5.1.3 ODATA–401
ODATA–401:
“Replace ‘substringof’ canonical function with ‘contains’” [components: OData Protocol, OData ABNF Construction Rules, OData URL Conventions] is New.

Discussion:

Stefan:

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

No further discussion. No objections. The motion passes.

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

5.5.2 OData CSDL

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

Discussion:

Martin:

I move to resolve ODATA–397 as proposed. Stefan seconds.

No further discussion. No objections. The motion passes.

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

5.5.3 OData Protocol

5.5.3.1 ODATA–374
ODATA–374:
“Returning heterogeneous types for a function call” [components: OData Protocol, OData CSDL] is New.

Discussion:

Mike:

I move we resolve ODATA–374 with no action as proposed. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–374:
“Returning heterogeneous types for a function call” [components: OData Protocol, OData CSDL] is Closed with no action as noted in the motion with no objections.
5.5.3.2 ODATA–399
ODATA–399:
“Describe expected life cycle management of next-links inside 11.2.4.7 Server-Driven Paging” [component: OData Protocol] is New.

Discussion:

Stefan:

I move to resolve ODATA–399 as updated by Mike as proposed. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–399:
“Describe expected life cycle management of next-links inside 11.2.4.7 Server-Driven Paging” [component: OData Protocol] is Resolved as noted in the motion with no objections.
5.5.3.3 ODATA–402
ODATA–402:
“Require services to support $expand on navigation properties” [components: OData URL Conventions, OData Protocol] is New.

Discussion:

Mike:

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

No further discussion. No objections. The motion passes.

ODATA–402:
“Require services to support $expand on navigation properties” [components: OData URL Conventions, OData Protocol] is Resolved with no objections.
5.5.3.4 ODATA–404
ODATA–404:
“Make Capabilities vocabulary a part of OData 4.0” [component: Vocabularies] is New.

Stefan:

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

No further discussion. No objections. The motion passes.

ODATA–404:
“Make Capabilities vocabulary a part of OData 4.0” [component: Vocabularies] is Resolved with no objections.
5.5.3.5 ODATA–403
ODATA–403:
“Mechanism to advertise conformance level of OData services” [components: OData Batch Processing Format, OData ATOM Format, OData Protocol, OData JSON Format, Vocabularies] is New.

Discussion:

Ram:

I move to resolve ODATA–404 as proposed with the understanding that the editors will add a reference to the capabilities section from conformance section. Stefan seconds.

No further discussion. No objections. The motion passes.

ODATA–403:
“Mechanism to advertise conformance level of OData services” [components: OData Batch Processing Format, OData ATOM Format, OData Protocol, OData JSON Format, Vocabularies] is Resolved as noted in the motion with no objections.

5.6 Issues in Applied state

5.6.1 OData ATOM Format, OData JSON Format, OData Protocol

5.6.1.1 ODATA–379
ODATA–379:
“Ensure consistency and clear description in specification of $count for ‘Delta Responses’ (public comment c201305e00000)” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Applied.

Note:

Not processed, but kept n the minutes as to document the status Applied to support the chairs in responding to the commenter.

No discussion. No objections.

ODATA–379:
“Ensure consistency and clear description in specification of $count for ‘Delta Responses’ (public comment c201305e00000)” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Applied with no objections.

5.6.2 OData CSDL

5.6.2.1 ODATA–387
ODATA–387:
“Replace (at least) the second example in Section 13 of the CSDL document (public comment c201305e00002)” [component: OData CSDL] is Applied.

Note:

Not processed, but kept n the minutes as to document the status Applied to support the chairs in responding to the commenter.

No discussion. No objections.

ODATA–387:
“Replace (at least) the second example in Section 13 of the CSDL document (public comment c201305e00002)” [component: OData CSDL] is Applied with no objections.
5.6.2.1.1 End of Issue Processing

Note:

Time slot for issue processing gone. Skip all remaining agenda sub items of 5.

6 Next Meeting

6.1 Next TC meeting is conference call on May 30, 2013 during 0800–1000 PT

Agreed

7 AOB

None.

Meeting adjourned on 1002 PT

Appendices

List of Open Action Items Before the Meeting

Retrieval time stamp: 2013-05-23 11:15 +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 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:

JIRA Issues:

Timeline Reference

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