2008/6/22 Richard Cyganiak <[EMAIL PROTECTED]>: > > Nicholas, > > I think it would be best to implement the mechanism described here: > http://www.w3.org/TR/cooluris/#hashuri > > This would mean: > <b00b07kw#episode> is the thing > <b00b07kw.rdf> is the RDF variant > <b00b07kw.html> is the HTML variant > <b00b07kw> is a generic, content-negotiated document; it serves the right > variant directly, without any redirect, and gives the URI of the selected > variant in the Content-Location header.
If you do a completely content negotiated, and not redirected view, please do include in the RDF and XHTML direct links between the variants, so that content negotiation doesn't stop direct resolution based on a known URL. You already have the following, which is nice. <link rel="alternate" type="application/rdf+xml" rel="b00b07kw.rdf" /> and although I am not completely sure what is the recommended practice for doing the reverse, from RDF to XHTML, because it is not done often when people start to rely wholly on content negotiation, foaf:page seems to be a good place to start. ie, <foaf:page>http://www.bbc.co.uk/programmes/b00b07kw.html</foaf:page> Note that in the above notation the page is an actual URL string and not an RDF resource which is intended because the person already has the semantic resource and just wants to get to the human readable version. Cheers, Peter
