On 4 February 2010 11:07, Elliotte Rusty Harold <elharo(_at_)ibiblio(_dot_)org>
wrote:
Not quite. Since this is XSL that's at issue here:
1. Validation is irrelevant. XSLT processors don't validate.
2. DTD resolution is relevant. XSLT processors have to load the
external DTD to resolve entities and perhaps supply default attribute
values. The XPath 1.0 data model simply does not support unresolved
entity references.
XSLT processors don't load the DTD, the XML parser does. If your xml
contains a doctype the only real options are to supply a
CustomURIResolver or use an XML Catalog to point to a local copy.
3. I suppose an XSLT processor might defer loading the DTD until it
finds an entity reference it needs a definition for. But then how does
it handle default attribute values for previously processed elements?
Start over?
XSLT processors don't know about entity references as they are all
resolved by the XML parser... (they aren't part of the XDM)
--
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--