From exim@www1.ietf.org Tue Sep 2 16:51:32 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06025 for ; Tue, 2 Sep 2003 16:51:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uI7H-0007cM-Un for speechsc-archive@odin.ietf.org; Tue, 02 Sep 2003 16:51:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h82Kp7rn029276 for speechsc-archive@odin.ietf.org; Tue, 2 Sep 2003 16:51:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uI7F-0007c7-Rw for speechsc-web-archive@optimus.ietf.org; Tue, 02 Sep 2003 16:51:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06012 for ; Tue, 2 Sep 2003 16:50:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19uI7D-0006ko-00 for speechsc-web-archive@ietf.org; Tue, 02 Sep 2003 16:51:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19uI7D-0006kk-00 for speechsc-web-archive@ietf.org; Tue, 02 Sep 2003 16:51:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uI7C-0007bn-2r; Tue, 02 Sep 2003 16:51:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uI6y-0007bG-Hk for speechsc@optimus.ietf.org; Tue, 02 Sep 2003 16:50:48 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06000; Tue, 2 Sep 2003 16:50:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19uI6v-0006kS-00; Tue, 02 Sep 2003 16:50:45 -0400 Received: from e31.co.us.ibm.com ([32.97.110.129]) by ietf-mx with esmtp (Exim 4.12) id 19uI6u-0006k7-00; Tue, 02 Sep 2003 16:50:44 -0400 Received: from westrelay04.boulder.ibm.com (westrelay04.boulder.ibm.com [9.17.193.32]) by e31.co.us.ibm.com (8.12.9/8.12.2) with ESMTP id h82KoERZ189448; Tue, 2 Sep 2003 16:50:14 -0400 Received: from d03nm120.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.193.82]) by westrelay04.boulder.ibm.com (8.12.9/NCO/VER6.6) with ESMTP id h82KoBn9082592; Tue, 2 Sep 2003 14:50:13 -0600 In-Reply-To: <4A3384433CE2AB46A63468CB207E209D4F66A1@zoe.office.snowshore.com> To: "Eric Burger" Cc: "IETF SPEECHSC (E-mail)" , speechsc-admin@ietf.org MIME-Version: 1.0 Subject: [Speechsc] FW: EMMA and Speechsc X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 From: Jeff Kusnitz Message-ID: Date: Tue, 2 Sep 2003 13:50:10 -0700 X-MIMETrack: Serialize by Router on D03NM120/03/M/IBM(Release 6.0.2CF2|July 23, 2003) at 09/02/2003 14:50:13, Serialize complete at 09/02/2003 14:50:13 Content-Type: text/plain; charset="US-ASCII" Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , Another option would be the XML format specified in the W3C VBWG Semantic Interpretation spec, located here (http://www.w3.org/TR/semantic-interpretation/#SI7.). It might fall into the same "not quite complete" bucket that EMMA does, but it's probably worth a quick look, and feedback for the SISR spec would be helpful as well. Thanks, Jeff > "Eric Burger" > Sent by: speechsc-admin@ietf.org > > 08/29/2003 11:10 AM > > > To: "IETF SPEECHSC (E-mail)" > cc: > Subject: RE: [Speechsc] FW: EMMA and Speechsc > > Anyone object? Alternate approaches? > > > -----Original Message----- > > From: Daniel Burnett [mailto:burnett@nuance.com] > > Sent: Mon, August 25, 2003 1:11 PM > > To: IETF SPEECHSC (E-mail) > > Subject: RE: [Speechsc] FW: EMMA and Speechsc > > > > > > Eric, > > > > I'd discourage our group from adopting EMMA yet. This > > document that was just published is a first working draft, > > and the W3C process can be quite slow. My preference would > > be to stay with our existing interchange format for MRCP2, > > both because EMMA is on a different maturity schedule and > > because it provides an easier transition to MRCP2. If and > > when we discuss MRCP3, it would be appropriate to re-evaluate > > the status of EMMA. > > > > However, it is reasonable for members of our group to review > > the EMMA draft and provide feedback at this early stage so > > that it can move towards what we eventually want it to be. > > > > -- dan > > > _______________________________________________ > Speechsc mailing list > Speechsc@ietf.org > https://www1.ietf.org/mailman/listinfo/speechsc _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Wed Sep 3 16:54:29 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07275 for ; Wed, 3 Sep 2003 16:54:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uedi-0004Qb-4f for speechsc-archive@odin.ietf.org; Wed, 03 Sep 2003 16:54:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h83Ks6fJ017021 for speechsc-archive@odin.ietf.org; Wed, 3 Sep 2003 16:54:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uedi-0004QS-05 for speechsc-web-archive@optimus.ietf.org; Wed, 03 Sep 2003 16:54:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07245 for ; Wed, 3 Sep 2003 16:53:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19uedf-0001ok-00 for speechsc-web-archive@ietf.org; Wed, 03 Sep 2003 16:54:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19uede-0001of-00 for speechsc-web-archive@ietf.org; Wed, 03 Sep 2003 16:54:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uedc-0004Pi-U7; Wed, 03 Sep 2003 16:54:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uech-0004Oj-TS for speechsc@optimus.ietf.org; Wed, 03 Sep 2003 16:53:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07185 for ; Wed, 3 Sep 2003 16:52:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19uecf-0001nl-00 for speechsc@ietf.org; Wed, 03 Sep 2003 16:53:01 -0400 Received: from grerelint01.net.external.hp.com ([192.6.111.88]) by ietf-mx with esmtp (Exim 4.12) id 19uece-0001nc-00 for speechsc@ietf.org; Wed, 03 Sep 2003 16:53:00 -0400 Received: from garonne.grenoble.hp.com (garonne.grenoble.hp.com [15.128.14.138]) by grerelint01.net.external.hp.com (Postfix) with ESMTP id 165A437C91; Wed, 3 Sep 2003 22:53:00 +0200 (CEST) Received: by garonne.grenoble.hp.com with Internet Mail Service (5.5.2655.55) id ; Wed, 3 Sep 2003 22:53:00 +0200 Message-ID: <90C1CD35C98F934D9D7C82240D2D59AD02923F5D@dumas.grenoble.hp.com> From: "BRANDT,MARC (HP-France,ex2)" To: Jeff Kusnitz , Eric Burger Cc: "IETF SPEECHSC (E-mail)" Subject: RE: [Speechsc] FW: EMMA and Speechsc Date: Wed, 3 Sep 2003 22:52:59 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: text/plain; charset="iso-8859-1" Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , would there be a way for MRCP v2 to tolerate different types of payload and making sure that implementers of media resources can decide what the best is in some situations (extensions, future features ...) ? I can envision this shall not prevent a protocol from working. Additionally speechsc may want to standardize some default profiles to make sure some level of interop is guaranteed. I feel important to split what shall be in the core protocol definitions from what is the responsibility of a media resource feature set. (if not already included in current draft) > -----Original Message----- > From: Jeff Kusnitz [mailto:jk@us.ibm.com] > Sent: Tuesday, September 02, 2003 10:50 PM > To: Eric Burger > Cc: IETF SPEECHSC (E-mail); speechsc-admin@ietf.org > Subject: [Speechsc] FW: EMMA and Speechsc > > > Another option would be the XML format specified in the W3C > VBWG Semantic > Interpretation spec, located here > (http://www.w3.org/TR/semantic-interpretation/#SI7.). It > might fall into > the same "not quite complete" bucket that EMMA does, but it's > probably > worth a quick look, and feedback for the SISR spec would be > helpful as > well. > > Thanks, > Jeff > > > "Eric Burger" > > Sent by: speechsc-admin@ietf.org > > > > 08/29/2003 11:10 AM > > > > > > To: "IETF SPEECHSC (E-mail)" > > cc: > > Subject: RE: [Speechsc] FW: EMMA and Speechsc > > > > Anyone object? Alternate approaches? > > > > > -----Original Message----- > > > From: Daniel Burnett [mailto:burnett@nuance.com] > > > Sent: Mon, August 25, 2003 1:11 PM > > > To: IETF SPEECHSC (E-mail) > > > Subject: RE: [Speechsc] FW: EMMA and Speechsc > > > > > > > > > Eric, > > > > > > I'd discourage our group from adopting EMMA yet. This > > > document that was just published is a first working draft, > > > and the W3C process can be quite slow. My preference would > > > be to stay with our existing interchange format for MRCP2, > > > both because EMMA is on a different maturity schedule and > > > because it provides an easier transition to MRCP2. If and > > > when we discuss MRCP3, it would be appropriate to re-evaluate > > > the status of EMMA. > > > > > > However, it is reasonable for members of our group to review > > > the EMMA draft and provide feedback at this early stage so > > > that it can move towards what we eventually want it to be. > > > > > > -- dan > > > > > > _______________________________________________ > > Speechsc mailing list > > Speechsc@ietf.org > > https://www1.ietf.org/mailman/listinfo/speechsc > > > > _______________________________________________ > Speechsc mailing list > Speechsc@ietf.org > https://www1.ietf.org/mailman/listinfo/speechsc > _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Fri Sep 5 07:03:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14208 for ; Fri, 5 Sep 2003 07:03:20 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19vEMk-0007L8-JS for speechsc-archive@odin.ietf.org; Fri, 05 Sep 2003 07:02:58 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h85B2w59028213 for speechsc-archive@odin.ietf.org; Fri, 5 Sep 2003 07:02:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19vEMk-0007Ky-E1 for speechsc-web-archive@optimus.ietf.org; Fri, 05 Sep 2003 07:02:58 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14178 for ; Fri, 5 Sep 2003 07:02:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19vEMa-0001pM-00 for speechsc-web-archive@ietf.org; Fri, 05 Sep 2003 07:02:49 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19vEMB-0001l5-00 for speechsc-web-archive@ietf.org; Fri, 05 Sep 2003 07:02:23 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19vELq-0007GC-Kh; Fri, 05 Sep 2003 07:02:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19vELR-0007Fk-P5 for speechsc@optimus.ietf.org; Fri, 05 Sep 2003 07:01:37 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14106 for ; Fri, 5 Sep 2003 07:01:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19vELD-0001iR-00 for speechsc@ietf.org; Fri, 05 Sep 2003 07:01:23 -0400 Received: from goalie.snowshore.com ([216.57.133.4] helo=webshield.office.snowshore.com) by ietf-mx with smtp (Exim 4.12) id 19vEKi-0001ga-00 for speechsc@ietf.org; Fri, 05 Sep 2003 07:00:53 -0400 Received: from zoe.office.snowshore.com(192.168.1.172) by webshield.office.snowshore.com via csmap id 18603; Fri, 05 Sep 2003 06:56:33 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Fri, 5 Sep 2003 06:59:21 -0400 Message-ID: <4A3384433CE2AB46A63468CB207E209D4F66F5@zoe.office.snowshore.com> Thread-Topic: Important Meeting Dates for IETF 58 Thread-Index: AcNzmxdwW3Gm7m9VRaujb9vUaTqCYg== From: "Eric Burger" To: "IETF SPEECHSC (E-mail)" Content-Transfer-Encoding: quoted-printable Subject: [Speechsc] Important Meeting Dates for IETF 58 Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable September 6, Thursday - Working Group and BOF scheduling begins =3D=3D=3D Consider this a call for discussion items Week of September 8 - Registration begins =3D=3D=3D Don't forget to register! October 20, Monday - Internet Draft Cut-off for initial document (-00) = submission at 09:00 ET =3D=3D=3D Get your drafts in by next week, and you will get an extra = week for a revision: October 27, Monday - Internet Draft final submission cut-off at 09:00 ET November 9-14 - 58th IETF Meeting in Minneapolis, MN, USA _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Fri Sep 19 22:04:47 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01626 for ; Fri, 19 Sep 2003 21:37:32 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.12.8/8.12.8) with ESMTP id h8K1VhDr020140 for ; Fri, 19 Sep 2003 21:37:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7PDtbp3031438 for speechsc-archive@odin.ietf.org; Mon, 25 Aug 2003 09:55:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rHom-0008Az-BV for speechsc-web-archive@optimus.ietf.org; Mon, 25 Aug 2003 09:55:36 -0400 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17817 for ; Mon, 25 Aug 2003 09:55:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rHoF-00085W-OC; Mon, 25 Aug 2003 09:55:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rHnT-00084f-1r for speechsc@optimus.ietf.org; Mon, 25 Aug 2003 09:54:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17758 for ; Mon, 25 Aug 2003 09:54:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rHnO-0001L3-00 for speechsc@ietf.org; Mon, 25 Aug 2003 09:54:10 -0400 Received: from [204.127.198.35] (helo=rwcrmhc11.comcast.net) by ietf-mx with esmtp (Exim 4.12) id 19rHnN-0001K4-00 for speechsc@ietf.org; Mon, 25 Aug 2003 09:54:09 -0400 Received: from chimaera (pcp01419711pcs.plmthm01.pa.comcast.net[68.81.38.152](untrusted sender)) by comcast.net (rwcrmhc11) with SMTP id <20030825134606013001diq7e>; Mon, 25 Aug 2003 13:46:06 +0000 From: "Deborah Dahl" To: "'Eric Burger'" , "'IETF SPEECHSC \(E-mail\)'" Subject: RE: [Speechsc] FW: EMMA and Speechsc Date: Mon, 25 Aug 2003 09:45:47 -0400 Message-ID: <000001c36b0f$33dd04b0$3a7ba8c0@chimaera> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal In-Reply-To: <4A3384433CE2AB46A63468CB207E209D59E646@zoe.office.snowshore.com> Content-Transfer-Encoding: 7bit Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Thanks, Eric. I forgot to mention that feedback should be sent to www-multimodal@w3.org, the Multimodal Interaction Working Group's public mailing list. Looking forward to any comments or suggestions you may have. regards, Debbie > -----Original Message----- > From: speechsc-admin@ietf.org > [mailto:speechsc-admin@ietf.org] On Behalf Of Eric Burger > Sent: Monday, August 25, 2003 9:09 AM > To: IETF SPEECHSC (E-mail) > Cc: dahl@conversational-technologies.com > Subject: [Speechsc] FW: EMMA and Speechsc > > > Debbie is the Chair of the W3C MMI Work Group. She is > soliciting feedback on EMMA, which is the leading candidate > as an interchange format for ASR results for MRCPv2. > > -----Original Message----- > From: Deborah Dahl [mailto:dahl@conversational-technologies.com] > Sent: Tue, August 12, 2003 10:24 AM > To: Eric Burger > Subject: EMMA and Speechsc > > > Hi Eric, > As you may be aware, the Multimodal Interaction Working > Group has just published a Working Draft of EMMA, > (Extensible MultiModal Annotation) the follow-on to NLSML, > for representing user input. We're looking for feedback from > other interested parties and we'd like specifically to get some > feedback from the Speechsc group. Either feedback from the group > as a whole or feedback from individual participants would be useful. > What do you think would be a good way to go about this? > > Best regards, > > Debbie > > Brief description of EMMA: > > EMMA is designed as a data exchange format for use in representing > application specific interpretations of user input together with > annotations such as confidence scores, time stamps and input medium > etc. Speech and handwriting recognizers, natural language engines, > media interpreters, and multimodal integration components generate > EMMA markup. > > EMMA spec: > http://www.w3.org/TR/2003/WD-emma-20030811/ Multimodal Interaction home page: http://www.w3.org/TR/2002/mmi/ More information about the role EMMA plays in the W3C Multimodal Interaction Framework can be found in: http://www.w3.org/TR/mmi-framework/ _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Fri Sep 19 22:04:48 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01649 for ; Fri, 19 Sep 2003 21:37:41 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.12.8/8.12.8) with ESMTP id h8K1VhEb020140 for ; Fri, 19 Sep 2003 21:37:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7PIJftG016277 for speechsc-archive@odin.ietf.org; Mon, 25 Aug 2003 14:19:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rLwJ-0004EP-Nr for speechsc-web-archive@optimus.ietf.org; Mon, 25 Aug 2003 14:19:39 -0400 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07054 for ; Mon, 25 Aug 2003 14:19:33 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rLvj-0004Aa-U5; Mon, 25 Aug 2003 14:19:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rKsf-00070M-Nz for speechsc@optimus.ietf.org; Mon, 25 Aug 2003 13:11:49 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00394 for ; Mon, 25 Aug 2003 13:11:42 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rKsd-0003xg-00 for speechsc@ietf.org; Mon, 25 Aug 2003 13:11:47 -0400 Received: from ns1.nuance.com ([208.252.220.9]) by ietf-mx with esmtp (Exim 4.12) id 19rKsc-0003vq-00 for speechsc@ietf.org; Mon, 25 Aug 2003 13:11:46 -0400 Received: from mpb1exbr01.nuance.com (mpb1exbr01.nuance.com [10.0.0.43]) by ns1.nuance.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h7PHGxc27470 for ; Mon, 25 Aug 2003 10:16:59 -0700 (PDT) Received: from mpb1exch02.nuance.com ([10.0.0.56]) by mpb1exbr01.nuance.com with Microsoft SMTPSVC(5.0.2195.5329); Mon, 25 Aug 2003 10:10:59 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Speechsc] FW: EMMA and Speechsc Date: Mon, 25 Aug 2003 10:10:59 -0700 Message-ID: Thread-Topic: EMMA and Speechsc Thread-Index: AcNg3XUsqNmtk4+SR7K6CdGv83E9uAKEDf+AAA9dfTA= From: "Daniel Burnett" To: "IETF SPEECHSC (E-mail)" X-OriginalArrivalTime: 25 Aug 2003 17:10:59.0929 (UTC) FILETIME=[DB0C5490:01C36B2B] Content-Transfer-Encoding: quoted-printable Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Eric, I'd discourage our group from adopting EMMA yet. This document that was = just published is a first working draft, and the W3C process can be = quite slow. My preference would be to stay with our existing = interchange format for MRCP2, both because EMMA is on a different = maturity schedule and because it provides an easier transition to MRCP2. = If and when we discuss MRCP3, it would be appropriate to re-evaluate = the status of EMMA. However, it is reasonable for members of our group to review the EMMA = draft and provide feedback at this early stage so that it can move = towards what we eventually want it to be. -- dan -----Original Message----- From: Eric Burger [mailto:eburger@snowshore.com] Sent: Monday, August 25, 2003 6:09 AM To: IETF SPEECHSC (E-mail) Cc: dahl@conversational-technologies.com Subject: [Speechsc] FW: EMMA and Speechsc Debbie is the Chair of the W3C MMI Work Group. She is soliciting = feedback on EMMA, which is the leading candidate as an interchange = format for ASR results for MRCPv2. -----Original Message----- From: Deborah Dahl [mailto:dahl@conversational-technologies.com] Sent: Tue, August 12, 2003 10:24 AM To: Eric Burger Subject: EMMA and Speechsc Hi Eric, As you may be aware, the Multimodal Interaction Working=20 Group has just published a Working Draft of EMMA,=20 (Extensible MultiModal Annotation) the follow-on to NLSML,=20 for representing user input. We're looking for feedback from other interested parties and we'd like specifically to get some=20 feedback from the Speechsc group. Either feedback from the group=20 as a whole or feedback from individual participants would be useful.=20 What do you think would be a good way to go about this? Best regards, Debbie=20 Brief description of EMMA: EMMA is designed as a data exchange format for use in representing application specific interpretations of user input together with annotations such as confidence scores, time stamps and input medium etc. Speech and handwriting recognizers, natural language engines, media interpreters, and multimodal integration components generate EMMA markup.=20 EMMA spec: http://www.w3.org/TR/2003/WD-emma-20030811/ Multimodal Interaction home page: http://www.w3.org/TR/2002/mmi/ More information about the role EMMA plays in the W3C Multimodal Interaction Framework can be found in: http://www.w3.org/TR/mmi-framework/ _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Fri Sep 19 22:36:53 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04334 for ; Fri, 19 Sep 2003 22:36:52 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.12.8/8.12.8) with ESMTP id h8K1VhF9020140 for ; Fri, 19 Sep 2003 21:37:28 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7TLQhhx020087 for speechsc-archive@odin.ietf.org; Fri, 29 Aug 2003 17:26:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19soHe-0006pv-2Y for speechsc-web-archive@optimus.ietf.org; Fri, 29 Aug 2003 14:47:42 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22718 for ; Fri, 29 Aug 2003 14:47:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19soHb-0003ZN-00 for speechsc-web-archive@ietf.org; Fri, 29 Aug 2003 14:47:39 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19soHa-0003ZJ-00 for speechsc-web-archive@ietf.org; Fri, 29 Aug 2003 14:47:38 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19snyy-0005p7-0d; Fri, 29 Aug 2003 14:28:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19sniU-000477-TH for speechsc@optimus.ietf.org; Fri, 29 Aug 2003 14:11:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19719 for ; Fri, 29 Aug 2003 14:11:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19sniS-0002df-00 for speechsc@ietf.org; Fri, 29 Aug 2003 14:11:20 -0400 Received: from goalie.snowshore.com ([216.57.133.4] helo=webshield.office.snowshore.com) by ietf-mx with smtp (Exim 4.12) id 19sniR-0002cS-00 for speechsc@ietf.org; Fri, 29 Aug 2003 14:11:19 -0400 Received: from zoe.office.snowshore.com(192.168.1.172) by webshield.office.snowshore.com via csmap id 29964; Fri, 29 Aug 2003 14:07:23 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Speechsc] FW: EMMA and Speechsc Date: Fri, 29 Aug 2003 14:10:49 -0400 Message-ID: <4A3384433CE2AB46A63468CB207E209D4F66A1@zoe.office.snowshore.com> Thread-Topic: EMMA and Speechsc Thread-Index: AcNg3XUsqNmtk4+SR7K6CdGv83E9uAKEDf+AAA9dfTAAy09+8A== From: "Eric Burger" To: "IETF SPEECHSC (E-mail)" Content-Transfer-Encoding: quoted-printable Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Anyone object? Alternate approaches? > -----Original Message----- > From: Daniel Burnett [mailto:burnett@nuance.com] > Sent: Mon, August 25, 2003 1:11 PM > To: IETF SPEECHSC (E-mail) > Subject: RE: [Speechsc] FW: EMMA and Speechsc >=20 >=20 > Eric, >=20 > I'd discourage our group from adopting EMMA yet. This=20 > document that was just published is a first working draft,=20 > and the W3C process can be quite slow. My preference would=20 > be to stay with our existing interchange format for MRCP2,=20 > both because EMMA is on a different maturity schedule and=20 > because it provides an easier transition to MRCP2. If and=20 > when we discuss MRCP3, it would be appropriate to re-evaluate=20 > the status of EMMA. >=20 > However, it is reasonable for members of our group to review=20 > the EMMA draft and provide feedback at this early stage so=20 > that it can move towards what we eventually want it to be. >=20 > -- dan _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Tue Sep 23 09:57:28 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13585 for ; Tue, 23 Sep 2003 09:57:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A1nf8-0005HP-At for speechsc-archive@odin.ietf.org; Tue, 23 Sep 2003 09:57:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h8NDv6tm020289 for speechsc-archive@odin.ietf.org; Tue, 23 Sep 2003 09:57:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A1nf8-0005HA-68 for speechsc-web-archive@optimus.ietf.org; Tue, 23 Sep 2003 09:57:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13557 for ; Tue, 23 Sep 2003 09:56:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A1nf6-00009R-00 for speechsc-web-archive@ietf.org; Tue, 23 Sep 2003 09:57:04 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A1nf5-00009N-00 for speechsc-web-archive@ietf.org; Tue, 23 Sep 2003 09:57:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A1nf3-0005GW-Mn; Tue, 23 Sep 2003 09:57:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A1nea-0005Fp-72 for speechsc@optimus.ietf.org; Tue, 23 Sep 2003 09:56:32 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13527; Tue, 23 Sep 2003 09:56:23 -0400 (EDT) Message-Id: <200309231356.JAA13527@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: speechsc@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Tue, 23 Sep 2003 09:56:23 -0400 Subject: [Speechsc] I-D ACTION:draft-ietf-speechsc-mrcpv2-00.txt Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Speech Services Control Working Group of the IETF. Title : Media Resource Control Protocol Version 2(MRCPv2) Author(s) : S. Shanmugham Filename : draft-ietf-speechsc-mrcpv2-00.txt Pages : 82 Date : 2003-9-23 This document describes a proposal for a Media Resource Control Protocol Version 2(MRCPv2) and aims to meet the requirements specified in the SPEECHSC working group requirements document. It is based on the Media Resource Control Protocol (MRCP), also called MRCPv1 developed jointly by Cisco Systems, Inc., Nuance Communications, and Speechworks Inc. The MRCPv2 protocol will control media service resources like speech synthesizers, recognizers, signal generators, signal detectors, fax servers etc. over a network. This protocol depends on a session management protocol such as the Session Initiation Protocol (SIP) to establish a separate MRCPv2 control session between the client and the media server. It also depends on SIP to establish the media pipe and associated parameters between the media source or sink and the media server. Once this is done, the MRCPv2 protocol exchange can happen over the control session established above allowing the client to command and control the media processing resources that may exist on the media server. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-speechsc-mrcpv2-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-speechsc-mrcpv2-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-speechsc-mrcpv2-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-9-23101638.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-speechsc-mrcpv2-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-speechsc-mrcpv2-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-9-23101638.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Thu Sep 25 11:32:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00928 for ; Thu, 25 Sep 2003 11:32:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2Y68-0000LQ-H6 for speechsc-archive@odin.ietf.org; Thu, 25 Sep 2003 11:32:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h8PFW4nP001319 for speechsc-archive@odin.ietf.org; Thu, 25 Sep 2003 11:32:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2Y68-0000LC-Co for speechsc-web-archive@optimus.ietf.org; Thu, 25 Sep 2003 11:32:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00910 for ; Thu, 25 Sep 2003 11:31:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A2Y67-00008m-00 for speechsc-web-archive@ietf.org; Thu, 25 Sep 2003 11:32:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A2Y66-00008i-00 for speechsc-web-archive@ietf.org; Thu, 25 Sep 2003 11:32:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2Y64-0000KW-Sc; Thu, 25 Sep 2003 11:32:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2Y5b-0000Jz-KL for speechsc@optimus.ietf.org; Thu, 25 Sep 2003 11:31:31 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00896 for ; Thu, 25 Sep 2003 11:31:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A2Y5a-00008U-00 for speechsc@ietf.org; Thu, 25 Sep 2003 11:31:30 -0400 Received: from pb-relay2.scansoft.com ([198.71.64.24] helo=smtp-relay1.scansoft.com) by ietf-mx with esmtp (Exim 4.12) id 1A2Y5a-00008H-00 for speechsc@ietf.org; Thu, 25 Sep 2003 11:31:30 -0400 Received: from pb-exchcon.pb.scansoft.com ([10.1.4.73] RDNS failed) by smtp-relay1.scansoft.com with Microsoft SMTPSVC(5.0.2195.5329); Thu, 25 Sep 2003 11:30:58 -0400 Received: by pb-exchcon.pb.scansoft.com with Internet Mail Service (5.5.2653.19) id ; Thu, 25 Sep 2003 11:30:58 -0400 Message-ID: From: "Reifenrath, Klaus" To: "'speechsc@ietf.org'" Date: Thu, 25 Sep 2003 11:34:02 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-OriginalArrivalTime: 25 Sep 2003 15:30:58.0279 (UTC) FILETIME=[04977770:01C3837A] Subject: [Speechsc] draft-ietf-speechsc-mrcpv2-00.txt: DTMF barge-in question Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , It is not clear to me, how the synthesizer is stopped on DTMF barge-in. In case of voice barge-in the recognizer is responsible to send START-OF-SPEECH (see chapter 8.12). Is this also true in case of DTMF barge-in? _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Thu Sep 25 12:02:33 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02338 for ; Thu, 25 Sep 2003 12:02:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2YZG-0002DS-Nc for speechsc-archive@odin.ietf.org; Thu, 25 Sep 2003 12:02:10 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h8PG2AsX008518 for speechsc-archive@odin.ietf.org; Thu, 25 Sep 2003 12:02:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2YZG-0002DJ-Iz for speechsc-web-archive@optimus.ietf.org; Thu, 25 Sep 2003 12:02:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02312 for ; Thu, 25 Sep 2003 12:02:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A2YZF-0000Yt-00 for speechsc-web-archive@ietf.org; Thu, 25 Sep 2003 12:02:09 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A2YZE-0000Yq-00 for speechsc-web-archive@ietf.org; Thu, 25 Sep 2003 12:02:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2YZ7-0002BZ-Ol; Thu, 25 Sep 2003 12:02:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2YYx-00029b-DN for speechsc@optimus.ietf.org; Thu, 25 Sep 2003 12:01:51 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02295 for ; Thu, 25 Sep 2003 12:01:43 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A2YYw-0000YR-00 for speechsc@ietf.org; Thu, 25 Sep 2003 12:01:50 -0400 Received: from vtg-um-e2k1.cisco.com ([171.70.93.55] helo=vtg-um-e2k1.sj21ad.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1A2YYv-0000X6-00 for speechsc@ietf.org; Thu, 25 Sep 2003 12:01:49 -0400 Received: from cisco.com ([10.21.81.97]) by vtg-um-e2k1.sj21ad.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Thu, 25 Sep 2003 09:00:02 -0700 Message-ID: <3F731149.2010601@cisco.com> Date: Thu, 25 Sep 2003 09:01:13 -0700 From: Sarvi Shanmugham Organization: Cisco Systems Inc. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Reifenrath, Klaus" CC: "'speechsc@ietf.org'" Subject: Re: [Speechsc] draft-ietf-speechsc-mrcpv2-00.txt: DTMF barge-in question References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 25 Sep 2003 16:00:02.0375 (UTC) FILETIME=[14276570:01C3837E] Content-Transfer-Encoding: 7bit Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit The purpose of the START-OF-SPEECH event was to address the implementation of bargein, both speech and DTMF barge-in. The START-OF-SPEECH event is expected to be generated when the user starts speaking or pressing digits. The client is responsible for conveying the barge-in event to the synthesizer. The synthesizer should then decided whether to barge-in the current playing prompt or not based on barge-in flags provided when the SPEAK command was issued. Sarvi If the source is Reifenrath, Klaus wrote: >It is not clear to me, how the synthesizer is stopped on DTMF barge-in. >In case of voice barge-in the recognizer is responsible to send >START-OF-SPEECH (see chapter 8.12). Is this also true in case of DTMF >barge-in? > > > >_______________________________________________ >Speechsc mailing list >Speechsc@ietf.org >https://www1.ietf.org/mailman/listinfo/speechsc > > > _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Thu Sep 25 12:08:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02660 for ; Thu, 25 Sep 2003 12:08:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2Yex-0002rP-7I for speechsc-archive@odin.ietf.org; Thu, 25 Sep 2003 12:08:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h8PG83oO010989 for speechsc-archive@odin.ietf.org; Thu, 25 Sep 2003 12:08:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2Yex-0002qz-40 for speechsc-web-archive@optimus.ietf.org; Thu, 25 Sep 2003 12:08:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02573 for ; Thu, 25 Sep 2003 12:07:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A2Yev-0000dm-00 for speechsc-web-archive@ietf.org; Thu, 25 Sep 2003 12:08:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A2Yev-0000dj-00 for speechsc-web-archive@ietf.org; Thu, 25 Sep 2003 12:08:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2Yev-0002q1-Id; Thu, 25 Sep 2003 12:08:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2Ye2-0002ZL-05 for speechsc@optimus.ietf.org; Thu, 25 Sep 2003 12:07:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02526 for ; Thu, 25 Sep 2003 12:06:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A2Ye0-0000d0-00 for speechsc@ietf.org; Thu, 25 Sep 2003 12:07:04 -0400 Received: from ns1.nuance.com ([208.252.220.9]) by ietf-mx with esmtp (Exim 4.12) id 1A2Ydz-0000cM-00 for speechsc@ietf.org; Thu, 25 Sep 2003 12:07:04 -0400 Received: from mpb1exbr01.nuance.com (mpb1exbr01.nuance.com [10.0.0.43]) by ns1.nuance.com (Postfix) with ESMTP id A2B8473FF5; Thu, 25 Sep 2003 09:12:50 -0700 (PDT) Received: from mtb1exch01.nuance.com ([10.3.2.6]) by mpb1exbr01.nuance.com with Microsoft SMTPSVC(5.0.2195.5329); Thu, 25 Sep 2003 09:06:32 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Speechsc] draft-ietf-speechsc-mrcpv2-00.txt: DTMF barge-in question Date: Thu, 25 Sep 2003 12:06:30 -0400 Message-ID: <7DE7C4EF3B7C8B4B82955191378290D8EDC643@mtb1exch01.nuance.com> Thread-Topic: [Speechsc] draft-ietf-speechsc-mrcpv2-00.txt: DTMF barge-in question Thread-Index: AcODfnutMkQRgiE3QcuFgAMaYbo+EQAADRsw From: "Pierre Forgues" To: "Sarvi Shanmugham" , "Reifenrath, Klaus" Cc: X-OriginalArrivalTime: 25 Sep 2003 16:06:32.0318 (UTC) FILETIME=[FC93F9E0:01C3837E] Content-Transfer-Encoding: quoted-printable Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Sarvi, I believe this should be made clearer in the specification document. I could not find the place where this is stated in the section on START-OF-SPEECH. /Pierre -----Original Message----- From: Sarvi Shanmugham [mailto:sarvi@cisco.com]=20 Sent: 25 septembre, 2003 12:01 To: Reifenrath, Klaus Cc: 'speechsc@ietf.org' Subject: Re: [Speechsc] draft-ietf-speechsc-mrcpv2-00.txt: DTMF barge-in question The purpose of the START-OF-SPEECH event was to address the=20 implementation of bargein, both speech and DTMF barge-in. The=20 START-OF-SPEECH event is expected to be generated when the user starts=20 speaking or pressing digits. The client is responsible for conveying the barge-in event to the synthesizer. The synthesizer should then decided=20 whether to barge-in the current playing prompt or not based on barge-in=20 flags provided when the SPEAK command was issued. Sarvi If the source is Reifenrath, Klaus wrote: >It is not clear to me, how the synthesizer is stopped on DTMF barge-in. >In case of voice barge-in the recognizer is responsible to send >START-OF-SPEECH (see chapter 8.12). Is this also true in case of DTMF >barge-in? > > > >_______________________________________________ >Speechsc mailing list >Speechsc@ietf.org >https://www1.ietf.org/mailman/listinfo/speechsc > > =20 > _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Thu Sep 25 16:27:30 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19818 for ; Thu, 25 Sep 2003 16:27:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2chf-00022s-IA for speechsc-archive@odin.ietf.org; Thu, 25 Sep 2003 16:27:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h8PKR7k5007858 for speechsc-archive@odin.ietf.org; Thu, 25 Sep 2003 16:27:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2chf-00022f-EQ for speechsc-web-archive@optimus.ietf.org; Thu, 25 Sep 2003 16:27:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19792 for ; Thu, 25 Sep 2003 16:26:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A2chd-0005bE-00 for speechsc-web-archive@ietf.org; Thu, 25 Sep 2003 16:27:05 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A2chd-0005bB-00 for speechsc-web-archive@ietf.org; Thu, 25 Sep 2003 16:27:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2chZ-000220-Ie; Thu, 25 Sep 2003 16:27:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2chP-00021j-0I for speechsc@optimus.ietf.org; Thu, 25 Sep 2003 16:26:51 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19781 for ; Thu, 25 Sep 2003 16:26:43 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A2chN-0005at-00 for speechsc@ietf.org; Thu, 25 Sep 2003 16:26:49 -0400 Received: from vtg-um-e2k1.cisco.com ([171.70.93.55] helo=vtg-um-e2k1.sj21ad.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1A2chM-0005ag-00 for speechsc@ietf.org; Thu, 25 Sep 2003 16:26:48 -0400 Received: from cisco.com ([128.107.171.121]) by vtg-um-e2k1.sj21ad.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Thu, 25 Sep 2003 13:25:05 -0700 Message-ID: <3F734F68.3070203@cisco.com> Date: Thu, 25 Sep 2003 13:26:16 -0700 From: Sarvi Shanmugham Organization: Cisco Systems Inc. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pierre Forgues CC: "Reifenrath, Klaus" , speechsc@ietf.org Subject: Re: [Speechsc] draft-ietf-speechsc-mrcpv2-00.txt: DTMF barge-in question References: <7DE7C4EF3B7C8B4B82955191378290D8EDC643@mtb1exch01.nuance.com> In-Reply-To: <7DE7C4EF3B7C8B4B82955191378290D8EDC643@mtb1exch01.nuance.com> Content-Type: multipart/alternative; boundary="------------050408080208010203010108" X-OriginalArrivalTime: 25 Sep 2003 20:25:05.0171 (UTC) FILETIME=[1AF57E30:01C383A3] Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. --------------050408080208010203010108 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit I agree this needs to be clarified. Since the explicit purpose of this message was for barge-in implementation, I guess there was some implied assumption of treating DTMF/speech. May be we should have named it START-OF-INPUT. :-)) Sarvi Pierre Forgues wrote: >Sarvi, I believe this should be made clearer in the specification >document. I could not find the place where this is stated in the >section on START-OF-SPEECH. /Pierre > >-----Original Message----- >From: Sarvi Shanmugham [mailto:sarvi@cisco.com] >Sent: 25 septembre, 2003 12:01 >To: Reifenrath, Klaus >Cc: 'speechsc@ietf.org' >Subject: Re: [Speechsc] draft-ietf-speechsc-mrcpv2-00.txt: DTMF barge-in >question > >The purpose of the START-OF-SPEECH event was to address the >implementation of bargein, both speech and DTMF barge-in. The >START-OF-SPEECH event is expected to be generated when the user starts >speaking or pressing digits. The client is responsible for conveying the > >barge-in event to the synthesizer. The synthesizer should then decided >whether to barge-in the current playing prompt or not based on barge-in >flags provided when the SPEAK command was issued. > >Sarvi > >If the source is > >Reifenrath, Klaus wrote: > > > >>It is not clear to me, how the synthesizer is stopped on DTMF barge-in. >>In case of voice barge-in the recognizer is responsible to send >>START-OF-SPEECH (see chapter 8.12). Is this also true in case of DTMF >>barge-in? >> >> >> >>_______________________________________________ >>Speechsc mailing list >>Speechsc@ietf.org >>https://www1.ietf.org/mailman/listinfo/speechsc >> >> >> >> >> > > >_______________________________________________ >Speechsc mailing list >Speechsc@ietf.org >https://www1.ietf.org/mailman/listinfo/speechsc > > > --------------050408080208010203010108 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit I agree this needs to be clarified. Since the explicit purpose of this message was for barge-in implementation, I guess there was some implied assumption of treating DTMF/speech.
May be we should have named it START-OF-INPUT. :-))

