[oslc-scm] SCM 1.0 spec updated to follow core spec draft - ready for convergence?

[Nick Crossley]

Frank,


> > Remark 11: Symlinks
> > Add that a symlink is a specific type of object version. If not, 
> > then changing a symlink will update all prior baselines that contain
> > the symlink.

> All SCM 1.0 resource types are subtypes of object version, including
> symbolic links.  This is specified in the description of the object 
> version resource type. 
> 
> I disagree with your reply. For files and directories it is 
> explicitly specified that they are "specific types of object type". 
> For files and directories this is more obvious than for symlinks. So
> I would really like to add this simple sentence to symlinks too, as 
> a reminder, similar to the description of files and directories.

I thought about this for a while.  I agree we want to be consistent in the 
description of each resource - so for a while I considered taking out the 
phrase you mentioned from the description of the file version and 
directory version, on the grounds that the phrase is redundant, and the 
shorter the spec, the better.  However, on reflection, I think it is 
likely that future revisions of the spec will introduce resource that 
might not be subtypes of object version, and so we would then need the 
phrase.  To make the change to such a hypothetical future version of the 
spec easier both for us to make and for the reader to read, it would be 
easier to start off now by stating explicitly for every resource type that 
it is a subtype of object version.

So that's what I've done - changing not only the symlink type but also all 
the other ones that did not explicitly state they were a subtype of 
objection version.

Also for consistency and compatibility with hypothetical future revisions 
of the spec, I have renamed the symlink resource type to SymlinkVersion, 
for exactly the same reasons that we named the file and directory types 
that way.

Nick.

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