Agenda for OData TC meeting 2012.10.25

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

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday October 25, 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.10.25 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 October 11, 2012 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/47230/odata_meeting-12_on-20121018-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]

2. Action items due by Oct 18, 2012

1. None

3. Action items NOT due by Oct 18, 2012 but MAY be ready for closure

2. Any?

5. Timeline and next steps [8:20am PT]

4. October 20^th, 2012: TC completes end-to-end review of the core specifications and files any remaining issues. Any Comments? Is the review completed?

 

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

5. Applied resolutions

3. OData ABNF Construction Rules v1.0

1. ODATA-137: Normalize percent-encoded values in URIs before applying ABNF rules
2. ODATA-128: Restrict scheme in OData URIs to http and https

4. OData CSDL v1.0

3. ODATA-125:  XML schema for Edmx wrapper constructs edmx:Edmx and edmx:DataServices

5. OData Protocol v1.0

4. ODATA-131: Canonical URL for media resources

6. OData URL Conventions v1.0

5. ODATA-141: Update non-normative ABNF snippets in prose document to match normative ABNF
6. ODATA-130: Describe canonical $metadata and $batch URLs in URL conventions

6. Issues in New and Proposed state

7. OData ABNF Construction Rules v1.0

7. ODATA-155: Allow functions to take properties as parameters when used in system query options

8. OData ATOM Format v1.0

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

9. OData CSDL v1-0

9. ODATA-138: Remove section 12 Model Functions
10. ODATA-154: Specify whether <Record> constructs must provide a <PropertyValue> child element for each declared property of the record type

1. OData JSON Format v1.0

1. ODATA-91: 2.1: explicitly state which format the server will return in response to each given set of headers

2. OData Protocol v1.0

2. ODATA-132: Support /$count in $select, $filter and $orderby
3. ODATA-36: Make $expand implicit if navigation properties are mentioned in $select or $aggregate
4. ODATA-129: Explicitly mention dynamic navigation properties in [Core]
5. ODATA-143: Define processing order for system query options
6. ODATA-145: Section 8.2 Define X-HTTP-Method request header
7. ODATA-148: 10.3.5: Allow PUT for changing to-one or to-zero-or-one relationships between entities
8. ODATA-150: Add section 9.2.2 describing behavior if HTTP method is not allowed (HTTP 405)
9. ODATA-151: 8.2.5 If-None-Match: describe reaction to If-None-Match header in read requests

3. ODATA URL Conventions v1.0

10. ODATA-144: "Scoping" syntax for $select and $aggregate

 

7. Next meeting [8:57am PT]

1. Thursday November 1, 2012 8-9am PT?

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:

• October 20, 2012

• TC completes end-to-end review of the core specifications and files any remaining issues

• Nov 8-9, 2012 2^nd F2F meeting (Littleton, MA)

• Discuss proposals and resolve issues

• Committee Specification Draft 01
• 30-day public review
• Committee Specification Draft 02
• 15-day public review
• Committee Specification
• Candidate OASIS Standard
• 60-day public review
• OASIS Standard

 

The timeline for the OData extension specifications is TBD.