W3C home > Mailing lists > Public > public-lod@w3.org > March 2013

Re: Important Change to HTTP semantics re. hashless URIs

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Sun, 24 Mar 2013 14:19:35 -0400
Message-ID: <514F43B7.6080804@openlinksw.com>
To: public-lod@w3.org
On 3/24/13 1:52 PM, Richard Cyganiak wrote:
> On 24 Mar 2013, at 17:39, Kingsley Idehen <kidehen@openlinksw.com> wrote:
>> Thus, if a client de-references the URI <http://dbpedia.org/resource/Barack_Obama> and it gets a 200 OK from the server combined with <http://dbpedia.org/page/Barack_Obama> in the Content-Location response header, the client (user agent) can infer the following:
>> 1. <http://dbpedia.org/resource/Barack_Obama> denotes the real-world entity 'Barack Obama' .
> Why can a client make this inference? I can't see any basis for the inference that the URI identifies a “real-world entity”. The described interaction does not provide any information regarding the nature of the identified resource, AFAICT.
> Best,
> Richard

To be a little clearer, "real-world entity" isn't the focal point of the 
comment per se. This is about disambiguating description document and 
description document subject URIs. Thus, if the request URI and the 
Content-Location URI are both hashless and the status returned is 200 OK 
a client can also infer that the request URI denotes a Web Document (or 
entity of type: Web Document).

Re. #1 above, it just denotes an entity that isn't of the Web realm 
i.e., not of type: Web Document.

Hope that's clearer?



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

Received on Sunday, 24 March 2013 18:19:58 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:16:31 UTC