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

Re: What if an URI also is a URL

From: r.j.koppes <rikkert@rikkertkoppes.com>
Date: Wed, 06 Jun 2007 20:51:49 +0200
Message-ID: <46670245.2010707@rikkertkoppes.com>
To: Tim Berners-Lee <timbl@w3.org>
CC: semantic-web@w3.org, "Lynn, James (Software Escalations)" <james.lynn@hp.com>

Then please read "look up" instead of "access", I am talking about 
visiting http://www.example.com/mophor#me as a web page, following a 
link with this as a reference or putting it in an address bar of a browser.

This action only identifies http://www.example.com/mophor as it is this 
URL that makes the server return a 200.

The URI http://www.example.com/mophor#me is not identified as a resource 
at this moment.

But what if I DO identify it, by means of an RDF triple stating that 
this URI (http://www.example.com/mophor#me) defines me (by linking it to 
my social security number or whatever)

As of what I understand, up till now there are no problems. 
http://www.example.com/mophor is identified as being a web page, 
http://www.example.com/mophor#me is identified as being me.

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.

Rikkert Koppes

Tim Berners-Lee wrote:
> 
> 
> On 2007-06 -06, at 13:13, r.j.koppes wrote:
> 
>> Ok, herby a follow-up to the semantic-web list.
>>
>> To summarize:
>>
>> Me: suppose I am identified by http://www.example.com/mophor and there 
>> is also a webpage http://www.example.com/mophor...
>>
>> Tim: this is an error, by returning a 200 for the webpage, it is 
>> identified, so these are two different things. 
>> http://www.example.com/mophor#me would be ok
>>
>> James: but what about fragment identifiers?
>>
>> Tim: no problem, since the client strips off fragment identifiers, so 
>> accessing the web page http://www.example.com/mophor#me would identify 
>> http://www.example.com/mophor as a webpage by returning a 200 (this is 
>> my interpretation of what is said)
> 
> 
> Woa.  Stop. No.   You can't access < http://www.example.com/mophor#me> 
> as it isn't a web page.
> The function 'access web page' takes a URI with no hash.
> 
> The fact that the id http://www.example.com/mophor#me is used at all 
> indicates that  "http://www.example.com/mophor" identifies a document, 
> before you even think of access it.
> Because the "foo#bar" means   "the thing identified by the local id bar 
> within foo" in the web architecture.
> 
> You can look up < http://www.example.com/mophor#me> which means, on the 
> CLIENT, stripping off the "#me"
> 
> 
> 
> 
Received on Wednesday, 6 June 2007 18:50:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 07:41:57 UTC