W3C home > Mailing lists > Public > www-voice@w3.org > July to September 2002

RE: The <nomatch> element inside a <record> element.

From: Scott McGlashan <scott.mcglashan@pipebeach.com>
Date: Thu, 19 Sep 2002 22:14:49 +0200
Message-ID: <2764A29BE430E64A92EB56561587D2E7107F93@se01ms02.i.pipebeach.com>
To: "Hoban, Thomas X." <thoban@shoptalk.com>, <www-voice@w3.org>

Hi Tom,

I agree -- there is no situation I can see in which a nomatch event
would be thrown during recording. However, the app developer could add a
<filled> inside <record> and then <throw> a nomatch event from there. 

In VoiceXML 2.0, when the recording exceeds maximum duration, recording
is terminated and the maxtime shadow variable is set to boolean true. On
a historical note, there is nothing in VoiceXML 1.0 which specifies that
a nomatch should be thrown if maxtime is reached (the simplest reading
of that spec for me is that the recording would terminate normally when
the maxtime is reached). 


-----Original Message-----
From: Hoban, Thomas X. [mailto:thoban@shoptalk.com]
Sent: Thursday, September 19, 2002 20:30
To: www-voice@w3.org
Subject: The <nomatch> element inside a <record> element.

In the newest VXML spec, it appears to me that <nomatch> is a valid
element inside of a <record> element.  However, I don't see anything in
the specification that describes what would cause a nomatch event to be
thrown while recording.  In one VXML 1.0 product that I'm working with,
I see nomatch thrown when the recording exceeds the maximum duration.

Can anyone give me insight into what should cause a nomatch while

Tom Hoban
Received on Thursday, 19 September 2002 16:14:53 UTC

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