Agenda for OData TC meeting 2012.12.06

["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 December 6, 2012 during 8-9am PT. For additional information, such as dial-in details and chat room, refer to [2]. Feel free to suggest additions or modifications.

 

Thanks.

 

[1] Agenda for 2012.12.06 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]
   1. Minutes from November 29, 2012 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/47595/odata-meeting-16_on-20121129-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]
   1. Action items due by Dec 6, 2012

                                                    i.     None

2. Action items NOT due by Dec 6, 2012 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 ABNF Construction Rules v1.0

1.      ODATA-80: Add ABNF rules for action parameters in request bodies

2.      ODATA-67 : Describe representation of ReferenceTypes in requests

                                                   ii.     OData ATOM Format v1.0

1.      ODATA-149 : Self-link for related and inlined feeds

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

3.      ODATA-135: Instance Annotations in Atom should use metadata:Annotation element

                                                  iii.     OData ATOM Format v1.0, OData CSDL v1.0

1.      ODATA-133: Attributes defined on odata elements should be in empty namespace

                                                  iv.     OData CSDL v1.0

1.      ODATA-191: Create subsections for attributes consistently as appropriate throughout [CSDL] document

2.      ODATA-185: Nullable attribute should be required to be false for collection valued navigation properties.

3.      ODATA-184: Relationships in CSDL examples should include Partner attribute

4.      ODATA-138: Remove sections 12 Model Functions and 10.4 Row Types including the subsections

                                                   v.     OData URL Conventions v1.0

1.      ODATA-174: Core Part 2: 1 Introduction, 1.1 Terminology, 1.2 Normative References and 3 ServiceRootURL somehow mixed up in view "final version"

2.      ODATA-26: Feedback to document revision

b.      Issues in Open and Proposed state

                                                    i.     OData CSDL v1.0

1.      ODATA-112: DateTime[Offset]: allow 24:00[:00] in time part [motion pending]

c.      Issues in New and Proposed state (carried over from Nov 29, 2012 TC meeting)

                                                    i.     OData ABNF Construction Rules v1.0

1.      ODATA-139: New system query option $search for free-text search within an entity set

2.      ODATA-172: EntitySet may be qualified with namespace or alias and EntityContainer

                                                   ii.     OData ATOM Format v1.0 and/or OData JSON Format v1.0

1.      ODATA-158: OData ATOM format should require <category> element    

2.      ODATA-162: Define OASIS XML namespaces for data: and metadata: in Atom payloads

3.      ODATA-169: Representation of named entities in the service document

                                                  iii.     OData CSDL v1.0

1.      ODATA-104: Consider supporting nullable complex typed properties

2.      ODATA-123: Referential constraint: prose text does not properly reflect case of optional principal

3.      ODATA-15: precision for functions that have Edm.DateTime or Edm.DateTimeOffset parameters

4.      ODATA-121: Please clarify whether agents handling DateTimeOffset must preserve the UTC offset

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

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

7.      ODATA-173: Remove OnDelete element

8.      ODATA-175: Define IsAlwaysBindable attribute for FunctionImport element

                                                  iv.     OData Protocol v1.0

1.      ODATA-157: Specify how client correlates requests within a changeset with responses

2.      ODATA-111: Define supported numeric promotions

3.      ODATA-3: Use CQL standard for query instead of odata-specific filter query protocol

4.      ODATA-177: Allow entities to be members of multiple entity sets

                                                   v.     OData URL Conventions v1.0

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

2.      ODATA-140: Describe rules for accessing derived entity and complex types in URLs

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

4.      ODATA-72: Describe any() and all() lambda filter expressions

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

d.      Issues in New and Proposed state (since previous TC meeting)

                                                    i.     OData ABNF Construction Rules v1.0

1.      ODATA-190: Remove primitive type Edm.Float as a synonym for Edm.Single

                                                   ii.     OData CSDL v1.0

1.      ODATA-180: Remove Extends attribute from EntityContainer element

2.      ODATA-181: Referencing/reusing a model element from a different schema does not require to "include" this schema via a Using element

3.      ODATA-189: Remove NavigationPropertyBinding

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

5.      ODATA-186: Multiple navigationpropertybindings for the same navigation property should be prohibited

6.      ODATA-193: Allow function imports to return entities from a different service

7.      ODATA-195: Simplify entity set qualification rules for NavigationPropertyBinding

8.      ODATA-188: Use <Property> element also for NavigationProperty

9.      ODATA-196: Remove section 15.2.6 FunctionReference

                                                  iii.     OData Protocol v1.0

1.      ODATA-166: Inconsistent lifted operators for $filter

2.      ODATA-187: Need to remove references to associations and associationsets from protocol doc

 

6.      Timeline [8:50am PT]

a.      Let’s assess progress on the planned activities during November and December 2012. And also briefly discuss the planned activities during Jan and Feb 2013. See timeline [3] for more details.

 

7.      Next meeting [8:55am PT]

1. Dec 13, 2012 during 8-9am PT.
2. TC meetings on Dec 20^th, Dec 27, and Jan 3^rd?
3. Next face-to-face meeting confirmed during Jan 30/31, Zürich, Switzerland.

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

 

Here is a rough draft of a timeline for the OData core specifications:

·        November 2012

o   Leading up to Nov 29

§  Editors to incorporate all issue resolutions and produce new revisions of core Work Products

§  Review and file issues on core Work Products resulting from new proposals

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

o   Nov 29 TC meeting

§  Continue to make progress on issues

·        December 2012

o   Continue to make progress on issues

o   December 19, 2012

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

·        January 2013

o   January 17, 2012

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

§  Continue to resolve issues

§  3rd F2F meeting January 30–31, 2013 (Zürich, Sitzerland) (details TBD)

·        Resolve all key issues on core Work Products

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

o   Continue to resolve issues

·        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

o   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 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)