This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: MSXML v. Saxon - whose bug?
- To: "'xsl-list at mulberrytech dot com'" <xsl-list at mulberrytech dot com>
- Subject: RE: MSXML v. Saxon - whose bug?
- From: Kay Michael <Michael dot Kay at icl dot com>
- Date: Wed, 13 Sep 2000 14:56:01 +0100
- Reply-To: xsl-list at mulberrytech dot com
> The following XML and XSL produces one more output element in
> Saxon 5.4
> than in MSXML3 July download - listings follow (with some removeal of
> blank lines):
> <xsl:template match="status" />
> <xsl:template match="itemStatus/status" />
> <xsl:template match="itemStatus/*">
> <attribute name="{name(.)}"><xsl:value-of
> select="text()"/></attribute>
> </xsl:template>
>
The second and third template rules above both match the <status> element.
This is technically an error. The processor is allowed to recover from this
error by choosing the template rule that comes last in the stylesheet, which
is what Saxon is doing. MSXML appears to be applying the itemStatus/status
rule, which I think is definitely incorrect.
But really you should be giving these rules explicit priorities.
Mike Kay
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list