Altova Mailing List Archives

System identifiers and base URIs

From: Norman Walsh <ndw@------.--->
To: xml-dev@---.---
Date: 8/4/2000 6:43:00 AM
It's possible that the following question is concretely answered
somewhere, in which case a simple whack on the head would be
appreciated. :-)

Suppose I attempt to parse a document: and that
attempt results in a redirect to RFC2396 makes it
clear that the resulting base URI is

  5.1.3. Base URI from the Retrieval URI

     [...] Note that if the retrieval was the
     result of a redirected request, the last URI used (i.e., that which
     resulted in the actual retrieval of the document) is the base URI.

What isn't well defined, AFAICT, is what "redirected request" really
means.  Suppose that my parser has an SAX entityResolver installed and
the entity resolver (through means that I don't think are important to
this question) decides to perform the redirection. What is the base
URI of the resulting document?

To make things concrete, suppose I have a document with a DOCTYPE
declaration that references (and I'm doing a
validating parse). The parser attempts to open,
and the entity resolver opens and returns

Subsequently, the parser encounters a relative URI "somefile.ent" in
the DTD. It must calculate an absolute URI in order to open it.

Is the resulting absolute URI "" or
""? Or is there not a definitive answer?

                                        Be seeing you,

Norman.Walsh@E... | Are you not the future of all the memories
XML Technology Center     | stored within you? The future of the
Sun Microsystems, Inc.    | past?--Val\'ery


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.