RE: pattern selection for outside the context node

["Vun Kannon, David" <dvunkannon@xxxxxxxx>]

We have had a similar problem. In our case, we visited a node, then followed
an ID attribute into another part of the node tree. To refer back to the
first node, we had to create a variable to store a pointer to that node and
then pass that variable down through all the template applications.
Cheers,
David vun Kannon
Manager, KPMG LLP

-----Original Message-----
From: Aaron Fischer [mailto:fischer17@xxxxxxxx]
Sent: Thursday, July 08, 1999 7:30 PM
To: java-xml-interest@xxxxxxxxxxxx; xml-dev-digest@xxxxxxxx;
xsl-list-digest@xxxxxxxxxxxxxxxx
Subject: Q: pattern selection for outside the context node


Hey everyone.  I have a data-driven XSL transformation script.  In other
words, I have a whole bunch of templates, one for every kind of element in
each level of the XML tree, with each template calling
<xsl:apply-templates/> on its children.

My problem is, within certain templates, I want to reference data in
certain elements located elsewhere in the XML tree.  However, when this
template is called upon, the context node is such that the element I want
to reference is NOT a descendant of the context node;  i.e. it's somewhere
else above, in the XML tree;  and at the moment it stands as inaccessible

Is there a pattern syntax for starting at the root or going above the
context node, up into the XML tree?  Every pattern selection I've tried is
always evaluated from the context node, which is the very thing I want to
bypass.  Is there a way to directly assign the value of the context node?

All help appreciated,

Aaron


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
*****************************************************************************
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. 

If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawful. When addressed to our clients any opinions or advice
contained in this email are subject to the terms and conditions expressed in
the governing KPMG client engagement letter.         
*****************************************************************************


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