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

[Bug 4551] K-NormalizeUnicodeFunc-13

From: <bugzilla@wiggum.w3.org>
Date: Wed, 30 May 2007 19:32:38 +0000
To: public-qt-comments@w3.org
Message-Id: <E1HtTuQ-0002Wz-6N@wiggum.w3.org>


andrew.eisenberg@us.ibm.com changed:

           What    |Removed                     |Added
         AssignedTo|andrew.eisenberg@us.ibm.com |frans.englich@telia.com

------- Comment #1 from andrew.eisenberg@us.ibm.com  2007-05-30 19:32 -------
I believe that another paragraph from section 2.3.4, Errors and Optimization,
must be considered:

"There is an exception to this rule: If a processor evaluates an operand E
(wholly or in part), then it is required to establish that the actual value of
the operand E does not violate any constraints on its cardinality. For example,
the expression $e eq 0 results in a type error if the value of $e contains two
or more items. A processor is not allowed to decide, after evaluating the first
item in the value of $e and finding it equal to zero, that the only possible
outcomes are the value true or a type error caused by the cardinality
violation. It must establish that the value of $e contains no more than one

The first parameter of normalize-unicode is of type string?. The operands of
the sequence constructor that makes up the first argument must be evaluated to
ensure that the sequence does not contain more than one item.

For this reason, I believe that the query cannot return a value other than an
error. Frans, do you agree with this?
Received on Wednesday, 30 May 2007 19:32:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:18 UTC