For oslc:range property, I wasn't sure if the zero-or-more was to deal with
the dependent typing (on value-type), or that leaving oslc:range unsaid was
acceptable, and if so, what does that mean.
How about that oslc:range is not REQUIRED in the case of Resource
value-types and that omission be defined to be interpreted as
<oslc:range rdf:resource="http://open-services.net/ns/core#Any"; />
The wording of the oslc:range description could be updated to say:
For properties with a resource value-type, Providers MAY also specify
the range of possible resource classes allowed, each specified by
URI. The default range is http://open-services.net/ns/core#Any.
Here i've also changed "OSLC specifications should" to "Providers MAY".
best wishes,
-ian
[email protected] (Ian Green1/UK/IBM@IBMGB)
Chief Software Architect, Requirements Definition and Management
IBM Rational