Sarvi

Pierre Forgues wrote:
Sarvi, I believe this should be made clearer in the specification
document.  I could not find the place where this is stated in the
section on START-OF-SPEECH. /Pierre

-----Original Message-----
From: Sarvi Shanmugham [mailto:sarvi@cisco.com] 
Sent: 25 septembre, 2003 12:01
To: Reifenrath, Klaus
Cc: 'speechsc@ietf.org'
Subject: Re: [Speechsc] draft-ietf-speechsc-mrcpv2-00.txt: DTMF barge-in
question

The purpose of the START-OF-SPEECH event was to address the 
implementation of bargein, both speech and DTMF barge-in. The 
START-OF-SPEECH event is expected to be generated when the user starts 
speaking or pressing digits. The client is responsible for conveying the

barge-in event to the synthesizer. The synthesizer should then decided 
whether to barge-in the current playing prompt or not based on barge-in 
flags provided when the SPEAK command was issued.

Sarvi

If the source is

Reifenrath, Klaus wrote:

  
It is not clear to me, how the synthesizer is stopped on DTMF barge-in.
In case of voice barge-in the recognizer is responsible to send
START-OF-SPEECH (see chapter 8.12). Is this also true in case of DTMF
barge-in?



_______________________________________________
Speechsc mailing list
Speechsc@ietf.org
https://www1.ietf.org/mailman/listinfo/speechsc

 

    


