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

View: New views
1 Messages — Rating Filter:   Alert me  

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

by johnston-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

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.


<system-report name="AT&T EMMA Implementation Report">
        <testimonial>
       
        <p><b>Executive Summary</b></p>
       
        <p>
        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.
        </p>
       
        <p>
        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.
        </p>
       
        <p>
        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.
        </p>
       
        <p><b>Technical Details</b></p>
       
        <p>Suggest use of emma:literal for raw recognition results as well as for
        literal semantic results from language understanding.</p>
       
        <p>Request removal of test 1501 since the use of emma:uninterpreted to
        indicate below threshold input is not described in the EMMA specification.
        </p>
       
        <p>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.
        </p>

    <p>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.</p>
       
        </testimonial>
        <assert id="100" res="pass"></assert>
        <assert id="200" res="pass"></assert>
        <assert id="201" res="pass"></assert>
        <assert id="300" res="pass"></assert>
        <assert id="301" res="pass"></assert>
        <assert id="310" res="not-impl">The use of embedded emma:one-of is under consideration for future implementations.</assert>
        <assert id="400" res="not-impl">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.</assert>
        <assert id="402" res="not-impl">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.</assert>
        <assert id="500" res="not-impl">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.</assert>
       
        <assert id="600" res="pass"></assert>
        <assert id="602" res="pass"></assert>
        <assert id="603" res="pass"></assert>
        <assert id="604" res="pass"></assert>
        <assert id="605" res="pass"></assert>
        <assert id="606" res="pass"></assert>
        <assert id="607" res="pass"></assert>
        <assert id="608" res="pass"></assert>
        <assert id="609" res="pass"></assert>
       
        <assert id="700" res="pass">emma:literal proved useful both for literal semantic results and for raw results from speech recognition.</assert>
       
        <assert id="800" res="pass"></assert>
        <assert id="801" res="not-impl">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.</assert>
        <assert id="810" res="pass"></assert>
        <assert id="811" res="pass"></assert>
       
        <assert id="901" res="pass"></assert>
        <assert id="902" res="pass">This constraint is not described in the specification. Request removal of this test.</assert>
        <assert id="903" res="pass">This constraint is not described in the specification. Request removal of this test.</assert>
        <assert id="904" res="pass"></assert>
       
        <assert id="910" res="pass"></assert>
        <assert id="911" res="pass"></assert>
        <assert id="1000" res="pass"></assert>
        <assert id="1001" res="pass"></assert>
        <assert id="1002" res="pass"></assert>
        <assert id="1100" res="pass"></assert>
        <assert id="1201" res="pass"></assert>
        <assert id="1300" res="pass"></assert>
        <assert id="1400" res="pass"></assert>
        <assert id="1500" res="not-impl">This feature is under consideration for future implementations of language understanding and multimodal integration.</assert>
        <assert id="1501" res="not-impl">This feature is not described in the specification. Request removal of this test. </assert>
        <assert id="1600" res="pass"></assert>
        <assert id="1700" res="pass"></assert>
        <assert id="1701" res="pass"></assert>
        <assert id="1800" res="pass"></assert>
        <assert id="1900" res="pass"></assert>
        <assert id="2000" res="pass"></assert>
        <assert id="2100" res="pass"></assert>
        <assert id="2101" res="pass"></assert>
        <assert id="2201" res="not-impl">emma:time-ref-uri feature under consideration for future implementations.</assert>
        <assert id="2202" res="not-impl">emma:time-ref-anchor feature under consideration for future implementations.</assert>
        <assert id="2203" res="not-impl">emma:offset-to-start feature under consideration for future implementations.</assert>
        <assert id="2204" res="pass"></assert>
        <assert id="2300" res="pass"></assert>
        <assert id="2301" res="not-impl">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.</assert>
        <assert id="2310" res="pass"></assert>
        <assert id="2311" res="not-impl">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.</assert>
        <assert id="2320" res="pass"></assert>
        <assert id="2330" res="pass"></assert>
        <assert id="2401" res="not-impl">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.</assert>
        <assert id="2500" res="pass"></assert>
        <assert id="2510" res="pass"></assert>
        <assert id="2600" res="pass"></assert>
        <assert id="2601" res="pass"></assert>
        <assert id="2700" res="not-impl"></assert>
        <assert id="2701" res="not-impl"></assert>
        <assert id="2710" res="not-impl"></assert>
        <assert id="2711" res="not-impl"></assert>
        <assert id="2713" res="not-impl"></assert>
        <assert id="2714" res="not-impl"></assert>
        <assert id="2715" res="not-impl"></assert>
        <assert id="2716" res="not-impl"></assert>
        <assert id="2717" res="not-impl"></assert>
        <assert id="2718" res="not-impl"></assert>
</system-report>
LightInTheBox - Buy quality products at wholesale price!