- From: <bugzilla@jessica.w3.org>
- Date: Mon, 23 Mar 2015 16:07:36 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20843
Tim Mills <tim@cbcl.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CLOSED |REOPENED
Resolution|FIXED |---
--- Comment #3 from Tim Mills <tim@cbcl.co.uk> ---
The intent of this test is to
"Test that all functions defined in the F+O 3.0 specification are NOT
implemented in a 2.0 processor."
It expects that no "missing-function" elements will be generated.
A missing-element is generate if a function in the 'fn' namespace is _not_
available.
<xsl:if test="if(@name/starts-with(., 'op')) then
function-available(@name, @arity) else not(function-available(@name, @arity))">
<missing-function name="{@name}" arity="{@arity}"/>
<xsl:message expand-text="yes">*** Missing function name={@name}
arity={@arity}</xsl:message>
</xsl:if>
For the input line:
<function name="fn:node-name" arity="0"/>
one would expect an XSLT 2.0 processor to return false for
function-available("fn:node-name", 0)
and therefore this would generate a missing-function element in the output and
therefore the assertion
<assert>empty(/out/*)</assert>
would fail.
The input data also includes some functions which have been moved from XSLT 2.0
into F&O 3.0 (e.g. format-number).
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 23 March 2015 16:07:38 UTC