<-Data Types       Go to ToC

HMC-CEC Profiles are defined based on the availability of six groups of processing capabilities:

Processing Processed Data
Receive Communication Items from a Machine or Audio-Visual Scenes from a real space.
Extract Personal Status from Modalities (Text, Speech, Face, or Gesture).
Understands Personal Status using or not spatial information.
Translates Text using Meaning of Entity’s Text.
Generates Response including Text and Personal Status.
Renders Response.

Table 1 defines the Attributes and Sub-Attributes of the HMC-CEC Profiles. The Sub-Attributes are expressed with three characters where the first two represent the medium followed by O representing Object:

  1. The Audio-Visual Scene represent Text Object (TXO), Speech Object (SPO), Audio Object (AUO), Visual Object (VIO), 3D Model Object, and Portable Avatar (PAF) Sub-Attributes, respectively.
  2. The Personal Status, Understanding, Translation, and Display Response represent Text (TXO), Speech (SPO), Face (FCO), and Gesture (GSO), respectively.

The PAF 1st-levelSub-Attribute (S-Attribute) includes the following 2nd-level SS-Attributes:

  1. AVA: The Avatar.
  2. LNG: the Avatar Language Preferences.
  3. TXO: Text Object associated with the Entity.
  4. NNM: Speech Model used to synthesise Speech.
  5. SPO: Speech Object associated with the Avatar.
  6. EPS: The Personal Status of the Avatar.
  7. SPC: The Space (SPaCe) where the Avatar is embedded.

The SPC Sub-Attribute of Understanding represents Spatial Information, i.e., the capability of an HMC-CEC implementation to use Spatial Information.

The LNG Sub-Attribute represent the ISO 639 Set 3 three-letter code.

Table 1 – Attribute and Sub-Attribute Codes of HMC-CEC.

Attributes Codes S-Attribute Codes SS-Attribute Code
AV Scene AVS TXO SPO AUO VIO PAF AVA LNG TXO NNM SPO EPS SPG
Personal Status EPS TXO SPO FCO GSO
Understanding UND TXO SPO FCO GSO SPC
Translation TRN TXO SPO FCO GSO LNG
Display DIS TXO SPO FCO GSO

The JSON file provides the formal specification of MPAI-HMC Profiles.

The Regular Expression can be interpreted by factoring it into its component rules:

^(ALL|NUL)([+-](AVS|UND|TRN|EPS|DIS)|
           @AVS#(TXO|SPO|AUO|VIO|PAF(#(AVA|LNG|NNM|EPS|SPC|(TXO|SPO)#([a-z]{3})(<->|->)([a-z]{3})))?)|
           @UND#(TXO|SPO|FCO|GSO|SPC)|
           @TRN#(TXO|SPO|FCO|GSO)#([a-z]{3})(<->|->)([a-z]{3})|
           @EPS#(TXO|PSO|FCO|GSO)|
           @DIS#(TXO|PSO|FCO|GSO))+$

An additional rule not specified by the Regular Expression is that ALL be always followed by “-” and NUL be always followed by “+”.

<-Data Types       Go to ToC