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

Re: What if an URI also is a URL

From: Tim Berners-Lee <timbl@w3.org>
Date: Wed, 6 Jun 2007 14:31:01 -0400
Message-Id: <387ED248-2015-4541-AA6E-48275CC59083@w3.org>
Cc: semantic-web@w3.org, "Lynn, James (Software Escalations)" <james.lynn@hp.com>
To: "r.j.koppes" <rikkert@rikkertkoppes.com>

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:31:06 UTC

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