Definition
Functional Requirements
Syntax
Semantics
Conformance Testing
Performance Assessment
Definition
Functional Requirements
- Header: The Data shall have Header “PGM-STN-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 (SelectedStanceID, SelectedStanceTime).
- Label: The Data shall include the stance.
- Role: The Data may include role.
- Locale: The Data may include locale.
- ExpressiveConstraints: The Data may include expressive constraints.
- MirrorsUserState: The Data may include true if the stance mirrors the User State.
- Rationale: The Data may include rationale.
- 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/SelectedStance.json
Semantics
Table 1 – Semantics of Selected Stance
| 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) |
| SelectedStanceID | Identifier of this instance. (required) |
| SelectedStanceTime | Time at which the Data was produced. (required) |
| Label | The stance. (required) |
| Role | Role of the A-User to apply. |
| Locale | Locale to apply. |
| ExpressiveConstraints | Expressive Constraints. |
| MirrorsUserState | True if the stance mirrors the User State. |
| Rationale | Reason for the proposal. |
| 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 Selected Stance 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.