ISSUE-72: Require meaningful minimal emotion representation

Require meaningful minimal emotion representation

State:
CLOSED
Product:
EmotionML
Raised by:
Marc Schröder
Opened on:
2009-11-02
Description:
http://www.w3.org/2002/mmi/Group/emotionml/#ISSUE-72
Maybe it should be required that at least one of <category>, <dimensions>, <appraisals> and <action-tendencies> MUST be present? Otherwise it is possible not to say anything about the emotion as such. Or should <intensity> be included in this list? Does it make sense to state the intensity of an emotion but not its nature?
Related Actions Items:
No related actions
Related emails:
  1. ISSUE-160: Represent an emotion's intensity but not it's nature [EmotionML] (from sysbot+tracker@w3.org on 2010-10-18)
  2. [emo] telco minutes (from Felix.Burkhardt@telekom.de on 2010-08-18)
  3. [emo] minutes from EmotionML call - 28 April 2010 (from paolo.baggia@loquendo.com on 2010-04-28)
  4. ISSUE-72 (EMO-3): Require meaningful minimal emotion representation [EmotionML] (from sysbot+tracker@w3.org on 2009-11-02)

Related notes:

Group agreed on 18-08-2010 to require at least one of <category>, <dimension>, <appraisal> and <action-tendency>.

Marc Schröder, 18 Aug 2010, 09:52:16

Display change log ATOM feed


Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 72.html,v 1.1 2017/02/13 15:51:02 ted Exp $