R: [Dmsp] RE: DMSP vs EMMA

["Baggia Paolo" <[e-mail]>]

Chris,

 

EMMA is a good candidate for representing a semantic content. MRCP for instance choose to standardize a former format called NLSML

because EMMA was still not stable enough, so also NLSML would be another candidate and even a serialization of ECMA-262.

 

SISR seems to me feature related to the grammar in use by the applications that should be independent to DMSP, but I might be

wrong.

 

Paolo.

 

________________________________

Da: Chris Cross [mailto:[e-mail]] 
Inviato: mercoledì 19 aprile 2006 16.13
A: Burger, Eric
Cc: [e-mail]
Oggetto: RE: [Dmsp] RE: DMSP vs EMMA

 

Eric,
I think the subject line of this thread is a red herring. DMSP is agnostic on the format of interpretation. It may well be that EMMA is the default that implementors choose. Table 9 shows RESULT_EX type which inclide SI_TYPE and SI. The intent is to allow the negotiation of semantic interpretation type by the endpoints. I show SISR as an example type because at the time of writing it was CR status in the W3C. EMMA is an obvious alternative. But SI type is an application choice orthogonal to the DMSP protocol. We may need to formalize SI_TYPE to include version...

thanks,
chris


Chris Cross
Multimodal Browser Architect
_________________________
IBM Boca Raton
[e-mail]
voice 561.862.2102 t/l 975.2102
mobile [phone]
fax [phone]

 "Burger, Eric" <[e-mail]>



"Burger, Eric" <[e-mail]> 

04/18/2006 05:50 PM

 

To

 
"Ferrans James-JFERRAN1" <[e-mail]>, Chris Cross/West Palm Beach/IBM@IBMUS



cc


<[e-mail]>



Subject


RE: [Dmsp] RE: DMSP vs EMMA

 






I'm not a fan of tunneling MRCPv2.  If one needs MRCPv2, my guess is one would use MRCPv2.

That said, I would offer the same approach to recognition results as we did in MRCPv2.  Virtually any deviation from EMMA is bound to result in a loss of functionality and you can bet that someone will want some extension that gets into EMMA put into DMSP.

Can anyone give a value to having a proprietary DMSP format that differs from EMMA?

The flip side is there are lots of benefits of reusing EMMA:

Same parser / generator
Same data format
Integrates directly with speech engines and browsers
Always "the latest": don't need to hack DMSP every time EMMA gets a new feature

________________________________________
From: Ferrans James-JFERRAN1 [mailto:[e-mail]] 
Sent: Friday, April 14, 2006 2:02 PM
To: Chris Cross; [e-mail]
Subject: RE: [Dmsp] RE: DMSP vs EMMA

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:[e-mail]] 
Sent: Friday, April 14, 2006 11:47 AM
To: [e-mail]
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



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 <mailto:[e-mail]>[e-mail]. Thank you<http://www.loquendo.com>www.loquendo.com
================================================

_______________________________________________
Dmsp mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/dmsp