- From: Eric Jain <Eric.Jain@isb-sib.ch>
- Date: Thu, 29 Jul 2004 10:20:02 +0200
- To: Natasha Noy <noy@smi.stanford.edu>
- Cc: public-swbp-wg@w3.org
>> :AfricanLion >> a :Animal; >> rdfs:subClassOf :Lion . >> >> :Animal >> a owl:Class; >> rdfs:subClassOf :Class . > I am not sure what :Class is. Sorry, this should be owl:Class. If I am not mistaken this makes the AfricanLion both an individual *and* a class, which would address the issue you outline below. > Also, in your example, AfricanLion is not a class but an individual. > This is not quite right for this example. Consider for instance what you > would do for the Lion class: you cannot make it an instance of the > Animal class since, among other things, you won't be able to say that > AfricanLion is a Lion. >> :LionsLifeInThePrideBook >> owl:sameAs <http://isbn.nu/0736809643> ; >> >> rather than >> >> :LionsLifeInThePrideBook >> rdfs:seeAlso <http://isbn.nu/0736809643> ; > I am not sure. I think either solution is correct. I would lean towards > the seeAlso simply because we don't have enough information to say that > the resources are equivalent (by using owl:sameAs) I agree that rdfs:seeAlso is always a safe choice, though I would argue that in this particular case we could dare provide additional information by stating that the two resources represent the same thing, rather than simply being related in some unspecified way. Incidently, is it correct to assume that if "x p a" and "y owl:sameAs x" then "y p a" ?
Received on Thursday, 29 July 2004 04:20:30 UTC