[Revision 1] Agenda for OData TC meeting 2013.10.03

["Ram Jeyaraman (MS OPEN TECH)" <Ram.Jeyaraman@microsoft.com>]

Here [1] is revision 1 of the draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday October 3, 2013 during 8-10am PT. For additional information, such as dial-in details and chat room, refer to [2]. For TC timeline, see [3]. Feel free to suggest additions or modifications.

 

Revision 1 changes:

·         Section 5a: Added issues ODATA-542 and ODATA-543.

·         Section 6: Added concrete motions for CSD03 approval

 

Note, prior to the meeting, the editors will endeavor to produce working drafts containing applications of all approved resolutions as well as the proposed resolutions to issues listed in section 5a. During the meeting, we will review the latest working drafts and determine if we are ready to approve them as Committee Specification Draft 03.

 

Thanks.

 

[1] Agenda for 2013.10.03 OData TC meeting

 

1.       Roll call [8:00am PT]

a.       Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=34217

 

2.       Approve agenda [8:05am PT]

 

3.       Approve minutes from previous meeting(s) [8:10am PT]

a.       Minutes from October 1, 2013 TC meeting: https://www.oasis-open.org/committees/download.php/50877/odata-meeting-54_on-20131001-minutes.html

 

4.       Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]

a.       Action items due by Oct 03, 2013

                                                               i.      None

 

5.       Process issues [Issues list: https://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10103] [8:20am PT]

a.       Issues for v4.0_CS02 in New or Open state

                                                               i.      OData ATOM Format, OData CSDL, OData JSON Format, OData Protocol

1.       ODATA-527: Relative URLs in OData and the ability to put OData services behind an HTTP proxy [Open]

                                                             ii.      OData Protocol

1.       ODATA-523: How do clients construct links from the context url for complex types? [Open] [Close with no action?]

                                                            iii.      OData CSDL

1.       ODATA-513: Special handling of derived types in the dynamic _expression_ edm:Record. Why? [Open]

2.       ODATA-535: Define specialization for terms [Open]

3.       ODATA-543: ODATA-532
Nullable attribute on collection property should specify whether collection can contain null values [New]

                                                           iv.      OData JSON Format

1.       ODATA-538 Clarify treatment of odata.type with derived types and odata.context for delta responses for odata.metadata=none [Open]

                                                             v.      OData ATOM Format, OData JSON Format, OData Protocol

1.       ODATA-539 Delta response encoding is unnecessarily verbose and change type is missing when odata.metadata=none [Open]

                                                           vi.      OData ABNF Construction Rules, OData Protocol

1.       ODATA-542: Clarify that $selected Actions/Functions are included in [project-list] within a ContextUrl [New]

b.      v4.0_CS02 issues in Applied state

                                                               i.      Issues whose applications may need some discussion

1.       ODATA-537: Ordering of navigationLink and associationLink annotations in JSON

2.       ODATA-532: Clarify whether collections can contain null values

                                                             ii.      Issues whose application is relatively straight forward

1.       ODATA-490: Clarify Referential Constraints have UpdateRule=Cascade semantics

2.       ODATA-531: Simplify OptimisticConcurrency in Core vocabulary

3.       ODATA-536 Treatment of circular references when using $levels

 

6.       Approve Committee Specification Draft 03 (of OData v4, OData JSON Format v4, OData ATOM Format v4 Work Products) and start public review for 15 days [9:45am PT]

a.      Sample motion (for approving OData v4 Work Product): I move that the TC approve OData v4.0 Working Draft 04 and all associated artifacts packaged together in https://www.oasis-open.org/committees/download.php/50907/odata-v4.0-wd04-2013-10-03.zip as Committee Specification Draft 03 and submit it for public review for a duration of 15 days. Further, I move to designate the MS Office version of the Work Product as authoritative.

b.      Sample motion (for approving OData JSON Format v4 Work Product): I move that the TC approve OData JSON Format v4.0 Working Draft 04 and all associated artifacts packaged together in https://www.oasis-open.org/committees/download.php/50906/odata-json-format-v4.0-wd04-2013-10-03.zip as Committee Specification Draft 03 and submit it for public review for a duration of 15 days. Further, I move to designate the MS Office version of the Work Product as authoritative.

c.       Sample motion (for approving OData v4 ATOM Work Product): I move that the TC approve OData ATOM Format v4.0 Working Draft 04 and all associated artifacts packaged together in https://www.oasis-open.org/committees/download.php/50905/odata-atom-format-v4.0-wd04-2013-10-03.zip as Committee Specification Draft 03 and submit it for public review for a duration of 15 days. Further, I move to designate the MS Office version of the Work Product as authoritative.

 

7.       Next meeting [9:55am PT]

a.       Thursday October 10, 2013 during 8-10am PT?

 

8.       AOB and wrap up [9:58am PT]

 

[2] References

·         Conference call details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/46401/TC%20meeting%20dial-in%20details.htm

·         Chat room: http://webconf.soaphub.org/conf/room/odatatc

 

[3] Timeline

·         https://www.oasis-open.org/committees/download.php/50823/TC%20Timeline%206.htm