|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Re: [Sax-devel] XInclude and SAX Incompatibility
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
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
|||||||||

Cart








