W3C home > Mailing lists > Public > www-tag@w3.org > January 2003

Re: URI Opacity Principle (was: Re: use of fragments as names is irresponsible)

From: Bill de hÓra <dehora@eircom.net>
Date: Wed, 15 Jan 2003 14:47:29 +0000
Message-ID: <3E257481.80304@eircom.net>
To: Dare Obasanjo <dareo@microsoft.com>
CC: noah_mendelsohn@us.ibm.com, Sandro Hawke <sandro@w3.org>, "Roy T. Fielding" <fielding@apache.org>, www-tag@w3.org

Dare Obasanjo wrote:
> Hopefully if the architecture document says anything in this direction
> it will lean away from URI opacity. The opacity of URIs is a problem for
> in XML application, specifically those that use XML namespaces. A number
> of issues that come up in XML applications would be a lot easier to
> solve (e.g. how does one version XML namespaces?) if namespace names
> were structured and not just glorified UUIDs. 

Yes. To ground this discussion perhaps the TAG could ask itself what 
  architectural advice it might give to Jon Udell regarding his 
library lookup code [1].

I suspect, crudely, the TAG findings will fall along the lines of 
opacity for identifiers good, opacity for name and information 
spaces, bad. The trick is of course that that individual URIs get 
used for both purposes (ie for RDF, and GET).

Bill de hÓra

[1] 
http://weblog.infoworld.com/udell/stories/2002/12/11/librarylookup.html
Received on Wednesday, 15 January 2003 09:49:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:15 GMT