On 8/16/06, Michael Kay <mike(_at_)saxonica(_dot_)com> wrote:
There's no direct support for composite grouping keys in xsl:for-each-group.
The simplest solution is to form the composite key yourself. The following
looks promising:
group-by="string-join(@*, '|')"
but is wrong, because the result depends on attribute order.
I think it's conceivable that two different XSLT processors could
return attributes in a different order.... but the same processor on
the same run? In this instance as long as the order is consistent per
transform then everything would be ok. Changing the read technique
mid-transform would be a bit strange, even if it was conformant (or am
I wide of the mark here, and the order the parser reports the
attributes is significant?)
--~------------------------------------------------------------------
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>
--~--