<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- 

Anvil implementation of the MUMIN 4 coding scheme,
created for the CLARIN annotations, June 2008, Copenhagen.
Authors:
Costanza Navarretta, Patrizia Paggio


Based on the MUMIN 3.3. coding scheme created by
Jens Allwood, Loredana Cerrato, Laila Dybkær, Kristiina Jokinen,
Costanza Navarretta and Patrizia Paggio.

See www.cst.dk/mumin.

Contact:
Patrizia Paggio
Center for Sprogteknologi
University of Copenhagen
Njalsgade 80
DK-2300 CPH S
patrizia@cst.dk 
-->

<annotation-spec>
  <head>
    <valuetype-def>

      <valueset name="F-Basic-type">
          <value-el color="light blue">FeedbackGive
<doc>
The subject shows they have perceived the message and are willing to
maintain contact and go on in the communication. In MUMIN 3.3, the two
subtypes CPU and CP were distinguished.
</doc>
          </value-el>
          <value-el color="light blue">FeedbackElicit
<doc>
The subject elicits willingness to maintain contact and go on in the
communication, or signs that the interlocutor has perceived the
message. In MUMIN 3.3, the two subtypes CPU and CP were distinguished.
</doc>
          </value-el>
      </valueset>

      <valueset name="F-Understand-type">
          <value-el color="yellow">Understand
<doc>
The subject gives or elicits signs that the message is being understood.
</doc>

          </value-el>
          <value-el color="yellow">NonUnderstand
<doc>
The subject gives or elicits signs that the message is not being understood.
</doc>

          </value-el>
      </valueset>

      <valueset name="F-Acceptance-type">
          <value-el color="yellow">Accept
<doc>
The subject gives or elicits signs of agreement.
</doc>
	    </value-el>
          <value-el color="yellow">NonAccept
<doc>
The subject gives or elicits signs of lack of agreement.
</doc>
          </value-el>
      </valueset>

      <valueset name="Emotion/Attitude-type">
        <value-el color="light red">Happy</value-el>
        <value-el color="light red">Sad</value-el>
        <value-el color="light red">Surprised</value-el>
	  <value-el color="light red">Disgusted</value-el>
	  <value-el color="light red">Angry</value-el>
        <value-el color="light red">Frightened</value-el>
	  <value-el color="light red">Certain</value-el>
	  <value-el color="light red">Uncertain</value-el>
	  <value-el color="light red">Interested</value-el>
	  <value-el color="light red">Uninterested</value-el>
	  <value-el color="light red">Disappointed</value-el>
	  <value-el color="light red">Satisfied</value-el>
	  <value-el color="light red">Other</value-el>
      </valueset>

      <valueset name="Turn-type">
          <value-el color="blue">TurnTake
<doc>
The speaker takes a turn that wasn't offered, possibly by interrupting.
</doc>
          </value-el>
          <value-el color="blue">TurnAccept
<doc>
The speaker accepts a turn that is being offered. 
</doc>
          </value-el>
          <value-el color="red">TurnYield
<doc>
The speaker releases the turn under pressure.
</doc>
          </value-el>
          <value-el color="red">TurnElicit
<doc>
The speaker offers the turn to the interlocutor.
</doc>
          </value-el>
          <value-el color="red">TurnComplete
<doc>
The speaker completes the turn as well as the conversation. The turn
is not passed on.
</doc>
          </value-el>
          <value-el color="magenta">TurnHold
<doc>
The speaker wishes to keep the turn (usually done by 
rotating the head and the gaze away from the listener).
</doc>
          </value-el>
      </valueset>

      <valueset name="Sequencing-type">
        <value-el color="pink">SeqOpen
<doc>
Opening uence indicates that a new speech sequence is 
   starting, e.g. a gesture occurring together with the phrase "by the way...".
</doc>
        </value-el>
		  <value-el color="pink">SeqResume
<doc>
Resume sequence indicates that a preceding speech sequence is resumed after an 
interruption or a false start.
</doc>
        </value-el>  
	  <value-el color="pink">SeqContinue
<doc>
Continue sequence indicates that the current speech sequence is going
on, e.g. a gesture occurring together with enumerative phrases such as
"the first... the second... the third...".
</doc>
        </value-el>      
	  <value-el color="pink">SeqClose
<doc>
Closing sequence indicates that the current speech sequence is closed,
e.g. a gesture occurring together with phrases such as "that's it,
that's all".
</doc>
        </value-el>
      </valueset>
      <valueset name="InformationStructure-type">
          <value-el color="pink">InfoStructure
          </value-el>
      </valueset>	
      <valueset name="Semiotic-type">
	  <value-el color="light orange">IndexDeictic
<doc>
Indexical gestures express a relation of cause-effect between the sign
(the gesture) and its meaning.  In particular, Indexical Deictics
locate aspects of the discourse in the physical space (e.g. by
pointing). They can also be used to index the addressee.
</doc>
        </value-el>
	  <value-el color="light orange">IndexNon-deictic
<doc>
Indexical gestures express a relation of cause-effect between the sign
(the gesture) and its meaning.  In Indexical Non-deictic the indexical
relation is between the gesture and the effect it establishes. Batonic
or beat gestures fall into this category.
</doc>
        </value-el>
	  <value-el color="light orange">Iconic
<doc>
Iconic gestures express a semantic feature by similarity or
homomorphism.  Examples are gestures that express size (length,
height, etc.) of an object mentioned in the discourse. Included in
this category are also gestures that are sometimes called metaphoric.
</doc>
        </value-el>
	  <value-el color="light orange">Symbolic
<doc>
Symbolic gestures (emblems) are gestures in which the relation between form and 
content is based on social convention (e.g. the okay gesture). They are 
culture-specific. 
</doc>
        </value-el>
	  <value-el color="light orange">IconicandIndexNon-deictic
<doc>
Iconic and IndexNon-deictic. New type wrt. MUMIN 3.3.
</doc>
        </value-el>
	  <value-el color="light orange">SymbolicandIndexNon-deictic
