W3C home > Mailing lists > Public > www-voice@w3.org > January to March 2007

Comments on CCXML Working Draft 19 January 2007 (2)

From: Hrvoje Nezic <hrvoje.nezic@envox-lab.hr>
Date: Wed, 7 Feb 2007 12:19:04 +0100
Message-ID: <005f01c74aa9$c718d3d0$1301a8c0@envox.local.hr>
To: <www-voice@w3.org>

9: Event handling

Current text:
"If a semantic error occurs that prevents an element in the transition from 
being executed (such as the 'cond' attribute of <if> being an invalid 
ECMAScript expression), then successive elements within that transition will 
NOT be executed; an error.semantic will be raised for the element that could 
not be executed. Note that elements that can be executed but that generate 
errors (such as a <disconnect> on an invalid connection ID) do not terminate 
execution of the transition."

I think that this explanation is not clear enough. The phrase "elements that 
can be executed but that generate errors" could be applied to most CCXML 
elements. I think that intention was probably to distinguish between 
synchronous and asynchronous elements. Synchronous elements are <var>, 
<assign>, <script>, <if>, <elseif>, <else>, <goto>, <exit>, <log>, while 
other elements are asynchronous and generate events to signal success or 
failure.

The new text could be something like this:
"If a semantic error occurs that prevents a synchronous element in the 
transition from being executed (such as the 'cond' attribute of <if> being 
an invalid ECMAScript expression), then successive elements within that 
transition will NOT be executed; an error.semantic will be raised for the 
element that could not be executed. If a semantic error occurs that prevents 
an asynchrounous element from being executed (such as a <disconnect> on an 
invalid connection ID), execution of the transition will not be terminated." 
Received on Wednesday, 7 February 2007 11:19:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 7 February 2007 11:19:42 GMT