[oslc-core] Resources that have Multiple rdf:type Values

[Arthur Ryman]

Dave,

I was pointing out the status quo. However, our desire is that types be 
used in a predictable way.

I am recommending that we add an explicit statement to our spec to avoid 
"capricious" use of OSLC-defined types. We don't "enforce" this via an 
ontology so we need to provide explicit guidance in the Core spec.

Regards, 
___________________________________________________________________________ 

Arthur Ryman, PhD, DE

Chief Architect, Project and Portfolio Management
IBM Software, Rational
Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063





From:
Dave <snoopdave at gmail.com>
To:
Arthur Ryman/Toronto/IBM at IBMCA
Cc:
oslc-core at open-services.net
Date:
12/08/2010 04:56 PM
Subject:
Re: [oslc-core] Resources that have Multiple rdf:type Values



On Wed, Dec 8, 2010 at 12:22 PM, Arthur Ryman <ryman at ca.ibm.com> wrote:
> At the Core telecon today, Jim raised this topic. We need to continue 
the
> discussion. Here is a suggestion for how to handle this:
>
> Any RDF resource representation MAY contain zero or more triples that 
have
> a given URI, S, as the subject, and rdf:type as the predicate,  If there
> is a triple of the form (S, rdf:type, T) where T is a type URI defined 
by
> some OSLC Domain specification, then the RDF representation of T SHOULD
> satisfy the OSLC Domain specification that defines T.

I thought you argued against this point today, saying that you can
only make that sort of inference when you that a resource is provided
by a service that implements an OSLC specification.

- Dave