[oslc-scm] OSLC SCM Meeting this week

[Nick Crossley]

As a reminder, there is a meeting this week, at the usual time of 12 noon 
Pacific on Wednesday.  We will be trying to resolve all the open issues 
with the SCM spec, as listed on the page 
http://open-services.net/bin/view/Main/ScmSpecIssuesV1.  Please review the 
spec and this issues page - if you have any comments, by all means add 
them to the relevant page or send out email  - you do not have to wait for 
the meeting!

The spec page itself, at http://open-services.net/bin/view/Main/ScmSpecV1, 
has been updated to catch up with the core spec and to include some of the 
proposed resolutions to some of the issues.  Here is a summary of the 
changes to the spec since our last meeting:

Changes to track the core spec:
The tables with resource property definitions have been reformatted to 
follow the new core spec standard.
The dc namespace prefix has been changed to dcterms, following the core 
spec
The concept of extended properties has been dropped
The oslc.limit and oslc.count parameters have been dropped

Changes in SCM itself:
I propose replacing the oslc_scm.recurse parameter with closure syntax on 
oslc.properties.  The oslc_scm.recurse option was too specific in its 
meaning, so could not be generally adopted by other OSLC domains.  There 
was also an ambiguity in the use of both oslc.properties and 
oslc_scm.recurse.
Proposed query parameter support now defined
Added resource definitions for directory and file version compare
Weakened the requirement for baseline and change set pickers from MUST to 
SHOULD support

Note that existing implementations may be affected by other changes to the 
core spec, such as the change to use a top-level rdf:RDF element in the 
rdf+xml representation.

Nick.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-scm_open-services.net/attachments/20100712/26c58375/attachment-0003.html>