W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2016

[Bug 29880] New: package-version - limits

From: <bugzilla@jessica.w3.org>
Date: Thu, 29 Sep 2016 09:59:51 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29880-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29880

            Bug ID: 29880
           Summary: package-version - limits
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: mike@saxonica.com
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

Test package-version-903 uses the ridiculous

package-version=
"123456789123456789123456789123456789123456789123456789123456789123456789.1234....

An implementation can actually throw this one out under the current rules (more
than 16 digits), but I don't think we should require implementations to support
version number portions as high as 16 digits. 

Note: on .NET the components of a version number are limited to the range
1..65534. There is also a maximum of four components.

SEMVER, which we reference non-normatively, has a maximum of three components.
It doesn't limit the range of each component but tells you to use common sense.

I propose we say that an implementation is required to accept a version number
with up to three numeric components each in the range 0..9999, and is allowed
to reject anything outside these ranges.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 29 September 2016 09:59:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:02 UTC