Go to XRV-LTP AI Modules

Function Ref. Model I/O Data SubAIMs JSON MData Profiles Ref. Software Conformance Performance

1. Functions

The Action Generation (XRV-ACG) AIM uses Performance Status, Participant Status, and Operator Status to produce

  1. RE Action IDs and VE Action IDs to instantiate Actions from the Action Table in the RE Experience Generation and VE Experience Generation AIMs per the Script.
  2. The next Cue Point ID to inform the Performance, Participant, and Operator Status Interpretation AIMs to look for the next Cue Conditions.

A Cue is represented by a combination of VE/RE Performance, Participant, and Operator Statuses. The matching is between the Cue and the current VE/RE Performance, Participant, and Operator Statuses.
Action Generation follows the show commands that the operator gives through the RE and VE Operator Status (Go, Hold, Skip, Back): the show is not started, running, held or ended. A Cue whose Conditions are never met waits for a Go or a Skip. A Hold of the show is not a Pause of the Module, which would stop the sensing too. A show with no operator runs from the first to the last Cue.

2. Reference Model

Figure 1 depicts the Action Generation (XRV-ACG) AIM Reference Model.

 

Figure 1 – Action Generation (XRV-ACG) AIM Reference Model

3. I/O Data

Table 1 specifies the Input/Output Data of Action Generation (XRV-ACG) AIM.

Table 1 – Input/Output Data of Action Generation (XRV-ACG) AIM

Input Data Description Port Number
RE Performance Status (optional) The elements of RE Performance Status as needed to meet the current Cue Point Conditions. Optional: a Cue may have no Condition on it. 1
VE Performance Status (optional) The elements of VE Performance Status as needed to meet the current Cue Point Conditions. Optional: a Cue may have no Condition on it. 1
RE Participant Status (optional) The elements of RE Participant Status as needed to meet the current Cue Point Conditions. Optional: a Cue may have no Condition on it. 1
VE Participant Status (optional) The elements of VE Participant Status as needed to meet the current Cue Point Conditions. Optional: a Cue may have no Condition on it. 1
RE Operator Status (optional) The elements of RE Operator Status as needed to meet the current Cue Point Conditions. Optional: a Cue may have no Condition on it. 1
VE Operator Status (optional) The elements of VE Operator Status as needed to meet the current Cue Point Conditions. Optional: a Cue may have no Condition on it. 1
Participant Data (optional) Non-identifying information about each Participant loaded into the system and modified in real time. Optional: the User Agent may have no Participant Data, as for an audience with no history. 1
Script A machine-readable functional description of the entire show performance including actions to be performed in the Real and Virtual Environment based on the Performance, Operator, and Participant behaviours. 1
Action Table Commands required to achieve a desired Action in the Real and Virtual Environments per the Script. 1
Script-Venue Associations Metadata that associates measurable elements of the Script (e.g., characters, objects, participants, operator consoles) with data sources and sinks specific to the Real and Virtual Environments, as defined by the Qualifiers in the Venue Specifications. 1
Output Data Description Port Number
RE Action ID A string (Text Object) that is the ID of an Action of the Action Table to be executed in the Real Environment. 1
VE Action ID A string (Text Object) that is the ID of an Action of the Action Table to be executed in the Virtual Environment. 2
Cue Point ID A string (Text Object) that is the Cue ID of the current Cue Point, i.e., a pointer to the current (Real, Virtual, or Mixed) Cue in the Script. 3
Participant Data Non-identifying information about each Participant updated in real time as the Performance evolves. 1

4. SubAIMs

No SubAIMs.

5. JSON Metadata

https://schemas.mpai.community/XRV1/V1.0/AIMs/ActionGeneration.json

6 Profiles

No Profiles.

7. Reference Software

Under development.

8. Conformance Testing

Table 2 provides the Conformance Testing Method for the Action Generation (XRV-ACG) AIM.

If a schema contains references to other schemas, conformance of data for the primary schema implies that any data referencing a secondary schema shall also validate against the relevant schema, if present, and conform with the Qualifier, if present.

Table 2 – Conformance Testing Method for the Action Generation (XRV-ACG) AIM

Receives RE Performance Status Shall validate against RE Performance Status schema.
VE Performance Status Shall validate against VE Performance Status schema.
RE Participant Status Shall validate against RE Participant Status schema.
VE Participant Status Shall validate against VE Participant Status schema.
RE Operator Status Shall validate against RE Operator Status schema.
VE Operator Status Shall validate against VE Operator Status schema.
Participant Data Shall validate against Participant Data schema.
Script Shall validate against Script schema.
Action Table Shall validate against Action Table schema.
Script-Venue Associations Shall validate against Script-Venue Associations schema.
Produces RE Action ID Shall validate against Basic Text Object schema. The string shall identify an Action of the Action Table.
VE Action ID Shall validate against Basic Text Object schema. The string shall identify an Action of the Action Table.
Cue Point ID Shall validate against Basic Text Object schema. The string shall identify a Cue of the Script.
Participant Data Shall validate against Participant Data schema.

9. Performance Assessment

Not part of this specification.

Go to XRV-LTP AI Modules