Go to PGM-AUA V1.0 Data Types

Definition
Functional Requirements
Syntax
Semantics
Conformance Testing
Performance Assessment

Definition

AUF Status (PGM‑AFS) is the Status produced by A‑User Formation in response to an AUF Directive. Before rendering, it reports what A‑User Formation is about to render, the Text Object and the per‑channel Personal Status it will use, so that A‑User Control can inspect and, if it chooses, override it. After rendering, it reports the formation outcome, the per‑SubAIM outcome of each formation step with the reason for any failure, and the A‑User Storage operation outcomes. It is correlated to the directive it answers.

Functional Requirements

  1. Status Identification and Traceability: The status shall include a unique identifier (AUFStatusID) and a timestamp (AUFStatusTime) to ensure traceability.
  2. Directive Correlation: The status shall include the AUFDirectiveID of the AUF Directive to which it responds.
  3. Environment Identification: The status shall include identifiers for the M-Instance (MInstance) and U-Environment (UEnvironment) in which the status applies.
  4. Session Identification: The status shall include a SessionID identifying the A-User session to which the status belongs.
  5. Render State Reporting: The status shall report the current render state (pending, rendering, rendered, not_rendered).
  6. Pre-render Reporting: Before rendering, the status shall report what A‑User Formation is about to render: the Text Object and the per‑channel Personal Status it will use.
  7. Formation Outcome Reporting: After rendering, the status shall report the overall formation result and the state of the produced avatar.
  8. SubAIM Outcome Reporting: The status shall report, for each formation step (speech synthesis, face description, body description, avatar synthesis), the outcome and, where the step failed, the reason for the failure.
  9. A-User Storage Outcome Reporting: The status shall report the outcomes of the A-User Storage operations performed during formation.
  10. Data Exchange Metadata: The status shall include DataXMData to provide standardised metadata supporting interoperability, traceability, and data exchange control.
  11. Descriptive Metadata: The status may include DescrMetadata to provide additional human-readable context.

Syntax

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

Semantics

Label Description
Header AUF Status header identifier. Value: “PGM-AFS-V1.0”.
MInstance Identifier of the M-Instance in which the status applies.
UEnvironment Identifier of the U-Environment associated with the status.
AUFStatusID Unique identifier for this AUF Status instance.
AUFStatusTime Timestamp indicating when the status was produced.
SessionID Identifier of the A-User session to which the status belongs.
AUFDirectiveID Identifier of the AUF Directive to which this status responds.
RenderState Current render state: pending | rendering | rendered | not_rendered.
AboutToRender Container reporting, before rendering, the inputs A-User Formation will use.
– TextObjectID Identifier of the Text Object (the BKN Final Response) to be rendered.
– SpeechPS Speech Personal Status to be used, compliant with MPAI-MMC V2.5.
– FacePS Face Personal Status to be used, compliant with MPAI-MMC V2.5.
– GesturePS Gesture Personal Status to be used, compliant with MPAI-MMC V2.5.
FormationOutcome Container reporting the overall outcome of avatar formation.
– FormationResult Overall outcome of avatar formation: success | failure | partial.
– AvatarState State of the produced avatar: rendered | not_rendered.
SubAIMOutcomes Container reporting, per formation step, the outcome and the reason for any failure.
– SpeechSynthesis Text-To-Speech step: Outcome (success | failure | not_requested) and, on failure, Reason (none | model_unavailable | asset_missing | synthesis_error | unsupported_qualifier | input_invalid).
– FaceDescription Entity Face Description step: Outcome (success | failure | not_requested) and, on failure, Reason (none | model_unavailable | asset_missing | synthesis_error | unsupported_qualifier | input_invalid).
– BodyDescription Entity Body Description step: Outcome (success | failure | not_requested) and, on failure, Reason (none | model_unavailable | asset_missing | synthesis_error | unsupported_qualifier | input_invalid).
– AvatarSynthesis Speaking Avatar Synthesis step: Outcome (success | failure | not_requested) and, on failure, Reason (none | model_unavailable | asset_missing | synthesis_error | unsupported_qualifier | input_invalid).
AUSOperationOutcomes Outcomes of the A-User Storage read and write operations performed during formation.
DataXMData Data Exchange Metadata compliant with MPAI-PTF V1.0.
DescrMetadata Optional descriptive metadata providing additional human-readable context.

Conformance Testing

Not part of this specification.

Performance Assessment

Not part of this specification.

Go to PGM-AUA V1.0 Data Types