[Bug 26648] New: [XSLT30] edge cases for numeric package version components comparisons

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 26648] New: [XSLT30] edge cases for numeric package version components comparisons

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26648

            Bug ID: 26648
           Summary: [XSLT30] edge cases for numeric package version
                    components comparisons
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: [hidden email]
          Reporter: [hidden email]
        QA Contact: [hidden email]

This was first covered in an email discussion, see
https://lists.w3.org/Archives/Member/w3c-xsl-wg/2014Aug/0014.html and
https://lists.w3.org/Archives/Member/w3c-xsl-wg/2014Aug/0015.html (member
only).

Summary: numeric version components are compared numerically according to the
new 3.6.1 section. Numeric overflow might happen when doing such comparisons.
The proposal in 0015.html is to describe the behavior in terms of the XPath gt,
lt and eq operators.

Maybe we can do the same for the string comparisons?

As mentioned in 0023.html, I think there is no need to re-cast XPath errors to
be XSLT errors for such (very rare) edge cases.

--
You are receiving this mail because:
You are the QA Contact for the bug.

Reply | Threaded
Open this post in threaded view
|

[Bug 26648] [XSLT30] edge cases for numeric package version components comparisons

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26648

Michael Kay <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Michael Kay <[hidden email]> ---
The WG accepted a suggestion that we can handle this by ensuring that the rules
for comparing integers in version numbers are defined by reference to the XPath
operator rules, which include rules for limits, overflow, and similar edge
cases.

To apply this, I have:

(a) specified that the integers follow the rules for XPath IntegerLiterals
(with mention that this includes the rules on limits)

(b) specified that comparison of integers or of NCNames follows the rules for
XPath value comparisons.

--
You are receiving this mail because:
You are the QA Contact for the bug.