OData meeting #40, Thursday, 06 JUN 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)
    Diane Downie (Citrix Systems)
    Edmond Bourne (BlackBerry)
    Gerald Krause (SAP AG)
    Hubert Heijkers (IBM)
    Ken Baclawski (Northeastern University)
    Matthew Borges (SAP AG) a.k.a. Matt
    Michael Pizzo (Microsoft) a.k.a. Mike
    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

Ralf suggests adding ODATA–419 to processing of proposed issues.

Agenda approved as ammended.

3 Approval of Minutes from Previous Meeting(s)

3.1 Approval of Minutes of 2013–05–30 Meeting#39

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

None.

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

None.

5 Review of Issues List (IL) and Progress

Notes:

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

5.1.1 OData Part 1: Protocol

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

Stefan:

I move to resolve ODATA–262 as proposed by adding it to the TC Note “Securing Open Data”. Ralf seconds.

No further discussion. No objections. The motion passes.

ODATA–262:
“Specify how OData services can be protected against cross-site request forgery (CSRF or XSRF)” [component: OData Protocol] is Resolved with no objections.
5.1.1.2 ODATA–314
ODATA–314:
“Please clarify the meaning of filter functions applied to DateTimeOffset values” [components: OData URL Conventions, OData Protocol] is Open.

Discussion:

Mike:

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

No further discussion. No objections. The motion passes.

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

5.1.2 OData JSON Format

5.1.2.1 ODATA–316
ODATA–316:
“Services select a default set of properties in absence of $select” [component: OData JSON Format] is Open.

Discussion:

Mike:

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

No further discussion. No objections. The motion passes.

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

5.2 Issues in Proposed state carried over from May 23, 2013

5.2.1 OData Part 3: CSDL

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

Discussion:

Patrick:

I move to resolve ODATA–413 as discussed. Mike seconds.

No further discussion. No objections. The motion passes.

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

5.3 Issues in Proposed state since May 30, 2013

5.3.1 OData Part 1: Protocol

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

Discussion:

Stefan:

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

No further discussion. No objections. The motion passes.

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

5.3.2 OData Part 3: CSDL

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

Discussion:

No further discussion. No objections.

ODATA–415:
“Use of ‘MUST,’ ‘MAY,’ ‘SHOULD,’ etc in Part 3 CSDL definitions” [component: OData CSDL] is Open with no objections.
5.3.2.2 ODATA–423
ODATA–423:
“Rename edm:Entity to edm:SingletonEntity and its Type attribute to EntityType” [components: OData CSDL, OData ATOM Format, OData Protocol, OData JSON Format, OData URL Conventions] is New.

Discussion:

Martin:

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

No further discussion. No objections. The motion passes.

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

5.3.3 OData Atom Format

5.3.3.1 ODATA–424
ODATA–424:
“Allow MicroXML as first class format (parallel to JSON and probably remove ATOM or remap the latter to MicroXML in future versions)” [components: OData ATOM Format, OData ABNF Construction Rules, OData Extension for JSON Data, OData CSDL, OData JSON Format, OData Extension for XML Data, OData URL Conventions, OData Protocol, Vocabularies] is New.

Discussion:

Stefan:

I move to defer ODATA–424. Mike seconds.

No further discussion. No objections. The motion passes.

ODATA–424:
“Allow MicroXML as first class format (parallel to JSON and probably remove ATOM or remap the latter to MicroXML in future versions)” [components: OData ATOM Format, OData ABNF Construction Rules, OData Extension for JSON Data, OData CSDL, OData JSON Format, OData Extension for XML Data, OData URL Conventions, OData Protocol, Vocabularies] is Deferred with no objections.

5.4 Issues deferred to next version

5.4.1 ODATA–405

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

Discussion:

Ralf:

I move to defer ODATA–405 to the next version of the spec. Hubert seconds.

No further discussion. No objections. The motion passes.

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

5.5 Issues in Applied state

5.5.1 Issues related to public comments (please review this changes that we can possibly close the issues)

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

Stefan:

I move to close ODATA–379 as applied. Martin seconds.

No further discussion. No objections. The motion passes.

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

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

Stefan:

I move to close ODATA–387 as applied. Patrick seconds.

No further discussion. No objections. The motion passes.

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

5.6 Additional Issues in Proposed state

Discussion:

5.6.1 ODATA–425

ODATA–425:
“Clarify rules around parameter overloads and return types” [component: OData CSDL] is New.

Discussion:

Mike:

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

No further discussion. No objections. The motion passes.

ODATA–425:
“Clarify rules around parameter overloads and return types” [component: OData CSDL] is Resolved with no objections.

5.6.2 ODATA–426

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

Discussion:

Hubert:

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

No further discussion. No objections. The motion passes.

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

5.6.3 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 Open.

Discussion:

Stefan:

I move to resolve ODATA–381 as proposed. Patrick seconds.

No further discussion. No objections. The motion passes.

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

6 Next Meeting

6.1 Next TC meeting is face to face meeting from Thursday, 13 June 2013, 09:00am to Friday, 14 June 2013, 06:00pm PDT in Redmond, Washington, USA

Agreed

7 AOB

None.

Meeting adjourned on 0958 PT

Appendices

List of Open Action Items Before the Meeting

Retrieval time stamp: 2013-06-06 16:10 +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:

None.

JIRA Issues:

Timeline Reference

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