Re: [Treebase-devel] reconfiguring the purls

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

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

>> Going from a canonical URI to the implementation URL sounds like a  
>> 302 to
>> me, not a 303.
>
> Really? I interpret the examples I've seen as 303, not 302.


I think the examples you've seen are for going from the thing URI to  
the information about the thing URL.

So for example, accessing http://treebase.org/phylows/tree/16354 would  
return a 303, with either http://treebase.org/phylows/tree/16354?format=rdf 
  or http://treebase.org/phylows/tree/16354?format=html as the  
Location parameter, determined by content negotiation. This one can't  
be a 301 or 302.

But why can't the redirection from http://purl.org/phylo/treebase/phylows/tree/16354 
  to http://treebase.org/phylows/tree/16354 be a 301 or a 302? They  
should probably also be connected by owl:sameAs. In fact, because they  
are owl:sameAs, shouldn't they be redirected through 301 or 302,  
because 303 says "See also". But this is not seeAlso - they are  
owl:sameAs!

Conversely, going from http://purl.org/phylo/treebase/phylows/tree/ 
16354 to http://purl.org/phylo/treebase/phylows/tree/16354?format=rdf  
would have to be a 303, as would going to http://treebase.org/phylows/tree/16354?format=rdf 
  have to be - but purl.org doesn't actually support those redirects.  
It just goes to another site, not to another representation, or to a  
site with information "about" the URI being redirected.

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