Behavior Specification

AsapRealizer uses the Behavior Markup Language (BML) for the specification and synchronization of multi-modal behavior. We widened the interpretation of BML's synchronization mechanism to allow the specification of synchronization to time predictions by an 'anticipator' and add the specification of physical controllers, procedural animation, transition animations as BML behaviors. These extensions are documented in our BMLA specification.

Core BML support

Currently no BML Realizer, including AsapRealizer, fully supports the core (=minimal) BML 1.0 specification. We are working towards supporting the  bml 1.0 standard. Here we list our progress.

BML Behavior/functionalitySupportImplementation
<locomotion> Not implemented -
<posture> Not implemented -
<postureShift> Implemented physical controller, static pose, or custom pose setup
<gesture> Implemented Can make use of procedural animation or mocap.
<pointing> Implemented Custom pointing controller.
<speech> Fully supported Speech can be generated through any Microsoft Speech API compliant TTS system, through  MaryTTS or using a custom system that renders the speech as scrolling text.
<head> Implemented procedural animation or mocap
<headDirectionShift> Not implemented -
<face> Not implemented -
<faceShift> Not implemented -
<faceFacs> Implemented Converts AUs to MPEG-4.
<faceLexeme> Implemented Use the facebinding to set up the mapping from lexemes to our various face units (MPEG4, Morphs, Coordinate on Plutchiks emotion model).
<gaze> Implemented influences: WAIST, SHOULDER, NECK, EYES Biologically motivated gaze model.
<gazeShift> Not implemented -
<wait> Implemented. Wait is implemented as a simple no-op behavior.
<constraint> <synchronize> is implemented, <before> and <after> are not
<required> Not implemented -

TODO: document extensions