quick advice on content negotiation

Hi,

Just need a quick bit of advice on whether the following is suitable for
exposing linked data.

I've implemented content negotiation as follows:
where we have a URI resource http://example.org/user/23
when that URI is requested then content negotiation using the Accept
header kicks in, if any of the RDF formats are specified and data exists
then serialized RDF in the requested format is returned;

if one of the HTML types is requested then an HTML document (essentially
the "page" is returned.

in addition adding the extension .n3 / .rdf to the uri causes content
RDF to be returned instead.

passable and usable?

regards;

nathan

Received on Tuesday, 8 December 2009 16:44:19 UTC