_______________________________________________
Speechsc mailing list
Speechsc@ietf.org
https://www1.ietf.org/mailman/listinfo/speechsc
--------------050408080208010203010108-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Thu Sep 25 16:30:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19971 for ; Thu, 25 Sep 2003 16:30:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2ckW-0002BD-6P for speechsc-archive@odin.ietf.org; Thu, 25 Sep 2003 16:30:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h8PKU4bx008373 for speechsc-archive@odin.ietf.org; Thu, 25 Sep 2003 16:30:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2ckV-0002Ay-Up for speechsc-web-archive@optimus.ietf.org; Thu, 25 Sep 2003 16:30:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19931 for ; Thu, 25 Sep 2003 16:29:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A2ckU-0005dN-00 for speechsc-web-archive@ietf.org; Thu, 25 Sep 2003 16:30:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A2ckT-0005dK-00 for speechsc-web-archive@ietf.org; Thu, 25 Sep 2003 16:30:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2ckU-00029M-Ft; Thu, 25 Sep 2003 16:30:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2cjp-00028Z-RT for speechsc@optimus.ietf.org; Thu, 25 Sep 2003 16:29:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19903 for ; Thu, 25 Sep 2003 16:29:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A2cjn-0005d7-00 for speechsc@ietf.org; Thu, 25 Sep 2003 16:29:19 -0400 Received: from ns1.nuance.com ([208.252.220.9]) by ietf-mx with esmtp (Exim 4.12) id 1A2cjn-0005cb-00 for speechsc@ietf.org; Thu, 25 Sep 2003 16:29:19 -0400 Received: from mpb1exbr01.nuance.com (mpb1exbr01.nuance.com [10.0.0.43]) by ns1.nuance.com (Postfix) with ESMTP id DC870741DD; Thu, 25 Sep 2003 13:35:07 -0700 (PDT) Received: from mtb1exch01.nuance.com ([10.3.2.6]) by mpb1exbr01.nuance.com with Microsoft SMTPSVC(5.0.2195.5329); Thu, 25 Sep 2003 13:28:47 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C383A3.9E375226" Subject: RE: [Speechsc] draft-ietf-speechsc-mrcpv2-00.txt: DTMF barge-in question Date: Thu, 25 Sep 2003 16:28:45 -0400 Message-ID: <7DE7C4EF3B7C8B4B82955191378290D8EDC64F@mtb1exch01.nuance.com> Thread-Topic: [Speechsc] draft-ietf-speechsc-mrcpv2-00.txt: DTMF barge-in question Thread-Index: AcODo0jUX9NLklV7RT6kkYhajx0FQgAAEBHg From: "Pierre Forgues" To: "Sarvi Shanmugham" Cc: "Reifenrath, Klaus" , X-OriginalArrivalTime: 25 Sep 2003 20:28:47.0526 (UTC) FILETIME=[9F7E2C60:01C383A3] Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C383A3.9E375226 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Exactly, but rather than change method names at this point, I would be happy if we just made it clear in the supporting text for that method. Thanks. /Pierre =20 -----Original Message----- From: Sarvi Shanmugham [mailto:sarvi@cisco.com]=20 Sent: 25 septembre, 2003 16:26 To: Pierre Forgues Cc: Reifenrath, Klaus; speechsc@ietf.org Subject: Re: [Speechsc] draft-ietf-speechsc-mrcpv2-00.txt: DTMF barge-in question =20 I agree this needs to be clarified. Since the explicit purpose of this message was for barge-in implementation, I guess there was some implied assumption of treating DTMF/speech. May be we should have named it START-OF-INPUT. :-)) Sarvi Pierre Forgues wrote: Sarvi, I believe this should be made clearer in the specification document. I could not find the place where this is stated in the section on START-OF-SPEECH. /Pierre =20 -----Original Message----- From: Sarvi Shanmugham [mailto:sarvi@cisco.com]=20 Sent: 25 septembre, 2003 12:01 To: Reifenrath, Klaus Cc: 'speechsc@ietf.org' Subject: Re: [Speechsc] draft-ietf-speechsc-mrcpv2-00.txt: DTMF barge-in question =20 The purpose of the START-OF-SPEECH event was to address the=20 implementation of bargein, both speech and DTMF barge-in. The=20 START-OF-SPEECH event is expected to be generated when the user starts=20 speaking or pressing digits. The client is responsible for conveying the =20 barge-in event to the synthesizer. The synthesizer should then decided=20 whether to barge-in the current playing prompt or not based on barge-in=20 flags provided when the SPEAK command was issued. =20 Sarvi =20 If the source is =20 Reifenrath, Klaus wrote: =20 =20 It is not clear to me, how the synthesizer is stopped on DTMF barge-in. In case of voice barge-in the recognizer is responsible to send START-OF-SPEECH (see chapter 8.12). Is this also true in case of DTMF barge-in? =20 =20 =20 _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc =20 =20 =20 =20 =20 =20 _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc =20 =20 ------_=_NextPart_001_01C383A3.9E375226 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Exactly, but rather than change = method names at this point, I would be happy if we just made it clear in the supporting text for that method.  Thanks.  = /Pierre

 

