This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 29491 - [XSLT30] Improve error description of XTDE0045
Summary: [XSLT30] Improve error description of XTDE0045
Status: CLOSED DUPLICATE of bug 29234
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: P2 minor
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-20 14:34 UTC by Abel Braaksma
Modified: 2016-10-06 18:42 UTC (History)
0 users

See Also:


Attachments

Description Abel Braaksma 2016-02-20 14:34:10 UTC
As mentioned at F2F Prague 2016, Day 2, and in Bug 29379, comment#4 and Bug 29379, comment#5, we decided that the description of this error should be updated to be in line with other parts of the spec that require the initial mode/function/template to be public.

Current text:

<quote>
[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.
</quote>

Which is not in line with 6.6.1:

"A named mode is not eligible to be used as the initial mode if its visibility is private."

We may also revise the wording a bit for the last part of the XTDE0045 error description, as this is no longer true for packages. I suggest something like:

<suggestion>
[...]or the expanded QName in the mode attribute of any template defined in the stylesheet if the implicit or explicit value of declared-modes equals false.
</suggestion>
Comment 1 Abel Braaksma 2016-02-20 14:57:22 UTC
Part of this may have been fixed through Bug 29234, but I'm leaving this open for review as it was an action for me to raise this bug.
Comment 2 Michael Kay 2016-02-28 22:52:07 UTC
This seems to duplicate both bug #29234 and bug #29475

*** This bug has been marked as a duplicate of bug 29234 ***
Comment 3 Michael Kay 2016-02-28 22:52:24 UTC
This seems to duplicate both bug #29234 and bug #29475