ISSUE-94: Position on a timeline for externally linked objects
Position on a timeline for externally linked objects
- State:
- CLOSED
- Product:
- EmotionML
- Raised by:
- Marc Schröder
- Opened on:
- 2009-11-02
- Description:
- http://www.w3.org/2002/mmi/Group/emotionml/#ISSUE-94
Position on a time line in externally linked objects needs to be finalized.
Agreement was found to include absolute and relative timing. Start and end provision is preferred over provision of a duration attribute. Further no onset, hold, or decay will be included at the moment. However, the following questions remain:
* How should timing be defined syntactically?
* It needs to be specified where timing may occur, that is, is it an element or an attribute (as presently contained by start and end). Thereby only one of these choices should exist.
- Related Actions Items:
- No related actions
- Related emails:
- [emo] minutes from EmotionML call - 28 April 2010 (from paolo.baggia@loquendo.com on 2010-04-28)
- [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-94 (EMO-25): Position on a timeline for externally linked objects [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:48:13Display change log