W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2016

[Bug 29379] [XT30] mode-1701 expects success, but should probably fail with XTDE0045

From: <bugzilla@jessica.w3.org>
Date: Sun, 17 Jan 2016 23:58:28 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29379-523-4F3FzoqCdH@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29379

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|needinfo?(mike@saxonica.com |
                   |)                           |

--- Comment #4 from Michael Kay <mike@saxonica.com> ---
I don't recall whether it's by design, but XTDE0045 says:

[ERR XTDE0045] It is a dynamic error if the invocation of the stylesheet
specifies an initial mode (other than the unnamed mode) that does not match
either the expanded QName in the name attribute of an xsl:mode declaration, or
the expanded QName in the mode attribute of any template defined in the
stylesheet.

while XTDE0040 says:

[ERR XTDE0040] It is a dynamic error if the invocation of the stylesheet
specifies a template name that does not match the expanded QName of a named
template defined in the stylesheet, *whose visibility is public or final*.

and XTDE0041 says:

[ERR XTDE0041] It is a dynamic error if the invocation of the stylesheet
specifies a function name and arity that does not match the expanded QName and
arity of a named stylesheet function defined in the stylesheet, *whose
visibility is public or final*.

Note the absence of the phrase *whose visibility is public or final* from
XTDE0045.

However, 6.6.1 says: "A named mode is not eligible to be used as the initial
mode if its visibility is private."

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 17 January 2016 23:58:33 UTC

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