1     Definition 2     Functional Requirements 3     Syntax
4     Semantics 5    Conformance Testing 6     Performance Assessment

1      Definition

A Data Type representing the information internal to an Entity that characterises their behaviour.

2. Functional Requirements

Personal Status is a Data Type composed of three Factors:

  1. Emotion (such as “angry” or “sad”).
  2. Cognitive State (such as “surprised” or “interested”).
  3. Social Attitude (such as “polite” or “arrogant”).

Factors are expressed by Modalities: Text, Speech, Face, and Gestures. (Other Modalities, such as body posture, may be handled in future MPAI Versions.)

Within a given Modality, the Factors can be analysed and interpreted via various Descriptors. For example, when expressed via Speech, the elements may be expressed through combinations of such features as prosody (pitch, rhythm, and volume variations); separable speech effects (such as degrees of voice tension, breathiness, etc.); and vocal gestures (laughs, sobs, etc.).

Each of Emotion, Cognitive State, and Social Attitude Factors is represented by a standard set of labels and associated semantics. For each of these Factors, two tables are provided:

  • A Label Set Table containing descriptive labels relevant to the Factor in a three-level format:
    • The CATEGORIES column specifies the relevant categories using nouns (e.g., “AN-GER”).
    • The GENERAL ADJECTIVAL column gives adjectival labels for general or basic la-bels within a category (e.g., “angry”).
    • The SPECIFIC ADJECTIVAL column gives more specific (sub-categorised) labels in the relevant category (e.g., “furious”).
  • A Label Semantics Table providing the semantics for each label in the GENERAL AD-JECTIVAL and SPECIFIC ADJECTIVAL columns of the Label Set Table. For example, for “angry” the semantic gloss is “emotion due to perception of physical or emotional damage or threat.”

These sets have been compiled in the interests of basic cooperation and coordination among AIM submitters and vendors complemented by a procedure whereby AIM submitters may propose extended or alternate sets for their purposes.

An Implementer wishing to extend or replace a Label Set Table for one of the three Factors is requested to do the following:

  1. Create a new Label Set Table where:
    1. Proposed additions are clearly marked (in case of extension).
    2. b. All the elements of the target Factor and levels (up to 3) are listed (in case of replacement).
  2. Create a new Label Semantics Table where the semantics of elements of the target Factor is:
    1. Added to the semantics of the existing target Factor (in case of extension).
    2. Provided (in case of replacement).
      The submitted semantics should have a level of detail comparable to the semantics given in the current Label Semantics Table.
  3. Submit both tables to the MPAI Secretariat (secretariat@mpai.community).

The appropriate MPAI Development Committee will examine the proposed extension or replac­ement. Only the adequacy of the proposed new tables in terms of clarity and completeness will be considered. In case the new tables are not clear or complete, a revision of the tables will be requested.

The accepted External Factor Set will be identified as proposed by the submitter and reviewed by the appropriate MPAI Committee and posted to the MPAI web site.

The versioning system is based on a name – MPAI for MPAI-generated versions or “organisation name” for the proposing organisation – with a suffix m.n where m indicates the version and n indicated the subversion.

3      Syntax

https://schemas.mpai.community/MMC/V2.3/data/PersonalStatus.json

4      Semantics

Label Size Description
Header N1 Bytes Personal Status Header
– Standard-PersonalStatus 9 Bytes The characters “MMC-EPS-V”
– Version N2 Bytes Major version – 1 or 2 characters
– Dot-separator 1 Byte The character “.”
– Subversion N3 Bytes Minor version – 1 or 2 characters
MInstanceID N4 Bytes Identifier of M-Instance.
PersonalStatusID N5 Bytes  Identifier of Meaning.
PersonalStatusSpaceTime N6 Bytes Space-Time info of PersonalStatus
PersonalStatus N7 Bytes Personal Status
– CognitiveState N8 Bytes Cognitive State component of Personal Status
– Emotion N9 Bytes Emotion component of Personal Status
– SocialAttitude N10 Bytes Social Attitude component of Personal Status
DescrMetadata N11 Bytes Descriptive Metadata

5     Conformance Testing

A Data instance Conforms with MPAI-MMC V2.3 Personal Status (MMC-EPS) if:

  1. The Data validates against the Personal Status’s JSON Schema.
  2. All Data in the  Personal Status’s JSON Schema
    1. Have the specified type.
    2. Validate against their JSON Schemas.
    3. Conform with their Data Qualifiers if present.

6     Performance Assessment