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:
- Mike proposes to discuss ODATA–346 in section 7.5 as it should not require deeper discussion any more.
- All agree.
Agenda approved as published and amended.
3 Approval of Minutes from Previous Meeting(s)
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
- AI#0018
- “Prepare Working Draft 01 (WD01) version of OData Extension for Temporal Data” [owner: Andrew Eisenberg] is Ongoing
Discussion:
- Hubert intends to take some of the task from the actions previously assigned to Andrew
- Ram asks for some date?
- Hubert is still planning to come up with a date in the next weeks
- Ram suggests to put the date end of June (end of CSD02 review) as a first milestone
- Hubert suggests to first come up with a seed document incorporating the ideas from Zurich and then plan further
- Mike intends to help
- Stefan also offers help in getting started with the documents
- Hubert asks to take owership of action item AI#0018
- AI#0018
- “Prepare Working Draft 01 (WD01) version of OData Extension for Temporal Data” [owner: Hubert Heijkers] is Ongoing
- AI#0019
- “Prepare Working Draft 01 (WD01) version of OData Extension for XML Data” [owner: Andrew Eisenberg] is Ongoing
Discussion:
- Susan tries to help push the xml extension (as vocabulary mainly)
- Stefan will support in writing and pushing
- Ralf and Mike will assist by commenting but have no time to drive it
- ALL: Idea is to focus on vocabulary as xml extension to be able to push this in parallel to the other work product
- Stefan: if standards or non-standards track should be decided from the start, as a non-normative document will never just change into a normative, it has to start from zero again.
- Mike suggests that we produce a vocabulary as xml extension as a TC but through the non-normative track
- Stefan also thinks this is a good goal, but likes to think about it a bit more
- Susan and Stefan will work together to decide how both the OData Extension for XML and JSON Data should be produced and in the longer term where the ownership will be placed for those two extensions
- The first target date (due date of the action) would be next face to face (end of meeting)
- AI#0019
- “Prepare Working Draft 01 (WD01) version of OData Extension for XML Data” [owner: Stefan Drees] is Ongoing (Note: Due 2013–06–14)
- 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:
- Ram walks us through the timeline
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:
- Issues in this section (7) may have been progressed out of sequence, but have been noted here to better group by components impacted as a service for the reader.
- There is an “Index of Issues Processed During the Meeting” section in the appendix.
7.1 Public Review Issues
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].
- ODATA–387:
- Replace (at least) the second example in Section 13 of the CSDL document (public comment c201305e00002)" [component: OData CSDL] is New.
Discussion:
- Mike notes, that inside the JIRA issue has been some discussion and we already have a proposal, thus we should open it.
- Ralf states, that the documentation w.r.t. the Partner attribute has also been enhanced as triggered by this comment.
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:
- All editors shortly present where and if they had to change the agreed resolutions when applying to the work products for ODATA–301, ODATA–219 and ODATA–164.
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
- 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.
- 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
- 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
- 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
- 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.
- 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
- 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
- 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:
- Mike updates proposal in JIRA to reflect the result of discussion during meeting.
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
- ODATA–388:
- “Remove ‘when’ from OData-specific items in delta responses” [component: OData JSON Format] is New.
Discussion:
- Mike would dislike making it optional.
- Mike received feedback from James Snell during the meeting on how to deal with a missing when element.
- All agree to come back to it next week.
- Mike updates the issue in the light of the current discussion and the received feedback from James.
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.
- 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)
- 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:
- Ram asks if the members think there might rise problems from inserting such a section
- Mike likes the idea of inserting the section, but would like to have feedback from the security experts from his company to be sure we only insert correct statements
- John likes it also to be inserted.
- Mike suggests to accept the proposal.
- Hubert seconds this.
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.
- 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:
- Mike notes that we cannot distinguish dynamic properties being null from those, that do not exist.
- Mike suggests to revisit the issue next week.
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.
- ODATA–392:
- “Expanded Navigation Properties should be implicitly added to $select” [component: OData URL Conventions] is New.
Discussion:
- Mike summarizes, why this issues topic is being worked on since the Boston face to face meeting.
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.
- 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 summarizes the issue and proposet the $it symbol and allow this in $filter and $orderby
- Ralf states the example:
GET ~/Customers(1)/EmailAddresses?$filter=endswith($it,‘.com’)
- Ralf further explains, that the following two lines are now equivalent
isof($it,Model.Manager)
isof(Model.Manager)
- Ralf updates the JIRA ticket
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.
- 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:
- ODATA–164 “Consider syntax and rules around client specifying custom aggregation functions for rollups” 7.2.2.1
- ODATA–219 “Detail state and procedures in format agnostic description of In-Stream Error handling” 7.2.1.2
- 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” 7.3.2.2
- ODATA–301 “Guidance around data authorization model and secure authenticated access to an OData Service” 7.2.1.1
- ODATA–346 “Order of child elements of <edm:Collection> MUST be preserved” 7.3.3.1
- ODATA–351 “Define ID, ReadLink and EditLink in Part 1: Protocol, define representation in Atom and JSON” 7.3.4.1
- 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” 7.3.1.1
- ODATA–379 “Ensure consistency and clear description in specification of $count for ‘Delta Responses’ (public comment c201305e00000)” 7.3.2.1
- ODATA–380 “Insert a section in protocol (and similar in JSON and ATOM) named ‘Security Considerations’ (before ‘Conformance’)” 7.5.1
- ODATA–387 “Replace (at least) the second example in Section 13 of the CSDL document (public comment c201305e00002)” 7.1.1.1
- ODATA–388 “Remove ‘when’ from OData-specific items in delta responses” 7.4.1.1
- ODATA–390 “Additional description of use of GeoJSON in OData JSON.” 7.4.1.2
- ODATA–391 “Add query function defined(PropertyPath) to determine whether an instance has a property of that name” 7.5.2
- ODATA–392 “Expanded Navigation Properties should be implicitly added to $select” 7.5.3
- ODATA–393 “Allow querying collections of primitive type instances similar to other collections” 7.5.4
- ODATA–396 “Partner attribute of edm:NavigationProperty is a property path, not a SimpleIdentifier” 7.5.5
Timeline Reference
Note: Please cf. the current revision of the TC timeline.