Re: [Treebase-devel] reconfiguring the purls

[Hilmar L. <hl...@ne...>]

On Jun 3, 2010, at 1:36 PM, Rutger Vos wrote:

> Linkeddata browsers apparently (according to @rdmpage, mind) expect  
> 303, but our purls give them 302. They won't know what to do with  
> that, so until we
> reconfigure our purls, we can't use them in a linkeddata context.


Where does it say that? So long as our URIs don't either always return  
RDF, or return RDF based on content negotiation and a 303 response, it  
won't work in an LD browser.

Changing the PURLs to 303 doesn't change that, does it?

It's a bit hard to believe that LD browsers will refuse to follow 302  
and 301 redirects from one site to another, but if there's a spec  
somewhere that states that I'll believe it. Until then, the crux of  
the problem is the LD non-compliant *endpoint*, not the initial PURL  
redirect.

Or are you saying the endpoint is LD compliant? That should be easily  
testable - just change the PURL base to the endpoint URL base  
(removing the PURL.org redirect), and point an LD client at it. Test  
it on dev.

	-hilmar
-- 
===========================================================
: Hilmar Lapp  -:- Durham, NC -:- informatics.nescent.org :
===========================================================