Re: quick advice on content negotiation

On Tue, Dec 8, 2009 at 11:43 AM, Nathan <> wrote:
> in addition adding the extension .n3 / .rdf to the uri causes content
> RDF to be returned instead.

How is that information communicated to the world?  Is it documented
somewhere, or expressed in-band?  If not the latter, then I'd say
that's not passable because, from a REST POV it's not respecting the
hypermedia constraint.  I'd suggest returning a Link header using the
"alternate" relation type, e.g.

GET /user/23 HTTP/1.1
Accept: application/rdf+xml


HTTP/1.1 200 Ok
Content-Type: application/rdf+xml
Link: <>; rel="alternate"; type="text/n3"
Link: <>; rel="alternate"; type="text/html"


Received on Tuesday, 8 December 2009 17:24:56 UTC