Go to PGM-AUA V1.0 Data Types

Definition
Functional Requirements
Syntax
Semantics
Conformance Testing
Performance Assessment

Definition

Domain Access Directive (PGM‑DAD) is a Directive issued by A‑User Control that specifies the domain context in which interpretation shall occur and defines the domain-level operations to be applied by Domain Access, including ambiguity resolution, constraint enforcement, semantic enrichment, cross-modal alignment, and context construction, along with associated metadata for identification, exchange, and description.

Functional Requirements

  1. Directive Identification and Traceability: The directive shall include a unique identifier (DACDirectiveID) and a timestamp (DACDirectiveTime) to ensure traceability and correlation with execution status.
  2. Domain Context Specification: The directive shall include a DomainContext identifying the semantic domain in which interpretation must occur.
  3. Domain Typing: The directive shall specify the DomainType (e.g., physical, intellectual, interactional) to define the category of knowledge space.
  4. Domain Instantiation: The directive shall include a DomainInstance identifying the specific domain (e.g., public square, scientific domain, training scenario).
  5. Ontology and Constraint Referencing: The directive may include references to domain ontologies (OntologyRef) and constraint sets (ConstraintSet) to guide semantic interpretation and validation.
  6. Interaction Framing: The directive may include an InteractionMode specifying the interaction context (e.g., simulation, dialogue, instruction).
  7. Domain Operation Control: The directive shall include ActionRequests specifying which domain-level operations shall be applied by Domain Access.
  8. Ambiguity Resolution Control: The directive shall enable explicit control of ambiguity resolution across modalities.
  9. Constraint Enforcement Control: The directive shall enable application of domain-specific rules and constraints to descriptors.
  10. Semantic Enrichment Control: The directive shall enable enrichment of descriptors with domain semantics and classifications.
  11. Cross-Modal Alignment Support: The directive shall support resolution of inconsistencies across audio and visual modalities.
  12. Context Construction Control: The directive shall enable construction of a domain-aligned execution context.
  13. Guide Generation Control: The directive shall enable creation of User Context Guide and Personality Context Guide.
  14. Prompt Steering: The directive shall enable generation of DA-Prompt for Basic Knowledge.
  15. Data Exchange Metadata: The directive shall include DataXMData to provide standardised metadata supporting interoperability, traceability, and data exchange control.
  16. Descriptive Metadata: The directive may include DescrMetadata to provide additional human-readable context.

Syntax

https://schemas.mpai.community/PGM1/V1.0/data/DACDirective.json

Semantics

Label Description
Header Directive header identifier matching pattern “PGM-DAD-Vx.y”.
DACDirectiveID Unique identifier for this DAC Directive instance.
DACDirectiveTime Timestamp indicating when the directive was produced.
DomainContext Container defining the domain in which semantic interpretation must occur.
– DomainType Category of domain (e.g., physical, intellectual, interactional).
– DomainInstance Specific domain instance (e.g., public square, literature domain, emergency scenario).
– OntologyRef Reference to domain ontology used for semantic interpretation.
– ConstraintSet Reference to domain-specific constraints applied during interpretation.
– InteractionMode Defines interaction context (e.g., training, conversational, simulation).
ActionRequests Set of flags defining which domain operations must be applied.
– ResolveAmbiguities Indicates whether DAC shall resolve ambiguities in descriptors.
– ApplyConstraints Indicates whether DAC shall enforce domain-specific constraints.
– SemanticEnrichment Indicates whether DAC shall enrich descriptors with domain semantics.
– CrossModalResolution Indicates whether DAC shall resolve cross-modal inconsistencies.
– ExecutionContext Indicates whether DAC shall construct a domain-aligned execution context.
– UserContextGuide Indicates whether DAC shall produce User Context Guide.
– PersonalityContextGuide Indicates whether DAC shall produce Personality Context Guide.
– DAPrompt Indicates whether DAC shall generate DA-Prompt for Basic Knowledge.
DataXMData Data Exchange Metadata compliant with MPAI-PTF V1.0, providing provenance, traceability, and interoperability information.
DescrMetadata Optional descriptive metadata providing additional human-readable context.