According to your description "it doesn't define which order
the conditions are applied in" the preceding stylesheet may
rightfully fail. However, in the more extreme case, when $doc
does not contain element b, but some other document available
(or will be available) do contains element b, egnine is
allowed to fail also.
This looks bizarre.
Yes. Unfortunately the error behaviour of XSLT and XPath have not really
been formalized in such a way as to guarantee interoperability. The same
applies to limits: there's nothing in the spec to stop an implementation
failing if a string is longer than 16 characters. In both cases, the spec
essentially leaves it to implementors and users to come to a consensus about
what behaviour is reasonable and what isn't.
In the case of xsl:key, I think it would be wise to make the use expression
error-free.
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
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>
--~--