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

Re: How to handle HTTP 301, 410

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Tue, 09 Mar 2010 12:20:40 -0500
Message-ID: <4B968368.6060003@openlinksw.com>
To: nathan@webr3.org
CC: Linked Data community <public-lod@w3.org>
Nathan wrote:
> Kingsley Idehen wrote:
>   
>> Nathan wrote:
>>     
>>> Hi All,
>>>
>>> I'm mainly wondering.. what the Linked Data implications of the
>>> following are:
>>>
>>> 301 Moved Permanently
>>>    The requested resource has been assigned a new permanent URI and any
>>>    future references to this resource SHOULD use one of the returned
>>>    URIs.  Clients with link editing capabilities ought to automatically
>>>    re-link references to the request-target to one or more of the new
>>>    references returned by the server, where possible. [1]
>>>   
>>>       
>> Representation of Data Object Description has new URL. Based on this
>> response, the calling user agent *may* update its local relation between
>> Data Object and the URL of the Resource that bears its Description
>> (Representation). This is where an explicit "isDescribeBy" relation
>> comes in handy re. Object Identifier association with Resource bearing
>> its Description.
>>
>>     
>
> I really think isDescribedBy is a good idea for many reasons, in this
> context I'm unsure though (more below).
>
> Unsure with regards "Representation of Data Object Description has new
> URL" as the documentation is pretty explicit in saying "resource has
> been assigned a new permanent URI".
>   
In my world view: Resources have URLs while Data Objects have Generic 
HTTP URIs.

I believe you can have Data Object ID: 
http://dbpedia.org/resource/<data-object>
Described by a Resource at: http://dbpedia.org/page/<data-object> .

So if <http://dbpedia.org/page/<data-object> changes, the UA can update 
its local cache or store or whatever mechanism it uses to handle 
interaction with Data Objects with  Identifiers that resolve to 
Description bearing Resource Locations.
> For instance if I changed by WebID and moved my FOAF profile at some
> point in the future I would potentially see this as a mechanism of
> informing all those who deference my "old" WebID about my new WebID,
> with the additional note that they should now use "new URI" as by WebID.
>   
WebID (a Data Object Identifier) is Referenced by your FOAF Profile 
Document (a Resource at a location).
> I guess I'd probably expect people to create something like <newid>
> replaces <oldid>; and then use new from here on..
>   
Yes, but try to be clear about what's changing here. Is it the Data 
Object Idenfifier or the location of its Resource bearing Description. 
Identifiers (irrespective of whether they resolve or not must be 
distinct from the things they are associated with).

Kingsley
>   
>>> 410 Gone
>>>    The requested resource is no longer available at the server and no
>>>    forwarding address is known.  This condition is expected to be
>>>    considered permanent.  Clients with link editing capabilities SHOULD
>>>    delete references to the request-target after user approval. [2]
>>>   
>>>       
>> Representation of Data Object Description is no longer available here. I
>> also have no clue as to if such a thing exists elsewhere. Based on this
>> response,  the calling user agent *may* decide to discard all references
>> to this Data Object.
>>
>>     
>
> as above
>
>   


-- 

Regards,

Kingsley Idehen	      
President & CEO 
OpenLink Software     
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen 
Received on Tuesday, 9 March 2010 17:21:08 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:25 UTC