Re: [xsl] Embedding the XPath of an input Text Fragment in output

Subject: Re: [xsl] Embedding the XPath of an input Text Fragment in output
From: David Carlisle <davidc@xxxxxxxxx>
Date: Thu, 12 Jun 2008 17:00:12 +0100
Wendell
> 
>    <xsl:template match="*" mode="xpath-step">
>      <xsl:text>/</xsl:text>
>      <xsl:value-of select="name()"/>
>      <xsl:if test="count(../*[name()=name(current())]) > 1">
>        <xsl:text>[</xsl:text>
>        <xsl:value-of 
> select="count(preceding-sibling::*[name()=name(current())]) + 1"/>
>        <xsl:text>]</xsl:text>
>      </xsl:if>
>    </xsl:template>


The schematron sources have several variants of this, targetting
different use cases. using name() is fine for human-oriented paths in
error reprorting etc, but if you need to execute the paths the problem
is thatit uses namespace prefixes from the  source file, so you need to
bind the same prefixes in the context that the xpath is executed.

   <xsl:template match="*" mode="xpath-step">
     <xsl:text>/*</xsl:text>
     <xsl:if test="count(../*) > 1">
       <xsl:text>[</xsl:text>
       <xsl:value-of select="count(preceding-sibling::*) + 1"/>
       <xsl:text>]</xsl:text>
     </xsl:if>
   </xsl:template>

makes xpaths that are a bit less informative to a human reader  /*[33]
instead of /xhtml:table[2]  but don't have a dependency on namespace
context.

(variants of this generate /*[local-name()='table'][2] or (for xpath 2)
/*:table[2] if you want a version which shows the variable name but
without namespace dependency)

David

________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.

This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs. 
________________________________________________________________________

Current Thread