<- Scope Go to ToC References ->
Table 1 defines the Terms specific to this Technical Specification and Table 2 those used across MPAI Technical Specifications. Chapters, Sections, and Annexes are Normative unless they are explicitly identified as Informative (as in this Introduction).
A dash “-” preceding a Term in Table 1 indicates the following readings according to the font:
- Normal font: the Term in the table without a dash and preceding the one with a dash should be read before that Term. For example, “Data” and “- Type” means “Avatar Model.”
- Italic font: the Term in the table without a dash and preceding the one with a dash should be read after that Term. For example, “AI Module” and “- Basic” means “Basic AI Module.”
General MPAI Terms are given by Table 2.
The definition of all MPAI Terms is available online.
Table 1 – Terms used in this Technical Specification
| Term | Definition |
| AI Module (AIM) | A data processing component performing a Function by processing AIM-specific Input Data and producing AIM-specific Output Data. |
| – Attribute | An input Data or an output Data or a functionality, such as the ability to translate. |
| – Basic | An AIM that does not aggregate other AIMs. |
| – Composite | An AIM aggregating more than one AIM. |
| – Profile | The label that uniquely identifies a set of Attributes. |
| Avatar | An Object rendered to represent a Human of a Machine in a virtual space. |
| – Model | An inanimate Avatar exposing animation interfaces. |
| – Portable | A Data Type including Avatar ID, Time, Visual Environment, Spatial Attitude, Avatar Model, Body Descriptors, Face Descriptors, Language Preference, Speech Coding, Speech Data, Text, and Personal Status. |
| Body | A digital representation of a human body. |
| – Descriptors | A Data Type representing the features of an Entity’s Body. |
| – Object | A Data Type representing the body of an Entity, head included, face excluded. |
| Context | Information surrounding an Entity and providing additional insight into the information the Entity communicates. |
| Data | Information in digital form. |
| – Format | A standard representation of Data. |
| – Type | An instance of Data with a specific Data Format |
| Entity | A human digitally represented as a Digitised Human in a Virtual Environment or a Virtual Human in a Virtual Environment. |
| Face | A digital representation of a human face. |
| – Descriptors | A Data Type representing the motion and conveying information on the Personal Status of the face of a human or an avatar. |
| – Object | A Data Type representing the face of an Entity. |
| Factor | One of Cognitive State, Emotion, and Social Attitude |
| Modality | One of Text, Speech, Face, or Gesture. |
| Object | Data that can be rendered to cause an Experience. |
| – Audio | A Data Type representing an object or a computer-generated Object that can be rendered to and perceived by a human ear. |
| – Audio-Visual | An Object composed of Audio and Visual Objects sharing the same Spatial Attitude. |
| – Instance | The instance of an Audio Object. |
| – Visual | The digital representation of an object captured by an electromagnetic or high-frequency audio signal or computer-generated that can be rendered to and perceived by a human eye. |
| Personal Status | A Data Type representing the ensemble of information internal to a person expressed by 3 Factors (Cognitive State, Emotion, Social Attitude) conveyed by one or more Modalities (Text, Speech, Face, and Gesture). |
| Point of View | The Spatial Attitude of an Entity user looking at an Environment. |
| Scene Descriptors | The digital representation of the features of a scene. |
| Audio | A Data Type representing the Audio Objects and their spatial arrangement in an Audio Scene. |
| Audio-Visual | A Data Type representing the Audio-Visual Objects and their spatial arrangement in an Audio-Visual Scene. |
| Visual | A Data Type representing the Visual Objects and their spatial arrangement in a Visual Scene. |
| Scene Descriptors | The digital representation of the arrangement of a Scene’s Objects. |
| – Audio | A Data Type representing the spatial arrangement of a Scene’s Audio Objects. |
| – Audio-Visual | A Data Type representing the spatial arrangement of a Scene’s Audio, Visual, and Audio-Visual Objects. |
| – Visual | A Data Type representing the spatial arrangement of a Scene’s Visual Objects. |
| Speech | Digital representation of analogue speech sampled at a frequency between 8 kHz and 96 kHz with a number of bits/sample of 8, 16 or 24, and non-linear and linear quantisation or compressed. Data with characteristics of Speech may be synthetically produced. |
| – Descriptors | A Data Type representing information elements incorporated in a Speech Segment, e.g., personal identity, Personal Status, additional factors such as vocal tension, creakiness, whispery quality, etc. |
| – Model | A Neural Network trained to generate utterances with specific Speech Descriptors. |
| – Object | An Object described by Speech Descriptors. |
| Text | A series of characters drawn from a finite alphabet of a Character Set. |
| – Descriptors | A Data Type including the digital representation of the features of Text. |
| – Object | A string of Text. |
| – Recognised | The Text produced by the Automatic Speech Recognition AIM. |
The capitalised Terms used in this standard that are not already included in Table 1 are defined in Table 2.
NOTE: A hyphenated entry for e.g., “- Testing” should be read as adding that word to the closest non-hyphenated entry above it – in this case, “Conformance,” giving “Conformance Testing” as the complete entry name.
Table 2 – Terms used across several MPAI Technical Specifications
| Term | Definition |
| Access | Static or slowly changing data that are required by an application such as domain knowledge data, data models, etc. |
| AI Framework (AIF) | The environment where AIWs are executed. |
| AI Model (AIM) | A data processing element receiving AIM-specific Inputs and producing AIM-specific Outputs according to according to its Function. An AIM may be an aggregation of AIMs. |
| AI Workflow (AIW) | A structured aggregation of AIMs implementing a Use Case receiving AIW-specific inputs and producing AIW-specific outputs according to the AIW Function. |
| Application Standard | An MPAI Standard designed to enable a particular application domain. |
| Assessment Laboratory | A laboratory accredited to Assess the Grade of Performance of Implementations. |
| Channel | A connection between an output port of an AIM and an input port of an AIM. The term “connection” is also used as synonymous. |
| Communication | The infrastructure that implements message passing between AIMs. |
| Component | One of the 7 AIF elements: Access, Communication, Controller, Internal Storage, Global Storage, Store, and User Agent |
| Composite AIM | An AIM aggregating more than one AIM. |
| Component | One of the 7 AIF elements: Access, Communication, Controller, Internal Storage, Global Storage, Store, and User Agent |
| Conformance | The attribute of an Implementation of being a correct technical Implementation of a Technical Specification. |
| – Testing | The normative document specifying the Means to Test the Conformance of an Implementation. |
| – Testing Dataset | A dataset used to Test the Conformance of an implementation to a Technical Specification. |
| – Testing Means | Procedures, tools, data sets and/or data set characteristics to Test the Conformance of an Implementation. |
| – Testing Procedure | The sequence of steps to be performed to Test the Conformance of an implementation. |
| – Testing Tools | Devices and/or software used to Test the Conformance of an implementation. |
| Connection | A channel connecting an output port of an AIM and an input port of an AIM. |
| Controller | A Component that manages and controls the AIMs in the AIF, so that they execute in the correct order and at the time when they are needed |
| Data | Information in digital form. |
| – Format | The standard digital representation of Data. |
| – Type | An instance of Data with a specific Data Format. |
| – Semantics | The meaning of Data. |
| Descriptor | Coded representation of a text, audio, speech, or visual feature. |
| Digital Representation | Data corresponding to and representing a physical entity. |
| Ecosystem | The ensemble of actors making it possible for a User to execute an application composed of an AIF, one or more AIWs, each with one or more AIMs potentially sourced from independent implementers. |
| Explainability | The ability to trace the output of an Implementation back to the inputs that have produced it. |
| Fairness | The attribute of an Implementation whose extent of applicability can be assessed by making the training set and/or network open to testing for bias and unanticipated results. |
| Function | The operations effected by an AIW or an AIM on input data. |
| Global Storage | A Component to store data shared by AIMs. |
| AIM/AIW Storage | A Component to store data of the individual AIMs. |
| Identifier | A name that uniquely identifies an Implementation. |
| Implementation | 1. An embodiment of the MPAI-AIF Technical Specification, or
2. An AIW or AIM of a particular Level (1-2-3) conforming with a Use Case of an MPAI Application Standard. |
| Implementer | A legal entity implementing MPAI Technical Specifications. |
| ImplementerID (IID) | A unique name assigned by the ImplementerID Registration Authority to an Implementer. |
| ImplementerID Registration Authority (IIDRA) | The entity appointed by MPAI to assign ImplementerID’s to Implementers. |
| Instance ID | Instance of a class of Objects and the Group of Objects the Instance belongs to. |
| Interoperability | The ability to functionally replace an AIM with another AIW having the same Interoperability Level |
| – Level | The attribute of an AIW and its AIMs to be executable in an AIF Implementation and to:
1. Be proprietary (Level 1) 2. Pass the Conformance Testing (Level 2) of an Application Standard 3. Pass the Performance Testing (Level 3) of an Application Standard. |
| Knowledge Base | Structured and/or unstructured information made accessible to AIMs via MPAI-specified interfaces |
| Message | A sequence of Records transported by Communication through Channels. |
| Normativity | The set of attributes of a technology or a set of technologies specified by the applicable parts of an MPAI standard. |
| Performance | The attribute of an Implementation of being Reliable, Robust, Fair and Replicable. |
| – Assessment | The normative document specifying the Means to Assess the Grade of Performance of an Implementation. |
| – Assessment Means | Procedures, tools, data sets and/or data set characteristics to Assess the Performance of an Implementation. |
| – Assessor | An entity Assessing the Performance of an Implementation. |
| Profile | A particular subset of the technologies used in MPAI-AIF or an AIW of an Application Standard and, where applicable, the classes, other subsets, options and parameters relevant to that subset. |
| Record | A data structure with a specified structure |
| Reference Model | The AIMs and theirs Connections in an AIW. |
| Reference Software | A technically correct software implementation of a Technical Specification containing source code, or source and compiled code. |
| Reliability | The attribute of an Implementation that performs as specified by the Application Standard, profile, and version the Implementation refers to, e.g., within the application scope, stated limitations, and for the period of time specified by the Implementer. |
| Replicability | The attribute of an Implementation whose Performance, as Assessed by a Performance Assessor, can be replicated, within an agreed level, by another Performance Assessor. |
| Robustness | The attribute of an Implementation that copes with data outside of the stated application scope with an estimated degree of confidence. |
| Scope | The domain of applicability of an MPAI Application Standard |
| Service Provider | An entrepreneur who offers an Implementation as a service (e.g., a recommendation service) to Users. |
| Standard | A set of Technical Specification, Reference Software, Conformance Testing, Performance Assessment, and Technical Report of an MPAI application Standard. |
| Technical Specification | (Framework) the normative specification of the AIF.
(Application) the normative specification of the set of AIWs belonging to an application domain along with the AIMs required to Implement the AIWs that includes: 1. The formats of the Input/Output data of the AIWs implementing the AIWs. 2. The Connections of the AIMs of the AIW. 3. The formats of the Input/Output data of the AIMs belonging to the AIW. |
| Time Base | The protocol specifying how Components can access timing information |
| Topology | The set of AIM Connections of an AIW. |
| Use Case | A particular instance of the Application domain target of an Application Standard. |
| User | A user of an Implementation. |
| User Agent | The Component interfacing the user with an AIF through the Controller |
| Version | A revision or extension of a Standard or of one of its elements. |
| Zero Trust | A cybersecurity model primarily focused on data and service protection that assumes no implicit trust. |
<- Scope Go to ToC References ->
