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

Re: HTTP response status code 303 See Other - Linked Data best practice

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Thu, 28 Mar 2013 10:30:07 -0400
Message-ID: <515453EF.4050202@openlinksw.com>
To: lotico-list@googlegroups.com, "public-lod@w3.org" <public-lod@w3.org>
On 3/28/13 9:46 AM, Marco Neumann wrote:
> thank you Kingsley but I am still not exactly sure about the different options.

In the past, the HTTP 303 redirection heuristic was the only option for 
using hashless HTTP URIs to denote entities such that dereference 
resolved to an entity description document that describes the hashless 
URI's referent [1][2] .

As result of the new HTTP clarification, its possible to factor in 
another heuristic, especially for the many that have been challenged by 
the 303 redirection approach. Thus, instead of inferring that a 200 OK 
implies that a request URI denotes a Web Document, it is now possible to 
leverage additional information (as delivered by the Content-Location 
header) with regards to disambiguating what a hashless URI actually 
denotes.

The Content-Location header actually identifies a Web Document. Thus, if 
you have a request URI that doesn't match the Content-Location header's 
URI, you can infer that the request URI denotes an Entity while the 
Content-Location header denotes its Description Document.
>
> do you provide a service that validates URIs? and list the respective
> configuration options?

We are going to contribute some changes to Vapour re. these matters [3].
>
> I currently use cURL to test URIs but do not always get the same
> run-time behavior my applications.

Vapour is an easier tool for this matter.

Links:


1. http://twitpic.com/cdfva5 -- DBpedia hashless URI and explicit 303 
based indirection (this will soon deploy support for the new heuristic)
2. http://twitpic.com/cbk8ul -- hash URI based implicit redirection
3. https://bitbucket.org/fundacionctic/vapour/wiki/Home -- Vapour Project .

Kingsley
>
>
>
>
>
>
> On Thu, Mar 28, 2013 at 9:30 AM, Kingsley Idehen <kidehen@openlinksw.com> wrote:
>> On 3/28/13 8:56 AM, Marco Neumann wrote:
>>> do you still use HTTP response status code 303 See Other in your
>>> linked data publishing process?
>>>
>>> I experience some push back from customers for the design pattern. I'd
>>> like to explore alternatives.
>>>
>>> Marco
>>>
>>>
>> Please see the discussion at:
>> http://lists.w3.org/Archives/Public/public-lod/2013Mar/0133.html .
>>
>> In a nutshell, the HTTP 303 status code based redirection heuristic is just
>> an option with regards to using hashless (or slash) HTTP URIs when
>> publishing and consuming  RDF based Linked Data.
>>
>> Personally, I encourage everyone to incorporate the new option into existing
>> Linked Data clients and servers.
>>
>> --
>>
>> 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
>>
>>
>>
>>
>>
>
>


-- 

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







Received on Thursday, 28 March 2013 14:30:29 UTC

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