This document:Public document·View comments·Disposition of Comments·
Nearby:Voice Browser Working Group Other specs in this tool
Quick access to LC-1667 LC-1668 LC-1669 LC-1670 LC-1671 LC-1672 LC-1673 LC-1674 LC-1675 LC-1676 LC-1677 LC-1678 LC-1679 LC-1683 LC-1684 LC-1685 LC-1687 LC-1688 LC-1689
Previous: LC-1674 Next: LC-1683
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."