This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: result tree fragments and node-sets
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: Re: [xsl] result tree fragments and node-sets
- From: "Chris Nolte" <nolte at silicon-age dot com>
- Date: Fri, 6 Jul 2001 11:34:15 -0700
- Organization: Silicon Age, Inc.
- References: <000a01c10647$158a89d0$6b4f3c3e@PCUKMKA>
- Reply-To: xsl-list at lists dot mulberrytech dot com
> > <xsl:template name='foo'>
> > <xsl:variable name='temp0'>
> > <xsl:apply-templates mode='zero'>
> > </xsl:variable>
> > <xsl:variable name='temp1'>
> > <xsl:apply-templates select='$temp0' mode='one'>
> > </xsl:variable>
> > <xsl:variable name='temp2'>
> > <xsl:apply-templates select='$temp1' mode='two'>
> > </xsl:variable>
> > <xsl:copy-of select='$temp2' />
> > </xsl:template>
> >
> You can do this according to the XSLT 1.1 Working Draft but not according
to
> XSLT 1.0. In most XSLT processors the last apply-templates has to be
> <xsl:apply-templates select="xx:node-set($temp1)"/>
> where xx refer's to the vendor's extension library prefix.
Why the last apply-templates and not the second one? (mode='one')
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list