Lists Home |
Date Index |
- From: Toby Speight <firstname.lastname@example.org>
- To: XML developers' list <email@example.com>
- Date: 10 Mar 1999 13:42:16 -0700
David> David Megginson <URL:mailto:firstname.lastname@example.org>
[I accidentally mailed this to David; it was meant for the list.
0> In article <email@example.com>, David
David> I've been thinking about this issue, and I'm fairly convinced
David> that the URI is the right choice.
I agree with this much.
David> Think of the URI a statement of ownership. Assume that my ISP
David> is host.net, and that I've been allocated 5MB of web space at
Okay, you own that name subspace *at this moment in time*. Who will
have the right to create names below that next March? Five years from
now? A hundred years from now? Persistent uniqueness of names is the
core work of the URN group, and the consensus there is that DNS names
are a poor basis for any kind of URN (and what we want is exactly what
URNs are for: naming things).
If you are saying that the use of URLs as names is just a stopgap
until the URN registration stuff is sorted, then I'll accept that, but
be aware of the precedent you're setting with the initial "well-known"
David> I am the only one who has the right to make a resource available at
David> http://host.net/foo/, so I am the one who has the (moral) right to
David> construct feature IDs based on http://host.net/foo/.
At this instant...
David> It is not sufficient simply to use the domain name "host.net",
David> because I don't own the domain (someone else could construct
David> the same feature ID), and it is not sufficient to use something
David> starting with net.host.foo, because I *don't* have the right to
David> make something available at, say, ftp://host.net/foo/ --
Nor do you own the host "foo.host.net"
In summary, I think URNs are a good fit, but not necessarily other
kinds of URI.
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)