(Tentative)

Definition Functional Requirements Syntax Semantics

Definition

Audio Scene Enhancers (ASE) is a decoupled, additive data type that overlays Domain Access (DAC) annotations on top of existing Basic Audio Scene Descriptors (ASD1) without modifying (Basic Audio Scene Descriptors (OSD-BAS) semantics. ASE introduces Roles, Rights & Rules, Events, Domain Context, and Confidence to produce an enriched ASD2 view.

Functional Requirements

  • Decoupled overlay: Must reference one or more ASD1 descriptors via BaseDescriptorRef and must not change OSD-BAS content. (Data-type index and OSD data-type families illustrate separation of base descriptors from overlays.)
  • Role attribution: Must allow per-object or global roles (speakerRole, authorityLevel, affiliation) with roleConfidence.
  • Rights & Rules binding: Must attach rightRef/ruleRef URIs and capture complianceStatus and requiredDelegation.
  • Event typing: Must classify events (eventType, optional eventSubType) and discourse acts with urgency.
  • Domain context: Must carry locationSemantic, activityPhase, and optionally zoneID.
  • Provenance & versioning: Must include EnrichmentTime, MInstanceID, validityInterval, and optional supersedes.
  • Confidence & justifications: Must provide numeric Confidence and optional Justifications URIs.
  • Referential integrity: Must ensure objectRef resolves to ASD1 ObjectID within validityInterval.

Syntax

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

Semantics

Label Description
Header Audio Scene Enhanchers Header
– Standard-ASE The characters PGM-VSE-V indicating schema family and type
– Version Major version – 1 or 2 characters
– Dot-separator The character . separating version components
– Subversion Minor version – 1 or 2 characters
MInstanceID Unique identifier for the M-Instance producing the enrichment
BaseDescriptorRef References to VSD1 descriptors; includes BVSSpaceTime, BVSIDOrBVS, BVSAIMID, EnrichmentTime
VSEData Array of enrichment entries; each contains:
– Scope Overlay scope: global, object, or zone
– ObjectID ObjectID referenced in VSD1 when Scope = object
– ZoneID Zone identifier when Scope = zone
– Roles Role attribution: visualRole, authorityLevel, affiliation, roleConfidence
– RightsID Rights instance as defined by MPAI-MMM TEC V2.1. Example: urn:rights:mmm:ViewInZone
– RuleID Rule instance as defined by MPAI-MMM TEC V2.1
– ComplianceStatus Indicates compliance with referenced Rights and Rule: compliant, violating, or unknown
– RequiredDelegation Indicates whether the right referenced by RightsID must be delegated from another entity
– Events Visual/scene events: EventType, optional EventSubType, urgency, channel, intensity
–– EventType Category of the event, e.g.: gesture, display_change, object_motion, occlusion_change, lighting_change, countdown
–– EventSubType Optional refinement of the event type, e.g.: gesture_subtype = wave, lighting_change = dim
–– Urgency Priority or criticality: low, medium, or high
–– Channel Source or transmission channel of the event, e.g.: system, UI, avatar
–– Intensity Numeric measure (0..1) of visual prominence or strength
– DomainContext Semantic location and phase: locationSemantic, activityPhase, optional zoneID
– Constraints DAC-injected constraints: reachable_from, visible_from, exclude_occluded, distance_limit_m
– ResolutionHints Strategy hints: prioritise_gaze, prioritise_proximity, prefer_affordance, exclude_background
– Confidence Numeric confidence score (0..1)
– Justifications Array of URIs pointing to supporting evidence
– Trace Provenance metadata for directive
–– Origin Module or subsystem that issued the directive
–– Timestamp Time of directive creation
DescrMetadata Descriptive Metadata