Re: Naive question on redirection.


This is a very interesting question, thanks for rising it.

On 6 Jun 2008, at 09:57, Phil Archer wrote:
> Suppose I have this triple
> <> ex:colour "red"
> and when I dereference the URI I get a 302 redirect to 
> .
> Do I know what colour is?

I don't want to dig too deeply into this, but here's an explanation  
that makes sense to me. This is an interpretation that is not fully  
supported by the wording of the specs, but to me it seems to be the  
most sane one.

An HTTP GET to a URI means “Please give me a representation of  

A 302 response means: “I can't or don't want to give you a  
representation of myself, but you can get a representation of myself  
over there.”

The important point in this interpretation: 302 from A to B means that  
you get a *representation of A* by doing a *GET on B*.

With this interpretation, we cannot deduce anything about B from the  
interaction, except that among its representations there is one that  
is also a representation of A. We cannot deduce any owl:sameAs or  
whatever else from the redirection. The only deduction we can make  
from an HTTP redirect is “A http:redirectsTo B”.

I strongly prefer this interpretation because it keeps the layering of  
the SemWeb *on top of* HTTP intact. Configuring the HTTP responses of  
a URI should *only* determine what representations clients can access,  
*not* what the resource is. (With the single additional constraint of  
httpRange-14, that only a special class of things called web documents  
can have representations, and having representations of other things  
like people is a form of unhealthy punning that is best avoided.)

So, in my eyes, you don't know the color of < 
home.asp> unless the RDF you get back from there tells you the color.


> I'm pretty sure the answer's no, but has anyone else grappled with  
> the joys of redirects in this way?
> Phil.
> -- 
> Phil Archer
> Chief Technical Officer,
> Family Online Safety Institute
> w.

Received on Saturday, 7 June 2008 09:25:44 UTC