[Bug 8217] [XSLT] Confusing text on function conversion rules for sequence constructors

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8217





--- Comment #1 from Michael Kay <mike@saxonica.com>  2009-11-06 14:51:22 ---
A better fix might be to make the definition into a real definition, and add a
clarifying note: change

[Definition: Except where otherwise indicated, the actual value of an
expression is converted to the required type using the function conversion
rules. These are the rules defined in [XPath 2.0]  for converting the supplied
argument of a function call to the required type of that argument, as defined
in the function signature. The relevant rules are those that apply when XPath
1.0 compatibility mode  is set to false.]

to

[Definition: When used in this specification without further qualification, the
term <term>function conversion rules</term> means the function conversion rules
defined in [XPath 2.0], applied with XPath 1.0 compatibility mode set to
false.]

Note: These are the rules defined in [XPath 2.0] for converting the supplied
argument of a function call to the required type of that argument, as defined
in the function signature. The same rules are used in XSLT for converting the
value of a variable to the declared type of the variable, or the result of
evaluating a function or template body to the declared type of the function or
template. They are also used when parameters are supplied to a template using
<xsl:with-param>. In all such cases, the rules that apply are the XPath 2.0
rules without XPath 1.0 compatibility mode. The rules with XPath 1.0
compatibility mode set to true are used only for XPath function calls, and for
the operands of certain XPath operators.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 6 November 2009 14:51:24 UTC