Re: Is 303 really necessary?

* [2010-11-27 15:24:53 -0500] Tim Berners-Lee <timbl@w3.org> écrit:

] <http://www.w3.org/2008/site/images/logo-w3c-mobile-lg.png>
] 	we know we can use to refer to the image in its PNG version.
] <http://www.w3.org/2008/site/images/logo-w3c-mobile-lg>
] 	we know nothing about.
] 
] Because the fetch returned a content-location header,
] we are now not allowed to use that URI to refer to anything -- it could
] after all refer to the Eiffel Tour, or the W3C as an organization
] according to the new system.
] 
] Does this make sense?

Yes and no. I see the distinction between representation and
description, but I don't think the line is necessarily so sharp. For
example, you could make
<http://www.w3.org/2008/site/images/logo-w3c-mobile-lg>
respond with,

	The W3C logo, white text on a teal background the characters
	"W" and "3" apparently raised and "C" apparently sunken. It is
	the large version of the logo intended for use with mobile
	browsers.

when asked for text/plain (pace "alt"). Maybe this is useful for blind
people.  For them it functions as a representation but is written
using descriptive language. I could imagine formalising the
descriptive language in RDF and returning that when asked for a
different content-type. Maybe I should do some background reading in
semiotics to get this clearer in my mind.

In the meantime,

% curl -I http://bnb.bibliographica.org/entry/GB5105626
HTTP/1.0 303 See Other
Server: nginx/0.7.65
Date: Sat, 27 Nov 2010 23:44:54 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 0
Pragma: no-cache
Cache-Control: no-cache
Vary: Accept
Location: http://bnb.bibliographica.org/entry/GB5105626.rdf
X-Cache: MISS from localhost
X-Cache-Lookup: MISS from localhost:80
Via: 1.0 localhost (squid/3.0.STABLE19)
Connection: close

Cheers,
-w
-- 
William Waites
http://eris.okfn.org/ww/foaf#i
9C7E F636 52F6 1004 E40A  E565 98E3 BBF3 8320 7664

Received on Sunday, 28 November 2010 13:48:05 UTC