Re: owl:sameAs - Is it used in a right way?

On 3/22/13 11:30 PM, David Booth wrote:
> A simple example is Ian Davis's famous toucan-versus-its-web-page 
> example,
> http://blog.iandavis.com/2010/11/04/is-303-really-necessary/
> in which the same URI "ambiguously" denotes both a toucan and the web 
> page describing that toucan.  One RDF graph, Gt, may be written under 
> the assumption that the URI denotes the toucan. Another graph, Gp, may 
> be written under the assumption that the URI denotes the toucan's web 
> page.  Gt may work perfectly well in an application that merely 
> categorizes different animal species -- *unambiguously* interpreting 
> the URI as denoting the toucan.  And Gp may work perfectly well in an 
> application that merely lists web page authors -- *unambiguously* 
> interpreting the URI as denoting the toucan's web page.  In fact, even 
> the merge of Gt and Gp may work perfectly well in both applications, 
> provided the RDF authors have not asserted that toucans are disjoint 
> from web pages! 

In that example disambiguation is handled by incorporating HTTP response 
data delivered by the Content-Type header. Also note that HTTP is now 
getting clearing about metadata thereby making the basis for Linked Data 
disambiguation heuristics clear [1].

Links:

1. http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-22#page-15 
-- how HTTP request and response Content-Type URI disparity can aid URI 
disambiguation re., RDF based Linked Data Description Documents and the 
Subjects they describe.

2. http://lists.w3.org/Archives/Public/public-lod/2013Mar/0115.html -- 
emerging thread .

-- 

Regards,

Kingsley Idehen 
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen