On Wed, Sep 2, 2015 at 2:41 PM, Nick Crossley <ncrossley@us.ibm.com> wrote:
I agree that the wording of the Core 2 vocabulary is inconsistent, and that the intent was to allow hash resources as well as blank nodes for inline resources. This is how I have interpreted the intent of the spec:
Value Type
Reference
Inline
Either
Resource
A link to an RDF resource with a stable URI. The target RDF resource SHOULD NOT contained within the same RDF graph or same http resource as the source resource; a client may expect to be able to GET this URI separately and independently from the source URI (and possibly PUT/POST to it).
A link to an RDF resource with a stable URI, which might be a hash URI. The target MUST be contained within the same RDF graph or same http resource as the source resource.
A link to an RDF resource with a stable URI, which might be a hash URI. The target RDF resource MAY be contained in the same graph or http resource as the source, so the GET of the source URI might also fetch the target resource.
LocalResource
n/a
A link to an RDF resource with a hash URI or blank node, The target MUST be contained within the same RDF graph or same http resource as the source resource. Clients MUST assume the resource is not separately fetchable or modifiable.
n/a
AnyResource
n/a
A link to an RDF resource. The target MUST be contained within the same RDF graph or same http resource as the source resource. Clients MUST NOT make any assumptions about the nature of the URI for this resource.
A link to a resource. The representation and location of the target is not defined. Clients MUST NOT make any assumptions about the nature of the URI for this resource.
Nick.
Martin P Pain ---09/02/2015 09:57:57 AM---While looking at the tables in OSLC v2 for the discovery resources (which use resource shape termin
From: Martin P Pain <martinpain@uk.ibm.com>
To: OASIS <oslc-core@lists.oasis-open.org>
Date: 09/02/2015 09:57 AM
Subject: [oslc-core] OSLCCORE-35: v2 Resource Shape oslc:Inline property incorreclty mentions blank nodes
Sent by: <oslc-core@lists.oasis-open.org>
While looking at the tables in OSLC v2 for the discovery resources (which use resource shape terminology, in particular the "valueType" and "representation" columns) I realised that the vocab file's definition of oslc:Inline does not seem correct.
For more info see the JIRA I raised: https://issues.oasis-open.org/browse/OSLCCORE-35
This has also raised the question in my mind as to whether most of the places in the v2 spec (or at least the discovery part) that say oslc:LocalResource for the "value type" (which requires use of a blank node - an RDF resource without a URI) ought to say oslc:AnyResource for "value type" and oslc:Inline for "representation" - the only difference (as far as I'm aware) is that the latter allows the resources to have a URI (which may or may not be a hash URI) - but still requires their representation to be inlined. I can't see any benefit to either clients or servers of requiring a blank node. I also don't think that would be a backwards-incompatible change, as clients who can deal with blank nodes should be able to deal with inlined representations (it's making the change the other way round that might break clients).
Any thoughts on either the vocab or the spec? I wouldn't be surprised if I've missed something.
Martin Pain
Software Developer - Green Hat
Rational Test Virtualization Server, Rational Test Control Panel
E-mail: martinpain@uk.ibm.com
Find me on:and within IBM on:
IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
