ISSUE-31: [cr] need to allow for emma:interpretation to be empty in case where emma:function=
[cr] need to allow for emma:interpretation to be empty in case where emma:function=
- State:
- CLOSED
- Product:
- EMMA
- Raised by:
- Michael Johnston
- Opened on:
- 2006-12-12
- Description:
- Following review of VBWG feedback, the specification needs to be revised
to allow for emma:interpretation to be empty not just when emma:uninterpreted
or emma:no-input are = true, but also if emma:function=\"recording\"
Need to adjust schema accordingly also. - Related Actions Items:
- No related actions
- Related emails:
- ISSUE-100 (EMO-31): Timing details: onset, hold, decay? [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)
- Re: [emma] resolution of open issues in issue tracker (from ashimura@w3.org on 2007-10-31)
- [emma] resolution of open issues in issue tracker (from johnston@research.att.com on 2007-10-29)
- Re: issue tracker issues (from ashimura@w3.org on 2007-03-28)
- [emma] draft 032107-diff (some more changes and list of open issues) (from paolo.baggia@loquendo.com on 2007-03-21)
- ISSUE-31: [cr] need to allow for emma:interpretation to be empty in case where emma:function=\\\'recording\\\' [EMMA] (from dean+cgi@w3.org on 2006-12-12)
Related notes:
Resolved in discussions. Specification updated (4.2.4) to explicitly describe the case of recordings as an instance of emma:uninterpreted="true"
The notation for uninterpreted input MAY refer to any possible stage of interpretation processing, including raw transcriptions. For instance, no interpretation would be produced for stages performing pure signal capture such as audio recordings. Likewise, if a spoken input was recognized but cannot be parsed by a language understanding component, it can be tagged as emma:uninterpreted as in the following example:
Display change log