<doc>
Simbolic and IndexNon-deictic. New type wrt. MUMIN 3.3.
</doc>
        </value-el>
	</valueset>
        <valueset name="Face-type">
	  <value-el>Smile
<doc>
The facial expression shows pleasure, favour, amusement, or
sometimes derision and scorn. Smile is characterized by an upturning of
the corners of the mouth and usually accompanied by a brightening of
the face and eyes.
</doc> 
	</value-el>
	  <value-el>Laughter
<doc>
The facial expression shows merriment, amusement, or derision,
or nervousness and it is accompanied by an audible vocal expulsion of
air from the lungs that can range from a loud burst of sound to a
series of chuckles.
</doc> 
	</value-el>
	  <value-el>Scowl
<doc>
An angry expression, like a frown. The term "frown" is reserved for
the attribute Eyebrows.
</doc> 
	</value-el>
	  <value-el>FaceOther
<doc>
To be used if none of the other values are appropriate. A comment
*must* be added.
</doc> 
	</value-el>
  	 </valueset>
        <valueset name="Eyebrows-type">
	  <value-el>Frown
<doc>
The eyebrows contract and move towards the nose.
</doc>
	</value-el>
	  <value-el>Raise
<doc>
The eyebrows are lifted.
</doc>
	</value-el>
	  <value-el>BrowsOther
<doc>
To be used if none of the other values are appropriate. A comment *must* be added.
</doc>
	</value-el>
	</valueset>
        <valueset name="Eyes-type">
	  <value-el>X-open
<doc>
Exaggerated Opening: the eyes are wide open as in the case of surprise.
</doc>
	</value-el>
	  <value-el>CloseBoth
<doc>
The eyes are both closed, e.g. to underline focusing, but not
	in case of a biological blinking. 
</doc>
	</value-el>
	  <value-el>CloseOne
<doc>
One eye winks, that is opens and closes quickly. 
</doc>
	</value-el>
	  <value-el>CloseRepeat
<doc>
Both eyes wink, that is open and close quickly. 
</doc>
	</value-el>
	  <value-el>EyesOther
<doc>
To be used if none of the other values are appropriate. A comment *must* be added.
</doc>
	</value-el>
	</valueset>
        <valueset name="Gaze-Direction-type">
	  <value-el>GazeForward
<doc>
The subject is looking forward wrt. own body.
</doc>
	</value-el>
	  <value-el>GazeBackward
<doc>
The subject is looking backward wrt. own body (implies turning the head and 
	naybe part of the torso).
</doc>
	</value-el>
	  <value-el>GazeUp
<doc>
The subject is looking up wrt. own body.
</doc>
	</value-el>
	  <value-el>GazeDown
<doc>
The subject is lookng down wrt. own body (the head may be bent or not).
</doc>
	</value-el>
	  <value-el>GazeSide
<doc>
The subject is looking to the side of own body.
</doc>
	</value-el>
	  <value-el>GazeDirectionOther
<doc>
To be used if none of the other values are appropriate, 
	for instance for complex movements. A comment *must* be added.
</doc>
	</value-el>
	</valueset>
        <valueset name="Gaze-Interlocutor-type">
	  <value-el>ToInterlocutor
<doc>
The subject is looking at the interlocutor.
</doc>
	</value-el>
	  <value-el>AwayFromInterlocutor
<doc>
The subject is looking at the interlocutor.
</doc>
	</value-el>
	</valueset>
        <valueset name="Mouth-Openness-type">
	  <value-el>OpenMouth
<doc>
The mouth is open or opens as in the case of surprise (that is not just to talk). 
</doc>
	</value-el>
	  <value-el>CloseMouth
<doc>
The mouth is close (relevant in combination with other values, e.g. lips retracted). 
</doc>
	</value-el>
	</valueset>
        <valueset name="Mouth-Lips-type">
        <value-el>CornersUp
<doc>
Corners up as in a smile. 
</doc>
	</value-el>
	  <value-el>CornersDown
<doc>
Corners down as in a scowl, sulk or sad expression.  
</doc>
	</value-el>
	  <value-el>Protruded
<doc>
The lips are rounded and protruded.
</doc>
	</value-el>
	  <value-el>Retracted
<doc>
The lips are sucked-in, retracted in the mouth.
</doc>
	</value-el>
	  <value-el>LipsOther
<doc>
To be used if none of the other values are appropriate. A comment *must* be added.
</doc>
	</value-el>
	</valueset>
        <valueset name="Head-Movement-type">
	  <value-el>Nod
<doc>
A head movement down-up. 
</doc>
	</value-el>
	  <value-el>Jerk
<doc>
A quick head movement backwards up. 

</doc>
	</value-el>
	  <value-el>HeadBackward
<doc>
A movement of the head backward (up), this can either be a 
	movement of the head only or can be movement of the whole trunk. 
	This movement occurs often as a turn accepting signal.
</doc>
	</value-el>
	  <value-el>HeadForward
<doc>
A movement of the head forward (down), this can either be 
	a movement of the head only or can be a movement of the whole trunk. 
	This movement occurs often as a turn elicit signal.
</doc>
	</value-el>
	  <value-el>Tilt
<doc>
A movement of the head leaning on one side.
</doc>
	</value-el>
	  <value-el>SideTurn
<doc>
A rotation of the head towards one side.
</doc>
	</value-el>
	  <value-el>Waggle
<doc>
A movement of the head back and forth, side to side, like a 
	mixture of shake and move backward or forward. Usually produced 
	to show uncertainty, doubtfulness.
</doc>
	</value-el>
	  <value-el>HeadOther
<doc>
To be used if none of the other values are appropriate. A comment *must* be added.
</doc>	
	</value-el>
	</valueset>
        <valueset name="Head-Repetition-type">
	  <value-el>Single
<doc>
The movement is not repeated.
</doc>
	</value-el>
	  <value-el>Repeated
<doc>
The movement is repeated.
</doc>
	</value-el>
	</valueset>
        <valueset name="Handedness-type">
	  <value-el>BothHands
<doc>
Both hands are involved
</doc>	</value-el>
	  <value-el>SingleHand
<doc>
Either right or left hand are involved alone
</doc>
	</value-el>
	</valueset>
        <valueset name="Palm-type">
	  <value-el>PalmOpen
