- From: Houghton,Andrew <houghtoa@oclc.org>
- Date: Wed, 1 Nov 2006 09:51:51 -0500
- To: <public-esw-thes@w3.org>
> From: public-esw-thes-request@w3.org > [mailto:public-esw-thes-request@w3.org] On Behalf Of Mark van Assem > Sent: 01 November, 2006 06:12 > To: Nabonita Guha > Cc: Bernard Vatant; public-esw-thes@w3.org > Subject: Re: SKOS Guide and owl:sameAs > > There is a confusion of different things here. > > 1- skos:Concept is a class. > 2- instances of skos:Concept are called "concepts" in the > SKOS documents. > > 3- mapping of skos:Concept to another class can be done with > owl:equivalentClass > 4- mapping of instances of skos:Concept to other skos:Concept > instances (from other vocabularies) can be done with owl:sameAs > 5- mapping of instances of skos:Concept to other instances (from other > vocabularies) can also be done with the SKOS mapping properties, e.g. > exactMatch [1] Maybe this additional explaination could be worked into the guide. The issue that I was looking into that led me to investigate owl:sameAs and owl:equivalentClass was the mapping of instances between editions, rather than between instances from other vocabularies. While SKOS mapping could be used in this situation I'm not comfortable with using that approach. After reviewing these comments, I think that it might be more appropriate to use dct:replaces and dct:isReplacedBy to indicate the notion of concept relocation and splitting between editions of a vocabulary. Andy.
Received on Wednesday, 1 November 2006 14:52:08 UTC