W3C home > Mailing lists > Public > public-rdf-in-xhtml-tf@w3.org > September 2004

Re: Use Cases for Bridging the Clickable Web and the Semantic Web

From: David Wood <dwood@tucanatech.com>
Date: Wed, 15 Sep 2004 15:22:45 -0400
Message-Id: <9F523D54-074C-11D9-9028-000A95C50022@tucanatech.com>
Cc: 'public-rdf-in-xhtml task force'' <public-rdf-in-xhtml-tf@w3.org>
To: Ben Adida <ben@mit.edu>

Of course, if I could spell I would have know that the REFERER header 
was only spelled with two Rs...

Regards,
Dave
--
David Wood
CTO, Tucana Technologies, Inc.
http://www.tucanatech.com

On Sep 15, 2004, at 12:10, David Wood wrote:

>
> Hi all,
>
> On Sep 8, 2004, at 19:05, Ben Adida wrote:
>> ---------
>> written by <a href="http://ben.adida.net">Ben Adida</a>
>> ---------
>
> In this example we want to represent the RDF statement:  <referrer 
> URI> <dc:creator> <http://ben.adida.net>, right?
>
> I have in mind something like:
>
> <a href="http://ben.adida.net" rel="dc:creator">Ben Adida</a>
>
> and the browser placing the rel information in the HTTP REFERRER 
> header to pass it to the server.
>
> The REFERRER header holds a URI and can therefore encode just about 
> anything.  Right now it encodes the URI of the referring document (the 
> RDF subject).  I propose allowing it to hold both the RDF subject and 
> the RDF predicate.  That is, the referring URI and the relationship 
> URI (dc:creator in this example).  There would be no change to the 
> HTTP spec as long as it was encoded as a URI.
>
> Regards,
> Dave
> --
> David Wood
> CTO, Tucana Technologies, Inc.
> http://www.tucanatech.com
>
>
Received on Wednesday, 15 September 2004 19:22:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:14:59 GMT