[oslc-core] Comments on Core Draft

[Ian Green1]

In the glossary, the definition of resource is the http definition of 
resource, whereas the use of that word elsewhere in the draft also 
includes use of the word in the RDF sense - an abstract thing identified 
by a URI.

I wonder if there would be some value in making a distinction here.

In several places the draft refers to a String property containing  the 
QName of the property.  This should be rdf:resource="uri of the property". 
reflecting the fact that QName is an XML concept not an RDF concept.

On resource shape:
        - I don't understand oslc:RdfTypeTest.  where can i find some 
explanation.  Is this duck typing?  By that I mean that a resource can be 
inferred to have some rdf:type, provided that it contains all of the OSLC 
Properties declared in a given RdfTypeTest resource.
        - "QName of type defined by this type-test " should read 
rdf:resource of the type-test (a URI Reference).
        - what is the role of rdf:type on a ResourceShape resource?  is 
this always http://open-services.net/xmlns/oslc#ResourceShape?
        - why is there no rdf:about for a ResourceShape?
 

On json reporesentations:

        - why isn't OSLC adopting existing JSON representation of RDF?  we 
seem to be inventing?
        - qname doesn't mean anything unless there is a mechanism to 
resolve the prefix.  the json representation doesn't seem to address this. 
 The talis representation uses the full URI which at least avoids the 
needs to deal with prefix mechanism, although the resulting json may be 
harder for humans to read.

best wishes,
    -ian

ian.green at uk.ibm.com (Ian Green1/UK/IBM at IBMGB)
Chief Software Architect, Requirements Definition and Management
IBM Rational





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