ACTION-259: Think about ways to identify potential features that might be "at risk"
Think about ways to identify potential features that might be "at risk"
- State:
- closed
- Person:
- Christian Peter
- Due on:
- January 11, 2012
- Created on:
- December 14, 2011
- Associated Product:
- EmotionML
- Related emails:
- [emo] mintues EmotionML meeting (from Felix.Burkhardt@telekom.de on 2012-02-08)
- [emo] minutes - 4 January 2012 (from ashimura@w3.org on 2012-01-05)
- [emo] minutes of call on 14 Dec 2011 (from christian.peter@igd-r.fraunhofer.de on 2011-12-14)
Related notes:
as confirmed by Phillippe we need
- 2 implementations for features that are "required"
- 1 implementation for features that are optional
Display change log.