OSLC Core Meeting February 8, 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 Jan 11 (no meeting Jan 25th).

New Workgroup Proposal for "Performance Monitoring" - DonCronin?

W3C Community Group trial proposed and CM first to trial - SteveSpeicher

Discussion on OSLC acronym, no action to take - SteveSpeicher

Review update to link label spec text in CM spec, as coordinated by Core - SteveSpeicher

OSLC Vocabulary and Guidance update - SteveSpeicher

OslcCoreSpecificationV2ImplGuidance - reminder to update

OslcCoreV2Issues - Outstanding issues and proposed updates

• OSLC Core Resource Shape Namespace defect - fixed, FYI only

Discussion about requirements for specification authoring - OslcCoreV3Plan

2012 meetings:

• Feb 22 - 3.0 progress

Minutes

Review Minutes from Jan 11 (no meeting Jan 25th).

New Workgroup Proposal for "Performance Monitoring" - DonCronin?

• Consensus on the creation, no objections on mailing list or in meeting.

W3C Community Group trial proposed and CM first to trial - SteveSpeicher

• FYI only

Discussion on OSLC acronym, no action to take - SteveSpeicher

• FYI only

Review update to link label spec text in CM spec, as coordinated by Core - SteveSpeicher

• JimConnallen? - Consider giviing guidance on what could be done of when the label is updated and when. Question on whether etag should be updated
• Consider adding some of the usage of the link label to the impl guidance
• ACTION: Update link guidance on link labels and consider providing a common/core statement instead of within each domain spec
• JohnArwe: Reification - no normative status in current RDF, according to some. Proposing to use name graphs, need to research.
  • ACTION: follow up on reification being on the chopping block

OSLC Vocabulary and Guidance update - SteveSpeicher

• Some minor updates, provide suggestions to list as needed

OslcCoreSpecificationV2ImplGuidance - reminder to update

• ACTION: Consider adding link label guidance

OslcCoreV2Issues - Outstanding issues and proposed updates

• OSLC Core Resource Shape Namespace defect - fixed, FYI only
• JohnArwe's agreement with the change

Discussion about requirements for specification authoring - OslcCoreV3Plan

2012 meetings:

• Feb 22 - 3.0 progress +
  • MichaelFiedler - look at conformance table for improvements
  • SteveSpeicher - spec outline in new form

Possible future topics:

• PaulMcMahan - would like to have more clarity on what is really supported for query - what does MUST really mean? Like which properties are queryable? how can a client learn what is supported?
• JohnArwe - dcterms:title vs. rdfs:label, which one? or both? if so why?

Attendees

SteveSpeicher (chair), PaulMcMahan, MichaelFiedler, SheehanAnderson, DonCronin? , DevangParikh, JimConallen, JohnArwe, BobSchloss?

Regrets: NickCrossley, PaulSlauenwhite

Invited: ArthurRyman, MikeLoeffler, GrayBachelor, NicholisKruk? , DavidHoney, ChrisLazzaro? , SofiaYeung, RainerErsch, AndyBerner, CharlesRankin, IanGreen