Altova Mailing List Archives


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

From: Michael Ludwig <mlu@------------->
To:
Date: 4/30/2008 2:06:00 PM
Manfred Staudinger schrieb:
 I'd still be interested to know if (a) there is more to LibXSLT's
 non-conformance
What I posted in a parallel thread
http://www.biglist.com/cgi-bin/wilma/wilma_hiliter/xsl-list@xxxxxxxxxxxxxxxxxxxxxx/200804/msg00515.html?line=8#hilite
may well turn out to be such a non-conformance.

With the context node having the string value of a QName, like
"xsl:number", xsltproc fails on "element-available(.)":

    runtime error: file staudinger.xsl line 56 element value-of
    element-available() : invalid arg expecting a string
    runtime error: file staudinger.xsl line 56 element value-of
    XPath evaluation returned no result.

For xsltproc, you have to explicitly extract the string value by coding
"element-available(string(.))".

At http://www.w3.org/TR/xslt#function-element-available, the spec says:



    Function: boolean element-available(string)
    The argument must evaluate to a string that is a QName.

In this case, LibXSLT is, indeed, not in compliance.



Michael

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.