[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Nested Muenchian Grouping

Subject: Re: Nested Muenchian Grouping
From: "Mukul Gandhi" <gandhi.mukul@xxxxxxxxx>
Date: Sat, 7 Oct 2006 23:43:16 +0530
xslt nested position
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="http://www.w3.org/1999/XSL/Transform">

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

<xsl:template match="/test">
 <group>
   <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="{.}"/>
                  </xsl:for-each>
               </position>
            </xsl:for-each-group>
          </team>
        </xsl:for-each-group>
     </state>
   </xsl:for-each-group>
 </group>
</xsl:template>

</xsl:stylesheet>


On 10/5/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.


--
Regards,
Mukul Gandhi

Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.