[oslc-core] Comment on Vocabulary Description Vocabulary

[Ian Green1]

The annotation vocabulary [1] defines oslc:inverseLabel and gives some 
examples of its use.

It seems to me that rdfs:label and oslc:inverseLabel ought not to be 
duals.  The RDFS spec has R rdfs:label L to mean "L is a human readable 
label for R".  I don't think our usage of rdfs:label reflects this 
intended usage - rather we're using the rdfs:label of the predicate to 
designate the role the subject plays in relation to the object of the 
link.  The idea of oslc:inverseLabel is to have something to designate the 
role the object plays in relation to the subject. 

The example on the wiki is to do with query building.  The suggestion is 
the user would see "validates" in the UI from the perspective of the 
testcase, and they would see "validated by" from the perspective of the 
requirement.  But in neither of these cases is the user examining the name 
of the resource whose URI is oslc_rm:validatedBy.  That resource has the 
label "validatedBy".  The query builder use case is about labelling the 
role of the testcase in relation to the requirement (or vice versa).  This 
is conceptually different from the human-readable name of the predicate.

Was this distinction discussed when the draft was being drawn up 
(apologies if so)?  Does this distinction matter? 

I looked through the RM 2.0 vocabulary and it is the case that all of the 
rdfs:labels "make sense" as a role name;  I looked at DC and most of those 
also follow that pattern, but not all do.  For example, dcterms:relation 
has the label "Relation", with the definition   "A related resource". I'd 
expect the role name for such a link to be "Related To". 

Any comments?


[1] http://open-services.net/wiki/core/Vocabulary-Annotation-Vocabulary/

best wishes,
    -ian

ian.green at uk.ibm.com (Ian Green1/UK/IBM at IBMGB)
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20131129/64ebdd40/attachment-0003.html>