We seem to agree on everything now.

Do we also agree that the following code does not produce the "Standard
expression to create a string for the path of the current node " ?

> <!-- Standard expression to create a string for the path of the
> current node --> <xsl:variable name='path'>
> /<xsl:for-each select="ancestor::*">
>    <xsl:value-of select="name()"
> />/</xsl:for-each><xsl:value-of select = "name()" />
> </xsl:variable>



=====
Cheers,

Dimitre Novatchev.
http://fxsl.sourceforge.net/ -- the home of FXSL



"Passin, Tom" <tpassin@xxxxxxxxxxxx> wrote in message
news:5D3C2276FD64424297729EB733ED1F7601D1BD1E@xxxxxxxxxxxxxxxxxxxxxx
> [Dimitre Novatchev]>
> > > I think I may have misunderstood here, and perhaps you
> > misunderstood me
> > > as well...  I understood the original question to ask for matching a
> > > __string__ containing a path expression, like "/a/b/c"
> > (that is the kind
> > > of example O thought that Yue Ma showed).  For my own post,
> > I put the
> > > path string into a variable, thinking that it would
> > probably eventually
> > > be sent in via a parameter.
> > >
> > > Re-reading your comment, I notice that you might have
> > thought that I
> > > was selecting a node set into the variable, instead of a string, but
> > > that is not the case.
> >
> > No, I also understand that the variable contains a string.
> >
> > The problem of the expression (1):
> >
> > /a/b/c
> >
> > being generated for the node uniquly matched by (2):
> >
> > /a/b[2]/c[3]
> >
> > is that the former matches more than one node.
> >
>
> You can produce a string like (2) with a modification to the expression
> I gave.  But ...
>
> > Whoever wants to identify a single node will not use (1) ,
> > but an expression
> > equivalent to (2).
> >
>
> Maybe, maybe not  - perhaps the original poster will tell us what he
> really wants to do...
>
> Cheers,
>
> Tom P
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>
>




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