- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 30 May 2007 19:32:38 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4551 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 item." 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