OData meeting #43, Monday, 24 Jun 2013, 1230 - 1330 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

1 Roll call

1.1 Members Present:

    Barbara Hartel (SAP AG)
    Gerald Krause (SAP AG)
    Hubert Heijkers (IBM)
    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
    Patrick Durusau (Individual)
    Ralf Handl (SAP AG)
    Stefan Drees (Individual)
    Susan Malaika (IBM)
    Ted Jones (Red Hat)

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

2 Approval of Agenda

Discussion:

Agenda approved as ammended.

3 Approval of Minutes from Previous Meeting(s)

3.1 Approval of Minutes of 2013–06–20 Meeting#42

Meeting minutes approved with no objections.

4 Review of Issues List (IL) and Progress

Notes:

4.1 ODATA–463

ODATA–463:
“Deleted-entry, link, and deleted-link should include {entity-set} in context URL” [components: OData ATOM Format, OData ABNF Construction Rules, OData Protocol, OData JSON Format] is New.

Hubert:

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

No further discussion. No objections. The motion passes.

ODATA–463:
“Deleted-entry, link, and deleted-link should include {entity-set} in context URL” [components: OData ATOM Format, OData ABNF Construction Rules, OData Protocol, OData JSON Format] is Resolved.

Note:

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

ODATA–463:
“Deleted-entry, link, and deleted-link should include {entity-set} in context URL” [components: OData ATOM Format, OData ABNF Construction Rules, OData Protocol, OData JSON Format] is Closed with no objections.

4.2 ODATA–464

ODATA–464:
“Disallows $format for delta and next links” [component: OData Protocol] is New.

Discussion:

Stefan:

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

ODATA–464:
“Disallows $format for delta and next links” [component: OData Protocol] is Resolved.

Note:

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

ODATA–464:
“Disallows $format for delta and next links” [component: OData Protocol] is Closed with no objections.

4.3 Usage of Parentheses with Functions vs. Actions

Discussion:

Stefan:

I move that the editors apply the alternate wording “To invoke an action bound to a resource, the client issues a POST request to an action URL. An action URL may be obtained from a previously returned entity representation or constructed by appending the namespace (or alias) qualified action name to a URL that identifies a resource whose type is the same as, or derives from, the type of the binding parameter of the action. ” consistent with ABNF and examples in the prose document. Martin seconds.

No further discussion. No objections. The motion passes.

4.4 Issues in Applied state

Stefan:

I move to close ODATA–262, ODATA–291, ODATA–377, ODATA–386, ODATA–391, ODATA–441, ODATA–445, ODATA–453, ODATA–454, ODATA–455, ODATA–456, ODATA–457, ODATA–458, ODATA–459, ODATA–460, ODATA–463 and ODATA–464 as applied. Martin seconds.

No further discussion. No objections. The motion passes.

4.4.1 ODATA–262

ODATA–262:
“Specify how OData services can be protected against cross-site request forgery (CSRF or XSRF)” [component: Securing Open Data] is Applied.

Note:

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

ODATA–262:
“Specify how OData services can be protected against cross-site request forgery (CSRF or XSRF)” [component: Securing Open Data] is Closed with no objections.

4.4.2 ODATA–291

ODATA–291:
“Consider adding a mechanism for idempotence with POST” [component: Idempotence] is Applied.

Note:

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

ODATA–291:
“Consider adding a mechanism for idempotence with POST” [component: Idempotence] is Closed with no objections.

4.4.3 ODATA–377

ODATA–377:
“Fix broken links in CSD01 documents ” [components: OData CSDL, OData ATOM Format, OData Protocol, OData JSON Format, OData URL Conventions] is Applied.

Note:

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

ODATA–377:
“Fix broken links in CSD01 documents ” [components: OData CSDL, OData ATOM Format, OData Protocol, OData JSON Format, OData URL Conventions] is Closed with no objections.

4.4.4 ODATA–386

ODATA–386:
“odata-v4.0-csprd01-part1-protocol, 3 Data Model, appears to be an unnumbered list of definitions, with annotations defined in a separate subsection - suggest new format, etc.” [component: OData Protocol] is Applied.

Note:

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

ODATA–386:
“odata-v4.0-csprd01-part1-protocol, 3 Data Model, appears to be an unnumbered list of definitions, with annotations defined in a separate subsection - suggest new format, etc.” [component: OData Protocol] is Closed with no objections.

4.4.5 ODATA–391

ODATA–391:
“Add query function isdefined(PropertyPath) to determine whether an instance has a property of that name” [component: OData Extension for Data Aggregation] is Applied.

Note:

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

ODATA–391:
“Add query function isdefined(PropertyPath) to determine whether an instance has a property of that name” [component: OData Extension for Data Aggregation] is Closed with no objections.

4.4.6 ODATA–441

ODATA–441:
“Specify canonical form of entity-id” [components: OData URL Conventions, OData Protocol] is Applied.

