Go to PGM-AUA V1.0 Data Types

Definition
Functional Requirements
Syntax
Semantics
Conformance Testing
Performance Assessment

Definition

Domain (PGM‑DOM) is the data type exchanged between Context Enhancement and Domain Access for domain reasoning. It carries one of three named domain exchanges, Audio Domain, Visual Domain, or User Domain, each of which is a request or a response correlated by a shared QueryID. A request supplies the relevant evidence and the candidate interpretations to be checked, together with the operations Domain Access is asked to perform; a response returns the outcome, the validated interpretations with updated confidences, and an explanation. The audio, visual, and user exchanges have distinct structures reflecting the different evidence each domain reasons over.

Functional Requirements

  1. Identification and Correlation: The data type shall include a unique QueryID linking a request to its response, and identifiers for the M‑Instance (MInstance) and U‑Environment (UEnvironment).
  2. Domain Selection: The data type shall carry one or more of the named domain exchanges: Audio Domain, Visual Domain, or User Domain.
  3. Request or Response: Each domain exchange shall be either a request or a response, never both, distinguished by the presence of the Request or the Response member.
  4. Audio Domain Evidence: An Audio Domain request may carry Audio Scene Descriptors and a temporal scope; a User Domain request may carry the User State; a Visual Domain request may carry Visual Scene Descriptors, a region of interest, and a viewpoint.
  5. Candidate Interpretations: A request may carry CandidateClasses, each a class reference with an optional confidence, and shall specify the RequestedOperations to be performed.
  6. Reasoning Outcome: A response shall carry a ResponseStatus and may carry validated classes, updated confidences, resolved targets, and an explanation.
  7. Data Exchange Metadata: The data type shall include DataXMData to provide standardised metadata supporting interoperability, traceability, and data exchange control.
  8. Descriptive Metadata: The data type may include DescrMetadata to carry additional human‑readable context.

Syntax

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

Semantics

Label Description
Header Domain header identifier. Value: “PGM-DOM-V1.0”.
MInstance Identifier of the M-Instance in which the exchange applies.
UEnvironment Identifier of the U-Environment associated with the exchange.
QueryID Identifier linking a request to its corresponding response.
AudioDomain The audio domain exchange, either a Request or a Response (see below).
VisualDomain The visual domain exchange, either a Request or a Response (see below).
UserDomain The user domain exchange, either a Request or a Response (see below).
DataXMData Data Exchange Metadata compliant with MPAI-PTF V1.0.
DescrMetadata Optional descriptive metadata providing additional human-readable context.
Audio Domain (Request or Response)
Request An audio domain request.
– DomainID Identifier of the domain the request concerns.
– Targets Identifiers of the entities the request concerns.
– AudioSceneDescriptors Audio Scene Descriptors supplied as evidence, compliant with MPAI-OSD V1.5.
– CandidateClasses Candidate interpretations, each a Class (URI) with an optional Confidence (0 to 1).
– RequestedOperations Operations requested: ResolveAmbiguities, ApplyConstraints, SemanticEnrichment, CrossModalResolution (booleans).
– TemporalScope StartTime and EndTime bounding the audio considered, compliant with MPAI-OSD V1.5.
Response An audio domain response.
– ResponseStatus Outcome: Affirmed | Rejected | Conditional | Inconclusive.
– ValidatedClasses Class references (URIs) confirmed by Domain Access.
– UpdatedConfidences Revised confidences, each a Class (URI) with a Confidence (0 to 1).
– ResolvedTargets Identifiers of the entities resolved.
– Explanation Human-readable explanation of the outcome.
Visual Domain (Request or Response)
Request A visual domain request.
– DomainID Identifier of the domain the request concerns.
– Targets Identifiers of the entities the request concerns.
– VisualSceneDescriptors Visual Scene Descriptors supplied as evidence, compliant with MPAI-OSD V1.5.
– CandidateClasses Candidate interpretations, each a Class (URI) with an optional Confidence (0 to 1).
– RequestedOperations Operations requested: ResolveAmbiguities, ApplyConstraints, SemanticEnrichment, CrossModalResolution (booleans).
– RegionOfInterest The region the request concerns, an OSD Location.
– Viewpoint The viewpoint for the request, an OSD Spatial Attitude.
Response A visual domain response.
– ResponseStatus Outcome: Affirmed | Rejected | Conditional | Inconclusive.
– ValidatedClasses Class references (URIs) confirmed by Domain Access.
– UpdatedConfidences Revised confidences, each a Class (URI) with a Confidence (0 to 1).
– ResolvedTargets Identifiers of the entities resolved.
– Explanation Human-readable explanation of the outcome.
User Domain (Request or Response)
Request A user domain request.
– DomainID Identifier of the domain the request concerns.
– Targets Identifiers of the entities (Users) the request concerns.
– UserState The User’s state supplied as evidence, an Entity State compliant with MPAI-MMC V2.5.
– CandidateClasses Candidate interpretations, each a Class (URI) with an optional Confidence (0 to 1).
– RequestedOperations Operations requested: ResolveAmbiguities, ApplyConstraints, SemanticEnrichment, CrossModalResolution (booleans).
Response A user domain response.
– ResponseStatus Outcome: Affirmed | Rejected | Conditional | Inconclusive.
– ValidatedClasses Class references (URIs) confirmed by Domain Access.
– UpdatedConfidences Revised confidences, each a Class (URI) with a Confidence (0 to 1).
– ResolvedTargets Identifiers of the entities resolved.
– Explanation Human-readable explanation of the outcome.

Conformance Testing

Not part of this specification.

Performance Assessment

Not part of this specification.

Go to PGM-AUA V1.0 Data Types