Subject: Re: [xsl] [XSLT 1.0] Q: recursively eliminate empty nodes From: "G. Ken Holman" <gkholman@xxxxxxxxxxxxxxxxxxxx> Date: Sat, 13 Nov 2010 07:58:41 -0500 |
For XSLT 1.0, I created a table listing these: http://lenzconsulting.com/how-xslt-works/#priority
There are only 6 patterns (not including their alternate "child::" or "attribute::" forms) that have a default priority of -0.5. That's because it's the only default priority level where no names (or steps or filters) are used. XSLT 2.0 adds a few more to the list with the ElementTest and AttributeTest forms.
I just noticed (from here: http://www.w3.org/TR/xslt20/#dt-default-priority) that in XSLT 2.0, "/" has priority -0.5, whereas it has +0.5 in XSLT 1.0.
http://www.w3.org/TR/1999/REC-xslt-19991116#conflict "Patterns less specific than this (patterns that just tests for nodes with particular types) have priority -0.5.
I was surprised to see this. Maybe it has no practical impact (other than invalidating my easy-to-remember rule). Or am I missing something?
-- Contact us for world-wide XML consulting & instructor-led training Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/ G. Ken Holman mailto:gkholman@xxxxxxxxxxxxxxxxxxxx Legal business disclaimers: http://www.CraneSoftwrights.com/legal
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] [XSLT 1.0] Q: recursively, Evan Lenz | Thread | Re: [xsl] [XSLT 1.0] Q: recursively, Evan Lenz |
Re: [xsl] [XSLT 1.0] Q: recursively, Evan Lenz | Date | Re: [xsl] getting the child element, ram |
Month |