Hi
Jarno(_dot_)Elovirta(_at_)nokia(_dot_)com wrote:
<xsl:template match="SubConcepts">
<xsl:copy>
<xsl:apply-templates select="@*"/>
<xsl:for-each select="descendant::SubConcept">
<xsl:copy>
<xsl:apply-templates select="@*"/>
<xsl:apply-templates select="*[1]" mode="walker"/>
</xsl:copy>
</xsl:for-each>
</xsl:copy>
</xsl:template>
<snip/>
Donno what that grouping method is called, but it's one of the ones that you
encounter if you search the list archives.
Cheers,
Jarno - Madam Zu: September 2002 Mix
So just for my clarification. Is this piece of code meant to sort out
the XML structure once the output has been generated? In other words,
will this piece of code form part of Processor2.xsl (as shown below) ?
Input.xml --> Processor1.xsl --> Output1.xml --> Processor2.xsl -->
FinalOutput.xml
Appreciate your help
Rahil
--~------------------------------------------------------------------
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>
--~--