[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Agenda for OData TC meeting 2013.01.17
Here [1] is a draft agenda for the OData TC (Technical Committee) meeting
scheduled on Thursday January 17, 2013 during 8-9am PT.
For additional information, such as dial-in details and chat room, refer to [2]. For TC timeline, see [1]. Feel free to suggest additions or modifications.
Thanks. [1] Agenda for 2013.01.17
OData TC meeting
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-190:
Remove primitive type
Edm.Float as a synonym for Edm.Single
ii. OData CSDL v1.0
1.
ODATA-15: precision for functions that have
Edm.DateTime or Edm.DateTimeOffset parameters
2.
ODATA-175: Define
IsAlwaysBindable attribute for FunctionImport element
3.
ODATA-186:
Multiple
navigationpropertybindings for the same navigation property should be prohibited
4.
ODATA-196: Remove sections 15.2.6
FunctionReference and 15.2.12 ParameterReference b.
Issues in Proposed state (carried over from Nov 29, 2012 TC meeting)
i. OData Protocol v1.0
1.
ODATA-166:
Inconsistent lifted operators for $filter
[New]
2.
ODATA-187:
Need to remove references to associations and associationsets from protocol doc
[New]
i. OData ABNF Construction Rules v1.0
1.
ODATA-172:
EntitySet may be qualified with namespace or alias and EntityContainer [Open] e.
Issues in Proposed state (carried over from Jan 10, 2013 TC meeting)
i. OData CSDL v1.0
1.
ODATA-54:
EnumType/@UnderlyingType: allow
Edm.String as underlying type for short code lists that are not numeric. [New]
2.
ODATA-60:
Allow complex properties or components of complex properties as key parts [Open]
3.
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]
4.
ODATA-197:
Define standard functions for edm:Apply element [New]
5.
ODATA-198:
Allow Type="Any" and Type="Collection(Any)" for
NavigationProperty elements [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,
OData JSON Format v1.0
1.
ODATA-199:
$expand should be allowed to return only ids for already seen objects [New]
v. 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]
9.
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 Here is a rough draft of a timeline for the OData core specifications: ·
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 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) |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]