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

Re: an xpath/xsl question: why must arguments be path expressions?

• From: David Carlisle <davidc@n...>
• To: james.anderson@a...
• Date: Thu, 08 Mar 2001 11:29:30 +0000 (GMT)

> The result of a literal parse of the xpath expression (from
> WD-xsl-19980818)

Why use such an early draft, which has a syntax completely different
from XPath 1.0 ?

> "list[attribute(ordered)='yes']/item[first-of-type()]"

That would be

 "list[attribute::ordered='yes']/item[1]"

in Xpath.

David

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet delivered
through the MessageLabs Virus Control Centre. For further information visit
http://www.star.net.uk/stats.asp

• Follow-Ups:
  • Re: an xpath/xsl question: why must (a QName in an) argument be a pathexpression?
    • From: james anderson <james.anderson@a...>

• References:
  • an xpath/xsl question: why must arguments be path expressions?
    • From: james anderson <james.anderson@a...>

• Prev by Date: re: an xslt question re modeling namespaces
• Next by Date: Re: an xpath/xsl question: why must arguments be path expressions?
• Previous by thread: an xpath/xsl question: why must arguments be path expressions?
• Next by thread: Re: an xpath/xsl question: why must (a QName in an) argument be a pathexpression?
• Index(es):
  • Date
  • Thread