Agenda for OData TC meeting 2013.01.24

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

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday January 24, 2013 during 8-9am 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.

 

Thanks.

 

[1] Agenda for 2013.01.24 OData TC meeting

 

1.      Roll call [8:00am PT]

2.      Approve agenda [8:05am PT]

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

a.      Minutes from January 17, 2013 TC meeting: https://www.oasis-open.org/committees/download.php/47933/odata-meeting-21_on-20130117-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 Jan 24, 2013

                                               i.          None

b.      Action items NOT due by Jan 24, 2013 but MAY be ready for closure

                                               i.          Any?

 

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 in Applied state

                                               i.          OData URL Conventions v1.0

1.      ODATA-183: The same navigation property should not be specified in multiple $expands

2.      ODATA-84: Define which system query options should be supported per URL pattern

3.      ODATA-71: Improve addition and subtraction Arithmetic Operators to handle time-related data types

4.      ODATA-13: A function that returns the current date and time is needed

                                              ii.          OData ATOM Format v1.0

1.      ODATA-136: Correct definition of Edm.Time in [ATOM]

                                             iii.          OData CSDL v1.0, OData URL Conventions v1.0

1.      ODATA-14: add Edm.Date to the OData primitive data types

2.      ODATA-11: date/time values without explicit time zones need further investigation

b.      Editorial issues

                                               i.          OData Delta Queries

1.      ODATA-206: Rephrasing of section Delta Links in ODQP proposal page 1/2 [New]

2.      ODATA-207: Rephrasing of section Requesting Delta Links in ODQP proposal page 2 [New]

3.      ODATA-208: Enhancement of "flat heterogeneous" structure definition and reference thereof in section Delta Responses inside ODQP proposal pages 3/4 (and later) [New]

4.      ODATA-209: Replace the term store by service and reduce number of triggerpoints in diagrams in section Client Interaction inside ODQP proposal pages 5/6 [New]

5.      ODATA-210: Declare OData object/concept name for tombstone before its usage in Result Maintenance and ATOM format describing sections inside ODQP proposal pages 6 and later [New]

6.      ODATA-211: Correct the sample inside section "JSON DeltaQuery Result Example" inside ODQP proposal pages 9/10 [New]

c.      Issues in Proposed state (carried over from Jan 10, 2013 TC meeting)

                                               i.          OData CSDL v1.0

1.      ODATA-194: Inside section 4.1.1 The Version Attribute, the version defined by this spec should be 4.0 and not 1.0 for the EDMX wrapper  [New]

                                              ii.          OData ABNF Construction Rules v1.0

1.      ODATA-96: Need to define semantics, serialization format, etc. for Enums [New]

                                             iii.          OData URL Conventions v1.0

1.      ODATA-142: Define URL functions geo.distance, geo.length, geo.intersects, and gettotaloffsetminutes [New]

2.      ODATA-203: Specify Operator Precedence more clearly [New]

                                             iv.          OData ATOM Format v1.0

1.       ODATA-200: Remove metadata:type attribute from example in section 5.1  [New]

2.      ODATA-202: Custom Mapping to Atom Elements not defined  [New]

d.      Issues in Proposed state (carried over from Jan 17, 2013)

                                               i.          OData CSDL v1.0

1.      ODATA-213: Allow all dynamic expressions of the appropriate type within edm:Collection expressions [New]

                                              ii.          OData ATOM Format v1.0, OData JSON Format v1.0, OData Protocol v1.0

1.      ODATA-212: Define request body format for Actions in Atom and JSON format specifications [New]

e.      Issues in Proposed state (since Jan 17, 2013)

                                               i.          OData CSDL v1.0

1.      ODATA-122: Please clarify the meaning of filter functions applied to DateTimeOffset values

2.      ODATA-173: Define Action values for OnDelete element

                                              ii.          OData ABNF Construction Rules v1.0

1.      ODATA-107: Should OData support a "clock time" (xs:time) datatype?

 

6.      Next meeting [8:58am PT]

a.      Jan 30-31, 2013 during 9am – 6pm CET (3^rd F2F meeting)

https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=34020

 

7.      AOB and wrap up [8:59am 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

 

Draft timeline for OData core Work Products:

·        December 2012

o   December 19, 2012

§  File all known issues on core Work Products resulting from new proposals

·        January 2013

o   January 17, 2013

§  File all known issues on core Work Products resulting from extension Work Products

o   3rd F2F meeting January 30–31, 2013 (Zürich, Switzerland) (details: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=34020)

§  Resolve all key issues on core Work Products

§  TC agrees to a high bar for accepting new issues on core Work Products

·        February 2013

o   February 7, 2013

§  Resolve all remaining issues on Core Work Products

§  Agree to advance core Work Products to Committee Specification Draft 01 (CSD01)

o   February 14, 2013

§  Editors to prepare Committee Specification Draft 01 (CSD01) of core Work Products containing resolutions to all issues

o   February 21, 2013

§  Approve Committee Specification Draft 01 (CSD01) of core Work Products and agree to start 30-day public review

·        March 2013

o   March 1 through March 30

§  30-day public review of core Work Products

§  Address public review comments on core Work Products

·        April 2013

o   4th F2F meeting (April 2–4, 2013)

§  Address public review comments on core Work Products

§  NOTE: If there are no public review comments on CSD01 AND no further substantive changes (requested by the TC) to the core Work Products, we can jump ahead to approving Committee Specification (CS)

o   April 18, 2013

§  Address all public review comments on core Work Products

§  Agree to advance core Work Products to Committee Specification Draft 02 (CSD02)

o   Leading up to April 25, 2013

§  Editors to prepare Committee Specification Draft 02 (CSD02) of core Work Products containing resolutions to all issues

o   April 25, 2013

§  Approve Committee Specification Draft 02 (CSD02) of core Work Products and agree to start 15-day public review

·        May 2013

o   May 1 through 15, 2013

§  15-day public review

o   May 23

§  Assuming there are no changes to core Work Products resulting from the preceding public review, approve Committee Specification (CS)

§  NOTE: If there are substantive changes to the core Work Products resulting from the preceding public review, we will need to extend the timeline and produce CSD03 and so on.

·        Early June 2013

o   Approve Candidate OASIS Standard (COS)

·        Mid-June and mid-August 2013

o   60-day public review

·        August 2013

o   OASIS Standard (OS)

 

Draft timeline for OData extension Work Products:

·        November 29, 2012

o   Review and file issues on core Work Products resulting from extension Work Products

·        January 17, 2013

o   File all known issues on core Work Products resulting from extension Work Products

·        February and March 2013

o   Resolve issues on extension Work Products

·        April 2–4, 2013 4th TC F2F meeting

o   Resolve issues and make progress on extension Work Products

·        May 2013

o   Approve Committee Specification Draft 01 of extension Work Products (depending on progress)