[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: an xpath/xsl question: why must (a QName in an) argument be a pathexpression?
- From: Matt Sergeant <matt@sergeant.org>
- To: james anderson <james.anderson@attglobal.net>
- Date: Thu, 08 Mar 2001 19:36:02 +0000 (GMT)
On Thu, 8 Mar 2001, james anderson wrote:
>
> Yes. I admit, I did use an example from a dated xsl description. Please
> do not be misled by the details.
>
> The question remains, is it intended, that a QName never appear in an
> argument list as such? The XPath grammar says only
>
> [16] FunctionCall ::= FunctionName '(' ( Argument ( ',' Argument )* )? ')'
> [17] Argument ::= Expr
>
> which subsumes a QName in the following forms only
>
> [35] FunctionName ::= QName - NodeType
> [36] VariableReference ::= '$' QName
> [37] NameTest ::= '*' | NCName ':' '*' | QName
>
> Am I missing something?
The fact that NameTest can be a QName?
example, function(qname, qname), in XML::XPath parses to:
(function((child::qname),(child::qname)))
--
<Matt/>
/|| ** Founder and CTO ** ** http://axkit.com/ **
//|| ** AxKit.com Ltd ** ** XML Application Serving **
// || ** http://axkit.org ** ** XSLT, XPathScript, XSP **
// \\| // ** mod_perl news and resources: http://take23.org **
\\//
//\\
// \\