OSLC Core Meeting September 21, 2011

Previous meeting

Link to OSLC Core spec: OslcCoreSpecification

Meeting logistics

How to dial-in to our telecon and login to our screen-sharing session.

Telecon Info

USA Toll-Free: 888-426-6840 USA Caller Paid: 215-861-6239 Participant Code: 3292849

Other numbers: https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=3292849&accessNumber=2158616239

Online meeting

For IBM employees, use the following link: http://w3.ibm.com/collaboration/meeting/join/?schedid=4440645 (IBM intranet authentication required)

For people outside IBM, use the following link: http://www.ibm.com/collaboration/meeting/join?id=4440645

Agenda

Call for additional agenda items

Workgroup news

• Automation WG looking to revive kickoff meeting is Sept 22nd 10 AM ET, contact CharlesRankin if interested
• Communications WG to kicked off on Sept 15th, contact AndyGurd if interested

2.0 Issues (still open)

• follow up with use of Core namespace URI in oslc:domain
• encoding of UI preview labels (still ongoing)
• json representation ambiguities (review proposal)
• RM vocab extension direction
• awkward statement in Core on pre-filling creation dialogs (proposal)
• oslc v2.0 spec - observed issue with oslc:shorttitle description

3.0 content and priorities discussion

• OslcCoreV3Plan

Upcoming meetings:

• Oct 5 - (tentative) PLM extensions discussion NOTE moved time to 12 PM Eastern (one time only)
• Oct 19 - Core 2.0 issues, Core 3.0 progress (note conflict with lead)
• Nov 2 - Core 2.0 issues, Core 3.0 progress (note conflict with lead)

Minutes

Workgroup news

• Automation WG looking to revive kickoff meeting is Sept 22nd 10 AM ET, contact CharlesRankin if interested
• Communications WG to kicked off on Sept 15th, contact AndyGurd if interested

2.0 Issues (still open)

• follow up with use of Core namespace URI in oslc:domain
  • consensus: recommend to relax the definition of this property to: a) allow other domains to define domains and b) define new domain URI for that purpose
• encoding of UI preview labels (still ongoing)
  • agreed on current spec (clarify intent and fix example) and a reminder the UI Preview is an XML format (not RDF/XML)
• json representation ambiguities (review proposal)
  • MichaelFiedler summarized issues to 4 issues and proposed 4 resolution in email
  • Concern that a null value property and non-existent property, need to further elaborate on this scenarios
  • PaulMcMahan articulated some scenarios needed for PATCH / partial-update such that only certain licensed users can update a limited set of properties, so PUT semantics fail
  • JohnArwe agrees with this approach
• RM vocab extension direction
  • ACTION: need guidance on handling inverse links (both from resource definition guidance and where it is actually stored in implementations)
  • ACTION: need for guidance on when correcting "minor" updates based on fixing link updates
  • Consensus: no issue of change in errata since: a) doesn't break implementations b) within current scope of RM 2.0 spec definition (or clarification). Core to review errata.
  • ACTION: sets precedence need to consider implications on how this affects downstream changes
• awkward statement in Core on pre-filling creation dialogs (proposal)
  • Consensus with proposal

• oslc v2.0 spec - observed issue with oslc:shorttitle description
• (from maillist) discussion of shapes associated with queryShape

Upcoming meetings:

• Oct 5 - (tentative) PLM extensions discussion NOTE moved time to 12 PM Eastern (one time only)
• Oct 19 - Core 2.0 issues, Core 3.0 progress (note conflict with lead)
• Nov 2 - Core 2.0 issues, Core 3.0 progress (note conflict with lead)

Attendees

SteveSpeicher (chair), SheehanAnderson, PaulMcMahan, PaulSlauenwhite, MichaelFiedler, JohnArwe, NickCrossley, ArthurRyman, MikeLoeffler

Regrets: JimConallen, AndyBerner, CharlesRankin