ISSUE-100: Timing details: onset, hold, decay?
Timing details: onset, hold, decay?
- State:
- CLOSED
- Product:
- EmotionML
- Raised by:
- Marc Schröder
- Opened on:
- 2009-11-02
- Description:
- http://www.w3.org/2002/mmi/Group/emotionml/#ISSUE-100
Is it important to provide for explicit elements or attributes to annotate onset, hold and decay phases? Here's an example for a possible syntax:
<emoml:timing>
<emoml:onset start="00:00:01:00" duration="00:00:04:00" />
<emoml:hold start="00:00:05:00" duration="00:00:02:00" />
<emoml:decay start="00:00:07:00" duration="00:00:06:00" />
</emoml:timing> - Related Actions Items:
- No related actions
- Related emails:
- [emo] Issues for EmotionML 1.1 (from enrico.zovato@loquendo.com on 2011-03-16)
- [emo] EmotionML draft: section on relative timing removed (from marc.schroeder@dfki.de on 2010-03-15)
- [emma] subgroup call tomorrow Dec 10th (from johnston@research.att.com on 2009-12-09)
- [emo] Issues in EmotionML (updated to tracker numbering scheme) (from schroed@dfki.de on 2009-11-06)
- ISSUE-100 (EMO-31): Timing details: onset, hold, decay? [EmotionML] (from sysbot+tracker@w3.org on 2009-11-02)
Related notes:
We settled for EMMA-like representations for absolute time, and media fragment URIs for the <link> tags, see http://www.w3.org/2010/03/03-multimodal-minutes.html
Marc Schröder, 15 Mar 2010, 09:46:22Display change log