W3C home > Mailing lists > Public > public-rdf-wg@w3.org > May 2011

Re: RDF-ISSUE-46 (revisit-rdfms-quoting): Revisit "Should RDF have a mechanism for declaring two uri's to be equivalent?" [Cleanup tasks]

From: Pierre-Antoine Champin <pierre-antoine.champin@liris.cnrs.fr>
Date: Tue, 03 May 2011 11:48:41 +0100
Message-ID: <4DBFDD89.9080402@liris.cnrs.fr>
To: RDF Working Group WG <public-rdf-wg@w3.org>
CC: RDF Working Group Issue Tracker <sysbot+tracker@w3.org>
On 05/03/2011 02:19 AM, RDF Working Group Issue Tracker wrote:
> 
> RDF-ISSUE-46 (revisit-rdfms-quoting): Revisit "Should RDF have a mechanism for declaring two uri's to be equivalent?" [Cleanup tasks]
> 
> http://www.w3.org/2011/rdf-wg/track/issues/46
> 
> Raised by: David Wood
> On product: Cleanup tasks
> 
> See http://www.w3.org/2000/03/rdf-tracking/#rdf-equivalent-uris
> rdf-equivalent-uri's: Should RDF have a mechanism for declaring two
> uri's to be equivalent?
> 
> RESOLVE: Closed, owl provides owl:sameAs already.
> 
> Pierre-Antoine wishes to continue discussion:
> http://lists.w3.org/Archives/Public/public-rdf-wg/2011Apr/0339.html

in the mail linked above, I said
"unless I was really the only one to argue in favour of including it"

it seemed like a good idea, as owl:sameAs is used in a number of
contexts where the rest of OWL is not really used.

However, some concerns have been raised that
* it may introduce nasty entailments in core RDF
* the intensive use of owl:sameAs raises a number of issues
* if "including it in core RDF" meant minting a new URI, that would
create more issues

I sympathise with all these arguments, so I am not going to champion
this inclusion unless others still feel like it.

  pa

> 
> NB: The Charter allows us to "Update and extend the RDF Primer. New features may include multi-syntax examples, more up-to-date in terms of the vocabularies used, may deal with issues around Linked Data like the use of “owl:sameAs”, the “follow-your-nose” algorithm, etc."
> 
> 
> 
Received on Tuesday, 3 May 2011 10:49:09 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:25:42 GMT