ISSUE-18: clarify that
clarify that
- State:
- CLOSED
- Product:
- MMI Architecture
- Raised by:
- Deborah Dahl
- Opened on:
- 2006-09-28
- Description:
- In section 5.2 (http://www.w3.org/TR/2006/WD-mmi-arch-20060414/#N10182) we
state that \"modality components are responsible for controlling the various
input and output modalities on the device\". However, at the Chicago f2f we
discussed use cases where a component doesn\'t directly process a modality.
Examples might be a flow controller or a natural language processing component
that receives either the tokens output by a speech recognizer or the tokens
output by a handwriting recognition component, and extracts their semantics.
The description of modality components would be clearer if some version of the
the following sentence were added. \"However, modality components may in
addition be used to perform general processing functions not directly
associated with a specific modality, for example, dialog flow control or
natural language processing.\" - Related Actions Items:
- No related actions
- Related emails:
- ISSUE-87 (EMO-18): Redundancy of <modality> with EMMA? [EmotionML] (from sysbot+tracker@w3.org on 2009-11-02)
- Re: [emo] Issues in EmotionML (from ashimura@w3.org on 2009-10-31)
- [emo] Issues in EmotionML (from schroed@dfki.de on 2009-10-30)
- ISSUE-18: clarify that \\\'modality\\\' components don\\\'t have to directly process modalities [MMI Architecture] (from dean+cgi@w3.org on 2006-09-28)
Related notes:
No additional notes.
Display change log
