Re: [xsl] xsl:key() and $variables.

[Steve <subsume@xxxxxxxxx>]

The plural goalpost you mention is actually the same goalpost. =)

Your solution was wonderful, but I failed to mention that one tree
happens to be contained in a variable via the document function. I
haven't since received any kind of specific help for this peculiar
need.

I'm not too keen on what you mean by 'pushing a result tree fragment',
but I can guarantee you I'm using 1.0.

-Steve

On 7/22/06, M. David Peterson <m.david@xxxxxxxxxx> wrote:
> It seems we crossed wires, Ken...  Wish I would have read your reply
> first, before hitting send.  Oh well, such is life :)
>
> G. Ken Holman wrote:
>
> > At 2006-07-21 15:54 -0400, Steve wrote:
> >
> >> Anyone have a 1.0 interpretation of this?
> >>
> >>>    <xsl:apply-templates
> >>>      select="key('records',
> >>>                  key('activities',
> >>>                      'yes',
> >>>                      document('blah.xml')),
> >>>                  $records)"/>
> >>
> >
> > I gave you one:
> >
> >   http://www.biglist.com/lists/xsl-list/archives/200607/msg00515.html
> >
> > but then you said "the <people> tree is actually a variable" in:
> >
> >   http://www.biglist.com/lists/xsl-list/archives/200607/msg00529.html
> >
> > and then you said "I have a variable containing <Records>" and
> > "<xsl:apply-templates select="$variable/..." in:
> >
> >   http://www.biglist.com/lists/xsl-list/archives/200607/msg00603.html
> >
> > Since you can't push a result tree fragment variable in XSLT 1.0, you
> > seem to obviously be using XSLT 2.0.
> >
> > So, since you are using XSLT 1.0, you cannot push a result tree
> > fragment variable, so you are back to using files, which is the answer
> > I already provided.
> >
> > We're only trying to help here ... you keep moving the goalposts.
> >
> > . . . . . . . . . . Ken