W3C home > Mailing lists > Public > semantic-web@w3.org > November 2006

"Hash URIs" and content negotiation

From: Richard Cyganiak <richard@cyganiak.de>
Date: Tue, 7 Nov 2006 16:39:25 +0100
Message-Id: <EE570AEC-10E0-4CC5-A4E8-3689E129D551@cyganiak.de>
To: Semantic Web <semantic-web@w3.org>

Hi all,

One good practice for identifying non-document resources is to use  
"hash URIs" like http://example/john#me, and to serve a description  
at the URI obtained by taking the part before the hash, e.g. http:// 

Now let's say I want to serve both RDF and HTML descriptions of John.  
That is, both formats should be available from http://example.org/ 
john, depending on the request's Accept: header. How to do this?

a) Just return the requested type of content right at http:// 

b) Redirect to two different URLs, depending on the requested type,  
e.g. http://example.org/john.html and http://example.org/john.rdf

I notice that the SWBP Vocabulary Recipes [1] suggest b). I have a  
hunch that a) is problematic because it's a bit ambiguous, http:// 
example.org/john#me could refer either to John, or to an anchor  
within an HTML page, if there's no 303 redirect in between. So, is  
only b) allowed, or is a) fine too?



[1] http://www.w3.org/TR/swbp-vocab-pub/#recipe3
Received on Tuesday, 7 November 2006 15:40:02 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:44:58 UTC