Jim,
Ken's solution is also a good one (assuming he wrote what he intended to
write in his untested code ;-). Note that he's optimized for performance on
the assumption the nodes are correctly ordered in the input. If they're
not, his solution will be slow on large datasets compared to mine, but it
has the advantage of not caring how many levels deep you have to go.
(Except for the output element naming bit: tricky, that. If you could name
them 'Level2Category' instead of 'LevelTwoCategory', etc., this problem
would go away).
Cheers,
Wendell
At 04:49 PM 3/26/2003, he wrote:
Untested but try the following approach
<xsl:template match="Categories">
<Categories>
<xsl:apply-templates
select="Category[length(string(Code))=1]" />
</Categories>
</xsl:template>
<xsl:template match="Category">
<xsl:variable name="code" select="string(Code)"/>
<xsl:variable name="code-length" select="length(string(Code))"/>
<xsl:variable name="name">
<xsl:choose>
<xsl:when
test="length(string(Code))=1">LevelOneCategory</xsl:when>
...etc
</xsl:choose>
</xsl:variable>
<xsl:element name="{$name}" Code="{$code}"
Description="{Description}">
<xsl:apply-templates
select="following-sibling::Category[substring(string(Code),1,$code-length)=string($code)]"
/>
</xsl:element>
</xsl:template>
following-sibling:: could be replaced with ../ if the order is not guaranteed.
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list