<doc>
The palm is open.
</doc>
	</value-el>
	  <value-el>PalmClosed
<doc>
The palm is closed.
</doc>
	</value-el>
	  <value-el>PalmOther
<doc>
To be used if none of the other values are appropriate. A comment *must* be added.
</doc>
	</value-el>
	</valueset>
        <valueset name="Palm-pos-type">
	  <value-el>PalmUp
<doc>
The palm is facing upwards.
</doc>
	</value-el>
	  <value-el>PalmDown
<doc>
The palm is facing down.
</doc>
	</value-el>
	  <value-el>PalmSide
<doc>
The palm is facing sideways.
</doc>
	</value-el>
	  <value-el>PalmPosOther
<doc>
To be used if none of the other values are appropriate. A comment *must* be added.
</doc>
	</value-el>
	</valueset>
        <valueset name="Fingers-type">
	  <value-el>IndexExtended
<doc>
The index is extended  while the rest of the fingers are not.
</doc>
	</value-el>
	  <value-el>ThumbExtended
<doc>
The thumb is extended while the rest of the fingers are not.
</doc>
	</value-el>
	  <value-el>AllFingersExtended
<doc>
All fingers are extended.
</doc>
	</value-el>
	  <value-el>FingersOther
<doc>
To be used if none of the other values are appropriate. A comment *must* be added.
</doc>
	</value-el>
	</valueset>
        <valueset name="Amplitude-type">
	  <value-el>Centre
<doc>
The centre refers to a region roughly corresponding to the subject's
torso.  See MacNeill, D. (1992).
</doc>
	</value-el>
	  <value-el>Periphery
<doc>
The periphery refers to a region outside of the subject's torso, that
 above neck and shoulders, to the side of the torso or beneath the
 stomach. This means that the arm is somewhat extended. See MacNeill,
 D. (1992).
</doc>
	</value-el>
	  <value-el>AmplitudeOther
<doc>
AmplitudeOther: To be used if none of the other values are appropriate. A comment *must* be added.
</doc>
	</value-el>
	</valueset>
        <valueset name="Trajectory-Right-Hand-type">
	  <value-el>RightHandForward</value-el>
	  <value-el>RightHandBackward</value-el>
	  <value-el>RightHandSide</value-el>
	  <value-el>RightHandUp</value-el>
	  <value-el>RightHandDown</value-el>
	  <value-el>RightHandComplex</value-el>
	  <value-el>RightHandOther</value-el>
	</valueset>
        <valueset name="Trajectory-Left-Hand-type">
	  <value-el>LeftHandForward</value-el>
	  <value-el>LeftHandBackward</value-el>
	  <value-el>LeftHandSide</value-el>
	  <value-el>LeftHandUp</value-el>
	  <value-el>LeftHandDown</value-el>
	  <value-el>LeftHandComplex</value-el>
	  <value-el>LeftHandOther</value-el>
	</valueset>
        <valueset name="Hand-Repetition-type">
	  <value-el>Single</value-el>
	  <value-el>Repeated</value-el>
	</valueset>
        <valueset name="Body-Direction-type">
	  <value-el>BodyForward
<doc>
The subject is leaning forward.
</doc>
	</value-el>
	  <value-el>BodyBackward
<doc>
The subject is leaning backward. 
</doc>
	</value-el>
	  <value-el>BodyUp
<doc>
The subject is arching or lifting the torso up. 
</doc>
	</value-el>
	  <value-el>BodyDown
<doc>
The subject is bending the torso down.
</doc>
	</value-el>
	  <value-el>BodySide
<doc>
The subject is leaning to the side.
</doc>
	</value-el>
	  <value-el>BodyDirectionOther
<doc>
To be used if none of the other values are appropriate, 
	for instance for complex movements. A comment *must* be added.
</doc>
	</value-el>
	</valueset>

     </valuetype-def>
  </head>


<doc>
<p>
Anvil implementation of the MUMIN 4 coding scheme,
created for the CLARIN annotations, June 2008, Copenhagen
and revised in January 2009.
</p>
<p>
Authors:
Costanza Navarretta, Patrizia Paggio
</p>
<p>
Based on the MUMIN 3.3. coding scheme created by
Jens Allwood, Loredana Cerrato, Laila Dybkær, Kristiina Jokinen,
Costanza Navarretta and Patrizia Paggio.
See <a href="http://www.cst.dk/mumin/resources/MUMIN-coding-scheme-V3.3.doc">original coding scheme</a>.
</p>
<h3>GENERAL PURPOSE</h3>
<p>
The purpose of this version of the MUMIN coding scheme is to allow functional 
annotation of multimodal expressions, as well as the way in which expressions 
belonging to different modalities are combined. 
The functions defined are:
</p>
<ul>
<li>
	Communicative
		(Feedback
		 TurnManagement
		 EmotionAttitude)
</li>
<li>
	Structuring
		(Sequencing
		 InformationStructure)
</li>
</ul>
<p>
Feedback, turn management and sequencing are formalised similarly to
what done in MUMIN 3.3. However, the current feature taxonomy is not
totally equivalent. In the old scheme, understanding and acceptance
were subtypes of FeedbackGive and FeedbackElicit. Now, they are
independent features that can be combined with a basic FeedbackGive or
FeedbackElicit feature. We no longer distinguish between CPU and CP
under Basic Feedback.
</p>
<p>
In this version of the coding scheme, the modalities taken into 
consideration in addition to speech are facial displays, hand
gestures and body posture. 
</p>
<h3>TRACKS</h3> 
<p>
Tracks are specified to code speech and gestures of two dialogue
participants, here called Speaker A and Speaker B. The names can
of course be changed, and more tracks may be added.
</p>
</doc>


  <body>
   <track-spec name="wave" type="waveform"/>
  <group name="SpeakerA">
    <track-spec name="words" type="primary">
    <doc>
    Speaker A: Speech track
    </doc>
    <attribute name="token" valuetype="String"/>
    </track-spec>
    <track-spec name="FacialDisplay" type="primary" color-attr="f-give-attention">
    <doc>
    Speaker A: Face track
    </doc>
	<attribute name="Face" valuetype="Face-type" display="true" >
