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

[Bug 4465] K2-SeqExprCast-52 et seq

From: <bugzilla@wiggum.w3.org>
Date: Fri, 13 Apr 2007 10:32:45 +0000
To: public-qt-comments@w3.org
Message-Id: <E1HcJ5B-0004nH-10@wiggum.w3.org>


           Summary: K2-SeqExprCast-52 et seq
           Product: XML Query Test Suite
           Version: unspecified
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XML Query Test Suite
        AssignedTo: andrew.eisenberg@us.ibm.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org

The correct result of


hinges on whether types such as unsignedInt allow the lexical forms "-0" and

This is something of an old chestnut. In the past there were ambiguities in
F+O. I believe that F+O now states unambiguously that if the string is in the
lexical space of the data type (after whitespace fudging, which isn't relevant
here), then it's OK. So the answer lies in Schema Part 2.

Schema Part 2 says in section "unsignedInt has a lexical
representation consisting of a finite-length sequence of decimal digits
(#x30-#x39). For example: 0, 1267896754, 100000.", and this appears to disallow
a sign.

However, there is nothing in the schema for schemas that disallows a sign, and
the text at the top of section 3.3 says: "the complete definitions of the
·built-in·  ·derived· datatypes are provided in Appendix A Schema for Datatype
Definitions (normative) (§A)." By implication the textual descriptions of the
types in section 3.3 are incomplete.

So I believe that the S4S wins, and that "-" and "+" are therefore allowed in
the lexical space.
Received on Friday, 13 April 2007 10:33:00 UTC

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