| Function | Ref. Model | I/O Data | SubAIMs | JSON MData | Profiles | Ref. Software | Conformance | Performance |
1. Function
The Motion Object Generation (PGM‑MOG) AIM is a Sub-AIM of A‑User Formation (PGM‑AUF). It receives the Final Response, which holds all the outputs of Basic Knowledge, and divides its Process Actions.
- A Process Action that concerns the A-User as an entity, that is, whose subject is the Persona of the A-User (its position, its movement, its gestures), is split into a sequence of Motion Objects (mini-Process Actions): Face Motion Objects and Body Motion Objects.
- A Process Action whose subject is another Item or Process (for example, a door to be opened) is passed unchanged to A-User Control.
MOG also derives Motion Objects from the Action Objects of the Final Response. Face actions come mostly from the speech, so MOG produces few Face Motion Objects.
PGM‑MOG:
- Receives the AUC-AUF Request and the Final Response.
- Divides the Process Actions of the Final Response.
- Produces the Face Motion Objects and the Body Motion Objects, which go to Entity Face Description and Entity Body Description, and the Process Actions that do not concern the A-User as an entity, which A-User Formation passes to A-User Control.
- Reports its processing and how the Process Actions were divided with an AUC-AUF Response.
2. Reference Model
Figure 1 depicts the Reference Model of the Motion Object Generation (PGM‑MOG) AIM. The AUF Reference Model figure is in the A-User Formation page.
3. Input/Output Data
Table 1 specifies the Input and Output Data of the Motion Object Generation (PGM‑MOG) AIM.
Table 1 – I/O Data of the Motion Object Generation (PGM‑MOG) AIM
| Input | Description |
| AUC-AUF Request | Request from A-User Control that controls the formation and each motion. |
| Final Response | The content produced by Basic Knowledge: the text to be uttered, the Action Objects and the Process Actions. |
| Output | Description |
| Face Motion Object | A motion of the face of the Persona, sent to Entity Face Description. |
| Body Motion Object | A motion of the body of the Persona, sent to Entity Body Description. |
| Process Actions | The Process Actions, in the syntax of MMM-TEC V2.2, that do not concern the A-User as an entity, passed unchanged to A-User Control. |
| AUC-AUF Response | Report to the AUF Status Multiplexing (PGM-FSM) AIM, with the way the Process Actions were divided. |
4. Sub-AIMs
No Sub-AIMs.
5. JSON Metadata
https://schemas.mpai.community/PGM1/V1.0/AIMs/MotionObjectGeneration.json
6. Profiles
No Profiles.
7. Reference Software
Not part of this specification.
8. Conformance Testing
Table 2 provides the Conformance Testing Method for the Motion Object Generation (PGM‑MOG) 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 Motion Object Generation (PGM‑MOG) AIM
| Receives | AUC-AUF Request | Shall validate against the AUC-AUF Request schema. |
| Final Response | Shall validate against the Final Response schema. | |
| Produces | Face Motion Object | Shall validate against the Face Motion Object schema. |
| Body Motion Object | Shall validate against the Body Motion Object schema. | |
| Process Actions | Shall validate against the Process Actions schema and shall not include a Process Action from which Motion Objects were produced. | |
| AUC-AUF Response | Shall validate against the AUC-AUF Response schema. |
9. Performance Assessment
Not part of this specification.
