[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: james anderson <firstname.lastname@example.org>
- To: email@example.com
- Date: Thu, 08 Mar 2001 19:35:37 +0100
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
 FunctionCall ::= FunctionName '(' ( Argument ( ',' Argument )* )? ')'
 Argument ::= Expr
which subsumes a QName in the following forms only
 FunctionName ::= QName - NodeType
 VariableReference ::= '$' QName
 NameTest ::= '*' | NCName ':' '*' | QName
Am I missing something?
ps. Is there a source for concise, up-to-date examples for
XPath/XPointer/XSL pattern expressions?
David Carlisle wrote:
> > 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
> in Xpath.
> This message has been checked for all known viruses by Star Internet delivered
> through the MessageLabs Virus Control Centre. For further information visit