Re: XPath grammar questions
The first case is in a path submitted by Tobias Reif, that originated, as I recall, from someone on this list:No, it says that *required* type of the argument must be boolean. Generally that is FunctionCall production (see http://www.w3.org/TR/xpath.html#NT-FunctionCall):
"A FunctionCall expression is evaluated by using the FunctionName to identify a function in the expression evaluation context function library, evaluating each of the Arguments, converting each argument to the type required by the function, and finally calling the function, passing it the converted arguments."
An argument is converted to boolean type "as if by calling boolean function".
The second (and at this point, more critical) problem I'm having is with function names. Take:
No, it shouldn't.
"normalize-space" is NCName itself and according to the spec "When tokenizing, the longest possible token is always returned.", so lexer must parse it as FunctionName according to "If the character following an NCName (possibly after intervening ExprWhitespace) is (, then the token must be recognized as a NodeType or a FunctionName."
No, lexer must return the longest token, which is "normalize-space" as NCName.
-- Oleg Tkachenko Multiconn International, Israel
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format