[emma] AT&T Implementation Report for EMMA 1.0 Specification

AT&T 

 

EMMA Implementation Report

 

Executive Summary:

 

AT&T recognizes the crucial role of standards in the 

creation and deployment of next generation services supporting 

more natural and effective interaction through spoken

and multimodal interfaces, and continues to be a firm supporter

of W3C's activities in the area of spoken and multimodal standards.

As a participating member of the W3C Multimodal Interaction

working group, AT&T welcomes the Extensible Multimodal Annotation (EMMA)

1.0 Candidate Recommendation.

 

EMMA 1.0 provides a detailed language for capturing the

range of possible interpretations of multimodal inputs and their

associated metadata through a full range of input processing stages,

from recognition, through understanding and integration, to 

dialog management. The creation of a common standard for

the representation of multimodal inputs is critical in enabling

rapid prototyping of multimodal applications, facilitating 

interoperation of components from different vendors, and

enabling effective logging and archiving of multimodal interactions.

            

AT&T is very happy to contribute to the further progress of the 

emerging EMMA standard by submitting an EMMA 1.0 implementation report.

EMMA 1.0 results are already available from an AT&T 

EMMA server which is currently being used in the development

of numerous multimodal prototypes and trial services.

            

Technical Details:

            

Suggest use of emma:literal for raw recognition results as well as for 

literal semantic results from language understanding.

            

Request removal of test 1501 since the use of emma:uninterpreted to

indicate below threshold input is not described in the EMMA
specification. 

            

Request removal of tests 902 and 903 since these constraints on the 

resource attribute on emma:derived-from are not described in the EMMA

specification.

 

Request removal of test assertion 801 for inline emma:model since

this test contradicts the EMMA schema, in which emma:model can only be

a child of emma:emma.