<doc> Face attributes refer to general face expressions. 
</doc>
      </attribute>
	<attribute name="Eyebrows" valuetype="Eyebrows-type" display="true">
<doc> Eyebrows attributes refer to eyebrows movements. 
</doc>
      </attribute>
	<attribute name="Eyes" valuetype="Eyes-type" display="true">
<doc>
Eyes refer to movements of the eyelids and not to gaze. 
</doc>
	</attribute>
	<attribute name="GazeDirection" valuetype="Gaze-Direction-type" display="true">
<doc>
Gaze direction is defined with respect to the subject's own body
axis. Gaze and head movement are related. For instance, if head is up,
gaze is also up if the subject does not move the pupils.
</doc>
	</attribute>
	<attribute name="GazeInterlocutor" valuetype="Gaze-Interlocutor-type" display="true">	
<doc>
GazeInterlocutor defines gaze direction with respect to the
interlocutor. This feature is new wrt. MUMIN 3.3.  GazeInterlocutor
and GazeDirection are of course related. Which is the default value of
GazeDirection when looking at the interlocutor depends of course on
how the dialogue participants are positioned wrt. each other. In case
of multi-party conversations, one may want to distinguish among
several interlocutors.
</doc>
	</attribute>
	<attribute name="MouthOpenness" valuetype="Mouth-Openness-type" display="true">
<doc>
Mouth openness can be combined with mouth lips values.
</doc>
	</attribute>
	<attribute name="MouthLips" valuetype="Mouth-Lips-type" display="true">
<doc>
Mouth lips can be combined with mouth openness values.
</doc>
	</attribute>
	<attribute name="HeadMovement" valuetype="Head-Movement-type" display="true">
<doc>
Head movements are defined similarly to gaze wrt. the subject's own
body. Gaze and head movement are related. For instance, if head is up,
gaze is also up if the subject does not move the pupils.  The values
are slightly different from MUMIN 3.3 in that repetition is now a
separate feature.
</doc>
	</attribute>
	<attribute name="HeadRepetition" valuetype="Head-Repetition-type" display="true">
<doc>
It indicates whether the movement is repeated or not. A repeated
gesture is a sequence of similar gestures in rapid succession. See
also HandRepetition.  New feature wrt. MUMIN 3.3.
</doc>
	</attribute>
      <attribute name="FeedbackBasic" valuetype="F-Basic-type">
<doc>
The basic feedback feature is used to distinguish between feedback
giving and eliciting.
</doc>
      </attribute>
	<attribute name="FeedbackUnderstanding" valuetype="F-Understand-type">
<doc>
Feedback understanding is used to specify whether basic feedback is
accompanied by signs of understanding or non-understanding.
</doc>
      </attribute>
	<attribute name="FeedbackAcceptance" valuetype="F-Acceptance-type">
<doc>
Basic feedback can also be accompanied by signs of agreeing or not agreeing.
</doc>
      </attribute>	
	<attribute name="Emotion/Attitude" valuetype="Emotion/Attitude-type">
<doc>
Emotions and attitudes can co-occur with any of the communicative
features. They include i.a. Ekman's six basic emotions: happiness,
surprise, anger, sadness, fear, disgust/contempt.
</doc>
      </attribute>
	<attribute name="Turn" valuetype="Turn-type">
<doc>
Turn features refer to the way in which one of the dialogue
participants gains, ends or holds the turn, and reflect whether this
is done in agreement or not. In a more coarse-grained scheme, one
could do with the three values TurnGain, TurnEnd and TurnHold (see MUMIN 3.3).
</doc>
      </attribute>
	<attribute name="Sequencing" valuetype="Sequencing-type">
<doc>
Sequencing is concerned with speech act organisation and structuring into 
sub-dialogues. It should not be confused with turn-management, that models 
turn shifts among dialogue participants.
</doc>
      </attribute>
	<attribute name="InformationStructure" valuetype="InformationStructure-type">
<doc>
The gesture has a function relating to information structure, i.e. the
organisation of the information within a sentence or utterance. It
could be underlining the topic, the focus or creating a contrast.
</doc>
	</attribute>
      <attribute name="SemioticType" valuetype="Semiotic-type">
<doc>
Based on Peirce's theory, three types are defined: indexical, iconic
and symbolic. Combinations are also allowed, which is new wrt. MUMIN 3.3.
</doc>
      </attribute>
	<attribute name="Addition" valuetype="MultiLink">
<doc>
The gesture adds information to the corresponding speech segment,
e.g. by making a concept more specific.  See Poggi and Magno
Caldognetto (1996). The feature was subsumed under Compatible in MUMIN 3.3.
</doc>
	</attribute> 	
	<attribute name="Reinforcement" valuetype="MultiLink">
<doc>
The gesture has the same meaning as the corresponding speech segment. See
Poggi and Magno Caldognetto (1996). It was subsumed under Compatible
in MUMIN 3.3.
</doc>
	</attribute>       
	<attribute name="Substitution" valuetype="MultiLink">
<doc>
The gesture occurs in absence of words. See Poggi and Magno
Caldognetto (1996). 
</doc>
	</attribute>       
      <attribute name="Contradiction" valuetype="MultiLink">
<doc>
The gesture contradicts the corresponding speech segment e.g. to
denote sarcasm or irony.  See Poggi and Magno Caldognetto (1996). It
corresponds to Incompatible in MUMIN 3.3.
</doc>
	</attribute>       
      <attribute name="RelationOther" valuetype="MultiLink">
<doc>
To be used if none of the other values are appropriate. A comment
*must* be added.
</doc>
	</attribute>       
   </track-spec>

   <track-spec name="HandGesture" type="primary" color-attr="f-give-attention">
<doc>
Speaker A: Hand gesture track
</doc>
	<attribute name="Handedness" valuetype="Handedness-type" display="true">
<doc>
It refers to whether one or two hands are involved.
</doc>
	</attribute>
	<attribute name="Palm" valuetype="Palm-type" display="true">
