OSLC Core Meeting June 13, 2012

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

Review Minutes from May 30

Update on new WGs

OSLC Steering Committee kickoff & governance changes

OslcCoreV2Issues - Outstanding issues and proposed updates OslcCoreV2Issues - Issue-43 - Read-only and friends (Arwe)

• Comeback on some proposals: A series of proposals

• NEW ISSUE - the usage of QName in this context is not valid. It should really state that we use hash URIs and this is the fragment segment of the URI. Need to promote/clarify OSLCCoreURINamingGuidance
• 43-5 : text suggestions made, JohnArwe to produce new recommendation...will follow up on mailing list and at next WG meeting
• 43-8+9 : text still needs some work.. will follow up on mailing list and at next WG meeting

V3 Spec Outline Draft for review - OslcCoreV3Plan

• Updates PATCH support
• Update on reification of labels alternatives -- looking at using named graphs
• Use cases and requirements for vocabulary definitions going forward, see thread on declaring valueType

Next meeting:

• June 27 - outstanding 2.0 issues and 3.0 progress

Minutes

Reviewed minutes from May 30

OSLC Steering Committee and governance updates

• Meeting occurred on June 3rd, overall good meeting
• New members agreement available, can sign but not required yet. Workgroup participants agreement coming.
• Still working out WPA and plan to launch near/late June.

OslcCoreV2Issues - Issue-43 - Read-only and friends (Arwe)

• Consensus on top-level issue - resource description tables in specs are SHOULDs, in other words implementations MAY contradict the table. SteveSpeicher to send note out to WG
• Reviewed sub-issues and need additional updates -- JohnArwe to provide comeback.

Update on reification of labels alternatives -- looking at using named graphs

• Most agree that named graphs are NOT the right solution
• ACTION to all to provide thoughts/feedback offline

Proposal included for updating link labels, all to review PATCH support

Attendees

SteveSpeicher (chair), JimConallen, SamPadgett, PaulSlauenwhite, SheehanAnderson, NickCrossley, JohnArwe, ArthurRyman, JulianneBielski

Possible attendees: SteveSpeicher (chair), MichaelFiedler, DevangParikh, PaulMcMahan, JohnArwe, PaulSlauenwhite, NickCrossley, SamPadgett, SheehanAnderson, SuzetteSamoojh? , DonCronin? , JimConallen, IanGreen, GrayBachelor, NicholisKruk? , DavidHoney, ChrisLazzaro? , SofiaYeung, RainerErsch, AndyBerner, CharlesRankin, MikeLoeffler, ArthurRyman, JulianneBielski