RE: Question

[Mike Dierken <mike@xxxxxxxxxxxxxxx>]

Paul,
I have also found this to be a problem.
I believe this is conceptually equivalent to a join in traditional
databases.
I feel that a 'context()' method might help in this situation. This
'context()' method would give you access to the DOM node that the current
action was being evaluated against. Access to the node gives you a richer
set of comparisons and data than variables.
I'm currently researching an implementation of this (with the DataChannel
Java based XSL processor) and I had intended to talk with the WG directly,
but your message popped up & I thought I would respond rather than wait.

Mike D
DataChannel



-----Original Message-----
From: Paul Prescod [mailto:paul@xxxxxxxxxxx]
Sent: Wednesday, February 03, 1999 1:13 PM
To: xsl-list@xxxxxxxxxxxxxxxx
Subject: Question


I have data like this:

<CLASS>
  <METHOD name="foo">...</METHOD>
  <METHOD name="bar">...</METHOD>
  <METHOD name="baz">...</METHOD>
  <METHOD name="jaz">...</METHOD>
<DESCRIPTION><METHODREF name="foo"/> is very fooey</DESCRIPTION>
</CLASS>

"foo" is not a globally unique id. I know that it will be unique in the
CLASS however. What I need is to do something like this:

<xsl:template match="METHODREF">
   <xsl:value-of select="ancestor(CLASS)/METHOD[@name=***]">
</xsl:template>

The problem is that at the point of the *** I've lost the context of the
METHODREF and don't have a way to get its @name anymore.
-- 
 Paul Prescod  - ISOGEN Consulting Engineer speaking for only himself
 http://itrc.uwaterloo.ca/~papresco


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