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

> Yes. I admit, I did use an example from a dated xsl description. Please
> do not be misled by the details.

yes function arguments are evaluated before being passed to the function
so have to evaluate to one of the XPath types. A Qname would evaluate to
the node set produced by selecting child element nodes of that name.

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 apathexpression?
    • From: james anderson <james.anderson@a...>

• References:
  • an xpath/xsl question: why must arguments be path expressions?
    • From: james anderson <james.anderson@a...>
  • Re: an xpath/xsl question: why must arguments be path expressions?
    • From: David Carlisle <davidc@n...>
  • Re: an xpath/xsl question: why must (a QName in an) argument be a pathexpression?
    • From: james anderson <james.anderson@a...>

• Prev by Date: Re: URIs and information typing
• Next by Date: Re: an xpath/xsl question: why must (a QName in an) argument be apathexpression?
• Previous by thread: Re: an xpath/xsl question: why must (a QName in an) argument be a pathexpression?
• Next by thread: Re: an xpath/xsl question: why must (a QName in an) argument be apathexpression?
• Index(es):
  • Date
  • Thread