- From: Bernard Vatant <bernard.vatant@mondeca.com>
- Date: Wed, 01 Nov 2006 00:09:17 +0100
- To: "Houghton,Andrew" <houghtoa@oclc.org>
- Cc: public-esw-thes@w3.org
Hi Andrew > The SKOS guide [1], in the "Concept Identity and Mapping" section, states that owl:sameAs *should not* be used to indicate that two concepts share the same meaning. It gives some rationale in the section for this. Looking at the OWL guide [2], in the "4.1. Equivalence between Classes and Properties" section, I'm wondering whether one can use owl:equivalentClass to indicate that two concepts share the same meaning. If there is a reason why owl:equivalentClass can/cannot be used for this, should it also be mentioned in "Concept Identity and Mapping" section? > Yes, there is a good reason. A skos:Concept is not a class, and the domain of owl:equivalentClass is owl:Class Cheers Bernard > > Thanks, Andy. > > [1] <http://www.w3.org/TR/2005/WD-swbp-skos-core-guide-20051102/#secidentity> > [2] <http://www.w3.org/TR/2004/REC-owl-guide-20040210/#equivalentClass1> > > > -- *Bernard Vatant *Knowledge Engineering ---------------------------------------------------- *Mondeca** *3, cité Nollez 75018 Paris France Web: www.mondeca.com <http://www.mondeca.com> ---------------------------------------------------- Tel: +33 (0) 871 488 459 Mail: bernard.vatant@mondeca.com <mailto:bernard.vatant@mondeca.com> Blog: Leçons de Choses <http://mondeca.wordpress.com/>
Received on Tuesday, 31 October 2006 23:09:36 UTC