Draft timeline for OData core Work Products:

·        July 2012 through November 2012

o   July 26-27, 2012 1st F2F meeting (Redmond, WA) and TC launch

o   Make progress on issues

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

o   Make progress on issues

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

§  Resolve all key issues on core Work Products

§  TC agrees to setting a higher bar for accepting new issues on core Work Products

·        February 2013

o   Starting Feb 7, 2013

§  Higher bar in effect for accepting issues on core Work Products. The TC will only accept class A, class B, and class C issues for processing on OData v4.0 core Work Products; class D issues will be deferred to a future revision (such as or v4.1 or v5.0). Classification of issues:

*     Class A: Purely editorial corrections

*     Class B: Something is broken (due to an existing flaw or due to a missing feature): Major/minor technical flaws or interoperability problems

*     Class C: Nothing is broken but need this for a “real good” reason (for example, this could not be deferred to a future revision): Major/minor technical changes

*     Class D: Nothing is broken but nice to have: Major/minor technical changes

o   Make progress on remaining issues on Core Work Products

·        March 2013

o   March 14, 2013

§  Aim to resolve all remaining issues on Core Work Products

·        April 2013

o   April 4, 2013

§  Resolve all remaining issues on Core Work Products

o   April 11, 2013

§  Detailed specification reviews during extended TC meeting

o   April 18, 2013

§  Detailed specification reviews during extended TC meeting

o   April 22, 2013

§  Editors to post candidate Committee Specification Draft 01 (CSD01) of core Work Products containing resolutions to all issues

o   4th F2F meeting April 25-26, 2013 (Walldorf, Germany)

§  Approve Committee Specification Draft 01 (CSD01) of core Work Products and agree to start 30-day public review

§  Continue work on extension Work Products

·        May 2013

o   May 1 through May 30

§  30-day public review of core Work Products

§  Address public review comments on core Work Products

·        June 2013

o   June 18, 2013

§  Address all public review comments on core Work Products

§  If are no substantive changes to the core Work Products resulting from the preceding public review, we can jump ahead to approving Committee Specification (CS)

§  If there are substantive changes to the core Work Products, agree to advance the core Work Products to Committee Specification Draft 02 (CSD02)

o   Leading up to June 25, 2013

§  Editors to prepare candidate Committee Specification Draft 02 (CSD02) of core Work Products containing resolutions to all issues

o   June 25, 2013

§  Approve Committee Specification Draft 02 (CSD02) of core Work Products and agree to start 15-day public review

·        July 2013

o   July 1 through 15, 2013

§  15-day public review

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

o   Three Statements of Use referencing the approved Committee Specification (CS)

§  Statement of Use is a written statement that a party has successfully used or implemented that specification in accordance with all or some of its conformance clauses, identifying those clauses that apply, and stating whether its use included the interoperation of multiple independent implementations. Note, this is a required step in order to advance to Candidate OASIS Standard.

§  If the use involves interoperation of multiple implementations, the TC may consider hosting a public interoperability demonstration (per the OASIS Interoperability Demonstration Policy) since this is a required step (per the OASIS Liaison Policy) in order to advance the Work Products to an International Standard. Note, public interoperability demonstration is NOT required for the production of the OASIS Standard; this is required ONLY if and when we want to advance the Work Products to an International Standard and thus could be done either before or after the production of the OASIS Standard. The reason for considering doing the public interoperability demonstration as part of the Statement of Use work item is to avoid duplication of interoperation demonstration efforts (once for the OASIS Standard and once again for the International Standard).

·        Early August 2013

o   Approve Candidate OASIS Standard (COS)

·        Mid-August and mid-October 2013

o   60-day public review

·        October 2013

o   OASIS Standard (OS)

 

Draft timeline for OData 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

·        4th F2F meeting April 25-26, 2013 (Walldorf, Germany)

o   Continue work on extension Work Products

·        May 2013

o   Approve Committee Specification Draft 01 of extension Work Products (depending on progress)