OSLC Core Meeting August 28, 2013
Previous meeting
Meeting logistics
Included in Meetings
Agenda / Minutes
Review Minutes from August 14
LDP 1.0 in Last Call, deadline Sept 2nd
Upcoming W3C RDF Validation Workshop
OSLC @ OASIS Updates
- Core TC to be first to transition
- Charter currently being drafted and looking for co-proposers. Let Steve know if you’d like a copy and more details
- Planning to start Core TC in November
TRS 2.0 Spec
OSLC Core V2 Issues - Outstanding issues and proposed updates (review only, no outstanding updates)
Note, no new issues…including previous agenda content to help with viewing
Open Issues
- TRS-6 Lack of needed exception handling: rollback is not clearly defined and needed error-free changlogs is not realistic
Resolved/Closed Issues
V3 Spec Drafting - Specifications
Next meeting:
- Sept 11 - Conflict for Arthur/Steve/Arnaud with W3C RDF Validation WS. Steve will wait until next week to cancel/reschedule/get-alt-chair
- Sept 25 - 3.0 development (Conflict for Steve, JavaOne)
Ed topic on feedback on annotation vocabularies
- Discussed how to mark/tag predicates as holding a “trace” relationship to help with scenarios around suspect links and query building.
- Going with suggestion of non-inferencing approach by just adding a statement like (my-predicate, oslc:isTraceable, true), no gag reflexes heard.
Attendees
Attendees: SteveSpeicher (chair), JohnArwe, PaulSlauenwhite, MichaelFiedler, EdGentry, TuanDang
Regrets: NickCrossley, IanGreen,
Possible Attendees: SteveSpeicher (chair), MichaelFiedler, EdGentry, StevePitschke, DevangParikh, PaulMcMahan, JohnArwe, PaulSlauenwhite, NickCrossley, SamPadgett, SheehanAnderson, SuzetteSamoojh, DonCronin, JimConallen, IanGreen, GrayBachelor, NicholasKruk, DavidHoney, ChristopherLazzaro, SofiaYeung, RainerErsch, AndyBerner, CharlesRankin, MikeLoeffler, ArthurRyman, JulianneBielski, RobertElves, TuanDang
Backlog topics
Open / future topics:
EdGentry suggested topic: Pickers: with preferred or restricted link types, limiting what can be selected or linked to resource type. SteveS suggests submitting the scenario + some details to either RM (or other appropriate WG) or Core to seed the discussion.
NickC suggested topic: need to extend the OSLC pickers (and other areas possibly like query) to allow a [configuration] context to be passed, so the provider can show the versions/variants of the resources in that context, and so the resulting link preserves that context.