W3C home > Mailing lists > Public > public-esw-thes@w3.org > February 2005

RE: SKOS Core review Re: issue: non-Literal "comment" properties Re: new draft of SKOS Core guide

From: Miles, AJ \(Alistair\) <A.J.Miles@rl.ac.uk>
Date: Fri, 25 Feb 2005 17:26:41 -0000
Message-ID: <F5839D944C66C049BDB45F4C1E3DF89D18DBBC@exchange31.fed.cclrc.ac.uk>
To: "Charles McCathieNevile" <charles@sidar.org>, <public-esw-thes@w3.org>
> > rdfs:comment does have to go as a super-prop for these 
> props because of  
> > its range, but I've been thinking that there still should 
> be a single  
> > property as the super-property for all SKOS Core documentation  
> > properties.   What if we add a new prop e.g. 
> 'skos:documentation' to  
> > SKOS Core to play the role that rdfs:comment currently does?
> What's the use-case for this property?

... to give you a short way of querying for all the 'documentation' in relation to a concept.  It would be an abstraction of the general notion of documentation (expresses the common semantics of all current SKOS Core 'documentation properties').

The same sort of design pattern is currently used in SKOS Core regarding 'lexical labelling properties' and 'semantic relation properties'.  I.e. for each of these groups of properties, there is a single superproperty that captures the higher level semantics (all lexical labelling properties descend from rdfs:label, and all semantic relation properties descend from skos:semanticRelation).

Do you think this is a good idea?



> Chaals
Received on Friday, 25 February 2005 17:27:13 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 2 March 2016 13:32:05 UTC