[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: SAX: ModSAX addition, general property query

• From: Kay Michael <Michael.Kay@i...>
• To: "XML Developers' List" <xml-dev@i...>
• Date: Tue, 9 Mar 1999 09:54:35 -0000

> I've been thinking about this issue, and I'm fairly convinced 
> that the URI is the right choice.
> 
> Think of the URI a statement of ownership.  Assume that my ISP is
> host.net, and that I've been allocated 5MB of web space at
> http://host.net/foo/.
> 
I don't often disagree with David, but I think this is quite misguided.

If we're only after a unique identifier we could use the longitude and
latitude of the house where I live. In fact that would be better, because it
identifies a unique place, whereas the "http:" idea also says you can get
there by bus and the buses are run by the host.net bus company: in fact it
invites you to "click here" to jump on the bus. But if you get on the bus
and ask for the destination the driver will tell you "Never heard of it,
guv."

And of course it ignores the fact that you can have two buses going to the
same place from different directions.

Just because Namespaces made this mistake (and confused all newbies by doing
so) doesn't mean we have to as well.

Mike Kay

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • RE: SAX: ModSAX addition, general property query
    • From: Dan Brickley <Daniel.Brickley@b...>

• Prev by Date: RE: Namespaces and DTDs
• Next by Date: RE: SAX: ModSAX addition, general property query
• Previous by thread: Re: SAX: ModSAX addition, general property query
• Next by thread: RE: SAX: ModSAX addition, general property query
• Index(es):
  • Date
  • Thread