Re: How to handle HTTP 301, 410

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.

> 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.

Kingsley
> Many Regards,
>
> Nathan
>
> [1]
> http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-08#section-8.3.2
> [2]
> http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-08#section-8.4.11
>
>
>   


-- 

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 16:09:53 UTC