OData meeting #37, Thursday, 16 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 Barbara Hartel and Ram Jeyaraman

Acting chair: Ram Jeyaraman

1 Roll call

1.1 Members Present:

    Barbara Hartel (SAP AG)
    Dale Moberg (Axway Software)
    Diane Downie (Citrix Systems)
    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
    Ralf Handl (SAP AG)
    Ram Jeyaraman (Microsoft)
    Stefan Drees (Individual)
    Susan Malaika (IBM)
    Ted Jones (Red Hat)

Regrets from Patrick Durusau.

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

2 Approval of Agenda

Discussion:

Agenda approved as published and amended.

3 Approval of Minutes from Previous Meeting(s)

3.1 Approval of Minutes of 2013–05–09 Meeting#36

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

None.

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

None.

4.3 Action items updates

4.3.1 AI#0018

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

Discussion:

AI#0018
“Prepare Working Draft 01 (WD01) version of OData Extension for Temporal Data” [owner: Hubert Heijkers] is Ongoing

4.3.2 AI#0019

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

Discussion:

AI#0019
“Prepare Working Draft 01 (WD01) version of OData Extension for XML Data” [owner: Stefan Drees] is Ongoing (Note: Due 2013–06–14)

4.3.3 AI#0020

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

Note:

Discussion points relevant to AI#0020 are noted in section 4.3.2 where the discussion took place.

AI#0020
“Prepare Working Draft 01 (WD01) version of OData Extension for JSON Data” [owner: Susan Malaika] is Ongoing (Note: Due 2013–06–14)

5 Preparing towards Committee Specification Draft 02

5.1 Issue Roadmap CSD02

Context:

Reminder please file significant technical issues by 2013–06–02 if possible.

5.2 Timeline Impact CSD02

Context:

Review timeline TL for CSD02.

Discussion:

6 Fifth TC face-to-face meeting

6.1 Any Questions?

Context:

5th TC face-to-face meeting.

7 Review of Issues List (IL) and Progress

Notes:

7.1 Public Review Issues

7.1.1 c201305e00002

Context:

We received the public Comment #20130500002 on 2013–05–12 with title “DiscontinuedProducts is a really bad example”. To prepare processing a corresponding JIRA issue ODATA–387 has been created with summary “Replace (at least) the second example in Section 13 of the CSDL document (public comment c201305e00002)” [component: OData CSDL].

7.1.1.1 ODATA–387
ODATA–387:
Replace (at least) the second example in Section 13 of the CSDL document (public comment c201305e00002)" [component: OData CSDL] is New.

Discussion:

Hubert:

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

No further discussion. No objections. The motion passes.

ODATA–387:
Replace (at least) the second example in Section 13 of the CSDL document (public comment c201305e00002)" [component: OData CSDL] is Resolved with no objections.

7.2 Issues in Applied state

Discussion:

Stefan:

I move to close ODATA–301, ODATA–219 and ODATA–164 as applied. Mike seconds.

No further discussion. No objections. The motion passes.

7.2.1 OData Protocol

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

Note:

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

ODATA–301:
“Guidance around data authorization model and secure authenticated access to an OData Service” [component: OData Protocol] is Closed with no objections.
7.2.1.2 ODATA–219
ODATA–219:
“Detail state and procedures in format agnostic description of In-Stream Error handling” [component: OData Protocol] is Resolved.

Note:

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

ODATA–219:
“Detail state and procedures in format agnostic description of In-Stream Error handling” [component: OData Protocol] is Closed with no objections.

7.2.2 OData Extension for Data Aggregation

7.2.2.1 ODATA–164

ODATA–164:
“Consider syntax and rules around client specifying custom aggregation functions for rollups” [component: OData Extension for Data Aggregation] is Applied.

Note:

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

ODATA–164:
“Consider syntax and rules around client specifying custom aggregation functions for rollups” [component: OData Extension for Data Aggregation] is Closed with no objections.

7.3 Issues in Proposed state (may be ripe for resolution) (carried over from May 9, 2013)

7.3.1 OData CSDL

7.3.1.1 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 Open.

Mike:

I move we resolve ODATA 364 as proposed. Ralf seconds.

No further discussion. No objections. The motion passes.

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

7.3.2 OData Protocol

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

Mike:

I move we resolve ODATA–379 as proposed. Hubert seconds.