<doc>
It refers to whether the palm is open or closed. New wrt. MUMIN 3.3.
</doc>
	</attribute>  
	<attribute name="PalmPos" valuetype="Palm-pos-type" display="true">  
<doc>
It refers to the position of the palm in space. New wrt. MUMIN 3.3.
</doc>
	</attribute>
	<attribute name="Fingers" valuetype="Fingers-type" display="true">
<doc>
It accounts for finger extension. New wrt. MUMIN 3.3.
</doc>
	</attribute>
	<attribute name="Amplitude" valuetype="Amplitude-type" display="true">
<doc>
It accounts for how broad the gesture is. New wrt. MUMIN 3.3.
</doc>
	</attribute>
	<attribute name="TrajectoryRightHand" valuetype="Trajectory-Right-Hand-type" display="true">
<doc>
Similar values to those used for the direction of gaze, head and
body. The feature also indicates the trajectory of the fingers if
extended. The value 'complex' is a combination of several of the more
basic ones. 'Other' should be used if none of the other values can be
applied, and a comment *must* then be added. In MUMIN 3.3. there is a
general trajectory feature that does not distinguish between left and
righ hands.
</doc>
	</attribute>
	<attribute name="TrajectoryLeftHand" valuetype="Trajectory-Left-Hand-type" display="true">
<doc>
The same values as for Trajectory Right Hand. The feature also
indicates the trajectory of the fingers if extended.  The value
'complex' is a combination of several of the more basic ones. 'Other'
should be used if none of the other values can be applied, and a
comment *must* then be added.  In MUMIN 3.3. there is a general
trajectory feature that does not distinguish between left and righ
hands.
</doc>
	</attribute>
	<attribute name="HandRepetition" valuetype="Hand-Repetition-type" display="true">
<doc>
It indicates whether the movement is repeated or not. A repeated
gesture is a sequence of similar gestures in rapid succession. See
also HeadRepetition.  New feature wrt. MUMIN 3.3.
</doc>
	</attribute>
      <attribute name="FeedbackBasic" valuetype="F-Basic-type">
<doc>
The basic feedback feature is used to distinguish between feedback
giving and eliciting.
</doc>
      </attribute>
	<attribute name="FeedbackUnderstanding" valuetype="F-Understand-type">
<doc>
Feedback understanding is used to specify whether basic feedback is
accompanied by signs of understanding or non-understanding.
</doc>
      </attribute>
	<attribute name="FeedbackAcceptance" valuetype="F-Acceptance-type">
<doc>
Basic feedback can also be accompanied by signs of agreeing or not agreeing.
</doc>
      </attribute>	
	<attribute name="Emotion/Attitude" valuetype="Emotion/Attitude-type">
<doc>
Emotions and attitudes can co-occur with any of the communicative
features. They include i.a. Ekman's six basic emotions: happiness,
surprise, anger, sadness, fear, disgust/contempt.
</doc>
      </attribute>
	<attribute name="Turn" valuetype="Turn-type">
<doc>
Turn features refer to the way in which one of the dialogue
participants gains, ends or holds the turn, and reflect whether this
is done in agreement or not. In a more coarse-grained scheme, one
could do with the three values TurnGain, TurnEnd and TurnHold (see MUMIN 3.3).
</doc>
      </attribute>
	<attribute name="Sequencing" valuetype="Sequencing-type">
<doc>
Sequencing is concerned with speech act organisation and structuring into 
sub-dialogues. It should not be confused with turn-management, that models 
turn shifts among dialogue participants.
</doc>
      </attribute>
	<attribute name="InformationStructure" valuetype="InformationStructure-type">
<doc>
The gesture has a function relating to information structure, i.e. the
organisation of the information within a sentence or utterance. It
could be underlining the topic, the focus or creating a contrast.
</doc>
	</attribute>
      <attribute name="SemioticType" valuetype="Semiotic-type">
<doc>
Based on Peirce's theory, three types are defined: indexical, iconic
and symbolic. Combinations are also allowed, which is new wrt. MUMIN 3.3.
</doc>
      </attribute>
	<attribute name="Addition" valuetype="MultiLink">
<doc>
The gesture adds information to the corresponding speech segment,
e.g. by making a concept more specific.  See Poggi and Magno
Caldognetto (1996). The feature was subsumed under Compatible in MUMIN 3.3.
</doc>
	</attribute> 	
	<attribute name="Reinforcement" valuetype="MultiLink">
<doc>
The gesture has the same meaning as the corresponding speech segment. See
Poggi and Magno Caldognetto (1996). It was subsumed under Compatible
in MUMIN 3.3.
</doc>
	</attribute>       
	<attribute name="Substitution" valuetype="MultiLink">
<doc>
The gesture occurs in absence of words. See Poggi and Magno
Caldognetto (1996). 
</doc>
	</attribute>       
      <attribute name="Contradiction" valuetype="MultiLink">
<doc>
The gesture contradicts the corresponding speech segment e.g. to
denote sarcasm or irony.  See Poggi and Magno Caldognetto (1996). It
corresponds to Incompatible in MUMIN 3.3.
</doc>
	</attribute>       
      <attribute name="RelationOther" valuetype="MultiLink">
<doc>
To be used if none of the other values are appropriate. A comment
*must* be added.
</doc>
	</attribute>       

   </track-spec>

   <track-spec name="BodyPosture" type="primary" color-attr="f-give-attention">
<doc>
Speaker A: Body posture track
</doc>
	<attribute name="BodyDirection" valuetype="Body-Direction-type" display="true">
<doc>
Body Posture is defined with respect to the subject's own body axis.
</doc>
	</attribute>  
      <attribute name="FeedbackBasic" valuetype="F-Basic-type">
<doc>
The basic feedback feature is used to distinguish between feedback
giving and eliciting.
</doc>
      </attribute>
	<attribute name="FeedbackUnderstanding" valuetype="F-Understand-type">
<doc>
Feedback understanding is used to specify whether basic feedback is
accompanied by signs of understanding or non-understanding.
</doc>
      </attribute>
	<attribute name="FeedbackAcceptance" valuetype="F-Acceptance-type">
