[Dmsp] RE: DMSP vs EMMA

"Engelsma Jonathan-QA2678" <Jonathan.Engelsma@motorola.com> Fri, 14 April 2006 14:05 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FUOv3-0007y0-Fr; Fri, 14 Apr 2006 10:05:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FUOv2-0007xv-Km for dmsp@ietf.org; Fri, 14 Apr 2006 10:05:04 -0400
Received: from motgate8.mot.com ([129.188.136.8]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FUOv1-0002lA-89 for dmsp@ietf.org; Fri, 14 Apr 2006 10:05:04 -0400
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131]) by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k3EELTR9015565 for <dmsp@ietf.org>; Fri, 14 Apr 2006 07:21:31 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25]) by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id k3EELWwO012630 for <dmsp@ietf.org>; Fri, 14 Apr 2006 09:21:32 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 14 Apr 2006 10:04:59 -0400
Message-ID: <6806C66D71ED9241BAECC0478173B71F7A87E0@de01exm69.ds.mot.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: DMSP vs EMMA
thread-index: AcZfm7ykm0/YDfKPSiKTi3xazvmyvgALF46A
From: "Engelsma Jonathan-QA2678" <Jonathan.Engelsma@motorola.com>
To: "GUILLOU Aurelien RD-SIRP-LAN" <aurelien.guillou@francetelecom.com>
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 88b11fc64c1bfdb4425294ef5374ca07
Cc: dmsp@ietf.org
Subject: [Dmsp] RE: DMSP vs EMMA
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="===============1419575148=="
Errors-To: dmsp-bounces@ietf.org

Hello Aurelien,
 
See my response embedded below.  Thanks for reading the draft and providing your input.
 
-jre
 
ps - I've cc'd the dmsp list on my response, as there are others there who have made similar suggestions.

________________________________

From: GUILLOU Aurelien RD-SIRP-LAN [mailto:aurelien.guillou@francetelecom.com] 
Sent: Friday, April 14, 2006 4:17 AM
To: Engelsma Jonathan-QA2678
Subject: DMSP vs EMMA



Hi Jonathan, 

I've read the specification of the EMMA at the W3C, and I wonder how we can insert the EMMA messages in the 
DMSP protocol. My view is that EMMA should describe the recognition results for example from the server to the client in 

a DSMP response MESSAGE. Is DSMP should really encapsulates EMMA messages ?  

JRE: Yes.  EMMA messages could be carried as "extended recognition results".  See section 4.2.2.9 in the spec. 

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) ?   

JRE: We intentionally designed the protocol to operate at the dialog level, as this helps keep the protocol amenable to implementations that involve low bandwidth, high latency networks and resource constrained clients.   That said, you aren't the first one to bring this point up both on the mailing list and in offline discussions.  If there are additional features required by the particular multimodal use cases you have in mind that aren't already adequately addressed by MRCP,  please share them on the dmsp list.    We would like to maintain support for dialog level control messages, but at the same time are open to supporting other configurations as well, as long as we can keep the message set and associated state machines simple and compact. 

Thanks for your response, 
Best Regards. 
Aurélien. 

Aurélien Guillou 
France Télécom 
Recherche & Développement 
SIRP/SIS/SIT 
Ingénieur R&D 
2, avenue Pierre Marzin 
22307 LANNION Cedex 
Tel : + 33 (0)2 96 05 94 26 
Fax : + 33 (0)2 96 05 18 49 
http://www.francetelecom.com/rd <http://www.francetelecom.com/rd>  


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