- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 07 Feb 2008 16:44:24 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5278 ------- Comment #2 from mike@saxonica.com 2008-02-07 16:44 ------- I propose that we handle this in the same way as errors in patterns (see 5.5.4). Specifically, I suggest that we add to the end of section 17: Any dynamic error that occurs while evaluating the select expression or the contained sequence constructor, and any serialization error that occurs while processing the result, is treated as a recoverable error even if the error would not be recoverable under other circumstances. The optional recovery action is implementation-dependent. Note: An example of such an error is the serialization error that occurs when processing the instruction <xsl:message select="@code"/> (on the grounds that free-standing attributes cannot be serialized). Making such errors recoverable means that it is implementation-defined whether or not they are signaled to the user and whether they cause termination of the transformation. If the processor chooses to recover from the error, the content of any resulting message is implementation-dependent.
Received on Thursday, 7 February 2008 16:44:35 UTC