<doc>
Basic feedback can also be accompanied by signs of agreeing or not agreeing.
</doc>
      </attribute>	
	<attribute name="Emotion/Attitude" valuetype="Emotion/Attitude-type">
<doc>
Emotions and attitudes can co-occur with any of the communicative
features. They include i.a. Ekman's six basic emotions: happiness,
surprise, anger, sadness, fear, disgust/contempt.
</doc>
      </attribute>
	<attribute name="Turn" valuetype="Turn-type">
<doc>
Turn features refer to the way in which one of the dialogue
participants gains, ends or holds the turn, and reflect whether this
is done in agreement or not. In a more coarse-grained scheme, one
could do with the three values TurnGain, TurnEnd and TurnHold (see MUMIN 3.3).
</doc>
      </attribute>
	<attribute name="Sequencing" valuetype="Sequencing-type">
<doc>
Sequencing is concerned with speech act organisation and structuring into 
sub-dialogues. It should not be confused with turn-management, that models 
turn shifts among dialogue participants.
</doc>
      </attribute>
	<attribute name="InformationStructure" valuetype="InformationStructure-type">
<doc>
The gesture has a function relating to information structure, i.e. the
organisation of the information within a sentence or utterance. It
could be underlining the topic, the focus or creating a contrast.
</doc>
	</attribute>
      <attribute name="SemioticType" valuetype="Semiotic-type">
<doc>
Based on Peirce's theory, three types are defined: indexical, iconic
and symbolic. Combinations are also allowed, which is new wrt. MUMIN 3.3.
</doc>
      </attribute>
	<attribute name="Addition" valuetype="MultiLink">
<doc>
The gesture adds information to the corresponding speech segment,
e.g. by making a concept more specific.  See Poggi and Magno
Caldognetto (1996). The feature was subsumed under Compatible in MUMIN 3.3.
</doc>
	</attribute> 	
	<attribute name="Reinforcement" valuetype="MultiLink">
<doc>
The gesture has the same meaning as the corresponding speech segment. See
Poggi and Magno Caldognetto (1996). It was subsumed under Compatible
in MUMIN 3.3.
</doc>
	</attribute>       
	<attribute name="Substitution" valuetype="MultiLink">
<doc>
The gesture occurs in absence of words. See Poggi and Magno
Caldognetto (1996). 
</doc>
	</attribute>       
      <attribute name="Contradiction" valuetype="MultiLink">
<doc>
The gesture contradicts the corresponding speech segment e.g. to
denote sarcasm or irony.  See Poggi and Magno Caldognetto (1996). It
corresponds to Incompatible in MUMIN 3.3.
</doc>
	</attribute>       
      <attribute name="RelationOther" valuetype="MultiLink">
<doc>
To be used if none of the other values are appropriate. A comment
*must* be added.
</doc>
	</attribute>       

   </track-spec>
</group>

  <group name="SpeakerB">
   <track-spec name="words" type="primary">
   <doc>
   Speaker B: Speech track
   </doc>
      <attribute name="token" valuetype="String"/>
    </track-spec>
    <track-spec name="FacialDisplay" type="primary" color-attr="f-give-attention">
    <doc>
    Speaker B: Face track. All attributes are the same as for Speaker A.
    </doc>
	<attribute name="Face" valuetype="Face-type" display="true" >
<doc> Face attributes refer to general face expressions. 
</doc>
      </attribute>
	<attribute name="Eyebrows" valuetype="Eyebrows-type" display="true">
<doc> Eyebrows attributes refer to eyebrows movements. 
</doc>
      </attribute>
	<attribute name="Eyes" valuetype="Eyes-type" display="true">
<doc>
Eyes refer to movements of the eyelids and not to gaze. 
</doc>
	</attribute>
	<attribute name="GazeDirection" valuetype="Gaze-Direction-type" display="true">
<doc>
Gaze direction is defined with respect to the subject's own body
axis. Gaze and head movement are related. For instance, if head is up,
gaze is also up if the subject does not move the pupils.
</doc>
	</attribute>
	<attribute name="GazeInterlocutor" valuetype="Gaze-Interlocutor-type" display="true">	
<doc>
GazeInterlocutor defines gaze direction with respect to the
interlocutor. This feature is new wrt. MUMIN 3.3.  GazeInterlocutor
and GazeDirection are of course related. Which is the default value of
GazeDirection when looking at the interlocutor depends of course on
how the dialogue participants are positioned wrt. each other. In case
of multi-party conversations, one may want to distinguish among
several interlocutors.
</doc>
	</attribute>
	<attribute name="MouthOpenness" valuetype="Mouth-Openness-type" display="true">
<doc>
Mouth openness can be combined with mouth lips values.
</doc>
	</attribute>
	<attribute name="MouthLips" valuetype="Mouth-Lips-type" display="true">
<doc>
Mouth lips can be combined with mouth openness values.
</doc>
	</attribute>
	<attribute name="HeadMovement" valuetype="Head-Movement-type" display="true">
<doc>
Head movements are defined similarly to gaze wrt. the subject's own
body. Gaze and head movement are related. For instance, if head is up,
gaze is also up if the subject does not move the pupils.  The values
are slightly different from MUMIN 3.3 in that repetition is now a
separate feature.
</doc>
	</attribute>
	<attribute name="HeadRepetition" valuetype="Head-Repetition-type" display="true">
<doc>
It indicates whether the movement is repeated or not. A repeated
gesture is a sequence of similar gestures in rapid succession. See
also HandRepetition.  New feature wrt. MUMIN 3.3.
</doc>
	</attribute>
      <attribute name="FeedbackBasic" valuetype="F-Basic-type">
<doc>
The basic feedback feature is used to distinguish between feedback
giving and eliciting.
</doc>
      </attribute>
	<attribute name="FeedbackUnderstanding" valuetype="F-Understand-type">
<doc>
Feedback understanding is used to specify whether basic feedback is
accompanied by signs of understanding or non-understanding.
</doc>
      </attribute>
	<attribute name="FeedbackAcceptance" valuetype="F-Acceptance-type">
