W3C home > Mailing lists > Public > public-qt-comments@w3.org > March 2015

[Bug 28371] New: [xslt30] XTTE0790 vs XPTY0004

From: <bugzilla@jessica.w3.org>
Date: Mon, 30 Mar 2015 08:15:27 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28371-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28371

            Bug ID: 28371
           Summary: [xslt30] XTTE0790 vs XPTY0004
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: mike@saxonica.com
        QA Contact: public-qt-comments@w3.org

XSLT 3.0 says (in 10.3.2, describing xsl:function/@param):

The as attribute of the xsl:param element defines the required type of the
parameter. The rules for converting the values of the actual arguments supplied
in the function call to the types required by each xsl:param element are
defined in [XPath 3.0]. The rules that apply are those for the case where XPath
1.0 compatibility mode is set to false.

[ERR XTTE0790] If the value of an argument to a stylesheet function cannot be
converted to the required type, a type error is signaled.

Now, the second paragraph contradicts the first. If the rules for converting
the values are those defined in XPath, then the error code is typically
XPTY0004, except in some special cases where it might be FOTY0013 or XPTY0117
(or others?).

The rule as written appears to apply both to static function calls and to
dynamic function calls. It is problematic to apply XSLT-specific rules to a
dynamic function call because there is no property of the function item that
says "I am a stylesheet function"; in a dynamic call all functions are treated
alike, regardless how they were implemented.

Even for static function calls, it's not a good idea to have an XSLT-defined
error code for a construct whose syntax and semantics are defined in XPath; for
the implementor, this can only be achieved by modifying the behaviour of the
XPath engine to conform to XSLT rules.

I recommend that we delete this error code.

The matter arises as a consequence of test suite bug #24048.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 30 March 2015 08:24:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:53 UTC