|
Subject: Re: MSXML v. Saxon - whose bug? From: David Carlisle <davidc@xxxxxxxxx> Date: Wed, 13 Sep 2000 14:31:30 GMT |
If the pattern contains multiple alternatives separated by
|, then it is treated equivalently to a set of template
rules, one for each alternative.
If the pattern has the form of a QName preceded by a
ChildOrAttributeAxisSpecifier or has the form
processing-instruction(Literal) preceded by a
ChildOrAttributeAxisSpecifier, then the priority is 0.
If the pattern has the form NCName:* preceded by a
ChildOrAttributeAxisSpecifier, then the priority is -0.25.
Otherwise, if the pattern consists of just a NodeTest
preceded by a ChildOrAttributeAxisSpecifier, then the
priority is
-0.5.
Otherwise, the priority is 0.5.
<xsl:template match="status" />
has priority 0
<xsl:template match="itemStatus/*">
appears to fall through to th elast case and so have priority o.5
me>
me>
me> <xsl:template match="status" />
me>has higher priority than
me> <xsl:template match="itemStatus/*">
hmm 0.5 > 0
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
| Current Thread |
|---|
|
| <- Previous | Index | Next -> |
|---|---|---|
| Re: MSXML v. Saxon - whose bug?, David Carlisle | Thread | Re: MSXML v. Saxon - whose bug?, Francis Norton |
| RE: xslide 0.2b1 XSL mode for Emacs, Pawson, David | Date | XSL transforms and SQL Sever XML Te, Lee Barwick |
| Month |