Agenda for OData TC meeting 2012.11.29

["Hartel, Barbara" <barbara.hartel@sap.com>]

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday November 29, 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. Because of the holiday period last week please let me know if you need more time to review a specific issue and if we should defer an issue to the meeting next week.

 

Thanks.

 

[1] Agenda for 2012.11.29 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 8/9, 2012 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/47432/odata-meeting-15_on-20121108_9-F2F-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 Nov 27, 2012

                                                               i.      #0026: Detail a proposal with regard to enumerations (Michael Pizzo)

                                                             ii.      #0003: Come up with examples / usecases (and proposals) for open types and document annotation for JSON extensions document (Susan Malaika)

2. Actions items deferred at the F2F but without new due date. Can we discuss a date when we want to get an update on these?

                                                               i.      #0005: Come up with a first milestone for the temporal extension (Andrew Eisenberg)

                                                             ii.      #006: Come up with estimate for first milestone for XML data extension (Andrew Eisenberg)

                                                            iii.      #007: Come up with estimate for first milestone for JSON data extension (Susan Malaika)

 

3. Action items NOT due by Nov 1, 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:25am PT]

a.       Issues in Applied state

                                                               i.      OData ABNF Construction Rules v1.0

1.       ODATA-127: Whitespace in URLs must be percent-encoded

2.       ODATA-117: Case-sensitivity of system query options

3.       ODATA-77: Are Edm primitive type names case-insensitive?

                                                             ii.      OData CSDL v1.0

1.       ODATA-167: 1.1 Terminology and 1.2 Normative References somehow mixed up in view "final version"

2.       ODATA-154: <Record> constructs must provide a <PropertyValue> child element for each non-nullable property of the record type

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

4.       ODATA-134: Multiplicity of FunctionImport ReturnType element

5.       ODATA-119: Allow definition of "simple" types that fix values for facet attributes of primitive types

6.       ODATA-118: XSD references Microsoft namespaces edm/annotation and codegeneration

7.       ODATA-62: Specify uniqueness of Association names within a Schema

8.       ODATA-61: Allow complex properties or components of complex properties as parts of a referential constraint

9.       ODATA-57: Remove xs:any and xs:anyAttribute from Informative XSD

10.   ODATA-52: Section 3.5 Primitive Types list the primitive types, but doesn't define their meaning

11.   ODATA-24: Simplify how Relationships are expressed in CSDL

                                                            iii.      OData Extension for Data Aggregation v1.0

1.       ODATA-161: Clarify and if possible add directions for 'stranded' readers in the ending note of section 1 Introduction

2.        ODATA-160: Repair Copy and Paste error in 1.1 Terminology i.e. delete the reference entry to OData-CSDL there

                                                           iv.      OData Protocol v1.0

1.       ODATA-176: Re-Order Ref-Entries in Section 1.2 Normative References  

2.       ODATA-171: Enhance facility listing for editing in Overview

3.       ODATA-170: Core Part 1: 1.1 Terminology and 1.2 Normative References somehow mixed up in view "final version"

4.       ODATA-163: Clarify, in OData Protocol, that $skip and $top are not allowed to be appended to a next link

5.       ODATA-156: Describe behavior when accessing related entities

6.       ODATA-151: 8.2.5 If-None-Match: describe reaction to If-None-Match header in read requests

7.       ODATA-150: Add section 9.2.2 describing behavior if HTTP method is not allowed (HTTP 405)

8.       ODATA-148: 10.3.5: Allow PUT for changing to-one or to-zero-or-one relationships between entities

9.       ODATA-145: X-HTTP-Method request header

10.   ODATA-143: Define processing order for system query options

11.   ODATA-97: 10.4.2.4 Action Overload Resolution: resolution is done by binding parameter type

12.   ODATA-79: PATCH for properties of complex properties

13.   ODATA-41: Specify which URL formats are acceptable within $batch, and which to prefer

                                                             v.      OData URL Conventions v1.0

1.       ODATA-38: Recursive $expand and $select

2.       ODATA-32: Allow filtering of expanded to-many navigation properties

3.       ODATA-26: Feedback to document

 

b.      Issues in Open and Proposed state

                                                               i.      OData CSDL v1.0

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

 

c.       Issues in New and Proposed state

                                                               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

 

6.       Next meeting [8:50am PT]

1. Dec  6, during 8-9am PT.
2. Next face-to-face meeting Jan 30/31, Zürich, Switzerland.
   
   

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