[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Quick Xpath

• To: "'Eric van der Vlist'" <vdv@d...>
• Subject: RE: Quick Xpath
• From: "Michael Kay" <michael.h.kay@n...>
• Date: Thu, 18 Jul 2002 09:50:45 +0100
• Cc: "'Mark Feblowitz'" <mfeblowitz@f...>,"'Jeni Tennison'" <jeni@j...>,"'Garland foster'" <garland_foster@s...>,"'Dare Obasanjo'" <dareo@m...>,<xml-dev@l...>
• Importance: Normal
• In-reply-to: <1026944989.19731.492.camel@ibook>
• Reply-to: <michael.h.kay@n...>

> What I don't find obvious in the recs is why this "reverse 
> order" property is lost when you assign the node set 
> "preceding-sibling::*" to a variable, but all the XSLT 
> processors seem to behave consistently in this respect.

Actually the "reverse order" property is lost as soon as you step
outside the step containing the reverse axis.

position() returns the position of the context node within some defined
sequence. The sequence depends on where the position() function is used:

* forwards-axis::x[position()=1]
    - position in document order
* reverse-axis::x[position()=1]
    - position in reverse document order
* (node-set)[position()=1]
    - position in document order
* <xsl:for-each><xsl:value-of select="position()">
    - position in document order
* <xsl:for-each><xsl:sort select="x"/><xsl:value-of select="position()">

    - position in sorted order   

Michael Kay
Software AG
home: Michael.H.Kay@n...
work: Michael.Kay@s... 

• References:
  • RE: Quick Xpath
    • From: Eric van der Vlist <vdv@d...>

• Prev by Date: RE: Quick Xpath
• Next by Date: XML and 3D
• Previous by thread: Re: Quick Xpath
• Next by thread: Re: Quick Xpath
• Index(es):
  • Date
  • Thread