Altova Mailing List Archives

RE: [xml-dev] Why is xml:base a URI *reference*?

From: "Simon St.Laurent" <simonstl@--------.--->
To: xml-dev@-----.---.---
Date: 1/10/2004 11:36:00 PM
michael.h.kay@n... (Michael Kay) writes:
>> Hmmm.... I'm a really lazy typist creating links to a 
>> collection of documents with a shared base URI.  I have to 
>> create a lot of links to a document at the base ID, and in 
>> fact to a particular fragid-identified location in that 
>> document.  Since I don't want to type the fragid repeatedly, 
>> I drop it in the base URI and type a lot of <a href="">.
>That runs you into another ghastly mess in the infamous RFC 2396,
>whereby zero-length relative URIs are invalid according to the syntax,
>but have defined semantics, in terms of a concept called the "current
>document" which appears to be distinct from the base URI but is nowhere

Thanks - it's good to know that there are horrors in RFC 2396 which I
have been lucky enough not to encounter (yet).

RFC 2396 is a remarkable document.  Holy writ and hellish mess all
wrapped into one package.  Separating the two is difficult, both in
theory and in practice.

I've stopped using the term "URI" except in cases where it is purely an
identifier - namespaces and RDF are the only two places I know of where
that usage feels comfortable.  Otherwise I'm back to URLs.

Simon St.Laurent - SSL is my TLA may be my URI may be my ascetic URI
urn:oid: is another possibility altogether


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.