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

Re: Re: [Sax-devel] XInclude and SAX Incompatibility

• To: xml-dev@l...
• Subject: Re: Re: [Sax-devel] XInclude and SAX Incompatibility
• From: Richard Tobin <richard@c...>
• Date: Wed, 25 Jun 2003 14:33:31 +0100 (BST)
• Cc:
• In-reply-to: <p04330100bb1ea4f86737@[192.168.254.4]>
• Organization: HCRC, University of Edinburgh

>>I'm envisioning the scenario when no URL is given (href="
>>#fragment-identifier").  This would be resolved against the current
>>document.  And the current document might not necessarily be able to be
>>reopened, if it is coming from an input stream other than a regular file.

>That's not legal. According to section 5.3 all element and document 
>information items *must* have base URI properties, against which a 
>relative URL can be resolved.

The base URI is not necessarily a URI that the document can be
retrieved from.  A completely synthetic document might have base
URI properties on the info items.

But this is just in the nature of streamed synthetic documents.
There are some things you can't do with them.

-- Richard

• References:
  • Re: [Sax-devel] XInclude and SAX Incompatibility
    • From: Elliotte Rusty Harold <elharo@m...>

• Prev by Date: Re: XML-escape string
• Next by Date: Re: XML-escape string
• Previous by thread: Re: Re: [Sax-devel] XInclude and SAX Incompatibility
• Next by thread: Re: Re: [Sax-devel] XInclude and SAX Incompatibility
• Index(es):
  • Date
  • Thread