• From: David Carlisle <davidc@n...>
• To: "Costello, Roger L." <costello@m...>
• Date: Mon, 26 Sep 2011 14:07:07 +0100

On 26/09/2011 13:54, Costello, Roger L. wrote:
> XSLT takes a different perspective. XSLT takes the perspective that markup is a definition. For example, the following XSLT makes this definition: "For each cost element, c, c is greater than 0":
>
> <xsl:for-each select="//cost">
>      <xsl:variable name="c" select="xs:integer(.)" />
>      <xsl:value-of select="c&gt; 0" />
> </xsl:for-eac

It does?? That's rather a strange reading of that piece of code.

xslt uses many diffferent meanings of parent/child.
there isn't much in common in the relationships shown by

xsl:stylesheet/xsl:template

xsl:template/xsl:param

xsl:for-each/xsl:sort

xsl:for-each/xhtml:p

David



-- 
google plus: https:/profiles.google.com/d.p.carlisle

________________________________________________________________________
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. 
________________________________________________________________________

• Follow-Ups:
  • RE: When you create a markup language, what do yourparent elements mean? What do your children elements mean?
    • From: "Costello, Roger L." <costello@m...>

• References:
  • When you create a markup language, what do your parent elementsmean? What do your children elements mean?
    • From: "Costello, Roger L." <costello@m...>