No further discussion. No objections. The motion passes.

ODATA–379:
“Ensure consistency and clear description in specification of $count for ‘Delta Responses’ (public comment c201305e00000)” [component: OData Protocol] is Resolved with no objections.
7.3.2.2 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 Open.

Hubert:

I move to close ODATA–296 with no action. Ralf seconds.

No further discussion. No objections. The motion passes.

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

7.3.3 OData CSDL

7.3.3.1 ODATA–346
ODATA–346:
“Order of child elements of MUST be preserved” [component: OData CSDL] is New.

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–346:
“Order of child elements of MUST be preserved” [component: OData CSDL] is Resolved with no objections.

7.3.4 OData ATOM Format, OData JSON Format, OData Protocol

7.3.4.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 Open.

Discussion:

Hubert:

I move to resolve ODATA–351 as per the updated proposal. Mike seconds.

No further discussion. No objections. The motion passes.

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

7.4 Issues in Proposed state (since May 9, 2013)

7.4.1 OData JSON Format

7.4.1.1 ODATA–388
ODATA–388:
“Remove ‘when’ from OData-specific items in delta responses” [component: OData JSON Format] is New.

Discussion:

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–388:
“Remove ‘when’ from OData-specific items in delta responses” [component: OData JSON Format] is Resolved with no objections.
7.4.1.2 ODATA–390
ODATA–390:
“Additional description of use of GeoJSON in OData JSON.” [component: OData JSON Format] is New.

Stefan:

I move to resolve ODATA–390 as proposed. John seconds.

No further discussion. No objections. The motion passes.

ODATA–390:
“Additional description of use of GeoJSON in OData JSON.” [component: OData JSON Format] is Resolved with no objections.

7.5 Issues that may be ripe for resolution (since May 9, 2013)

7.5.1 ODATA–380

ODATA–380:
“Insert a section in protocol (and similar in JSON and ATOM) named ‘Security Considerations’ (before ‘Conformance’)” [components: OData JSON Format, OData ATOM Format, OData Protocol] is New.

Discussion:

Mike:

I move to approve ODATA–380 a proposed. Hubert seconds.

No further discussion. No objections. The motion passes.

ODATA–380:
“Insert a section in protocol (and similar in JSON and ATOM) named ‘Security Considerations’ (before ‘Conformance’)” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Resolved with no objections.

7.5.2 ODATA–391

ODATA–391:
“Add query function defined(PropertyPath) to determine whether an instance has a property of that name” [components: OData URL Conventions, OData Extension for Data Aggregation] is New.

Discussion:

No further discussion. No objections.

ODATA–391:
“Add query function defined(PropertyPath) to determine whether an instance has a property of that name” [components: OData URL Conventions, OData Extension for Data Aggregation] is Open with no objections.

7.5.3 ODATA–392

ODATA–392:
“Expanded Navigation Properties should be implicitly added to $select” [component: OData URL Conventions] is New.

Discussion:

Hubert:

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

No further discussion. No objections. The motion passes.

ODATA–392:
“Expanded Navigation Properties should be implicitly added to $select” [component: OData URL Conventions] is Resolved with no objections.

7.5.4 ODATA–393

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

Discussion:

Ralf:

I move to resolve ODATA–393 minus the optional part. Hubert seconds.

No further discussion. No objections. The motion passes.

ODATA–393:
“Allow querying collections of primitive type instances similar to other collections” [components: OData URL Conventions, OData ABNF Construction Rules] is Resolved as noted in the motion with no objections.

7.5.5 ODATA–396

ODATA–396:
“Partner attribute of edm:NavigationProperty is a property path, not a SimpleIdentifier” [component: OData CSDL] is New.

Hubert:

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

No further discussion. No objections. The motion passes.

ODATA–396:
“Partner attribute of edm:NavigationProperty is a property path, not a SimpleIdentifier” [component: OData CSDL] is Resolved with no objections.
7.5.5.1 End of Issue Processing

Note:

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

8 Next Meeting

8.1 Next TC meeting is conference call on May 23, 2013 during 0800–1000 PT

Agreed

9 AOB

None.

Meeting adjourned on 1000 PT

Appendices

List of Open Action Items Before the Meeting

Retrieval time stamp: 2013-05-15 23:51 +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 7. 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:

JIRA Issues:

Timeline Reference

Note: Please cf. the current revision of the TC timeline.