OData meeting #36, Thursday, 09 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)
    Jeffrey Turpin (Axway Software)
    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

Mike suggests to talk about ODATA–378 at the end of the planned processing of proposed issues on agenda.

Agenda approved as ammended.

3 Approval of Minutes from Previous Meeting(s)

3.1 Approval of Minutes of 2013–05–02 Meeting#35

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

None.

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

None.

5 Preparing towards Committee Specification Draft 02

5.1 Timeline Impact CSD02

Context:

In order to stick to the timeline TL, we need to file any remaining technical issues ASAP, so we can process those issues (along with any public review comments) by mid-June, in time for approving CSD02 by end of June.

Discussion:

5.2 Issue Roadmap CSD02

Context:

Are there significant technical issues you plan to file? If so, when do you expect to file them?

Discussion:

6 Fifth TC face-to-face meeting

6.1 Daterange of Meeting

Context:

At the recently concluded face-to-face meeting in Walldorf, Germany, we discussed the possibility of holding the next F2F meeting during the week of June 17th.

Discussion:

6.2 Venue of Meeting

Context:

Would the week of June 17 or June 10th work for you, if it were to be held in Redmond, WA?

Discussion:

Tentative planned participation:

7 Documentation of changes between OData version 3 and version 4

Context:

Recently there were some questions about what are the changes between OData v3 and v4. Let’s discuss the next steps towards identifying what those changes are and how to publish them.

Discussion:

8 Review of Issues List (IL) and Progress

Notes:

8.1 Public Review Issues

8.1.1 ODATA–379

ODATA–379:
“Ensure consistency and clear description in specification of $count for ‘Delta Responses’ (public comment c201305e00000)” [component: OData Protocol] is New.

Discussion:

No further discussion. No objections.

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

8.2 Issues in Proposed state (may be ripe for resolution)

8.2.1 OData CSDL

8.2.1.1 ODATA–373

ODATA–373:
“Add boolean expressions that can be used in <edm:If>” [component: OData CSDL] is New.

Discussion:

Stefan:

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

No further discussion. No objections. The motion passes.

ODATA–373:
“Add boolean expressions that can be used in <edm:If>” [component: OData CSDL] is Resolved with no objections.

8.2.1.2 ODATA–370

ODATA–370:
“Disallow Nullable facet for collection-valued properties” [component: OData CSDL] is New.

Stefan:

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

No further discussion. No objections. The motion passes.

ODATA–370:
“Disallow Nullable facet for collection-valued properties” [component: OData CSDL] is Resolved with no objections.

8.2.1.3 ODATA–364

ODATA–364:
“Explicitly state that the restriction that a property MUST NOT have the same name as its containing type only applies to directly declared properties” [component: OData CSDL] is New.

Discussion:

No further discussion. No objections.

ODATA–364:
“Explicitly state that the restriction that a property MUST NOT have the same name as its containing type only applies to directly declared properties” [component: OData CSDL] is Open with no objections.

8.2.2 OData Protocol

8.2.2.1 ODATA–371

ODATA–371:
“Clearly describe behavior of PUT for structural and navigation properties” [component: OData Protocol] is New.

Discussion:

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–371:
“Clearly describe behavior of PUT for structural and navigation properties” [component: OData Protocol] is Resolved with no objections.

8.2.2.2 ODATA–369

ODATA–369:
“POST to navigation link with binding information leading to a different ‘parent’ is invalid” [component: OData Protocol] is New.

Discussion:

Mike:

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

No further discussion. No objections. The motion passes.

ODATA–369:
“POST to navigation link with binding information leading to a different ‘parent’ is invalid” [component: OData Protocol] is Resolved with no objections.

8.2.2.3 ODATA–367

ODATA–367:
“Explicitly state that server MAY expand results beyond what’s requested with $expand” [component: OData Protocol] is New.

Discussion:

Mike:

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

No further discussion. No objections. The motion passes.

ODATA–367:
“Explicitly state that server MAY expand results beyond what’s requested with $expand” [component: OData Protocol] is Resolved with no objections.

