W3C home > Mailing lists > Public > www-voice@w3.org > April to June 2010

Re: Dialog and Connection semantic error handling

From: Chris Davis <davisc@iivip.com>
Date: Fri, 07 May 2010 08:26:47 -0500
Message-ID: <4BE41517.8060007@iivip.com>
To: Petr Kuba <kuba@optimsys.cz>
CC: www-voice@w3.org

Our SPOT browser would queue up an error.semantic in your examples of 
because section 9.3.2 says error.semantic is appropriate when "passing 
an invalid value for an attribute."

9.3.2 is a bit of a "catch all" because other tags often define specific 
error events they want to see
for invalid attributes such as <send>'s error.send.targettype.

For a <dialogstart> error, SPOT assumes no dialog is created in an error 
condition because by definition
the request has failed. I can't think of a rational use for failed 
dialogs to an application developer. It seems
to us either it got created ok and exists, or there was an error and no 
dialog exists.


Petr Kuba wrote:
> Hello,
> Could you please clarify the following issues?
> Description of the connectionid attribute of the <dialogstart> element 
> states:
>     If the attribute value is invalid an error.semantic event must be
>     thrown.
> The question is whether this statement applies only to ECMAScript 
> errors such as accessing non-declared variable or also to the case 
> where unknown connection is referenced. For example:
>     <dialogstart ... connectionid="'fake_conn_id'"/>
> Value of connectionid will be evaluated correctly in this case but 
> there is no connection with the given id. Shall error.semantic be 
> thrown in this case?
> Another question is what shall be done when error.semantic is thrown 
> when executing <dialogstart>. Is it allowed to call <dialogstart> 
> again, shall <dialogterminate> be called, or shall the Dialog Object 
> be destroyed automatically?
> Please note that these questions apply also to <dialogprepare> and 
> connection-related elements and the following statement is related to 
> this issue:
>     10.2.4: Connection Operations
>     If the element cannot be evaluated, for example if the referenced
>     connectionid  contained an invalid ECMAScript expression, then an
>     'error.semantic' event is thrown - as is the case for all CCXML
>     elements. The error.semantic event MUST NOT change the state of the
>     associated Connection Object(s).
> So if the dialog behaves the same way as connection it should not be 
> destroyed automatically after error.semantic.
> Thanks for clarification,
> Petr Kuba

Chris Davis
Interact Incorporated R&D
Received on Friday, 7 May 2010 13:27:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:07:41 UTC