<doc>
Basic feedback can also be accompanied by signs of agreeing or not agreeing.
</doc>
      </attribute>	
	<attribute name="Emotion/Attitude" valuetype="Emotion/Attitude-type">
<doc>
Emotions and attitudes can co-occur with any of the communicative
features. They include i.a. Ekman's six basic emotions: happiness,
surprise, anger, sadness, fear, disgust/contempt.
</doc>
      </attribute>
	<attribute name="Turn" valuetype="Turn-type">
<doc>
Turn features refer to the way in which one of the dialogue
participants gains, ends or holds the turn, and reflect whether this
is done in agreement or not. In a more coarse-grained scheme, one
could do with the three values TurnGain, TurnEnd and TurnHold (see MUMIN 3.3).
</doc>
      </attribute>
	<attribute name="Sequencing" valuetype="Sequencing-type">
<doc>
Sequencing is concerned with speech act organisation and structuring into 
sub-dialogues. It should not be confused with turn-management, that models 
turn shifts among dialogue participants.
</doc>
      </attribute>
	<attribute name="InformationStructure" valuetype="InformationStructure-type">
<doc>
The gesture has a function relating to information structure, i.e. the
organisation of the information within a sentence or utterance. It
could be underlining the topic, the focus or creating a contrast.
</doc>
	</attribute>
      <attribute name="SemioticType" valuetype="Semiotic-type">
<doc>
Based on Peirce's theory, three types are defined: indexical, iconic
and symbolic. Combinations are also allowed, which is new wrt. MUMIN 3.3.
</doc>
      </attribute>
	<attribute name="Addition" valuetype="MultiLink">
<doc>
The gesture adds information to the corresponding speech segment,
e.g. by making a concept more specific.  See Poggi and Magno
Caldognetto (1996). The feature was subsumed under Compatible in MUMIN 3.3.
</doc>
	</attribute> 	
	<attribute name="Reinforcement" valuetype="MultiLink">
<doc>
The gesture has the same meaning as the corresponding speech segment. See
Poggi and Magno Caldognetto (1996). It was subsumed under Compatible
in MUMIN 3.3.
</doc>
	</attribute>       
	<attribute name="Substitution" valuetype="MultiLink">
<doc>
The gesture occurs in absence of words. See Poggi and Magno
Caldognetto (1996). 
</doc>
	</attribute>       
      <attribute name="Contradiction" valuetype="MultiLink">
<doc>
The gesture contradicts the corresponding speech segment e.g. to
denote sarcasm or irony.  See Poggi and Magno Caldognetto (1996). It
corresponds to Incompatible in MUMIN 3.3.
</doc>
	</attribute>       
      <attribute name="RelationOther" valuetype="MultiLink">
<doc>
To be used if none of the other values are appropriate. A comment
*must* be added.
</doc>
	</attribute>       

   </track-spec>

   <track-spec name="HandGesture" type="primary" color-attr="f-give-attention">
   <doc>
   Speaker B: Hand gesture track. All attributes are the same as for Speaker A.
   </doc>
	<attribute name="Handedness" valuetype="Handedness-type" display="true">
<doc>
It refers to whether one or two hands are involved.
</doc>
	</attribute>
	<attribute name="Palm" valuetype="Palm-type" display="true">
<doc>
It refers to whether the palm is open or closed. New wrt. MUMIN 3.3.
</doc>
	</attribute>  
	<attribute name="PalmPos" valuetype="Palm-pos-type" display="true">  
<doc>
It refers to the position of the palm in space. New wrt. MUMIN 3.3.
</doc>
	</attribute>
	<attribute name="Fingers" valuetype="Fingers-type" display="true">
<doc>
It accounts for finger extension. New wrt. MUMIN 3.3.
</doc>
	</attribute>
	<attribute name="Amplitude" valuetype="Amplitude-type" display="true">
<doc>
It accounts for how broad the gesture is. New wrt. MUMIN 3.3.
</doc>
	</attribute>
	<attribute name="TrajectoryRightHand" valuetype="Trajectory-Right-Hand-type" display="true">
<doc>
Similar values to those used for the direction of gaze, head and
body. The feature also indicates the trajectory of the fingers if
extended. The value 'complex' is a combination of several of the more
basic ones. 'Other' should be used if none of the other values can be
applied, and a comment *must* then be added. In MUMIN 3.3. there is a
general trajectory feature that does not distinguish between left and
righ hands.
</doc>
	</attribute>
	<attribute name="TrajectoryLeftHand" valuetype="Trajectory-Left-Hand-type" display="true">
<doc>
The same values as for Trajectory Right Hand. The feature also
indicates the trajectory of the fingers if extended.  The value
'complex' is a combination of several of the more basic ones. 'Other'
should be used if none of the other values can be applied, and a
comment *must* then be added.  In MUMIN 3.3. there is a general
trajectory feature that does not distinguish between left and righ
hands.
</doc>
	</attribute>
	<attribute name="HandRepetition" valuetype="Hand-Repetition-type" display="true">
<doc>
It indicates whether the movement is repeated or not. A repeated
gesture is a sequence of similar gestures in rapid succession. See
also HeadRepetition.  New feature wrt. MUMIN 3.3.
</doc>
	</attribute>
      <attribute name="FeedbackBasic" valuetype="F-Basic-type">
<doc>
The basic feedback feature is used to distinguish between feedback
giving and eliciting.
</doc>
      </attribute>
	<attribute name="FeedbackUnderstanding" valuetype="F-Understand-type">
<doc>
Feedback understanding is used to specify whether basic feedback is
accompanied by signs of understanding or non-understanding.
</doc>
      </attribute>
	<attribute name="FeedbackAcceptance" valuetype="F-Acceptance-type">
<doc>
Basic feedback can also be accompanied by signs of agreeing or not agreeing.
</doc>
      </attribute>	
	<attribute name="Emotion/Attitude" valuetype="Emotion/Attitude-type">
<doc>
Emotions and attitudes can co-occur with any of the communicative
features. They include i.a. Ekman's six basic emotions: happiness,
surprise, anger, sadness, fear, disgust/contempt.
</doc>
      </attribute>
	<attribute name="Turn" valuetype="Turn-type">
