Re: [xsl] Nested Muenchian Grouping

Subject: Re: [xsl] Nested Muenchian Grouping
From: "Mukul Gandhi" <gandhi.mukul@xxxxxxxxx>
Date: Sat, 7 Oct 2006 23:43:16 +0530
I am not sure if you are in a position to use XSLT 2.0. But if you
can, this problem is easier to solve using XSLT 2.0.

Here is the solution for the same (tested with Saxon 8.8J):

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0" xmlns:xsl="";>

<xsl:output method="xml" indent="yes" />

<xsl:template match="/test">
   <xsl:for-each-group select="group/player" group-by="@state">
     <state name="{@state}">
        <xsl:for-each-group select="current-group()" group-by="@team">
          <team name="{@team}">
            <xsl:for-each-group select="current-group()" group-by="@position">
               <position name="{@position}">
                  <xsl:for-each select="current-group()">
                    <player name="{@name}" number="{.}"/>


On 10/5/06, Minervini, Chris <christopher.minervini@xxxxxxxxxx> wrote:

I need to turn this:

               <player name="joe" position="pitcher" team="mets"
               <player name="mark" position="outfielder" team="mets"
               <player name="john" position="pitcher" team="mets"
               <player name="pete" position="outfielder" team="mets"
               <player name="roy" position="outfielder" team="mets"
               <player name="carl" position="infielder" team="mets"

Into something like this:

       <state name="ny">
               <team name="mets">
                       <position name="pitcher">
                               <player name="joe" number="2"/>
                               <player name="john" number="23"/>
                       <position name="outfielder">
                               <player name="mark" number="11"/>
                               <player name="pete" number="27"/>
                               <player name="roy" number="13"/>
                       <position name="infielder">
                               <player name="carl" number="32"/>

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">
               <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"
                       <state name="{$state}">
select="$state_node_set[(count(. | key('team-grouping', @team)[1]) =
                                       <xsl:variable name="team"
name="team_node_set" select="$state_node_set[@team = $team]"/>
                                       <team name="{$team}">
select="$team_node_set[(count(. | key('position-grouping',
@position)[1]) = 1)]">
name="position" select="@position"/>
name="position_node_set" select="$team_node_set[@position =

<xsl:for-each select="$position_node_set">

<player name="{@name}" number="{.}" />


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.

Mukul Gandhi

Current Thread