W3C home > Mailing lists > Public > public-lod@w3.org > August 2008

Re: Content negotiation: add Topic Maps?

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Wed, 06 Aug 2008 12:09:04 -0400
Message-ID: <4899CCA0.2080803@openlinksw.com>
To: Richard Light <richard@light.demon.co.uk>
CC: public-lod@w3.org

Richard Light wrote:
>
>
> Hi,
>
> It occurs to me that we could extend the idea of content negotiation 
> to include Topic Map data describing a resource.
>
> As an example, I have extended my Wordsworth Trust sandbox application 
> so that the same URL, e.g.:
>
> http://collections.wordsworth.org.uk/object/GRMDC.C104.15
>
> delivers RDF if you say you want application/rdf+xml, XTM 2.0 if you 
> say you want application/xtm+xml, and HTML otherwise.  (If you want to 
> go directly to a specific format, add "rdf/" or "xtm/" after "object/" 
> in the above URL.)
>
> This means that the same non-information resource URL can be used for 
> both RDF and XTM descriptions of that resource.  Good idea?  Bad idea?
>
> Richard
Richard,

Cool!

Entity ID/ URI/ Pointer: 
http://collections.wordsworth.org.uk/object/GRMDC.C104.15

The essence/description of this Entity is now projected via a myriad of 
representations via content negotiation.


yn234:~ kidehen$ curl -I -H "Accept: application/rdf+xml" 
http://collections.wordsworth.org.uk/object/GRMDC.C104.15
HTTP/1.1 303 See Other
Date: Wed, 06 Aug 2008 15:57:26 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Location: http://collections.wordsworth.org.uk/object/rdf/GRMDC.C104.15
Connection: close
Accept-Ranges: bytes
Vary: accept
Content-Length: 0
Content-Type: application/rdf+xml;qs=1
Set-Cookie: ASPSESSIONIDQATBSSCQ=CHGNGAJADBHKIKBFFGBNCBPB; path=/
Cache-control: private

dyn234:~ kidehen$ curl -I -H "Accept: application/text/html" 
http://collections.wordsworth.org.uk/object/GRMDC.C104.15
HTTP/1.1 303 See Other
Date: Wed, 06 Aug 2008 15:57:51 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Location: http://collections.wordsworth.org.uk/object/page/GRMDC.C104.15
Connection: close
Accept-Ranges: bytes
Vary: accept
Content-Length: 0
Content-Type: text/html;qs=1
Set-Cookie: ASPSESSIONIDQATBSSCQ=DHGNGAJAKFFPMBPCIAHHGGGM; path=/
Cache-control: private

dyn234:~ kidehen$ curl -I -H "Accept: application/xtm+xml" 
http://collections.wordsworth.org.uk/object/GRMDC.C104.15
HTTP/1.1 303 See Other
Date: Wed, 06 Aug 2008 15:58:34 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Location: http://collections.wordsworth.org.uk/object/xtm/GRMDC.C104.15
Connection: close
Accept-Ranges: bytes
Vary: accept
Content-Length: 0
Content-Type: application/xtm+xml;qs=1
Set-Cookie: ASPSESSIONIDQATBSSCQ=EHGNGAJANFGMMGJFBNDPJMCK; path=/
Cache-control: private


This is why HTTP is a big deal. It delivers a network based pointer 
system via URIs :-)

-- 


Regards,

Kingsley Idehen	      Weblog: http://www.openlinksw.com/blog/~kidehen
President & CEO 
OpenLink Software     Web: http://www.openlinksw.com
Received on Wednesday, 6 August 2008 16:09:44 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:17 UTC