[oslc-rm] Editorial changes to RM spec for "link property" ranges

[Scott Bosworth]

I wanted to draw your attention to some clarifying changes I made (with
Ian's permission) to the RM spec
These arose as a result of discussion and direction in the Core workgroup
[1].

The changes specifically have to do with a relationship/link property's
stated range. Link properties that can be expected
by clients to have a specific resource type at their uri endpoint, like
those linking to an OSLC service document or and OSLC shape resource,
were left unchanged (though I did put a live link to the referred to
resources). Link properties where clients cannot assume
what kind of resource is at the uri endpoint, like those linking to another
domain resource were changed to have their Range say "any"
instead of n/a. This is in keeping with the Core workgroup guidance.

These are not functional or substantive changes to the spec, but are
intended to be more explicit about
what clients can assume about link properties. Thanks...Scott


[1] -
http://open-services.net/pipermail/oslc-core_open-services.net/2010-September/000589.html



Scott Bosworth | IBM Rational CTO Team | bosworth at us.ibm.com | 919.486.2197
(w) | 919.244.3387(m) | 919.254.5271(f)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-rm_open-services.net/attachments/20101006/29eae704/attachment-0003.html>