Are you saying earlier versions of Saxon 6 silently converted
a result tree fragment to a node-set? That would have been a bug.
It's a long time ago so my memory may be hazy, but I think there was a time
when Saxon releases aimed to conform to the draft XSLT 1.1 specification and
not to XSLT 1.0. Later they reverted to XSLT 1.0 conformance when the plug
was pulled on 1.1. So it wasn't a bug, it was a design decision.
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>
--~--