<doc>
Turn features refer to the way in which one of the dialogue
participants gains, ends or holds the turn, and reflect whether this
is done in agreement or not. In a more coarse-grained scheme, one
could do with the three values TurnGain, TurnEnd and TurnHold (see MUMIN 3.3).
</doc>
      </attribute>
	<attribute name="Sequencing" valuetype="Sequencing-type">
<doc>
Sequencing is concerned with speech act organisation and structuring into 
sub-dialogues. It should not be confused with turn-management, that models 
turn shifts among dialogue participants.
</doc>
      </attribute>
	<attribute name="InformationStructure" valuetype="InformationStructure-type">
<doc>
The gesture has a function relating to information structure, i.e. the
organisation of the information within a sentence or utterance. It
could be underlining the topic, the focus or creating a contrast.
</doc>
	</attribute>
      <attribute name="SemioticType" valuetype="Semiotic-type">
<doc>
Based on Peirce's theory, three types are defined: indexical, iconic
and symbolic. Combinations are also allowed, which is new wrt. MUMIN 3.3.
</doc>
      </attribute>
	<attribute name="Addition" valuetype="MultiLink">
<doc>
The gesture adds information to the corresponding speech segment,
e.g. by making a concept more specific.  See Poggi and Magno
Caldognetto (1996). The feature was subsumed under Compatible in MUMIN 3.3.
</doc>
	</attribute> 	
	<attribute name="Reinforcement" valuetype="MultiLink">
<doc>
The gesture has the same meaning as the corresponding speech segment. See
Poggi and Magno Caldognetto (1996). It was subsumed under Compatible
in MUMIN 3.3.
</doc>
	</attribute>       
	<attribute name="Substitution" valuetype="MultiLink">
<doc>
The gesture occurs in absence of words. See Poggi and Magno
Caldognetto (1996). 
</doc>
	</attribute>       
      <attribute name="Contradiction" valuetype="MultiLink">
<doc>
The gesture contradicts the corresponding speech segment e.g. to
denote sarcasm or irony.  See Poggi and Magno Caldognetto (1996). It
corresponds to Incompatible in MUMIN 3.3.
</doc>
	</attribute>       
      <attribute name="RelationOther" valuetype="MultiLink">
<doc>
To be used if none of the other values are appropriate. A comment
*must* be added.
</doc>
	</attribute>       

   </track-spec>

   <track-spec name="BodyPosture" type="primary" color-attr="f-give-attention">
<doc>
Speaker B: Body posture track. All attributes are the same as for Speaker A.
</doc>
	<attribute name="BodyDirection" valuetype="Body-Direction-type" display="true">
<doc>
Body Posture is defined with respect to the subject's own body axis.
</doc>
	</attribute>  
      <attribute name="FeedbackBasic" valuetype="F-Basic-type">
<doc>
The basic feedback feature is used to distinguish between feedback
giving and eliciting.
</doc>
      </attribute>
	<attribute name="FeedbackUnderstanding" valuetype="F-Understand-type">
<doc>
Feedback understanding is used to specify whether basic feedback is
accompanied by signs of understanding or non-understanding.
</doc>
      </attribute>
	<attribute name="FeedbackAcceptance" valuetype="F-Acceptance-type">
<doc>
Basic feedback can also be accompanied by signs of agreeing or not agreeing.
</doc>
      </attribute>	
	<attribute name="Emotion/Attitude" valuetype="Emotion/Attitude-type">
<doc>
Emotions and attitudes can co-occur with any of the communicative
features. They include i.a. Ekman's six basic emotions: happiness,
surprise, anger, sadness, fear, disgust/contempt.
</doc>
      </attribute>
	<attribute name="Turn" valuetype="Turn-type">
<doc>
Turn features refer to the way in which one of the dialogue
participants gains, ends or holds the turn, and reflect whether this
is done in agreement or not. In a more coarse-grained scheme, one
could do with the three values TurnGain, TurnEnd and TurnHold (see MUMIN 3.3).
</doc>
      </attribute>
	<attribute name="Sequencing" valuetype="Sequencing-type">
<doc>
Sequencing is concerned with speech act organisation and structuring into 
sub-dialogues. It should not be confused with turn-management, that models 
turn shifts among dialogue participants.
</doc>
      </attribute>
	<attribute name="InformationStructure" valuetype="InformationStructure-type">
<doc>
The gesture has a function relating to information structure, i.e. the
organisation of the information within a sentence or utterance. It
could be underlining the topic, the focus or creating a contrast.
</doc>
	</attribute>
      <attribute name="SemioticType" valuetype="Semiotic-type">
<doc>
Based on Peirce's theory, three types are defined: indexical, iconic
and symbolic. Combinations are also allowed, which is new wrt. MUMIN 3.3.
</doc>
      </attribute>
	<attribute name="Addition" valuetype="MultiLink">
<doc>
The gesture adds information to the corresponding speech segment,
e.g. by making a concept more specific.  See Poggi and Magno
Caldognetto (1996). The feature was subsumed under Compatible in MUMIN 3.3.
</doc>
	</attribute> 	
	<attribute name="Reinforcement" valuetype="MultiLink">
<doc>
The gesture has the same meaning as the corresponding speech segment. See
Poggi and Magno Caldognetto (1996). It was subsumed under Compatible
in MUMIN 3.3.
</doc>
	</attribute>       
	<attribute name="Substitution" valuetype="MultiLink">
<doc>
The gesture occurs in absence of words. See Poggi and Magno
Caldognetto (1996). 
</doc>
	</attribute>       
      <attribute name="Contradiction" valuetype="MultiLink">
<doc>
The gesture contradicts the corresponding speech segment e.g. to
denote sarcasm or irony.  See Poggi and Magno Caldognetto (1996). It
corresponds to Incompatible in MUMIN 3.3.
</doc>
	</attribute>       
      <attribute name="RelationOther" valuetype="MultiLink">
<doc>
To be used if none of the other values are appropriate. A comment
*must* be added.
</doc>
	</attribute>       

   </track-spec>

</group>

  </body>
</annotation-spec>


