RE: VXML2.0 question pertaining to timing and scoping of error.semantic on bad property names

Hi David,
There can be platform specific properties defined by any platform and the
platforms not supporting that MUST ignore the property..

So...in case there is a typo in the VoiceXML document for a particular
property ...then it will be ignored and the property will be accessed from
higher scopes or the default ones will be picked.

Regards,
Harbhanu

****************************************************************************
***********

            This e-mail and attachments contain confidential information
from HUAWEI, which is intended only for the person or entity whose address
is listed above. Any use of the information contained herein in any way
(including, but not limited to, total or partial disclosure, reproduction,
or dissemination) by persons other than the intended recipient's) is
prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!

-----Original Message-----
From: www-voice-request@w3.org [mailto:www-voice-request@w3.org] On Behalf
Of David Nicol
Sent: Tuesday, December 19, 2006 11:44 PM
To: www-voice@w3.org
Subject: VXML2.0 question pertaining to timing and scoping of error.semantic
on bad property names


I can't figure out if the VXML2.0 spec specifies the scope at which
the error.semantic
for a bad property name is thrown.  Is a bad property name a parsing
error that will foul
the document so that the error would be thrown in the referring
context, like a badfetch
on a goto next, or is a bad property name an execute-time error that
may be handled
by a catch elt that is sibling to the offending property elt, the
throwing of it deferred until
the elt in question is initialized (for a dialog) or executed (for a form
item)?

-- 
He thought he could organize freedom
how naive and controlling of him

Received on Thursday, 21 December 2006 08:33:36 UTC