Re: quick advice on content negotiation

On Tue, Dec 8, 2009 at 12:35 PM, Kingsley Idehen <kidehen@openlinksw.com> wrote:
> Nathan: see URIBurner or DBpedia responses which also include LINK response
> headers :-)

I had no idea the community was using it.  Excellent!

>
> Sequence example via cURL:
>
> kidehen$ curl -I -H "Accept: text/html" http://dbpedia.org/resource/London
> HTTP/1.1 303 See Other
> Server: Virtuoso/06.00.3124 (Solaris) x86_64-sun-solaris2.10-64  VDB
> Connection: close
> Content-Type: text/html; charset=ISO-8859-1
> Date: Tue, 08 Dec 2009 17:31:21 GMT
> Accept-Ranges: bytes
> Location: http://dbpedia.org/page/London
> Content-Length: 0
>
> kidehen$ curl -I -H "Accept: text/html" http://dbpedia.org/page/London
> HTTP/1.1 200 OK
> Server: Virtuoso/06.00.3124 (Solaris) x86_64-sun-solaris2.10-64  VDB
> Connection: Keep-Alive
> Content-Type: text/html; charset=UTF-8
> Date: Tue, 08 Dec 2009 17:31:37 GMT
> Accept-Ranges: bytes
> Expires: Tue, 15 Dec 2009 17:31:35 GMT
> Link: <http://dbpedia.org/data/London.rdf>;
> rel="alternate"; title="Metadata in RDF/XML format",
> <http://dbpedia.org/data/London.n3>;
> rel="alternate"; title="Metadata in N3/Turtle format",
> <http://dbpedia.org/data/London.json>;
> rel="alternate"; title="Metadata in JSON+RDF format"
> Content-Length: 2095119

That seems to be missing the type attribute which is required for
automated variant selection.  Humans could figure it out by the title
of course...

Mark.

Received on Tuesday, 8 December 2009 18:10:22 UTC