Definition
Functional Requirements
Syntax
Semantics
Conformance Testing
Performance Assessment
Definition
Resolved Context (PGM-RCX): The interaction context obtained by Context Resolution (Personality Alignment) and reconciled with the User State, so that the selection of the stance is context-aware.
Functional Requirements
- Header: The Data shall have Header “PGM-RCX-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 (ResolvedContextID, ResolvedContextTime).
- InteractionContext: The Data shall include the interaction context: the setting, the participants, the topic and the formality of the exchange.
- UserState: The Data may include the User State with which the context was reconciled.
- Discrepancies: The Data may include points where the context and the User State do not agree.
- Confidence: The Data may include confidence, 0 to 1.
- Metadata: The Data shall include DataXMData and may include DescrMetadata.
Syntax
https://schemas.mpai.community/PGM1/V1.0/data/ResolvedContext.json
Semantics
Table 1 – Semantics of Resolved Context
| 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) |
| ResolvedContextID | Identifier of this instance. (required) |
| ResolvedContextTime | Time at which the Data was produced. (required) |
| InteractionContext | The interaction context: the setting, the participants, the topic and the formality of the exchange. (required) |
| – Setting | Setting. |
| – Participants | Participants. |
| – Topic | Topic. |
| – Formality | Formality. |
| UserState | The User State with which the context was reconciled. |
| Discrepancies | Points where the context and the User State do not agree. |
| Confidence | Confidence, 0 to 1. |
| 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 Resolved Context 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.
