OData meeting #39, Thursday, 30 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 Ram Jeyaraman

1 Roll call

1.1 Members Present:

    Dale Moberg (Axway Software)
    Diane Downie (Citrix Systems)
    Edmond Bourne (BlackBerry) a.k.a. Ed
    Hubert Heijkers (IBM)
    Jeffrey Turpin (Axway Software)
    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)
    Ralf Handl (SAP AG)
    Ram Jeyaraman (Microsoft)
    Stan Mitranic (CA Technologies)
    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–05–23 Meeting#38

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

None.

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

None.

5 Preparing towards Committee Specification Draft 02

5.1 State of pending issues

Reminder:

as discussed earlier, please file significant technical issues by June 2nd.

Discussion:

No further discussion. No objections.

6 Review of Issues List (IL) and Progress

Notes:

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

6.1.1 OData Protocol

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

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.

6.1.2 OData Protocol, OData URL Conventions

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

6.1.3 OData JSON Format

6.1.3.1 ODATA–316
ODATA–316:
“Services MUST NOT omit structural properties from responses unless asked to do so via $select” [component: OData JSON Format] is Open.

Discussion:

No further discussion. No objections.

ODATA–316:
“Services MUST NOT omit structural properties from responses unless asked to do so via $select” [component: OData JSON Format] is Open with no objections.

6.2 Issues in Proposed state since May 23, 2013

6.2.1 Vocabularies

6.2.1.1 ODATA–410
ODATA–410:
“Consider moving terms OptimisticConcurrencyControl and AcceptableMediaTypes from Core to Capabilities” [component: Vocabularies] is New.

Discussion:

Stefan:

I move to close ODATA–410 as proposed. Ralf seconds.

No further discussion. No objections. The motion passes.

ODATA–410:
“Consider moving terms OptimisticConcurrencyControl and AcceptableMediaTypes from Core to Capabilities” [component: Vocabularies] is Closed with no objections.

6.2.2 OData CSDL

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

Discussion:

Hubert:

I move to resolve OData–411 as proposed. Stefan seconds.

No further discussion. No objections. The motion passes.

ODATA–411:
“Reconsider placement and semantics of OnDelete element” [component: OData CSDL] is Resolved with no objections.
6.2.2.2 ODATA–418
ODATA–418:
“EntitySet attribute or NavigationPropertyBinding child elements for Named Entities (edm:Entity)” [component: OData CSDL] is New.

Discussion:

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–418:
“EntitySet attribute or NavigationPropertyBinding child elements for Named Entities (edm:Entity)” [component: OData CSDL] is Resolved with no objections.
6.2.2.3 ODATA–287
ODATA–287:
“Consider adding a primitive type that corresponds with JSR 310 (JDK 1.8 time API) ZonedDateTime” [component: OData CSDL] is New.

Discussion:

Mik:

I move to resolve ODATA–287 as proposed by deferring to v5.0. Ralf seconds.

No further discussion. No objections. The motion passes.

ODATA–287:
“Consider adding a primitive type that corresponds with JSR 310 (JDK 1.8 time API) ZonedDateTime” [component: OData CSDL] is Deferred as noted in the motion with no objections.
6.2.2.4 ODATA–220
ODATA–220:
“Please consider the restoration of DateTime (without offset)” [component: OData CSDL] is New.

Discussion:

Mike:

I move we resolve ODATA–220 as proposed by deferring to version 5.0. Ed seconds.

No further discussion. No objections. The motion passes.

ODATA–220:
“Please consider the restoration of DateTime (without offset)” [component: OData CSDL] is Deferred as noted in the motion with no objections.

6.2.3 OData ATOM Format, OData JSON Format, OData Protocol

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

Discussion:

Mike:

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

No further discussion. No objections. The motion passes.

ODATA–412:
“Consistent representation of empty values” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Resolved with no objections.
6.2.3.2 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 New.

Discussion:

Stefan:

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

No further discussion. No objections. The motion passes.

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

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

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

Discussion:

No further discussion. No objections.

Mike:

I move we accept ODATA–414 as proposed. Hubert seconds.

No further discussion. No objections. The motion passes.

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

6.2.5 OData Protocol

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

Discussion:

Stefan:

I move we resolve ODATA–420 as proposed. Mike seconds.

No further discussion. No objections. The motion passes.

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

6.2.6 OData ATOM Format, OData JSON Format, OData URL Conventions

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

Discussion:

Ralf:

I move to resolve ODATA–417 as proposed, also reserving application/atom+xml for $metadata. Hubert seconds.

No further discussion. No objections. The motion passes.

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 Resolved as noted in the motion with no objections.

6.2.7 OData JSON Format, OData Protocol

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

Discussion:

Mike:

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

No further discussion. No objections. The motion passes.

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

6.2.8 OData CSDL, OData URL Conventions

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

Discussion:

No further discussion. No objections.

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

6.3 Issues in Applied state

Discussion:

7 Next Meeting

7.1 Next TC meeting is conference call on Jun 06, 2013 during 0800–1000 PT

Agreed

7.2 Next TC meeting is face to face meeting on Jun 13, 2013 and Jun 14, 2013

Discussion:

8 AOB

None.

Meeting adjourned on 0949 PT

Appendices

List of Open Action Items Before the Meeting

Retrieval time stamp: 2013-05-30 15: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 6. 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.