Re: Comments on CCXML Working Draft 19 January 2007 (2)

This is being tracked as ISSUE-108

	RJ
---
RJ Auburn
CTO, Voxeo Corporation
tel:+1-407-418-1800



On Feb 7, 2007, at 6:19 AM, Hrvoje Nezic wrote:

>
> 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 Thursday, 8 February 2007 15:26:11 UTC