W3C home > Mailing lists > Public > public-webarch-comments@w3.org > July to September 2004

section 2.2 - what does it mean to 'take on meaning'

From: Daniel Weitzner <djweitzner@w3.org>
Date: Tue, 14 Sep 2004 16:18:33 -0400
Message-Id: <401F4545-068B-11D9-B327-000393CFED62@w3.org>
To: public-webarch-comments@w3.org

Section 2.2 on URI/Resource relationships proposes that URIs take on 
;'meaning' based on the HTTP spec.

> For example, the HTTP URI scheme (RFC2616) uses DNS so that names such 
> as “http://example.com/somepath#someFrag” take on meaning by way of 
> HTTP GET response messages from the domain holder (or an agent they 
> delegate to).

I would suggest that it is unclear what it means for a name such as the 
one given in the example to have 'meaning.' There's inevitable 
confusion about the distinction between the meaning of a URI and the 
resources which is references. Personally, I don't believe that the URI 
itself has any meaning at all separate from the resource which it 
identifies. But this is a philosphical rathole that I think the 
document should try to avoid. If the TAG has some reason to leave the 
reference to 'meaning' in, I hope it can be clarified.



Daniel J. Weitzner                                          
+1.617.253.8036 (MIT)
World Wide Web Consortium                       +1.202.364.4750 (DC)
Technology & Society Domain Leader      <djweitzner@w3.org>
Received on Tuesday, 14 September 2004 21:14:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:26:47 UTC