Re: [www-voice] <none>

Jon,

   One of the main reasons that the XPath data model was removed from 
the final draft of the specification was because there wasn't agreement 
on the underlying data structures.   In particular, the wasn't agreement 
on what XPath XSLT file should produce as output.   As a result, the 
existing XSLT file for Xpath is just a first cut that was never 
completed.  If you are working on an XPath data model for SCXML, you 
should define the data structures as you see fit and produce your own 
XSLT transformations.

- Jim

On 5/1/2016 5:02 PM, Jon Kerny wrote:
> Hi,
>
> I've been looking at test354.txml 
> <https://www.w3.org/Voice/2013/scxml-irp/354/test354.txml> in the 
> scxml irp. For xpath it makes use of a template implemented like this:
>
> <xsl:templatematch="//@conf:eventDataNamelistValue">
> <xsl:attributename="expr">
> $_event/data/data[@id='Var
> <xsl:value-ofselect="."/>
> ']/data/text()
> </xsl:attribute>
> </xsl:template>
>
> It creates an expression like this:
>
> expr="$_event/data/data[@id='Var1']/data/text()"
>
> I don't understand why there should be three levels of data?
>
> The first is from event, ok.
> The second is from 2.7.1 in the xpath specification, ok
>
> But why is there a third data element?
>
> Why isn't a template below used?
>
> <xsl:templatematch="//@conf:eventDataNamelistValue">
> <xsl:attributename="expr">
> $_event/data/data[@id='Var
> <xsl:value-ofselect="."/>
> ']/text()
> </xsl:attribute>
> </xsl:template>
>
> Where in the specifications does it say that there should be a 
> event/data/data[@id='']/data/ structure when using xpath?
>
> For ecmascript the template looks like:
>
> <xsl:templatematch="//@conf:eventDataNamelistValue">
> <xsl:attributename="expr">
> _event.data.Var
> <xsl:value-ofselect="."/>
> </xsl:attribute>
> </xsl:template>
>
> I cannot understand why there is a difference.
>
> Best regards,
>
> Jon
>
>