OData meeting #71, Thursday, 24 Apr 2014, 0800 - 1000 PDT

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:

    Edmond Bourne (BlackBerry)
    Hubert Heijkers (IBM)
    John Willson (Individual)
    Ken Baclawski (Northeastern University)
    Mark Biamonte (Progress Software)
    Martin Zurmuehl (SAP AG)
    Matthew Borges (SAP AG) a.k.a. Matt
    Michael Pizzo (Microsoft) a.k.a. Mike
    Ram Jeyaraman (Microsoft)
    Stefan Drees (Individual)
    Susan Malaika (IBM)
    Ted Jones (Red Hat)

Quorum achieved. Details cf. normative attendance sheet for this meeting.

2 Approval of Agenda

Approved as published.

3 Approval of Minutes from Previous Meeting(s)

3.1 Approval of Minutes of 2014–04–03 Meeting#70

Meeting minutes approved as published (latest revision) 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 2014–04–24 (end of day)

None.

4.2 Action items NOT due by 2014–04–24 (end of day) but MAY be ready for closure

None.

5 Review of Timeline

Discussion:

6 OData webinar

Discussion:

7 Interoperation testing

Discussion:

8 Review of Issues List (IL) and Progress

Notes:

8.1 OData v4 Errata issues in New or Open state

Hubert:

I move to resolve ODATA–637, ODATA–638, ODATA–642, ODATA–644, ODATA–647, and ODATA–648 as proposed. Mark seconds.

No further discussion. No objections. The motion passes.

8.1.1 ODATA–642

ODATA–642: “$select wording clarification; specify, rather than restrict, set of properties” [component: OData URL Conventions] is New

Discussion:

Note:

For details cf. 8.1 where the motion is documented.

No further discussion. No objections. The motion passes.

ODATA–642: “$select wording clarification; specify, rather than restrict, set of properties” [component: OData URL Conventions] is Proposed with no objections.

8.1.2 ODATA–646

ODATA–646: “Clarify; returning content from a data modification should be same as GET” [component: OData Protocol] is New

Discussion:

No further discussion. No objections.

ODATA–646: “Clarify; returning content from a data modification should be same as GET” [component: OData Protocol] is Open with no objections.

8.1.3 ODATA–647

ODATA–647: “Define ‘Edit URL’ of primitive property” [component: OData Protocol] is New

Discussion:

Note:

For details cf. 8.1 where the motion is documented.

No further discussion. No objections. The motion passes.

ODATA–647: “Define ‘Edit URL’ of primitive property” [component: OData Protocol] is Proposed with no objections.

8.1.4 ODATA–645

ODATA–645: “Default for PUT/PATCH is not to return data” [component: OData Protocol] is New

Discussion:

No further discussion. No objections.

ODATA–645: “Default for PUT/PATCH is not to return data” [component: OData Protocol] is Open with no objections.

8.1.5 ODATA–600

ODATA–600: “Ensure future compatibility by reference to draft-bray-i-json-n (The I-JSON Message Format)” [component: OData JSON Format] is New

Discussion:

No further discussion. No objections.

ODATA–600: “Ensure future compatibility by reference to draft-bray-i-json-n (The I-JSON Message Format)” [component: OData JSON Format] is New with no objections.

8.1.6 ODATA–644

ODATA–644: “Example 18 should use ‘Orders’ instead of ‘Items’” [component: OData JSON Format] is New

Discussion:

Note:

For details cf. 8.1 where the motion is documented.

No further discussion. No objections. The motion passes.

ODATA–644: “Example 18 should use ‘Orders’ instead of ‘Items’” [component: OData JSON Format] is Proposed with no objections.

8.1.7 ODATA–638

ODATA–638: “Clarify Delta responses with Minimal Metadata” [component: OData Extension for JSON Data] is New

Discussion:

Note:

For details cf. 8.1 where the motion is documented.

No further discussion. No objections. The motion passes.

ODATA–638: “Clarify Delta responses with Minimal Metadata” [component: OData Extension for JSON Data] is Proposed with no objections.

8.1.8 ODATA–648

ODATA–648: “Ambiguity between prose and examples for atom:category element” [component: OData ATOM Format] is New

Discussion:

Note:

For details cf. 8.1 where the motion is documented.

No further discussion. No objections. The motion passes.

ODATA–648: “Ambiguity between prose and examples for atom:category element” [component: OData ATOM Format] is Proposed with no objections.

8.1.9 ODATA–637

ODATA–637: “ATOM and JSON formats do not define representation of operation results” [components: OData JSON Format, OData ATOM Format] is New

Discussion:

Note:

For details cf. 8.1 where the motion is documented.

No further discussion. No objections. The motion passes.

ODATA–637: “ATOM and JSON formats do not define representation of operation results” [components: OData JSON Format, OData ATOM Format] is Proposed with no objections.

8.1.9.1 End fo Issue Processing

Note:

All issues scheduled for processing have been processed.

9 Next meeting

All agree, that next meeting will be on Apr 30, 0800–0900 PDT

Note: Duration will be only one hour.

10 AOB

No other business

Meeting adjourned at 1006 PDT.

List of Open Action Items Before the Meeting

Retrieval time stamp: 2014-04-24 11:22 +02:00.

None.

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.