OSLC Core Meeting April 10, 2013
Previous meeting
Meeting logistics
Included in Meetings
Agenda
Review Minutes from March 13
Reconciliation is requesting to go final
TRS is requesting to transition to finalize
PerfMon is requesting to go final
Specification development transition to OASIS update
OSLC Core V2 Issues - Outstanding issues and proposed updates
- No new issues
- Issue 42
- Call to WG members to close out any issues that appear to be “OPEN”. Think some are complete but paperwork (updating wiki page of issues) hasn’t been completed.
V3 Spec Drafting - OSLCCoreSpecificationsV3
Updates PATCH support - looking at named graph syntax to support model
- Approach has been presented to the W3C LDP workgroup. Working through the feedback
Use cases and requirements for vocabulary definitions going forward and a proposal
Delegated resource editors:
- Steve recommends Ed send out a oslc-core email to help define the scenario and outline requirements for the solution.
Next meeting:
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.
Minutes
Reviewed Minutes from March 13
Reconciliation is requesting to go final
- Core supports this going to final, no objections
TRS is requesting to transition to finalize
- Core supports transitioning to finalizing
- Criteria for finalization: 2 consumer impl (with report) and 2 provider impls (with report) + test suite for providers
PerfMon is requesting to go final
- Need to list additional implementations, only have 1 provider but are at least 3 consumers that are known of
- Need to list test suite (and also work to merge in contribution)
Update text in beginning of document to remove ‘red’ text warning about version numbering to match that of Recon spec
Moving forward with ems:Metrics finalization as well Arthur to update wiki page to clarify the text and to put links into the vocabulary terms
- Use vs:term_status with values from the note. Need to provide guidance on status values and how they map to OSLC ones. Agreed to this mapping:
- ‘unstable’ - anything before convergence
- ‘testing’ - in convergence
- ‘stable’ - finalizing or final
- ‘archaic’ - deprecated
Specification development transition to OASIS update
- Moving along with good chance of OASIS board approval for member section creation on May 1st.
- Core WG will be first TC(WG) to move, proposed timeframe September
- Domain WGs will move after that and on a timeframe that makes sense for spec maturity and WG feedback
OSLC Core V2 Issues - Outstanding issues and proposed updates
- Issue 42
- Need to update proposal with removing error case instead should just return nothing. MikeF to update and redistribute
- Reminder to WG members need to close on issues, including updating status wiki
V3 Spec Drafting - OSLCCoreSpecificationsV3
- General overview of owners and direction, need contributors to step up
Next meeting:
- April 24 - conflict for JohnArwe and JulianneBielski
Attendees
Attendees: SteveSpeicher (chair), MichaelFiedler, NickCrossley, JohnArwe, TuanDang, EdGentry, ArthurRyman, JulianneBielski
Regrets: PaulSlauenwhite, 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
