Re: [xsl] Nested Muenchian Grouping

["Dimitre Novatchev" <dnovatchev@xxxxxxxxx>]

GRouping with many levels could become complicated, because the keys
to be used with the Muenchian method must be concatenations of several
simple grouping keys.

I guess you can find many examples of using the Muenchian method for
grouping on two levels, but very few examples for using it for
grouping on many levels.

THis is why I would recommend as an alternative (which in some cases
will be noticeably slower) the following method for grouping with
potentially unlimited number of levels:

  http://www.oxygenxml.com/archives/xsl-list/200412/msg01032.html

    <xsl:call-template name="RecursiveGrouping">
       <xsl:with-param name="list" select="book"/>
       <xsl:with-param name="attrList" select="/*/book[1]/@*"/>
     </xsl:call-template>

All grouping is supposed to happen on the values of different
attributes, which are passed via the parameter "attrList"

The elements to be grouped using these attribute values are passed
using the parameter "list"

It would be good to construct the node-set for the "attrList"
parameter in such a way that the attribute nodes are in the desired
order.


--
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
---------------------------------------
To invent, you need a good imagination and a pile of junk
-------------------------------------
You've achieved success in your field when you don't know whether what
you're doing is work or play



On 10/4/06, Minervini, Chris <christopher.minervini@xxxxxxxxxx> wrote:
> I need to turn this:
>
> <test>
>        <group>
>                <player name="joe" position="pitcher" team="mets"
> state="ny">2</player>
>                <player name="mark" position="outfielder" team="mets"
> state="ny">11</player>
>                <player name="john" position="pitcher" team="mets"
> state="ny">23</player>
>                <player name="pete" position="outfielder" team="mets"
> state="ny">27</player>
>                <player name="roy" position="outfielder" team="mets"
> state="ny">13</player>
>                <player name="carl" position="infielder" team="mets"
> state="ny">32</player>
>        </group>
> </test>
>
> Into something like this:
>
> <group>
>        <state name="ny">
>                <team name="mets">
>                        <position name="pitcher">
>                                <player name="joe" number="2"/>
>                                <player name="john" number="23"/>
>                        </position>
>                        <position name="outfielder">
>                                <player name="mark" number="11"/>
>                                <player name="pete" number="27"/>
>                                <player name="roy" number="13"/>
>                        </position>
>                        <position name="infielder">
>                                <player name="carl" number="32"/>
>                        </position>
>                </team>
>        </state>
> </group>
>
> Assuming there can be many states, many teams and many positions
>
> I tried to nest the Muenchian method like this:
>
> <xsl:key name="state-grouping" match="player" use="@state"/>
> <xsl:key name="team-grouping" match="player" use="@team"/>
> <xsl:key name="position-grouping" match="player" use="@position"/>
>
> <xsl:template match="test/group">
>        <group>
>                <xsl:for-each select="player[count(. |
> key('state-grouping', @player_ownership_details)[1]) = 1]">
>                        <xsl:variable name="state" select="@state"/>
>                        <xsl:variable name="state_node_set"
> select="../player[@state=$state]"/>
>                        <state name="{$state}">
>                                <xsl:for-each
> select="$state_node_set[(count(. | key('team-grouping', @team)[1]) =
> 1)]">
>                                        <xsl:variable name="team"
> select="@team"/>
>                                        <xsl:variable
> name="team_node_set" select="$state_node_set[@team = $team]"/>
>                                        <team name="{$team}">
>                                                <xsl:for-each
> select="$team_node_set[(count(. | key('position-grouping',
> @position)[1]) = 1)]">
>                                                        <xsl:variable
> name="position" select="@position"/>
>                                                        <xsl:variable
> name="position_node_set" select="$team_node_set[@position =
> $position]"/>
>                                                        <position
> name="{$position}">
>
> <xsl:for-each select="$position_node_set">
>
> <player name="{@name}" number="{.}" />
>
> </xsl:for-each>
>                                                        </position>
>                                                </xsl:for-each>
>                                        </team>
>                                </xsl:for-each>
>                        </state>
>                </xsl:for-each>
>        </group>
> </xsl:template>
>
> But it doesn't produce the correct output when I add more data (more
> teams, position, etc.)
>
> Am I using the muenchian method correctly?  Is this something that can
> be done?  I've been working on a solution all day (with more complicated
> data) and I can't seem to get it to work.  Anyone out there ever pull
> off something like this?
>
>
> ------------------------------------------------------------------------------
> This message is intended only for the personal and confidential use of the designated recipient(s) named above.  If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited.  This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers.  Email transmission cannot be guaranteed to be secure or error-free.  Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such.  All information is subject to change without notice.
>
> --------
> IRS Circular 230 Disclosure:
> Please be advised that any discussion of U.S. tax matters contained within this communication (including any attachments) is not intended or written to be used and cannot be used for the purpose of (i) avoiding U.S. tax related penalties or (ii) promoting, marketing or recommending to another party any transaction or matter addressed herein.