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 24864 - [xslt 3.0] Error codes XTDE0060 and XTDE0700
Summary: [xslt 3.0] Error codes XTDE0060 and XTDE0700
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Last Call drafts
Hardware: PC All
: P2 normal
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: 2014-02-28 16:13 UTC by Michael Kay
Modified: 2014-05-15 14:00 UTC (History)
0 users

See Also:


Attachments

Description Michael Kay 2014-02-28 16:13:31 UTC
These two errors are:

[ERR XTDE0060] It is a dynamic error if the initial template defines a template parameter that specifies required="yes" and no value is supplied for that parameter.

[ERR XTDE0700] It is a dynamic error if a template that is invoked using xsl:apply-templates, xsl:apply-imports, or xsl:next-match declares a template parameter with required="yes" and no value for this parameter is supplied by the calling instruction. The same error is reported in the case of a tunnel parameter whether invoked using one of these three instructions or by xsl:call-template, as explained in 10.1.2 Tunnel Parameters.

I propose that we fold XTDE0060 into XTDE0700.

In the past, XTDE0060 read 

[ERR XTDE0060] It is a non-recoverable dynamic error if the initial template defines a template parameter that specifies required="yes".

We now allow template parameters to be supplied, so we changed the error description. However, the absence of a required parameter is likely to be detected in the same way regardless how the template was called, so it is inconvenient to have to generate two different error codes depending how the value was supplied.
Comment 1 Michael Kay 2014-03-28 10:43:42 UTC
The WG agreed, and the change has been made.