Re: [xsl] Matching attribute with condition in predicate

Subject: Re: [xsl] Matching attribute with condition in predicate
From: "G. Ken Holman" <gkholman@xxxxxxxxxxxxxxxxxxxx>
Date: Tue, 22 Dec 2009 09:53:07 -0500
At 2009-12-22 17:44 +0300, PP8QP0P8P; P!P0P1QQP5P=P:P>P2 wrote:
I make two-pass transformation in my XSL using exsl:node-set (libxslt).
  <xsl:template match="tree">
    <node attr="foo"/>
  <xsl:template match="@attr[/root/@condition='ru']" mode="parse">
Last template should (i hope so) match my @attr 'cause it's more exact.

(note below)

And it's working w/o predicate.

But it doesn't with.

Any thoughts why?

Because the "/" at the start of "/root/@condition" is the top of the _current tree_, not the top of the initial tree. Thus it is at the top of the tree with the attribute because it is in the predicate tested when the attribute is the current node.

You want a global variable something like:

<xsl:variable name="orig" select="/"/>

... and then in your predicate
@attr[$orig/root/@condition='ru'] in order to
switch to the original tree from your temporary tree.

The note about "more exact" is that is too
general a statement.  Everything more complex
than a simple name all have the same
priority.  The priority doesn't somehow steadily
increase with more and more information.

So, yes, "@attr[$orig/root/@condition='ru']" has
higher priority than "@attr" but it does not have
higher priority than, say,
which is at the same numeric level of priority of .5.

I hope this helps.

. . . . . . . Ken

UBL and Code List training:      Copenhagen, Denmark 2010-02-08/10
XSLT/XQuery/XPath training after 2010-03-15/19
XSLT/XQuery/XPath training:   San Carlos, California 2010-04-26/30
Vote for your XML training:
Crane Softwrights Ltd.
Training tools: Comprehensive interactive XSLT/XPath 1.0/2.0 video
Video lesson:
Video overview:
G. Ken Holman                 mailto:gkholman@xxxxxxxxxxxxxxxxxxxx
Male Cancer Awareness Nov'07
Legal business disclaimers:

Current Thread