-----Origi= nal Message-----
From: Sarvi Shanmugham [mailto:sarvi@cisco.com]
Sent: 25 septembre, 2003 = 16:26
To: Pierre Forgues
Cc: Reifenrath, Klaus; speechsc@ietf.org
Subject: Re: [Speechsc] draft-ietf-speechsc-mrcpv2-00.txt: DTMF barge-in = question

 

I agree this = needs to be clarified. Since the explicit purpose of this message was for barge-in implementation, I guess there was some implied assumption of treating DTMF/speech.
May be we should have named it START-OF-INPUT. :-))

Sarvi

Pierre Forgues wrote:

Sarvi, I believe =
this should be made clearer in the =
specification
document.  I could not find the place =
where this is stated in the
section on START-OF-SPEECH. =
/Pierre
 
-----Original =
Message-----
From: Sarvi Shanmugham [mailto:sarvi@cisco.com] =

Sent: 25 septembre, 2003 =
12:01
To: Reifenrath, =
Klaus
Cc: 'speechsc@ietf.org'
Subject: Re: [Speechsc] =
draft-ietf-speechsc-mrcpv2-00.txt: DTMF =
barge-in
question
 
The purpose of the START-OF-SPEECH event was =
to address the 
implementation of bargein, both speech and =
DTMF barge-in. The 
START-OF-SPEECH event is expected to be =
generated when the user starts 
speaking or pressing digits. The client is =
responsible for conveying the
 
