burtonator <[EMAIL PROTECTED]> wrote:
> True... but why?
An unknown extension has to be distinguished from a literal result element.
So, if Xalan sees a Saxon extension element, it needs to be able to ignore
it, not treat it as a literal result element. (note: "An XSLT processor
must not signal an error merely because a template contains an extension
element for which no implementation is available."
[http://www.w3.org/TR/xslt#extension-element]).
Also, the processor must know that it is an extension element so that it
can execute the xsl:fallback children: "However, when an XSLT processor
performs fallback for an instruction element, if the instruction element
has one or more xsl:fallback children, then the content of each of the
xsl:fallback children must be instantiated in sequence; otherwise, an error
must be signaled." [http://www.w3.org/TR/xslt#fallback]
And, in any case, it is mandated by the XSLT recommendation, so it can not
be up to us to make up rules... otherwise a XSLT stylesheet with Xalan
extensions would cease to be an XSLT stylesheet.
-scott
