[Bug 27011] New: [xslt 3.0] Problems with xsl:fork example

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

[Bug 27011] New: [xslt 3.0] Problems with xsl:fork example

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

            Bug ID: 27011
           Summary: [xslt 3.0] Problems with xsl:fork example
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: [hidden email]
          Reporter: [hidden email]
        QA Contact: [hidden email]

Reported by Martin Honnen on xsl-list:

The first example in http://www.w3.org/TR/xslt-30/#splitting-examples uses no
schema as far as I can tell but then tries a comparison with the operators 'lt'
and 'ge' of an attribute node value with an xs:integer:

transactions/transaction[@value lt 0]
transactions/transaction[@value ge 0]

That generates warnings "Comparison of xs:untypedAtomic? to xs:integer will
fail unless the first operand is empty" with Saxon 9.6 EE so I think the
comparisons need to be written as

transactions/transaction[number(@value) lt 0]
transactions/transaction[number(@value) ge 0]

or

transactions/transaction[xs:decimal(@value) lt 0]
transactions/transaction[xs:decimal(@value) ge 0]

to work as intended or the operators '<' and '>' need to be used.

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

Reply | Threaded
Open this post in threaded view
|

[Bug 27011] [xslt 3.0] Problems with xsl:fork example

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

Michael Kay <[hidden email]> changed:

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

--- Comment #1 from Michael Kay <[hidden email]> ---
The WG agreed that this error needs to be fixed.

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