OSLC Core Meeting April 28, 2010

Meeting logistics

See the OslcCoreMeetings for telecon number, passcode and online meeting info.

Agenda

What I would like to cover today is status, discussion of the two open issues and a proposal for two more long review sessions.

Status - Item #1 - We've whittled down the list of open issues to just this short list:

• Question: Do we really need both OSLC Core and OSLC Domain version strings?
• Question: Do we really need two query response formats?
• Task: Ensure that we are including the right common properties
• Task: Add common property oslc:instanceShape (Resource, zero-or-many)
• Task: complete Atom representation examples
• Task: complete Query examples (assuming we need two formats)

Status - Item #2 - We almost finished a review of the UI Preview spec. Where are we on this now?

• http://open-services.net/bin/view/Main/OslcCoreUiPreview

Discussion: consider those two questions above, can we close either issue today?

Next Steps - Item #1 - Plan is to review Guidance on Partial Update next week. First draft will be ready Friday.

Next Steps - Item #2 - It's time to review the RESOLVED items so that we can mark them CLOSED. I believe that we'll need two more sessions and I would like to proposed these possible times:

• 9:30AM ET to 11:30AM Thursday Apr 29
• 9:30AM ET to 11:30AM Friday Apr 30
• 9:30AM ET to 11:30AM Monday May 3
• 9:30AM ET to 11:30AM Tuesday May 4

Meeting Minutes

Possible Attendees

• DaveJohnson - X
• JimConallen - X
• ArthurRyman - X
• ScottBosworth
• SteveSpeicher - X
• PaulMcMahan - X
• NickCrossley - X
• TackTong - X

Discussed need for both OSLC Core and OSLC Domain version string

Nick C - OSLC Core version string is needed for writing a truly generic client

Scott B - need to establish use cases before allowing two version strings, need to thoroughly understand this issue

Scott B - need versioning story for versioned services not just versioned

Dave J - need to reconcile the various places that we use version strings

• one version string or two
• need for version number in namespace
• need for version string for each resource

Dave J - we will work on use cases and have a meeting to review and resolve this issue

Discussed need for both single-subject and multi-subject query

Arthur R - we can live without mutli-subject query

Dave J - I don't full understand the implications of this, we should talk offline