Yes. It's a few lines of easily readable XQuery Update, versus a few
complete XSLT templates and an explanation of how the identity transform
works.
XQuery Update solution:
[snip]
XSLT 2.0 solution:
[snip]
So, what is the prize for the "best" solution? (separate prize for
defining "best" that everyone agrees on)
This is already an old argument... those who use XQuery day in day out
prefer the XQuery solution, those who use XSLT will prefer that (but
if you're modifying a file in an XML database you'd use XQuery, if
you're using the filesystem, probably XSLT). So it doesn't really
matter.
(btw, it's funny that you think an explanation of the identity
template is needed, but not XQuery update syntax? Neither are exactly
intuitive...! )
--
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>
--~--