Can't comment on whether it's a 'Microsoft extension' because I have
only used their parser stuff. As to where it came from, I just tried it
one day and it worked, and I never found anything very explicit in the
XSL 1.0 draft that said it shouldn't.

Admittedly, now you've drawn my attention to it, I can see that Appendix
A *doesn't* allow it - both in XSL and XSLT - so I absolutely promise
that I will never, ever, use it again.

Honest.

Regards,

Mark

PS I shall miss it. I think it keeps things quite neat.

> -----Original Message-----
> From: Kay Michael 
> Sent: 25 May 1999 10:26
> To: 'xsl-list@xxxxxxxxxxxxxxxx'
> Subject: RE: select nodes only one level with same name
> 
> 
> > Mark Birbeck [mailto:Mark.Birbeck@xxxxxxxxxxxxx] suggested:
> > 
> > <xsl:template match="/">
> >     <xsl:apply-templates>
> >         <xsl:template match="operation">
> >             do something for level 1 ...
> >             <xsl:apply-templates>
> >                 <xsl:template match="operation">
> >                     before doing something for level 2
> >                 </xsl:template>
> >             </xsl:apply-templates>
> >         </xsl:template>
> >     </xsl:apply-templates>
> > </xsl:template>
> > 
> Where on earth does this come from? (Not another Microsoft extension,
> surely?)
> The April XSLT WD allows only xsl:sort and xsl:param to appear within
> xsl:apply-templates.
> 
> Mike Kay
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list