[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [oslc-core] Review of OSLC Discovery
Things are getting clear, but I have still have some doubts with stating that a Service resource can be both a Local resource as well as a LDPC.
In your feedback, you say that “Local resource is about the representation of the content, not necessarily its URIs. The shape constraint for ServiceProvider just indicates the Service resources’ properties must also be included in the representation of the ServiceProvider - it doesn’t require them to be blank nodes or have fragment URIs within that representation”.
But in the Resource Shape specs (https://tools.oasis-open.org/version-control/svn/oslc-core/trunk/specs/resource-shape.html), it is clearly stated that for a oslc:LocalResource, “The object resource MUST be identified with a blank node.”
And, when you say above “Local resource is about the representation of the content”, this sounds more like about the Representation being “inline”, rather than the value-type being LocalResource?
When it comes to the constraints of the ServiceProvider resource, the oslc:service property is currently constraint to:
representation: inline à This agrees with your description
value-type: AnyResource à This means it can also be an oslc:LocalResource, which MUST be a blank node.
Would representation: inline & value-type: Resource be more appropriate?
I may be over-interpreting the text, and this could stem from the usual confusion I have between Representation and Value-type. But I‘ll try one last time …
Jad El-khoury, PhD
KTH Royal Institute of Technology
School of Industrial Engineering and Management, Mechatronics Division
Brinellvägen 83, SE-100 44 Stockholm, Sweden
Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
From: firstname.lastname@example.org [mailto:email@example.com]
On Behalf Of Jim Amsden