Note:

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

ODATA–441:
“Specify canonical form of entity-id” [components: OData URL Conventions, OData Protocol] is Closed with no objections.

4.4.7 ODATA–445

ODATA–445:
“odata.type relative to odata.type in surrounding entities” [components: OData JSON Format, OData ATOM Format] is Applied.

Note:

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

ODATA–445:
“odata.type relative to odata.type in surrounding entities” [components: OData JSON Format, OData ATOM Format] is Closed with no objections.

4.4.8 ODATA–453

ODATA–453:
“deal with KEY function” [components: OData URL Conventions, OData ABNF Construction Rules] is Applied.

Note:

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

ODATA–453:
“deal with KEY function” [components: OData URL Conventions, OData ABNF Construction Rules] is Closed with no objections.

4.4.9 ODATA–454

ODATA–454:
“Need a way to specify a property is unavailable” [components: OData JSON Format, OData ATOM Format, Vocabularies] is Applied.

Note:

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

ODATA–454:
“Need a way to specify a property is unavailable” [components: OData JSON Format, OData ATOM Format, Vocabularies] is Closed with no objections.

4.4.10 ODATA–455

ODATA–455:
“Make EntityContainer a Singleton in MetadataService” [component: OData CSDL] is Applied.

Note:

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

ODATA–455:
“Make EntityContainer a Singleton in MetadataService” [component: OData CSDL] is Closed with no objections.

4.4.11 ODATA–456

ODATA–456:
“Don’t require client to specify odata.trackchanges preference on each page” [component: OData Protocol] is Applied.

Note:

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

ODATA–456:
“Don’t require client to specify odata.trackchanges preference on each page” [component: OData Protocol] is Closed with no objections.

4.4.12 ODATA–457

ODATA–457:
“Require hash (#) on odata.type” [components: OData ATOM Format, OData ABNF Construction Rules, OData Extension for JSON Data] is Applied.

Note:

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

ODATA–457:
“Require hash (#) on odata.type” [components: OData ATOM Format, OData ABNF Construction Rules, OData Extension for JSON Data] is Closed with no objections.

4.4.13 ODATA–458

ODATA–458:
“odata.isolation should be a header rather than an expectation” [component: OData Protocol] is Applied.

Note:

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

ODATA–458:
“odata.isolation should be a header rather than an expectation” [component: OData Protocol] is Closed with no objections.

4.4.14 ODATA–459

ODATA–459:
“State consequences of using IRIs that are not URLs” [component: OData Protocol] is Applied.

Note:

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

ODATA–459:
“State consequences of using IRIs that are not URLs” [component: OData Protocol] is Closed with no objections.

4.4.15 ODATA–460

ODATA–460:
“Add terms to capability vocabulary” [components: Vocabularies, OData Protocol] is Applied.

Note:

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

ODATA–460:
“Add terms to capability vocabulary” [components: Vocabularies, OData Protocol] is Closed with no objections.

5 Approve CSD002

5.1 OASIS Open Data Protocol (OData) version 4.0 multi-part Work Product

Stefan:

I move to approve the latest Working Draft of the OASIS Open Data Protocol (OData) version 4.0 multi-part Work Product including associated files, all contained in https://www.oasis-open.org/committees/download.php/49675/odata-v4.0-wd02-final–2013–06–24.zip Committee Specification Draft 02, and start a 15-day public review. Hubert seconds.

No further discussion. No objections. The motion passes.

5.2 OASIS OData Atom Format version 4.0 Work Product

Stefan:

I move to approve the latest Working Draft of the OASIS OData Atom Format version 4.0 Work Product including associated files, all contained in https://www.oasis-open.org/committees/download.php/49673/odata-atom-format-v4.0-wd02-final–2013–06–24.zip, as Committee Specification Draft 02, and start a 15-day public review. Mike seconds.

No further discussion. No objections. The motion passes.

5.3 OASIS OData JSON Format version 4.0 Work Product

Stefan:

I move to approve the latest Working Draft of the OASIS OData JSON Format version 4.0 Work Product including associated files, all contained in https://www.oasis-open.org/committees/download.php/49674/odata-json-format-v4.0-wd02-final–2013–06–24.zip, as Committee Specification Draft 02, and start a 15-day public review. Mike seconds.

No further discussion. No objections. The motion passes.

6 Next Meetings

6.1 Meeting on 2013–07–11 by Call during 0800–1000 PT

Note:

Meeting 2013–06–27 skipped due to missing agenda items, meeting 2013–07–04 skipped due to public holiday in the US. The meeting on 2013-.07–11 is planned with two hours duration, so we may process any issues triggered by public comments from the CSD02 public review period.

7 AOB

None.

Meeting adjourned on 1332 PT

Index of Issues Processed During the Meeting

Note: The actual issue processing is documented in sections 4. 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.