- From: Nabonita Guha <nabonitaguha@yahoo.com>
- Date: Tue, 31 Oct 2006 21:11:18 -0800 (PST)
- To: Bernard Vatant <bernard.vatant@mondeca.com>
- Cc: public-esw-thes@w3.org
- Message-ID: <20061101051119.19343.qmail@web30003.mail.mud.yahoo.com>
Bernard Vatant <bernard.vatant@mondeca.com> wrote: >A skos:Concept is not a class, and the domain of owl:equivalentClass is >owl:Class Whereas in SKOS Core guide (http://www.w3.org/TR/2005/WD-swbp-skos-core-guide-20051102/#secconcept), skos:Concept has been described as a class. If it's not a Class then what it can be considered as? Best, Nabonita Guha Senior Research Fellow Documentation Research & Training Centre Indian Statistical Institute Bangalore INDIA 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] > [2] > > > -- *Bernard Vatant *Knowledge Engineering ---------------------------------------------------- *Mondeca** *3, cité Nollez 75018 Paris France Web: www.mondeca.com ---------------------------------------------------- Tel: +33 (0) 871 488 459 Mail: bernard.vatant@mondeca.com Blog: Leçons de Choses --------------------------------- Want to start your own business? Learn how on Yahoo! Small Business.
Received on Wednesday, 1 November 2006 05:11:30 UTC