barge-in event to the synthesizer. The =
synthesizer should then decided 
whether to barge-in the current playing =
prompt or not based on barge-in 
flags provided when the SPEAK command was =
issued.
 
Sarvi
 
If the source =
is
 
Reifenrath, Klaus =
wrote:
 
  =

It is not clear to me, how the synthesizer is =
stopped on DTMF barge-in.
In case of voice barge-in the recognizer is =
responsible to send
START-OF-SPEECH (see chapter 8.12). Is this =
also true in case of DTMF
barge-in?
 
 
 
______________________________________________=
_
Speechsc mailing =
list
Speechsc@ietf.org=

https://www1.iet=
f.org/mailman/listinfo/speechsc
 
 
 
    =

 
 
______________________________________________=
_
Speechsc mailing =
list
Speechsc@ietf.org=

https://www1.iet=
f.org/mailman/listinfo/speechsc
 
  =
=00 ------_=_NextPart_001_01C383A3.9E375226-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Tue Sep 30 15:48:30 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11899 for ; Tue, 30 Sep 2003 15:48:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4QTf-0001Ed-98 for speechsc-archive@odin.ietf.org; Tue, 30 Sep 2003 15:48:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h8UJm7BJ004743 for speechsc-archive@odin.ietf.org; Tue, 30 Sep 2003 15:48:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4QTf-0001EQ-4U for speechsc-web-archive@optimus.ietf.org; Tue, 30 Sep 2003 15:48:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11860 for ; Tue, 30 Sep 2003 15:47:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A4QTd-00040L-00 for speechsc-web-archive@ietf.org; Tue, 30 Sep 2003 15:48:05 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A4QTd-00040H-00 for speechsc-web-archive@ietf.org; Tue, 30 Sep 2003 15:48:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4QTZ-0001DX-It; Tue, 30 Sep 2003 15:48:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4QTQ-0001DI-2c for speechsc@optimus.ietf.org; Tue, 30 Sep 2003 15:47:52 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11847 for ; Tue, 30 Sep 2003 15:47:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A4QTO-000405-00 for speechsc@ietf.org; Tue, 30 Sep 2003 15:47:50 -0400 Received: from bay1-f78.bay1.hotmail.com ([65.54.245.78] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 1A4QTO-0003zq-00 for speechsc@ietf.org; Tue, 30 Sep 2003 15:47:50 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 30 Sep 2003 12:47:19 -0700 Received: from 129.33.49.251 by by1fd.bay1.hotmail.msn.com with HTTP; Tue, 30 Sep 2003 19:47:19 GMT X-Originating-IP: [129.33.49.251] X-Originating-Email: [m_wade_hartley@hotmail.com] From: "Matthew Hartley" To: speechsc@ietf.org Date: Tue, 30 Sep 2003 15:47:19 -0400 Mime-Version: 1.0 Content-Type: text/html Message-ID: X-OriginalArrivalTime: 30 Sep 2003 19:47:19.0767 (UTC) FILETIME=[A8BD0670:01C3878B] Subject: [Speechsc] Status of MRCP v2 Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: ,

Hello,

I just wanted to know the status of MRCP v2 interms of its submission to the IESG. 

Thanks,

Matt


Get McAfee virus scanning and cleaning of incoming attachments. Get Hotmail Extra Storage! _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Tue Sep 30 17:29:24 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16668 for ; Tue, 30 Sep 2003 17:29:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4S3K-0007Bm-LB for speechsc-archive@odin.ietf.org; Tue, 30 Sep 2003 17:29:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h8ULT2UV027633 for speechsc-archive@odin.ietf.org; Tue, 30 Sep 2003 17:29:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4S3K-0007Bc-Hy for speechsc-web-archive@optimus.ietf.org; Tue, 30 Sep 2003 17:29:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16652 for ; Tue, 30 Sep 2003 17:28:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A4S3I-0005a8-00 for speechsc-web-archive@ietf.org; Tue, 30 Sep 2003 17:29:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A4S3H-0005a5-00 for speechsc-web-archive@ietf.org; Tue, 30 Sep 2003 17:28:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4S3I-0007Ax-TL; Tue, 30 Sep 2003 17:29:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4S2U-0007AU-GN for speechsc@optimus.ietf.org; Tue, 30 Sep 2003 17:28:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16645 for ; Tue, 30 Sep 2003 17:28:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A4S2F-0005Zk-00 for speechsc@ietf.org; Tue, 30 Sep 2003 17:27:55 -0400 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1A4S2F-0005ZY-00 for speechsc@ietf.org; Tue, 30 Sep 2003 17:27:55 -0400 Received: from cisco.com (171.68.223.137) by sj-iport-3.cisco.com with ESMTP; 30 Sep 2003 14:32:20 -0700 Received: from [10.32.254.182] (stealth-10-32-254-182.cisco.com [10.32.254.182]) by sj-core-3.cisco.com (8.12.6/8.12.6) with SMTP id h8ULRNYb022355; Tue, 30 Sep 2003 14:27:23 -0700 (PDT) Date: Tue, 30 Sep 2003 17:27:20 -0400 From: "David R. Oran" To: Matthew Hartley , speechsc@ietf.org Subject: Re: [Speechsc] Status of MRCP v2 Message-ID: <119879000.1064942840@[10.32.254.182]> In-Reply-To: References: X-Mailer: Mulberry/3.1.0b8 (Win32) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========6393E93EB024617B9C4B==========" Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , --==========6393E93EB024617B9C4B========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable --On Tuesday, September 30, 2003 3:47 PM -0400 Matthew Hartley=20 wrote: > > > > Hello, > > I just wanted to know the status of MRCP v2 interms of its submission to > the IESG. > The first version of the draft confirming to the working group requirements = has recently appeared in the archives. We still need to incorporate material on SI and SV to complete the=20 technical scope. The specification also needs wide review and some "cooking time" in the=20 technical community. We will be going over comments on and issues with the=20 specification on the WG mailing list and at the next IETF meeting in=20 November. Assuming everything goes smoothly, we have a milestone to submit to the=20 IESG for proposed standards track sometime around the end of the calendar=20 year. Please take time and energy to give the spec a thorough review! > Thanks, > > Matt Dave Oran, speechsc WG co-chair. ------------------------ David R. Oran Cisco Systems 7 Ladyslipper Lane Acton, MA 01720 Office: +1 978 264 2048 VoIP: +1 408 571 4576 Email: oran@cisco.com --==========6393E93EB024617B9C4B========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: Mulberry PGP Plugin v3.0 Comment: processed by Mulberry PGP Plugin iQA/AwUBP3n1OY1mhLZU3SrmEQI69QCePC95y9sL9jKH2t4wNT2ASd+X6VcAoOuF rVWsqzam6yTDNyN3GoVwh7Jw =0Y88 -----END PGP SIGNATURE----- --==========6393E93EB024617B9C4B==========-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc