IETF Logo Mail Archive

Re: [Dmsp] RE: DMSP vs EMMA

Chris Cross <xcross@us.ibm.com> Fri, 14 April 2006 16:47 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FURSA-0002pm-Ie; Fri, 14 Apr 2006 12:47:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FURS8-0002iE-M2 for dmsp@ietf.org; Fri, 14 Apr 2006 12:47:24 -0400
Received: from e34.co.us.ibm.com ([32.97.110.152]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FURS8-00086O-AS for dmsp@ietf.org; Fri, 14 Apr 2006 12:47:24 -0400
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e34.co.us.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k3EGlNa4032060 for <dmsp@ietf.org>; Fri, 14 Apr 2006 12:47:23 -0400
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay04.boulder.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id k3EGohV5178416 for <dmsp@ietf.org>; Fri, 14 Apr 2006 10:50:43 -0600
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id k3EGlN7g019717 for <dmsp@ietf.org>; Fri, 14 Apr 2006 10:47:23 -0600
Received: from d03nm119.boulder.ibm.com (d03nm119.boulder.ibm.com [9.17.195.145]) by d03av01.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id k3EGlN4Q019707 for <dmsp@ietf.org>; Fri, 14 Apr 2006 10:47:23 -0600
In-Reply-To: <6806C66D71ED9241BAECC0478173B71F7A87E0@de01exm69.ds.mot.com>
Subject: Re: [Dmsp] RE: DMSP vs EMMA
To: dmsp@ietf.org
X-Mailer: Lotus Notes Release 7.0 HF85 November 04, 2005
Message-ID: <OF6BE5985B.2209C9E9-ON85257150.005B9D73-85257150.005C339D@us.ibm.com>
From: Chris Cross <xcross@us.ibm.com>
Date: Fri, 14 Apr 2006 12:47:05 -0400
X-MIMETrack: Serialize by Router on D03NM119/03/M/IBM(Release 6.53HF654 | July 22, 2005) at 04/14/2006 10:50:31
MIME-Version: 1.0
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
X-BeenThere: dmsp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Multimodal Synchronization Protocol <dmsp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dmsp>, <mailto:dmsp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/dmsp>
List-Post: <mailto:dmsp@ietf.org>
List-Help: <mailto:dmsp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dmsp>, <mailto:dmsp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1689489158=="
Errors-To: dmsp-bounces@ietf.org




> DSMP messages are really closed to VoiceXML events / commands
> (NOINPUT, NOMATCH,…). Multimodal services can be done without
> VoiceXML browser (without VXML scripts) with only simple ASR/TTS
> ressources (only launch recognition or synthesis process). Do you
> plan to open / enlarge the DMSP protocol to "simple" Voice server
> (ASR+TTS without VoiceXML) ?

I agree with other's responses to Aurelien. However, we must take care to
not duplicate the function of MRCP. The domain we're working in is the
sychronization of modalities within a dialog. I think if all an application
wants to do is speech enable itself through a low level speech engine
interface then MRCP may be the correct route for that.

chris cross
_______________________________________________
Dmsp mailing list
Dmsp@ietf.org
https://www1.ietf.org/mailman/listinfo/dmsp

v2.23.0 | Report a Bug | By Email