W3C home > Mailing lists > Public > semantic-web@w3.org > June 2007

Re: What if an URI also is a URL

From: Ian Davis <lists@iandavis.com>
Date: Thu, 07 Jun 2007 08:53:35 +0100
Message-ID: <4667B97F.90002@iandavis.com>
To: "r.j.koppes" <rikkert@rikkertkoppes.com>
CC: Tim Berners-Lee <timbl@w3.org>, semantic-web@w3.org, "Lynn, James (Software Escalations)" <james.lynn@hp.com>

On 06/06/2007 19:51, r.j.koppes wrote:
> But if, on the web page http://www.example.com/mophor there is a section 
> with id "me", how do I refer to that particular section in the web page 
> in a RDF document (which might contain anything, even unrelated to me as 
> a person)? How do I make sure that the reader (machine / human) 
> interprets this reference as being a web location (fragment in web page) 
> instead of the thing, me.

Be careful not to mix up the resource identified by 
http://www.example.com/mophor#me and the representation obtained by 
looking up http://www.example.com/mophor. The resource doesn't change 
but the representation might depending on headers you send and the time 
when you send them.

By convention I would expect #me in the HTML document to be some markup 
describing the same thing that #me in the RDF document refers to. 
Remember the RDF document you get is also markup expressing information. 
Different representations of the same resource.

Now, if you want to assert things about that particular fragment of the 
particular HTML document you got when you issued a GET to the server 
then you need to identify that by specifying all the criteria you used 
to obtain it: the URI, the headers and the time.

It might look something like this made up example:

   a ex:HtlmlFragment ;
   ex:isIdentifiedBy <http://www.example.com/mophor#me> ;
   ex:partOf <http://www.example.com/mophor> ;
   ex:contentType "text/html" ;
   ex:timeObtained "2007-06-07T08:50:00Z" ;
   ex:note "Needs checking for factual correctness" .

work - http://www.talis.com/platform
play - http://iandavis.com/blog
Received on Thursday, 7 June 2007 17:40:44 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:45:01 UTC