This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: sorting by attribute + element vs attribute
- To: "'xsl-list at mulberrytech dot com'" <xsl-list at mulberrytech dot com>
- Subject: RE: sorting by attribute + element vs attribute
- From: "Pawson, David" <DPawson at rnib dot org dot uk>
- Date: Mon, 28 Feb 2000 08:18:18 -0000
- Reply-To: xsl-list at mulberrytech dot com
Steve Muench
>How about:
>
><wrapper xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>xsl:version="1.0">
> <xsl:for-each select="sender/a">
> <xsl:sort select="@clli"/>
> <a><xsl:value-of select="@clli"/></a>
> <b><xsl:value-of select="@b"/></b>
> </xsl:for-each>
></wrapper>
>
>This produces:
>
><wrapper><a>100</a><b>10</b><a>200</a><b>20</b></wrapper>
Thanks Steve.
I knew the current context changed within for-each,
I made the wrong assumption that is also changed
(to the attribute) within the sort, which I had not
written as an empty element.
===============
I keep tripping up over 'attribute vs element content'
problems. I.e. when to use the empty element, when
to have it contain something; hence my amazement
at Davids use of variable last week.
Am I right in thinking this is one of XSLT's more
subtle aspects, left to the user to work out?
Regards, DaveP
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list