- From: <bugzilla@jessica.w3.org>
- Date: Sat, 05 Nov 2016 10:43:11 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29979 Bug ID: 29979 Summary: [XSLT30] Imposing limits on the priority attribute Product: XPath / XQuery / XSLT Version: Candidate Recommendation Hardware: PC OS: Windows NT Status: NEW Severity: minor Priority: P2 Component: XSLT 3.0 Assignee: mike@saxonica.com Reporter: abel.braaksma@xs4all.nl QA Contact: public-qt-comments@w3.org Target Milestone: --- We have recently allowed processors to impose limits on version numbers for packages. Another aspect of the spec that has unlimited range is the priority attribute for templates. I propose we do something similar as we did with versioning, except we can choose a more natural limit here, since it is only one number. I propose a rule something like the following: <proposal> Implementations may impose limits on the range of allowed decimal values and its precision, but it *must* be no less than 16 digits precision. </proposal> This range follows the minimal range XSD 1.1 imposes. I don't propose to use a new error for this, implementations can re-use error XTSE0020 (invalid attribute value). -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Saturday, 5 November 2016 10:43:18 UTC