Subject: [Speechsc] barge-in-able event clarification

From: Manzone Vittorio <[email-masked]>
Date: Thu, 26 May 2005 18:09:13 +0200

hi, 
we need a clarification about barge-in-able events:

in BARGE-IN-OCCURRED method description, only START-OF-SPEECH event is mentioned as event that can drive barge-in actions.
However, in hotword recognition this event will never be generated, and the only event that can drive barge-in is RECOGNITION-COMPLETE, for which is not described proxy-sync-id header usage: if client wants to stop SPEAK method, it can do it with the STOP method only, because it has no valid proxy-sync-id header to send to the server in a BARGE-IN-OCCURRED method. In this way, client cannot stop SPEAK methods depending on Kill-On-Barge-In header.

In order to solve this problem, we can consider also RECOGNITION-COMPLETE as a barge-in-able event, and document proxy-sync-id usage in its description.
In normal recognition (non hotword), START-OF-SPEECH and RECOGNITION-COMPLETE events should carry the same proxy-sync-id header, in order to stop synthesis  only on the first event.

Vittorio Manzone 
+39 011 2913470
[email-masked]

Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.

====================================================================
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to 
[email-masked]. Thank you
====================================================================

_______________________________________________
Speechsc mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/speechsc