W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2007

[Bug 4601] specification of fs:convert-operand() inconsistent

From: <bugzilla@wiggum.w3.org>
Date: Thu, 07 Jun 2007 08:09:00 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1HwD3E-0005dG-5q@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4601

           Summary: specification of fs:convert-operand() inconsistent
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Formal Semantics
        AssignedTo: jmdyck@ibiblio.org
        ReportedBy: jens.teubner@in.tum.de
         QAContact: public-qt-comments@w3.org


The specification of fs:convert-operand() is inconsistent in the XQuery Formal
Semantics Recommendation.

Section 4.5.2, Paragraph "Normalization" says:  `The internal function
fs:convert-operand is applied to each pair of atomic values. If the first
argument to this function has type xs:untypedAtomic, then the first argument is
cast to type of the second argument.'

Section 7.1.1, "The fs:convert-operand function", in contrast, says:  `If
$actual is an instance of type xs:untypedAtomic, then [...] if $expected is of
numeric type, returns $actual cast to xs:double.'

Note that (for e of type xs:untypedAtomic)

  e = 1

would be interpreted as an integer comparison according to the first definition
of fs:convert-operand(), but as a double comparison according to the second.
Received on Thursday, 7 June 2007 08:09:03 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:33 UTC