Definition
Functional Requirements
Syntax
Semantics
Conformance Testing
Performance Assessment
Definition
CXE Directive (PGM‑CED) is a Directive issued by A‑User Control to Context Enhancement. It specifies what A‑User Control needs Context Enhancement to deliver: enhanced descriptions of the audio scene, of the visual scene, or a first‑pass User State. A‑User Control may express its need at the composite level, naming the deliverables and leaving the CXE‑AUS Interface to derive the per‑modality directives, or it may address a single modality directly by populating the corresponding per‑modality directive (Audio CXE Directive, Visual CXE Directive, or User CXE Directive). Each per‑modality directive carries, for that modality, the subjects referenced by identifier, the baseline semantic information elements requested, watch requests over referenced entities, and execution controls. A‑User Control does not specify the signal‑processing method, which is Context Enhancement’s own competence; it names what it needs, and Context Enhancement decides how. Context Enhancement performs its own interaction‑history operations as needed; A‑User Control does not instruct them.
Functional Requirements
- Session and Directive Identification: The directive shall include a SessionID, a unique CXEDirectiveID, and a CXEDirectiveTime timestamp to ensure traceability and correlation with execution status.
- Environment Identification: The directive shall include identifiers for the M‑Instance (MInstance) and U‑Environment (UEnvironment) in which the directive applies.
- Exchange Phase: The directive shall indicate whether it opens a new exchange or continues an existing one, and on a continuation shall reference the CXE Status (CXEStatusID) it follows.
- Deliverable Specification: The directive shall specify, in Deliver, the deliverable type or types required: Enhanced Audio Scene Descriptors, Enhanced Visual Scene Descriptors, or User State.
- Per‑Modality Directives: The directive may carry an Audio CXE Directive, a Visual CXE Directive, and a User CXE Directive, each detailing, for its modality, the subjects, requested semantic information elements, watch requests, and controls. These may be populated by A‑User Control to address a single modality directly, or derived by the CXE‑AUS Interface from the composite request.
- Subject Identification: Each per‑modality directive may identify the subjects of enhancement by reference, an M‑Location, Objects, or Users, each provided inline or by identifier.
- Semantic Property Requests: Each per‑modality directive may request, in Properties, baseline semantic information elements about referenced entities, drawn from a defined vocabulary.
- Watch Requests: Each per‑modality directive may install, in Watches, requests to report when a spatial‑relational predicate over referenced entities holds, each identified by a WatchID.
- Execution Control: Each per‑modality directive may include a Duration, a PriorityLevel, and a Deadline.
- Data Exchange Metadata: The directive shall include DataXMData to provide standardised metadata supporting interoperability, traceability, and data exchange control.
- Descriptive Metadata: The directive may include DescrMetadata to carry additional human‑readable context.
Syntax
https://schemas.mpai.community/PGM1/V1.0/data/CXEDirective.json
Semantics
| Label | Description |
|---|---|
| Header | CXE Directive header identifier. Value: “PGM-CED-V1.0”. |
| MInstance | Identifier of the M-Instance in which the directive applies. |
| UEnvironment | Identifier of the U-Environment associated with the directive. |
| CXEDirectiveID | Unique identifier for this CXE Directive instance. |
| CXEDirectiveTime | Timestamp indicating when the directive was produced, compliant with MPAI-OSD V1.5. |
| SessionID | Identifier of the A-User session to which the directive belongs. |
| Exchange | Container indicating the directive’s place in the interaction. |
| – Phase | Whether the directive opens a new exchange or continues one: new | continuation. |
| – CXEStatusID | Identifier of the CXE Status this directive follows, present on a continuation. |
| Deliver | The deliverable type or types required: EnhancedAudioSceneDescriptors | EnhancedVisualSceneDescriptors | UserState. |
| AudioCXEDirective | Per-modality directive for the audio modality. A Modality Directive (see below). Populated by A-User Control to address audio directly, or derived by the CXE-AUS Interface. |
| VisualCXEDirective | Per-modality directive for the visual modality. A Modality Directive (see below). |
| UserCXEDirective | Per-modality directive for the user modality. A Modality Directive (see below). |
| DataXMData | Data Exchange Metadata compliant with MPAI-PTF V1.0. |
| DescrMetadata | Optional descriptive metadata providing additional human-readable context. |
| Modality Directive (structure of each per-modality directive) | |
| Subject | Container identifying the subjects of enhancement by reference. |
| – MLocation | One or more M-Locations of interest, each an OSD Location or its identifier. |
| – Objects | One or more Objects of interest, each an Audio or Visual Object or its identifier. |
| – Users | One or more Users of interest, by identifier. |
| Properties | Requested baseline semantic information elements about referenced entities. |
| – Element | The requested element: ObjectClassification | Salience | InteractionPotential | Occlusion | Depth | ProximityClass | Correspondence | IsUser | AttentionTarget | UserAffect | UserEngagement. |
| – EntityIDs | Identifiers of the entities the element concerns. |
| Watches | Requests to report when a spatial-relational condition over referenced entities holds. |
| – WatchID | Identifier of this watch, used to correlate the reported event. |
| – Predicate | The condition watched: enters | leaves | reaches | contacts | approaches | proximity_threshold. |
| – Entities | Identifiers of the entities the predicate relates. |
| – Reference | A reference entity or region the predicate is evaluated against, an OSD Location or its identifier. |
| – Threshold | Numeric threshold for predicates that require one, such as proximity. |
| Control | Container of execution controls. |
| – Duration | Duration of the processing window in milliseconds. May be zero for a snapshot. |
| – PriorityLevel | Execution urgency: low | normal | high. |
| – Deadline | Time by which the enhancement is required, compliant with MPAI-OSD V1.5. |
Conformance Testing
Not part of this specification.
Performance Assessment
Not part of this specification.
