ISSUE-151: Shortcut attributes for specifying e.g. gender, age (convapps issue 2, 7)
Shortcut attributes for specifying e.g. gender, age (convapps issue 2, 7)
- State:
- CLOSED
- Product:
- EMMA 1.1
- Raised by:
- Michael Johnston
- Opened on:
- 2010-07-22
- Description:
- If they are sufficiently common use cases, for metadata such as the emotional state of the user,
would be it be desirable to have simple attributes in EMMA for specifying these without having to embed more detailed markup in the application semantics or in emma:info.
e.g. an emma:emotion attribute
Alternatively, we could add some information text about how you can use emma:info for this purpose.
- Related Actions Items:
- No related actions
- Related emails:
- [emma] minutes June 30, 2011 (from dahl@conversational-technologies.com on 2011-06-30)
- [convapps workshop] summary of MMI discussion of use cases (from dahl@conversational-technologies.com on 2010-09-10)
- [emma] EMMA minutes August 12, 2010 (from dahl@conversational-technologies.com on 2010-08-12)
- Re: [EMMA] minutes 22 July 2010 (ISSUE-151, ISSUE-152, ISSUE-153, ISSUE-144) (from ashimura@w3.org on 2010-07-23)
- Re: [EMMA] minutes 22 July 2010 (ISSUE-151, ISSUE-152, ISSUE-153, ISSUE-144) (from johnston@research.att.com on 2010-07-22)
- [EMMA] minutes 22 July 2010 (ISSUE-151, ISSUE-152, ISSUE-153, ISSUE-144) (from dburnett@voxeo.com on 2010-07-22)
- ISSUE-151: Shortcut attributes for specifying e.g. gender, age [EMMA 1.1] (from sysbot+tracker@w3.org on 2010-07-22)
Related notes:
(from the June 2011 f2f) Gender, age, etc.,seem like a relatively low priority, but they might be useful and don't seem too hard to specify. Emotion, on the other hand, should be specified with EmotionML. The other question is should we define an extensibility mechanism, so that we can handle other attributes, especially ones that might come up in other modalities?
Deborah Dahl, 20 Jun 2011, 21:18:53(from the June 2011 f2f) Gender, age, etc.,seem like a relatively low priority, but they might be useful and don't seem too hard to specify. Emotion, on the other hand, should be specified with EmotionML. The other question is should we define an extensibility mechanism, so that we can handle other attributes, especially ones that might come up in other modalities?
Deborah Dahl, 20 Jun 2011, 21:19:30Display change log