8.2.2.4 ODATA–365

ODATA–365:
“Rename edm:AssertType to edm:Cast and clarify behavior of edm:Cast and cast()” [component: OData Protocol] is New.

Discussion:

Martin:

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

No further discussion. No objections. The motion passes.

ODATA–365:
“Rename edm:AssertType to edm:Cast and clarify behavior of edm:Cast and cast()” [component: OData Protocol] is Resolved with no objections.

8.2.2.5 ODATA–296

ODATA–296:
“Change tracking may require server-side state, but client cannot advise server to stop tracking in order to allow server to release resources” [component: OData Protocol] is New.

Discussion:

No further discussion. No objections.

ODATA–296:
“Change tracking may require server-side state, but client cannot advise server to stop tracking in order to allow server to release resources” [component: OData Protocol] is Open with no objections.

8.2.2.6 ODATA–368

ODATA–368:
“Deep insert: if server responds with 201 Created it MUST respond with at least the expansion depth of the insert operation” [component: OData Protocol] is New.

Discussion:

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–368:
“Deep insert: if server responds with 201 Created it MUST respond with at least the expansion depth of the insert operation” [component: OData Protocol] is Resolved with no objections.

8.2.2.7 ODATA–366

ODATA–366:
“Clarify whether server-generated properties can be omitted in POST, even if they are not nullable” [component: OData Protocol] is New.

Discussion:

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–366:
“Clarify whether server-generated properties can be omitted in POST, even if they are not nullable” [component: OData Protocol] is Resolved with no objections.

8.2.3 OData ATOM Format, OData JSON Format, OData Protocol

8.2.3.1 ODATA–351

ODATA–351:
“Define ID, ReadLink and EditLink in Part 1: Protocol, define representation in Atom and JSON” [components: OData JSON Format, OData ATOM Format, OData Protocol] is New.

Discussion:

No further discussion. No objections.

ODATA–351:
“Define ID, ReadLink and EditLink in Part 1: Protocol, define representation in Atom and JSON” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Open with no objections.

8.2.4 OData ABNF Construction Rules, OData URL Conventions

8.2.4.1 ODATA–375

ODATA–375:
“Allow querying collections of complex type instances similar to querying collections of entities” [components: OData URL Conventions, OData ABNF Construction Rules] is New.

Discussion:

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–375:
“Allow querying collections of complex type instances similar to querying collections of entities” [components: OData URL Conventions, OData ABNF Construction Rules] is Resolved with no objections.

8.2.5 OData JSON Format

8.2.5.1 ODATA–376

ODATA–376:
“Navigation link representation for navigation properties of complex type instances” [component: OData JSON Format] is New.

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–376:
“Navigation link representation for navigation properties of complex type instances” [component: OData JSON Format] is Resolved with no objections.

8.2.6 OData JSON Format, OData ATOM Format

8.2.6.1 ODATA–378

ODATA–378:
“Support relative IRIs for ids in JSON” [components: OData JSON Format, OData ATOM Format] is New.

Discussion:

Mike:

I move to accept ODATA 378 as proposed. Stefan seconds.

No further discussion. No objections. The motion passes.

ODATA–378:
“Support relative IRIs for ids in JSON” [components: OData JSON Format, OData ATOM Format] is Resolved with no objections.

8.3 Issues in Applied state

8.3.1 OData Protocol

8.3.1.1 ODATA–301

ODATA–301:
“Guidance around data authorization model and secure authenticated access to an OData Service” [component: OData Protocol] is Applied.

Discussion:

Martin:

I move to resolve ODATA–301 as proposed, server should consider implementing basic auth. Mike 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 as noted in the motion with no objections.
8.3.1.1.1 End of Issue Processing

Note:

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

9 Next Meeting

9.1 Next TC meeting is conference call on May 16, 2013 during 0800–1000 PT

Agreed

10 AOB

None.

Meeting adjourned on 1002 PT

Appendices

List of Open Action Items Before the Meeting

Retrieval time stamp: 2013-05-08 11:33 +02: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 8. 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.