W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2005

[Bug 1207] Is unsignedInt("+123") an error?

From: <bugzilla@wiggum.w3.org>
Date: Thu, 21 Jul 2005 19:23:13 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1DvgdV-0001zO-AE@wiggum.w3.org>

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


mike@saxonica.com changed:

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




------- Additional Comments From mike@saxonica.com  2005-07-21 19:23 -------
The working group discussed this and decided by a majority that we should make
casting from string (and, by implication, constructor functions taking a string
argument) consistent with schema validation: that is, if the target type is a
type derived by restriction using a pattern, the source string should be checked
against the pattern. This means that xs:unsignedInt("+123") becomes an error.
Similarly, for a target type derived from boolean whose pattern allows only
"true" and "false", casting from "0" or "1" would be an error.

As you were present during the discussion, I will mark the issue as closed.
Received on Thursday, 21 July 2005 19:23:15 UTC

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