RE: Question

Subject: RE: Question
From: "Vun Kannon, David" <dvunkannon@xxxxxxxx>
Date: Thu, 4 Feb 1999 08:58:17 -0500
This problem is why I suggested earlier on the list a "follow(href)"
function. My choice of syntax for the pointer is, of course, the syntax of
select patterns, not the current XPointer syntax. It would probably be
appropriate to follow the pattern of id() and xsl:id to make the stylesheet
aware of which attributes were link attributes if there was no clue from the
David vun Kannon
Manager, KPMG LLP

> -----Original Message-----
> From:	Paul Prescod [SMTP:paul@xxxxxxxxxxx]
> Sent:	Wednesday, February 03, 1999 4:13 PM
> To:	xsl-list@xxxxxxxxxxxxxxxx
> Subject:	Question
> I have data like this:
>   <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
> "Remember, Ginger Rogers did everything that Fred Astaire did,
> but she did it backwards and in high heels."
>                                                --Faith Whittlesey
>  XSL-List info and archive:

 XSL-List info and archive:

Current Thread