OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



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

[ Lists Home | Date Index | Thread Index ]

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

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

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


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS