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

Re: Overloaded URIs (was Re: XLink: behavior must go!)

• From: "Oren Ben-Kiki" <oren@c...>
• To: "XML List" <xml-dev@i...>
• Date: Mon, 17 May 1999 17:55:50 +0200

Simon St.Laurent <simonstl@s...> wrote:
>How much more weight should we really be putting on URIs?  We're going to
>need to be issuing directories of URIs and their meanings in different
>(Web, namespaces, now XLink) context if this keeps up.  I realize that
>they're about the only mechanism for which large-scale unique registration
>is currently available, but wow, this could be genuinely ugly in a few
>years (even months!).


It's genuinely ugly already :-) As you point out, don't really have a
choice. The alternatives have been pretty thoroughly discussed in the SAX
extensions naming threads a few months back, and all boil down to URIs or
something else based on DNS.

I haven't thought of the problem of the same URI used in different contexts
(namespaces, XLink, maybe a name in XSLT). I think the recommended practice
should be not to use the same URI in more then one context. I'd hesitate to
make it an actual requirement, though, unless sufficient experience is
gained. Another thing to keep in mind for version 2 of your favorite XML
standard...

Have fun,

    Oren Ben-Kiki


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: Overloaded URIs (was Re: XLink: behavior must go!)
    • From: David Megginson <david@m...>

• Prev by Date: RE: A milestone in XML
• Next by Date: XML Document creation using SAX model
• Previous by thread: SGML lawyer questions
• Next by thread: Re: Overloaded URIs (was Re: XLink: behavior must go!)
• Index(es):
  • Date
  • Thread