- From: Bijan Parsia <bparsia@cs.man.ac.uk>
- Date: Wed, 9 Jul 2008 21:27:10 +0100
- To: "Booth, David (HP Software - Boston)" <dbooth@hp.com>
- Cc: Richard Cyganiak <richard@cyganiak.de>, Peter Ansell <ansell.peter@gmail.com>, Dan Brickley <danbri@danbri.org>, semantic-web at W3C <semantic-web@w3c.org>, "public-lod@w3.org" <public-lod@w3.org>
On Jul 9, 2008, at 8:33 PM, Booth, David (HP Software - Boston) wrote: > >> From: Bijan Parsia >> [ . . . ] >> 1) sameAs tends to merge annotations and similar meta data, because >> it's extensional. >> E.g., If I say someTerm dc:creator "Bijan" and someone else >> someOtherTerm dc:creator "BoogerHead Jones", and then we say that >> someTerm sameAs someOtherTerm, we've (semantically) lost the >> distinguish between who created what. > > As described, that example looks to me more like an illustration of > the misuse of dc:creator than of owl:sameAs. If :someTerm and > someOtherTerm really denote the same thing, and then according to > my reading of owl:sameAs semantics, > > someTerm dc:creator "Bijan" . > > means *exactly* the same thing as > > someOtherTerm dc:creator "Bijan" . > > so I don't see any inappropriate loss of information. Am I missing > something? I don't know how you determine which is the "real" mistake. Typically, people mean that to be an annotation (e.g., myClass dc:creator "Bijan"). You can argue that the annotation system is broken (I've done that), but that really just pushes things around. Cheers, Bijan
Received on Wednesday, 9 July 2008 20:27:50 UTC