Overloaded URIs (was Re: XLink: behavior must go!)
nikita.ogievetsky at csfb.com
Fri May 21 19:32:46 BST 1999
James Tauber wrote:
I suggested this to TimBL at WWW8 but he didn't buy it. My argument
something like this:
1. Namespace URIs don't have to point to anything retrievable, they
2. Some URI schemes might not be web-retrievable (eg
3. Some URI schemes *are* web-retrievable (eg
4. So namespaces URIs *can* point to something, though, such as a
human-readable description of the namespace, if they use a URI
5. If this is done, how does one distinguish referencing the
referencing the file describing the namespace
And in some cases like with xsl, xlink, etc.
the alias itself becomes unique ( even though one can use the word
And the URI becomes a version number.
Let us say I will start using "xthing:" alias for namespaces
in my documents. How can I be guarantied that next year
somebody will not come up with XThing recommendation
and future versions of XML parsers will make it a reserved word?
Isn't it against some basic XML principles?
6. My suggestion: come up with a new URI scheme that has the same
scheme-specific syntax as an http URI but that is only intended as a
Another crazy idea: use xlink to describe namespaces
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
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 at ic.ac.uk the following message;
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
More information about the Xml-dev