W3C home > Mailing lists > Public > semantic-web@w3.org > May 2008

Re: Managing Co-reference (Was: A Semantic Elephant?)

From: Peter Ansell <ansell.peter@gmail.com>
Date: Fri, 16 May 2008 09:20:28 +1000
Message-ID: <a1be7e0e0805151620l15049aa2u7c2dcd99b558b182@mail.gmail.com>
To: "Jim Hendler" <hendler@cs.rpi.edu>
Cc: "Semantic Web Interest Group" <semantic-web@w3.org>

2008/5/16 Jim Hendler <hendler@cs.rpi.edu>:
> (note reduced cc-list, wish everyone would do that)
> Fwiw, seems to me what we need is rdfs:sameas - with owl: sameas being a
> special, more restricted, case - like rdf vs owl class defs

I agree. There is a big difference between being able to merge RDF
graphs and merge OWL "Things". I use owl:sameAs to do the former when
the properties are all going to be relevant to both, but the two URI's
still don't necessarily match a given whole-world OWL structure.
rdfs:seeAlso has never been a big attraction to me due to its lack of
actually saying anything about what you are going to get, possibly due
to its colloquial use with FOAF and sending you off to a random foaf
file for more information about an, as yet unnamed, entity.

Given that you are never sure how someone is going to utilise your OWL
structures in future you cannot be held accountable for every
statement you make retrospectively, particularly if the dependent
vocabularies (or the assumptions of the person utilising the
vocabulary) are the cause of the breakage.

> Sent from my iPhone


Received on Thursday, 15 May 2008 23:21:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 07:42:04 UTC