This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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).
This bug was discussed today by the WG and decided to leave it unchanged, noting that this attribute is defined in terms of xs:decimal, which in turn has an implementation-defined limit itself already. Closed with no action.