<- Scope Go to ToC References ->
Capitalised Terms have the meaning defined in Table 1. Lowercase Terms have the meaning commonly defined for the context in which they are used. For instance, Table 1 defines Object and Scene but does not define object and scene.
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, “Avatar” and “- Model” will yield “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, “Avatar” and “- Portable” will yield “Portable Avatar.”
All MPAI-defined Terms are accessible online.
Table 1 – General MPAI-AIF terms
| 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 Module (AIM) | A 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. AIMs operate in the Trusted Zone. |
| AI Workflow (AIW) | A structured aggregation of AIMs implementing a Use Case receiving AIM-specific inputs and producing AIM-specific outputs according to its Function. AIWs operate in the Trusted Zone. |
| Attestation | Confirmation that an AIF Implementation has cybersecurity posture |
| Authentication | The process of verifying the identity of a user, device, or application. |
| Metadata | Data associated to Data. |
| – AIF | The data set describing the capabilities of an AIF as set by the AIF Implementer. |
| – AIM | The data set describing the capabilities of an AIM as set by the AIM Implementer. |
| – AIW | The data set describing the capabilities of an AIW as set by the AIW Implementer. |
| Channel | A physical or logical connection between an output Port of an AIM and an input Port of an AIM. The term “connection” is also used as synonymous. Channels are part of the Trusted Zone. |
| Communication | The infrastructure that implements message passing between AIMs. Communication operates in the Trusted Zone. |
| Component | One of the 9 elements of the AIF Reference Model: Access, AI Module, AI Workflow, Communication, Controller, AIM Storage, Shared Storage, Store, and User Agent. |
| Composite AIM | An AIM aggregating more than one AIM. |
| Controller | A Component that manages and controls the AIMs belonging to the AIW(s) being run by the Controller, so that they execute in the correct order and at the time when they are needed. The Controller operates in the Trusted Zone. |
| Cypher |
A system for encrypting and decrypting data.
|
| Data Type | An instance of the Data Types defined by 6.1.1. |
| Device | A hardware and/or software entity running at least one instance of an AIF. |
| Encryption | The conversion of data to unrecognisable data |
| – Asymmetric | An encryption method that uses a pair of keys – public key and private key – for data encryption and decryption. |
| – Symmetric | An encryption method of where data encryption and decryption uses the same key. |
| Event | An occurrence acted on by an Implementation. |
| Group Element | An AIF in a proximity-based scenario. |
| Hashing | The conversion of data of any size into a fixed-length string of characters for data authentication, security, etc. |
| Key management | The operation on cryptographic keys such as generation, exchange, and storage to ensure the security of encrypted data. |
| Knowledge Base | Structured and/or unstructured information made accessible to AIMs via MPAI-specified interfaces. |
| Message | A sequence of Records. |
| MPAI Ontology | An MPAI-managed dynamic collection of terms with a defined semantics. |
| MPAI Server | A remote machine executing one or more AIMs. |
| MPAI Store | The repository of Implementations. |
| Port | A physical or logical communication interface of an AIM. |
| – External | An input or output Port of an AIM providing communication with an external Controller. |
| – Remote | A Port associated with a specific remote AIM. |
| Record | Data with a specified Format. |
| Resource policy | The set of conditions under which specific actions may be applied. |
| Security Abstraction Layer | (SAL) The set of Trusted Services that provide security functionalities to AIF. |
| Shared Storage | A Component to store data shared among AIMs. The Shared Storage is part of the Trusted Zone. |
| Signature | A specific pattern added to data enabling cybersecurity technologies to recognise threats. |
| Status | The set of parameters characterising a Component. |
| Storage | |
| – AIM | A Component to store data of individual AIMs. An AIM may only access its own data. The AIM Storage is part of the Trusted Zone. |
| – Secure | |
| Structure | A composition of Records. |
| Time Base | The protocol specifying how Components can access timing information. The Time Base is part of the Trusted Zone. |
| Topology | The set of Channels connecting AIMs in an AIW. |
| Trusted Zone | An environment that contains only trusted objects, i.e., object that do not require further authentication. |
| User Agent | The Component interfacing the user with an AIF through the Controller. |
| Zero Trust | A cybersecurity model primarily focused on data and service protection that assumes no implicit trust [28]. |
