• From: james anderson <james.anderson@a...>
• To: xml-dev@l...
• Date: Fri, 09 Mar 2001 00:44:03 +0100

David Carlisle wrote:
> 
> > 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.
> 

Aha. Ok. So that is, in fact, the nature of the XPath-World. Still, I'm
surprised that QNames, as important as they are, then cannot be passed
to functions. So be it.


thanks...

• Follow-Ups:
  • Re: an xpath/xsl question: why must (a QName in an) argument be apathexpression?
    • From: David Carlisle <davidc@n...>

• 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...>
  • Re: an xpath/xsl question: why must (a QName in an) argument be a pathexpression?
    • From: David Carlisle <davidc@n...>

• Prev by Date: Re: an xpath/xsl question: why must (a QName in an) argument be a pathexpression?
• Next by Date: Re: URIs and information typing
• 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