W3C home > Mailing lists > Public > www-voice@w3.org > January to March 2004

Re: Evidently someone is confused as to what "barge in" means.

From: Dean Sturtevant <deansturtevant@comcast.net>
Date: Thu, 11 Mar 2004 07:10:57 -0500
Message-ID: <005001c40761$e95c9f00$24683c18@presario>
To: "Sturtevant Dean" <Dean.Sturtevant@comverse.com>, "Robert Barkan" <rhb@cisco.com>
Cc: <www-voice@w3.org>

Hi Robert - like I said, I may be confused. But I don't think so. I didn't
make clear that what I was talking about was the description of the
"hotword" value of "bargeintype".  My objection was to to the parenthetical
statement that the bargeintype "hotword" applies even to the timeout at the
end of the prompt.

- Dean
----- Original Message ----- 
From: "Robert Barkan" <rhb@cisco.com>
To: "Sturtevant Dean" <Dean.Sturtevant@comverse.com>
Cc: <www-voice@w3.org>
Sent: Wednesday, March 10, 2004 9:24 PM
Subject: Re: Evidently someone is confused as to what "barge in" means.


>
> Dean, are you confusing the "bargein" attribute with the "bargeintype"
> attribute?  You quoted the behavior for when the bargeintype attribute
> (or property) is set to "hotword".  If bargeintype is set to "speech"
> then the prompt is stopped on the start of speech or DTMF, ie:
> when the person "interrupts" the prompt.
>
> The bargeintype default is platform-specific, but I would think that
> the "speech" value is the more common default to avoid the
> stutter-effect for all but special hotword-based applications.
> -Rob
>
> At 05:52 PM 3/10/2004 -0500, Sturtevant Dean wrote:
>
> >I would have thought that "barge in" is what happens if the person on the
> >phone interrupts prompts. But perhaps the VoiceXML committee feels
> >differently, as evidenced by the addition of the parenthetical statement
in
> >the VoiceXML 2.0 proposal:
> >
> >The prompt will not be stopped until a complete match of an active
grammar
> >is detected. Input that does not match a grammar is ignored (note that
this
> >even applies during the timeout period); as a consequence, a nomatch
event
> >will never be generated in the case of hotword bargein.
> >
> >That "note" is not by my definition of bargein a clarification, but
rather a
> >significant change to the specification. Am I the only one who thinks so?
> >
> >- Dean
> >
> >
> >> Dean Sturtevant
> >> Comverse - Voice Solutions
> >> 100 Quannapowitt Pkwy, Wakefield, MA 01880-1315
> >> voice: (781) 213-2114
> >> email: dean.sturtevant@comverse.com
> >>
> >>
> >>
>
Received on Thursday, 11 March 2004 07:14:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 October 2006 12:48:59 GMT