← Prev in month
← Prev in thread
Next in thread →
Next in month →
Agenda for OData TC meeting 2012.10.25
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 Roll call [8:00am PT] Approve agenda [8:05am PT] Approve minutes from previous meeting(s) [8:10am PT] 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 Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT] Action items due by Oct 18, 2012 None Action items NOT due by Oct 18, 2012 but MAY be ready for closure Any? Timeline and next steps [8:20am PT] October 20th, 2012: TC completes end-to-end review of the core specifications and files any remaining issues. Any Comments? Is the review completed? Process issues [Issues list: https://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10103] [8:25am PT] Applied resolutions OData ABNF Construction Rules v1.0 ODATA-137: Normalize percent-encoded values in URIs before applying ABNF rules ODATA-128: Restrict scheme in OData URIs to http and https OData CSDL v1.0 ODATA-125: XML schema for Edmx wrapper constructs edmx:Edmx and edmx:DataServices OData Protocol v1.0 ODATA-131: Canonical URL for media resources OData URL Conventions v1.0 ODATA-141: Update non-normative ABNF snippets in prose document to match normative ABNF ODATA-130: Describe canonical $metadata and $batch URLs in URL conventions Issues in New and Proposed state OData ABNF Construction Rules v1.0 ODATA-155: Allow functions to take properties as parameters when used in system query options OData ATOM Format v1.0 ODATA-149: Self-link for related and inlined feeds OData CSDL v1-0 ODATA-138: Remove section 12 Model Functions ODATA-154: Specify whether <Record> constructs must provide a <PropertyValue> child element for each declared property of the record type OData JSON Format v1.0 ODATA-91: 2.1: explicitly state which format the server will return in response to each given set of headers OData Protocol v1.0 ODATA-132: Support /$count in $select, $filter and $orderby ODATA-36: Make $expand implicit if navigation properties are mentioned in $select or $aggregate ODATA-129: Explicitly mention dynamic navigation properties in [Core] ODATA-143: Define processing order for system query options ODATA-145: Section 8.2 Define X-HTTP-Method request header ODATA-148: 10.3.5: Allow PUT for changing to-one or to-zero-or-one relationships between entities ODATA-150: Add section 9.2.2 describing behavior if HTTP method is not allowed (HTTP 405) ODATA-151: 8.2.5 If-None-Match: describe reaction to If-None-Match header in read requests ODATA URL Conventions v1.0 ODATA-144: "Scoping" syntax for $select and $aggregate Next meeting [8:57am PT] Thursday November 1, 2012 8-9am PT? 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 2nd 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.
← Prev in month
← Prev in thread
Next in thread →
Next in month →