IETF Logo Mail Archive

RE: [Dmsp] RE: DMSP vs EMMA

"Ferrans James-JFERRAN1" <James.Ferrans@motorola.com> Fri, 14 April 2006 18:02 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FUScL-0002qU-Fl; Fri, 14 Apr 2006 14:02:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FUScL-0002qP-57 for dmsp@ietf.org; Fri, 14 Apr 2006 14:02:01 -0400
Received: from motgate3.mot.com ([144.189.100.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FUScI-0001ya-N2 for dmsp@ietf.org; Fri, 14 Apr 2006 14:02:01 -0400
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234]) by motgate3.mot.com (8.12.11/Motgate3) with ESMTP id k3EINliP026511 for <dmsp@ietf.org>; Fri, 14 Apr 2006 11:23:47 -0700 (MST)
Received: from de01exm66.ds.mot.com (de01exm66.am.mot.com [10.176.8.17]) by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id k3EIDOZ4008181 for <dmsp@ietf.org>; Fri, 14 Apr 2006 13:13:25 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Dmsp] RE: DMSP vs EMMA
Date: Fri, 14 Apr 2006 14:01:56 -0400
Message-ID: <E230F70DA44FB143B1EF1CE5A96F605E014E683C@de01exm66.ds.mot.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Dmsp] RE: DMSP vs EMMA
Thread-Index: AcZf4ysJ19G7qhtzSWmMRNewWGHM9wACQ+mQ
From: Ferrans James-JFERRAN1 <James.Ferrans@motorola.com>
To: Chris Cross <xcross@us.ibm.com>, dmsp@ietf.org
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Cc:
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="===============1629982925=="
Errors-To: dmsp-bounces@ietf.org

I strongly agree.
 
An interesting thought experiment would be to consider if CMD_LOAD_SRC
could contain an MRCP request and the result be an MRCP response.
According to our studies this is quite inefficient, but if it were
possible to (mis)use DMSP in this way, that would indicate that DMSP
isn't making assumptions about its payload, and that we're not
duplicating MRCP's functionality.
 
Jim

________________________________

From: Chris Cross [mailto:xcross@us.ibm.com] 
Sent: Friday, April 14, 2006 11:47 AM
To: dmsp@ietf.org
Subject: Re: [Dmsp] RE: DMSP vs EMMA



> 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