• To: xml-dev@l...
• Subject: Re: XPath brain teaser
• From: Richard Tobin <richard@c...>
• Date: Wed, 27 Aug 2003 01:56:23 +0100 (BST)
• Cc:
• In-reply-to: <0b1301c36c23$36de0140$6401a8c0@snobird>
• Organization: HCRC, University of Edinburgh

>This is easier to understand if you think of it in terms of set construction
>and iterators. The two expressions with abbreviations eliminated are:
>
>/descendant-or-self::node()/para[1]
>/descendant::para[1]

You might ask why // means the first of these, rather than the more
obvious second.  The answer (I think) is precisely so that expressions
like //para[1] will mean what they do; it's more common to want to
treat the first paragraph in each section specially than the first
paragraph in the while document.

-- Richard

• Follow-Ups:
  • Re: XPath brain teaser
    • From: Jonathan Robie <jonathan.robie@d...>
  • Re: XPath brain teaser
    • From: "Bob Foster" <bob@o...>

• References:
  • Re: XPath brain teaser
    • From: "Bob Foster" <bob@o...>

• Prev by Date: Re: XML CMM and ISO9000 compliance? - was A standard approach to glueing together reusableXML fragments in prose?
• Next by Date: Re: XML CMM and ISO9000 compliance? - was A standard approach to glueing together reusableXML fragments in prose?
• Previous by thread: Re: XPath brain teaser
• Next by thread: Re: XPath brain teaser
• Index(es):
  • Date
  • Thread