<-Scope Go to ToC References->
The terms whose first letter is a capital letter defined by this document are defined by Table 1. Other Terms of general use across MPAI Standards are accessible online.
Table 1 –Terms used in this document
| Term | Definition |
| Accessory Technical Specification | A Technical Specification specifying how to assess the impact of functionalities additional to those specified in a Technical Specification. |
| Application-oriented Technical Specification | An MPAI Technical Specification designed to enable domain-specific applications. |
| Conformance | The attribute of an Implementation of being a technically correct reification of a Technical Specification. |
| Conformance Tester | An entity authorised by MPAI to Test the Conformance of an Implementation. |
| Conformance Testing Means | Procedures, tools, data sets and/or data set characteristics to Test the Conformance of an Implementation. |
| Conformance Testing Specification | The Normative document specifying the Means to Test the Conformance of an Implementation. |
| Data Format | The standard digital representation of Data and their semantics. |
| Data Semantics | The meaning of Data. |
| Ecosystem | The ensemble of MPAI, MPAI Store, Implementers, Performance Assessors, and Users of Implementations enabling User to ripe the benefits of Interoperable Implementation. |
| Explainability | The ability to trace the output of an Implementation back to the inputs that have produced it. |
| Fairness | The attribute of an Implementation describing to which extent the Implementation does not produce biased or unanticipated results. |
| Function | The operation of an AIW or an AIM on Input Data as specified by an Application-oriented Specification to produce Output Data. |
| Grade | The Performance of an Implementation measured against a scale specified in the relevant Performance Assessment Specification. |
| Implementation | 1. An embodiment of the MPAI-AIF Technical Specification. 2. An embodiment of an AIW or AIM of a particular Interoperability Level. |
| 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 authorised by MPAI to assign ImplementerID’s to Implementers. |
| Interoperability | The ability to functionally replace an AIM or an AIW with another AIM having the same Interoperability Level. |
| Interoperability Level | The attribute of an AIW and its AIMs to be executable in an AIF Implementation and to: 1. Pass the AIF Conformance Testing (Level 1). 2. Pass the Conformance Testing (Level 2) of an Application Standard. 3. Pass the Performance Assessment (Level 3) of an Application Standard. |
| Means | The procedures, tools, data sets and/or the definition of suitable data sets used to Test the Conformance or Assess the Performance of an implementation. |
| Performance | The attribute of an Implementation to have Replicability, Robustness, Replicability, and Fairness. |
| Performance Assessment Specification | The MPAI-produced document that: 1. Specifies the Means to Validate the Replicability of an Implementation. 2. Provides guidelines on how to assess Robustness, Replicability and Fairness of an Implementation. |
| Performance Assessment Means | Procedures, tools, data sets and/or data set characteristics to Assess the Performance of an Implementation. |
| Performance Assessor | An entity appointed by MPAI to assess that the Replicability of an Implementation is above Performance of an Implementation is above a Grade specified by a Performance Assessment Specification. |
| Profile | A particular subset of the technologies that are used in AIF, AIW or AIM and, where applicable, the classes, other subsets, options, and parameters relevant to that subset. |
| Reference Model | The AIMs and their Connections in an AIW. |
| Reference Software Specification | The Normative document specifying the characteristics of the associated Reference Software Implementation. |
| Reference Software Implementation | 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 describing to which extent its operation can be replicated, within an agreed level, by another user. |
| Reputation | The collection of reviews of an Implementation made by Users. |
| Robustness | The attribute of an Implementation describing to which confidence degree it can cope with data outside of its stated application scope. |
| Security Validation | The result of the application of the procedure specified in the MPAI-AIF Conformance Testing on an implementation. |
| Service Provider | An entrepreneur who offers an Implementation as a service (e.g., a recommendation service) to Users. |
| Standard | The ensemble of Technical Specification, Reference Software, Conformance Testing and Performance Assessment of an MPAI 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. |
| Use Case | A particular instance of the Application domain targeted by an Application Standard. |
| User | A user of an Implementation. |
| Version | A revision or extension of a Standard or of one of its elements. |
