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.

 The use of embedded emma:one-of is under consideration for future implementations. AT&T considers emma:group an important feature for capturing multimodal inputs and intends to include this in future implementations. This feature was not relevant for the EMMA implementation described in this report. AT&T considers emma:group-info an important feature for capturing multimodal inputs and intends to include this in future implementations. This feature was not relevant for the EMMA implementation described in this report. AT&T considers emma:sequence an important feature for representing sequences of gestured input and intends to include this in future implementations. This feature was not relevant for the EMMA implementation described in this report. emma:literal proved useful both for literal semantic results and for raw results from speech recognition. This test assertion covers the case where emma:model is embedded inline in an emma:interpretation or emma:one-of. This case is not described in the specification. Furthermore, this contradicts the schema, which only permits emma:model as a child of emma:emma. Request removal of this test assertion. This constraint is not described in the specification. Request removal of this test. This constraint is not described in the specification. Request removal of this test. This feature is under consideration for future implementations of language understanding and multimodal integration. This feature is not described in the specification. Request removal of this test. emma:time-ref-uri feature under consideration for future implementations. emma:time-ref-anchor feature under consideration for future implementations. emma:offset-to-start feature under consideration for future implementations. AT&T considers this feature important for implementations of multimodal integration, however the implementation described here does not integrate multimodal inputs and so this feature was not implemented. AT&T considers this feature important for implementations of multimodal integration, however the implementation described here does not integrate multimodal inputs and so this feature was not implemented. AT&T considers this feature important for implementations of multimodal integration, however the implementation described here does not integrate multimodal inputs and so this feature was not implemented.