OData meeting #30, Thursday, 21 Mar 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:

    Andrew Eisenberg (IBM)
    Anila Kumar GVN (CA Technologies)
    Barbara Hartel (SAP AG)
    Dale Moberg (Axway Software)
    Diane Downie (Citrix Systems)
    Gerald Krause (SAP AG)
    Jeffrey Turpin (Axway Software)
    John Willson (Individual)
    Ken Baclawski (Northeastern University)
    Martin Zurmuehl (SAP AG)
    Michael Pizzo (Microsoft) a.k.a. Mike
    Patrick Durusau (Individual)
    Ralf Handl (SAP AG)
    Ram Jeyaraman (Microsoft)
    Robert Richards (Mashery)
    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–03–14 Meeting#29

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

None.

4.2 Action items NOT due by 2013–03–21 (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 (carried over from Feb 21, 2013 TC meeting)

5.1.1 OData JSON Format, OData Protocol

5.1.1.1 ODATA–283
ODATA–283:
“Accept-Charset HTTP Request Header and charset content-type parameter” [components: OData Protocol, OData JSON Format] is Open.

Discussion:

Mike:

I move we resolve ODATA–283 by saying that the Accept-Charset header has priority, and the service MUST NOT return a charset=format parameter unless specified in the request. Ralf seconds.

No further discussion. No objections. The motion passes.

ODATA–283:
“Accept-Charset HTTP Request Header and charset content-type parameter” [components: OData Protocol, OData JSON Format] is Resolved as noted in the motion with no objections.

5.2 Issues in Proposed state (since March 14, 2013)

5.2.1 OData CSDL

5.2.1.1 ODATA–239
ODATA–239:
“Allowing expressions to be passed as parameters to (super) functions” [component: OData CSDL] is New.

Discussion:

No further discussion. No objections.

ODATA–239:
“Allowing expressions to be passed as parameters to (super) functions” [component: OData CSDL] is Open with no objections.
5.2.1.2 ODATA–266
ODATA–266:
“Strengthen the requirements for the URL Attribute in edmx:Reference and edmx:AnnotationReference” [component: OData CSDL] is New.

Discussion:

No further discussion. No objections.

Martin:

I move as proposal to change in subchapter 4.4.1 and 4.3.1 of the csdl part 3 specification the sentence “The URL may be backed by a CSDL document describing the referenced model” to “The URL SHOULD be backed by a CSDL document describing the referenced model”. If it’s NOT backed, it should be well known. Mike seconds.

No further discussion. No objections. The motion passes.

ODATA–266:
“Strengthen the requirements for the URL Attribute in edmx:Reference and edmx:AnnotationReference” [component: OData CSDL] is Resolved as noted in the motion with no objections.
5.2.1.3 ODATA–271
ODATA–271:
“Support IsAlwaysBindable through annotation, rather than attribute of function/action” [component: OData CSDL] is New.

Discussion:

No further discussion. No objections.

ODATA–271:
“Support IsAlwaysBindable through annotation, rather than attribute of function/action” [component: OData CSDL] is Open with no objections.
5.2.1.4 ODATA–299
ODATA–299:
“Should Duration be renamed DayTimeDuration in anticipation that we may wish to add YearMonthDuration at a later point?” [component: OData CSDL] is New.

Stefan:

I move to close ODATA–299 without action. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–299:
“Should Duration be renamed DayTimeDuration in anticipation that we may wish to add YearMonthDuration at a later point?” [component: OData CSDL] is Closed as noted in the motion with no objections.
5.2.1.5 ODATA–303
ODATA–303:
“Support abstract entity types without key properties” [component: OData CSDL] is New.

Discussion:

Martin:

I move to resolve ODATA–303 as proposed with the additions discussed. Mike seconds.

No further discussion. No objections. The motion passes.

ODATA–303:
“Support abstract entity types without key properties” [component: OData CSDL] is Resolved as noted in the motion with no objections.
5.2.1.6 ODATA–304
ODATA–304:
“Add TargetKey attribute to <PropertyRef> within a <ReferentialConstraint>” [component: OData CSDL] is New.

Discussion:

Martin:

I move to resolve 304 as proposed. Mike seconds.

No further discussion. No objections. The motion passes.

ODATA–304:
“Add TargetKey attribute to <PropertyRef> within a <ReferentialConstraint>” [component: OData CSDL] is Resolved with no objections.
5.2.1.7 ODATA–305
ODATA–305:
“Annotations: introduce path segment to address the count of a collection” [component: OData CSDL] is New.

Martin:

I move to resolve 305 as proposed. Stefan seconds.

No further discussion. No objections. The motion passes.

ODATA–305:
“Annotations: introduce path segment to address the count of a collection” [component: OData CSDL] is Resolved with no objections.

5.2.2 OData Protocol OData URL Conventions

5.2.2.1 ODATA–9
ODATA–9:
“allow expressions in the $select query option” [components: OData URL Conventions, OData Protocol] is New.

Mike:

I move we defer ODATA–9 to be considered in version 5.0. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–9:
“allow expressions in the $select query option” [components: OData URL Conventions, OData Protocol] is Deferred as noted in the motion with no objections.
5.2.2.2 ODATA–10
ODATA–10:
“operator that returns the content of a Stream as either a String or Binary value” [components: OData URL Conventions, OData Protocol] is New.

Stefan:

I move we defer ODATA–10 to be considered in version 5.0. Mike seconds.

No further discussion. No objections. The motion passes.

ODATA–10:
“operator that returns the content of a Stream as either a String or Binary value” [components: OData URL Conventions, OData Protocol] is Deferred as noted in the motion with no objections.

5.2.3 OData Protocol

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

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.2.3.2 ODATA–297
ODATA–297:
“State explicitly if Content-Length is required, and if so, for which request types it is required” [component: OData Protocol] is New.

Discussion:

No further discussion. No objections.

ODATA–297:
“State explicitly if Content-Length is required, and if so, for which request types it is required” [component: OData Protocol] is Open with no objections.
5.2.3.3 ODATA–301
ODATA–301:
“Guidance around data authorization model and secure authenticated access to an OData Service” [component: OData Protocol] is New.

Discussion:

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–301:
“Guidance around data authorization model and secure authenticated access to an OData Service” [component: OData Protocol] is Resolved with no objections.
5.2.3.4 ODATA–165
ODATA–165:
“Support Cross-joins” [component: OData Protocol] is Open.

Discussion:

Stefan:

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

No further discussion. No objections. The motion passes.

ODATA–165:
“Support Cross-joins” [component: OData Protocol] is Resolved with no objections.

5.3 Introduction to conformance levels.

Context:

Uploaded current revision of Conformance Levels.

Discussion:

5.4 Issues in Applied state (since March 7, 2013)

5.4.1 OData Protocol

Stefan:

I move to close ODATA–282 and ODATA–243 as applied. Mike seconds.

No further discussion. No objections. The motion passes.

5.4.1.1 ODATA–282
ODATA–282:
“Support individual data modification statements within a batch without wrapping in a changeset” [component: OData Protocol] is Applied.

Note:

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

ODATA–282:
“Support individual data modification statements within a batch without wrapping in a changeset” [component: OData Protocol] is Closed with no objections.
5.4.1.2 ODATA–243
ODATA–243:
“Add client preferences for server-driven paging” [component: OData Protocol] is Applied.

Note:

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

ODATA–243:
“Add client preferences for server-driven paging” [component: OData Protocol] is Closed with no objections.
5.4.1.2.1 End of Issue Processing

Note:

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

6 Next Meetings

6.1 No TC meeting on 2013–03–28

Please use the time for the document review.

6.2 Next TC meeting will be 2013–04–04 during 8–10am PT.

Agreed.

7 AOB

None.

Meeting adjourned on 1000 PT

Appendices

List of Open Action Items Before the Meeting

Retrieval time stamp: 2013-03-21 15:15 +01:00.

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

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.