Lists Home |
Date Index |
- From: "Hunter, David" <dhunter@Mobility.com>
- To: 'James Tauber' <firstname.lastname@example.org>, 'XML Dev' <email@example.com>
- Date: Mon, 31 May 1999 09:53:04 -0400
James Tauber wrote:
> They just didn't seem to have a problem with the notion that
> a single URL
> scheme would be used for both retrieving machine readable
> information and
> for an irretrievable unique name.
> I used the example of the XSLT namespace URI:
> The URI above currently gives a 404. It is an irretrievable
> unique name.
Using HTTP for URIs sounds intrinsically <em>bad</em> to me. Suppose we
change that URI to something more like:
(Just because most companies' web space may not be as tightly administered
as the W3C's...) What happens when my web administrator decides to put a
default web page there, which happens to be a page about his cat Mittens?
Apart from the facetiousness of this example, we have the potential of the
same URI pointing to two completely different resources; I thought this was
not supposed to happen with URIs.
> *However*, I asked TimBL why on earth use an http URI for
> this. He and Rohit
> both chimed that, some time down the track, it will the URL
> for a document
> describing the namespace.
> I told them that my problem with that is that is then you
> have the *same*
> URI being used for both the namespace itself and a document
> describing the
> Both TimBL and Rohit (who invoked Roy Fielding's PhD thesis) said they
> didn't see that there was any distinction that warranted
> different URIs.
> Maybe I've just missed something. When TimBL, Rohit Khare and (by proxy)
> Roy Fielding disagree with you on a URI matter, it is worth being nervous.
I agree with <em>this</em> too. I'm in way over my head here... ;-)
MediaServ Information Architects
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)