In the case of node-set(), however, it is just about the commonest
extension function out there (most processors have a version of it), so
(given you have to mind your namespace bindings and all that) it's still
quite portable. Also, its functionality will be built into XSLT/XPath 2.0,
which also mitigates the problem of application-dependency over the longer
term (not that there won't be adjustments to make).
ok. so I'll be able to build a tree in 2.0 also. but you had said that it
would be transparent. do you feel that vendors of 2.0 will still support
node-set() usage? (I guess we can ask michael kay about saxon, at least).
also, leaving aside compatibility issues, what do you think about
constructing a tree within one xslt vs. having a 2-step transform?
abie
_________________________________________________________________
Compare Cable, DSL or Satellite plans: As low as $29.95.
https://broadband.msn.com
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list