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 29987 - [xslt30] Definition of "implicitly mandatory"
Summary: [xslt30] Definition of "implicitly mandatory"
Status: RESOLVED INVALID
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Candidate Recommendation
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: 2016-11-06 15:02 UTC by Michael Kay
Modified: 2016-11-06 15:04 UTC (History)
0 users

See Also:


Attachments

Description Michael Kay 2016-11-06 15:02:21 UTC
We say 

[Definition: If a parameter has an implicit default value which cannot be converted to the required type (that is, if it has an as attribute which does not permit the empty sequence), then the parameter is implicitly mandatory.]

However, the implicit default may be either the zero-length string or the empty sequence. So the parenthetical remark in this definition should more accurately say

(that is, if it has an as attribute which does not permit the zero length string or the empty sequence as appropriate)
Comment 1 Michael Kay 2016-11-06 15:04:05 UTC
Sorry, no, the remark is correct as written. The implicit default can only be a zero-length string if there is no "as" attribute.