I've used a set of templates that call each other and work their way
down the list, and use parameters to keep the id and name
fields that
I need. I think it works, and I'll test it on some bigger data sets
and see how I go.
That's the right approach. But you don't need to pass parameters for the id
and name fields: you can always navigate back up to them using the parent
and ancestor axes.
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>
--~--