• To: xml-dev@l...
• Subject: Re: Re: [Sax-devel] XInclude and SAX Incompatibility
• From: Oleg Tkachenko <olegt@m...>
• Date: Wed, 25 Jun 2003 10:17:56 +0200
• In-reply-to: <p04330100bb1ea4f86737@[192.168.254.4]>
• Organization: Multiconn Technologies
• References: <OFADB10D5A.7AC22BE9-ON85256D4F.006BE8DD@t...> <p04330100bb1ea4f86737@[192.168.254.4]>
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030612

Elliotte Rusty Harold wrote:

>> 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.

Probably Peter has meant the following example from "4.5 Creating the Result
Infoset"[1]:

<x xmlns:xi="http://www.w3.org/2001/XInclude">
   <xi:include href="something.xml"/>
   <xi:include href="#xmlns(xi=http://www.w3.org/2001/XInclude)
                      xpointer(x/xi:include[1])"
               parse="xml"/>
</x>


[1] http://www.w3.org/TR/xinclude/#creating-result
-- 
Oleg Tkachenko
http://www.tkachenko.com/blog
Multiconn Technologies, Israel

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

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

• Prev by Date: xml data mining
• Next by Date: RE: How Standards Get a Bad Reputation
• Previous by thread: Re: [Sax-devel] XInclude and SAX Incompatibility
• Next by thread: Re: Re: [Sax-devel] XInclude and SAX Incompatibility
• Index(es):
  • Date
  • Thread