xsl-list
[Top] [All Lists]

RE: [xsl] xsltproc/LibXSLT - non-compliance?

2008-04-30 18:06:38
Well, in this case the argument *does* evaluate to a string 
that is a 
QName. It consequently matches the quoted description.

No, it evaluates to a nodeset with one node whose string 
value matches QName. That is not the same as evaluating to a string.

Is this interpretation of your words correct?
yes

And the definitions of element-available() and function-available() 
don't say that much, so you can't rely on automatic 
conversion to just 
happen.

Yes, although to be honest I would expect them to happen in 
this case (as apparently would implementors of other xslt 
systems.)

Section 3.2 of XPath 1.0 (function calling) says that the supplied argument
is converted to the required type, which in this case is string. The second
argument of key() is different because the declared type is "object".

Michael Kay
http://www.saxonica.com/


--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--