The 23 Attributes of Table 3 represented with 3-character codes have been found necessary to identify Attributes of AI Modules.

Table 1 – Coding of AIM Attributes

Attributes Code
Audio Object AUO
Audio-Visual Scene Geometry AVG
Avatar Model AVM
Body Object BDO
Body Descriptors BDD
Face Object FCO
Face Descriptors FCD
Input Personal Status IPS
Language Preferences LGP
Memory MEM
Speech Model SPM
Object Instance ID OII
Point of View POV
Portable Avatar PAV
Speech Descriptors SPD
Speaker ID SPI
Speech Object SPO
Text Descriptors TXD
Text Object TXO
Recognised Text TXR
Translation TRN
Visual Object VIO

A specific AIM Profile is signaled by:

  1. The three characters identifying the Technical Specification that specifies the AIM.
  2. The three characters identifying the AIM of that Technical Specification.
  3. The Version and Subversion of the Technical Specification.
  4. The Profile-specific sequence of coded Attributes drawn from Table 1.

For instance, the Profile of a Natural Language Understanding (HMC-NLU) AIM that does not handle spatial information (see Section 7.3) is labelled in two ways, allows more compact signaling matched to the number of Attributes supported by an AIM:

Removing unsupported Attributes MMC-NLU-V2.1(ALL-AVG-OII)
Adding supported Attributes MMC-NLU-V2.1(NUL+TXO+TXR)

Attributes, however, are not always sufficient to identify the capabilities of an AIM instance. For instance, an AIM instance of Personal Status Display (PAF-PSD) may support Personal Status, but only the Speech (PS-Speech) and Face (PS-Face) Personal Status Factors. This is illustrated by the following two examples:

Removing unsupported Attributes PAF-PSD-V1.1(ALL@IPS#SPE#FCE)
Adding supported Attributes PAF-PSD-V1.1(NUL+TXT+AVM@IPS#FCE#GST

Here @ prefixed to IPS signals that the AIM supports Personal Status, but only of Speech and Face and of Face and Gesture represented by PSS, PSF, and GST, the codes of the PS-Speech, PS-Face, and PS-Gesture Sub-Attributes, respectively (the full list of Personal Status Sub-Attributes is provided by Table 4). The second case may apply for a sign-language capable AIM.

Currently, MPAI-PRF supports another use of Sub-Attributes. The Test and Speech Translation AIM needs Sub-Attributes to signal which languages are supported in which direction as exemplified below:

Removing unsupported Attributes MMC-TST-V2.1(NUL@TRN#eng→ita)
Adding supported Attributes MMC-TST-V2.1(ALL-ISD@TRN#kor↔fra#ger→swa)

The first case refers to an AIM than only supports text translation from English to Italian and the second to an AIM that does not support Speech Descriptors but supports text and speech translation from both Korean to and from French, and from German to Swahili (the TRN Sub-Attributes are specified by the Stabdard).