This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: XInclude
- From: "Michael Kay" <michael dot h dot kay at ntlworld dot com>
- To: <xsl-list at lists dot mulberrytech dot com>
- Date: Fri, 31 May 2002 09:10:19 +0100
- Subject: RE: [xsl] XInclude
- Reply-to: xsl-list at lists dot mulberrytech dot com
> Are xslt processors required to use XML parsers that
> recognize and implement xinclude
> (http://www.w3.org/2001/XInclude)? If not, will they when it
> becomes an official recommendation of the W3C? Do any
> processors recognize it already?
>
No they are not required to expand XInclude.
There has been some debate on xml-dev about whether they are even
allowed to expand XInclude. Apparently one processor does so (I forget
which) and the user was complaining that they didn't want this.
It's not easy to see how we would extend the document() function to give
users control over the processing pipeline that generates the returned
tree. Pragmatically, I think this will be left up to implementors, using
techniques such as the JAXP URIResolver.
Michael Kay
Software AG
home: Michael.H.Kay@ntlworld.com
work: Michael.Kay@softwareag.com
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list