OData day 2 minutes

[Diane Jordan <drj@us.ibm.com>]

Apologies for the delay in posting minutes
from day 2 .  Details of discussions can be found in the chat transcript.
   

Meeting resumed July 27 9am. 
Transcript of chatroom for day: 
First agenda item:  Review OData
extension for XML.  Andrew presents:   
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/46561/OData%20Extension%20for%20XML%20Data%20v1.0.doc

Next agenda item: OData extension
for JSON.  Susan presents 
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/46574/2012-07-27.OData.JSON.Extensions.slides.v02.pdf

TC agreed to agenda adjustment
to allow further discussion on JSON and more time for temporal.

During discussion of JSON, request
made to include examples and use cases for extensions.  
ACTION (Susan and Mark):
Come up with examples / usecases (and proposals) for open types and document
annotation for JSON extensions document.

Next agenda item: OData extension
for Temporal data: Andrew presents https://www.oasis-open.org/apps/org/workgroup/odata/download.php/46565/20120727%20OData%20Extension%20for%20Temploral%20Data.pdf

Next agenda item:  Workplan
and timeline 
Ram discusses slide with projection
based on OASIS TC process as a starting point discussion and agreement
by TC: 
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/46553/TC%20timeline.htm

Discussion about achieving balance
between addressing all requirements, refining the specification versus
moving quickly.  Point made that stable standards are important and
iterating on versions causes problems with dependencies and migration/upgrades.
 

TC discussed potential milestones:
getting issues into jira, produce working draft - then committee spec draft
- then public review - changes, then another public review - then get to
committee specification - at that point should be feature complete, no
more work required
Ram reviewed the approval process
to go from committee specification to OASIS standard. This will require
statements of use from 3 implementations.  TC members will be expected
to help obtain them although 2 of the 3 can be made by non-OASIS members
according to a new process change. 

Ram asked OASIS board members
the reason OASIS required 60 day public review for OASIS standard.  Jim
Huges (MSFT OASIS board representative) explained it has to do with requirements
in international organizations based on WTO agreement on technical barriers
to trade. Path from OASIS Standard to ISO discussed.  

Discussion on how much work
will be required for Core specifications. The V3 specifications are fairly
new documents - while OData has been worked on for a while, these versions
are new and untested.  Errors should be expected and will take time
to find but will probably not be hard to fix, mostly editorial. This process
could take 2 months depending on the time each member can contribute to
do review. 

Then, there is a list of more
substantive changes: issues in current specs and new features.  We
can take an incremental approach, work through versions of the working
draft.  We need to get solid, consistent spec that satisfies a number
of use cases, is internally consistent, can be implemented, and accommodates
things that will be needed for extensions, and future capabilities.. We
need to identify the things in extensions that will cause changes to the
core spec as early as possible.

The extension specs are not
in same level of maturity as the core - it will take longer to get them
to level and then start working on issues that may have impact on core
- may not be possible to get to that point by Dec. 
 
For the core, the V3 spec was
written with the OASIS template in mind.  It should take a few weeks,
not months to put into into the template.   

Suggestion - target a date to
get all known issues on the core specs written down so can tell how much
work there is. Then package them into working sprints - each sprint represents
a working draft version.  After 2 or 3 review status and set a plan
for the CSD.

Consensus to aim for end
of August to get all know issues into jira, target 2 weeks to prioritize
the issues into batches for inclusion into working drafts.  Target
for that will be Sept. 15.

For extension specs, the first
milestone will be to get the initial draft spec. Working meetings around
official tc meetings can be scheduled to facilitate collaboration.  Interim
reviews of extension content with TC may be worthwhile. Issues will not
be opened in jira until first drafts are available. 
ACTION: extension spec editors
to provide target date for initial specs   
  
Also target end of August
to get core specs into the OASIS templates. 

New topic: Attendance on TC
web page not updated correctly.  Barbara fixes by end of meeting.


Next agenda topic:  Known
issues.  Mike presents  
<add link > 
 
Next agenda topic: Association
simplification.  Mike presents: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/46626/OData%20known%20issues%207-26-2012.docx


Next agenda topic:  Deltas
extension. Mike presents.https://www.oasis-open.org/apps/org/workgroup/odata/download.php/46575/OData%20Deltas.pptx
 
Ram calls for any other business.
 None.

Ram points out attendance on
web site has been updated - anyone who feels their status is wrong should
let Barbara know
Ram summarizes - talked about issues, work plan - going forward think about
dates - also actions coming out of meeting - request to make sure each
member is on top of deliverables
Next meeting is aug 9 - agenda will be ready a few days in advance
Lets keep the momentum going
- this was a good start.   

Regards, Diane
Program Director, IBM Emerging Software Standards
(919)254-7221 or 8-444-7221, Mobile: 919-624-5123, Fax 845-491-5709
drj@us.ibm.com

Attachment: OData TC Chat transcript July 27.doc
Description: Binary data