Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


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

From: "Michael Kay" <mike@------------>
To:
Date: 5/1/2008 1:07:00 AM
> > 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/


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent