Definition
Functional Requirements
Syntax
Semantics
Conformance Testing
Performance Assessment
Definition
Functional Requirements
- Header: The Data shall have Header “PGM-UME-V1.0”.
- Identification: The Data shall carry the identifiers of the M‑Instance, of the U‑Environment and of the session, and a unique identifier and a time (UnmatchedEntitiesID, UnmatchedEntitiesTime).
- Entities: The Data shall include the Entities.
- Metadata: The Data shall include DataXMData and may include DescrMetadata.
Syntax
https://schemas.mpai.community/PGM1/V1.0/data/UnmatchedEntities.json
Semantics
Table 1 – Semantics of Unmatched Entities
| Label | Description |
| Header | Header of the Data Type, with the version. (required) |
| MInstance | Identifier of the M-Instance. (required) |
| UEnvironment | Identifier of the U-Environment. (required) |
| SessionID | Identifier of the A-User session. (required) |
| UnmatchedEntitiesID | Identifier of this instance. (required) |
| UnmatchedEntitiesTime | Time at which the Data was produced. (required) |
| Entities | The Entities. (required) |
| – Modality | The modality of the Entity. One of: audio, visual. (required) |
| – EntityID | Identifier of the Entity concerned. (required) |
| – Reason | The reason. One of: no_candidate, lost_competing_claim, excluded_by_directive, other. (required) |
| – Description | Description of the reason. |
| DataXMData | Data Exchange Metadata of MPAI-PTF: provenance, authorisation, security and confidence of the Data. |
| DescrMetadata | Descriptive metadata (plain text, at most 2048 characters). |
Conformance Testing
Data conforms with Unmatched Entities if it validates against the schema of Section 3. If a schema contains references to other schemas, conformance of data for the primary schema implies that any data referencing a secondary schema shall also validate against the relevant schema.
Performance Assessment
Not part of this specification.