[oslc-core] Issue: Using "local" and "inline" to Describe Resource Types

[Dave]

Arthur, I like that a lot. Does anybody object to this change in terminology?

- Dave


On Mon, Apr 12, 2010 at 2:33 PM, Arthur Ryman <ryman at ca.ibm.com> wrote:
> I propose that we use the following resource type naming scheme that uses
> a more orthogonal approach.
>
> "inline" means that the value of the resource is given by a node element
> (i.e. the resource is given inline).
>
> "local" means that the resource is a blank node, which may have a local
> identifier.
>
> Each of these adjectives may modify the term "resource". The combinations
> are as follows:
>
> "resource" - the property element. has an rdf:resource attribute that
> gives the URI of the resource.
>
> "local resource" - the property element has an rdf:nodeID attribute that
> gives the local blank node ID of the resource (the ID is local to the
> RDF/XML document)
>
> "inline resource" - the property element contains a node element that
> contains the resource's properties, and the node element has an rdf:about
> attribute that gives the URI of the resource.
>
> "local inline resource" - the property element contains a node element
> that contains the resource's properties, and the node element does NOT
> have an rdf:about attribute. It MAY have an rdf:nodeID attribute that
> gives the local ID of the resource.