ISSUE-127: Emotion attributes for easier use with other markup languages, e.g. HTML 5
Emotion attributes for easier use with other markup languages, e.g. HTML 5
- State:
- OPEN
- Product:
- EmotionML1.1
- Raised by:
- Kazuyuki Ashimura
- Opened on:
- 2010-02-03
- Description:
- Related Actions Items:
- No related actions
- Related emails:
- [emo] Issues for EmotionML 1.1 (from enrico.zovato@loquendo.com on 2011-03-16)
- [emo] Deferring work on emotion for HTML5 to time beyond EmotionML 1.0 (from marc.schroeder@dfki.de on 2010-11-04)
- [all] f2f agenda (from ashimura@w3.org on 2010-11-01)
- [all] MMI agenda for October 25, 2010 and draft agenda for Lyon f2f (from dahl@conversational-technologies.com on 2010-10-25)
- [emo] minutes from EmotionML call - 28 April 2010 (from paolo.baggia@loquendo.com on 2010-04-28)
- Re: [emo] EmotionML validation, namespaces vs. HTML5, and element names vs. attribute values (from ashimura@w3.org on 2010-02-04)
- RE: [emo] EmotionML validation, namespaces vs. HTML5, and element names vs. attribute values (from dahl@conversational-technologies.com on 2010-02-03)
- [emo] EmotionML validation, namespaces vs. HTML5, and element names vs. attribute values (from marc.schroeder@dfki.de on 2010-02-03)
- [emo] minutes - 3 Feb. 2010 (from ashimura@w3.org on 2010-02-03)
- ISSUE-127: Must Emotion ML work with HTML 5? (from sysbot+tracker@w3.org on 2010-02-03)
Related notes:
During informal discussions at the EmotionML workshop, the difficulties of capturing multimodal user behaviour in web applications was identified as an important obstacle to web applications able to sense user emotions (part of our use case 2).
On the other hand, examples were given for use case 1 (human annotation of emotional data): crowdsourcing, live annotation of video, and for use case 3 (web pages with an avatar showing emotional expressivity).
Discussion at the f2f in Lyon on 4 November clarified issues around use of emotion in webapps. Key issues would be "hooks" that could be used in relation to emotion, such as a JavaScript API or DOM Events, to relate emotion-related events to what is happening in the browser.
It was pointed out that it is important to represent only the small piece of most relevant information -- people would not want to parse 30kB of XML to find out that nothing has changed. So the idea would be to think of emotion-related events and representations for web applications separately from the current EmotionML.
renaming issue to reflect the current plan. See also issue raised by WAI-PF -- http://www.w3.org/2002/mmi/Group/track/issues/184
Marc Schröder, 7 Sep 2011, 09:33:49ach, not http://www.w3.org/2002/mmi/Group/track/issues/184 -- the correct link is http://www.w3.org/2002/mmi/Group/track/issues/185
Marc Schröder, 7 Sep 2011, 09:35:19Display change log
