| 1 Function | 2 Reference Model | 3 Input/Output Data |
| 4 SubAIMs | 5 JSON Metadata | 6 Profiles |
| 7 Reference Software | 8 Conformance Texting | 9 Performance Assessment |
1 Functions
Entity Dialogue Processing (MMC-EDP):
| Receives | Text Object | Text of the entity upstream to be processed. |
| Object Instance ID | Of an object in a scene. | |
| Personal Status | of the entity upstream. | |
| Text Descriptors | Descriptors of input Text Object. | |
| AV Scene Geometry | Geometry of the AV scene containing object whose ID is provided. | |
| Speaker ID | ID of speaker uttering the speech that contains the Text Object. | |
| Face ID | ID of the face of the speaker uttering the speech that contains the Text Object. | |
| Summary | A summary of the discussions being held in the environment. | |
| Handles | One Text Object at a time | From an entity upstream. |
| Recognises | The identity | Of entity upstream using speech and/or face. |
| Takes into account | Past Text Objects | and their spatial arrangement. |
| Produces | Summary | Edited summary based on input data. |
| Text Object | of Machine. | |
| Personal Status | of Machine. |
2 Reference Model
Figure 1 depicts the Reference Model of the Entity Dialogue Processing (MMC-EDP) AIM.
Figure 1 – Entity Dialogue Processing (MMC-EDP) AIM Reference Model
3 Input/Output Data
Table 1 specifies the Input and Output Data of the Entity Dialogue Processing (MMC-EDP) AIM.
Table 1 – I/O Data of the Entity Dialogue Processing (MMC-EDP) AIM
| Input | Description |
| Summary | The summary in the current state. |
| Text Object | Text or Refined Text from the Entity the Machine is communicating with. |
| Meaning | Descriptors of Text and/or Translated Text of the Entity the Machine is communicating with. |
| Personal Status | Personal Status of the Entity the Machine is communicating with. |
| Instance ID | ID of the Audio of Visual Object the Entity refers to. |
| Audio-Visual Scene Geometry | The Geometry of the AV Scene. |
| Speaker ID | The ID of the Speaker. |
| Face ID | The ID of the Face. |
| Output | Description |
| Machine Text | Text produced by the Machine in response to input. |
| Machine Personal Status | The Personal Status the Machine intends to add to its Modalities. |
| Summary | The result of refining the input Summary taking comments into consideration. |
4 SubAIMs
No SubAIMs.
5 JSON Metadata
https://schemas.mpai.community/MMC/V2.3/AIMs/EntityDialogueProcessing.json
6 Profiles
Profiles of Entity Dialogue Processing are specified.
7 Reference Software
8 Conformance Testing
Table 2 provides the Conformance Testing Method for MMC-EDP 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 – MMC-EDP AIM Conformance Testing
| Input | Text Object | Shall validate against Text Object schema. Text Data shall conform with Text Qualifier. |
| Object Instance ID | Shall validate against Instance Identifier schema. | |
| Input Personal Status | Shall validate against Personal Status schema. | |
| Meaning | Shall validate against Text Descriptors schema. | |
| Audio-Visual Scene Geometry | Shall validate against AV Scene Geometry schema. | |
| Speaker ID | Shall validate against Instance ID schema. | |
| Face ID | Shall validate against Face ID schema. | |
| Summary | Shall validate against Summary schema. Shall validate against Text Object schema. Text Data shall conform with Text Qualifier. |
|
| Output | Edited Summary | Shall validate against Summary schema. Shall validate against Text Object schema. Text Data shall conform with Text Qualifier. |
| Machine Text Object | Shall validate against Text Object schema. Text Data shall conform with Text Qualifier. |
|
| Machine Personal Status | Shall validate against Personal Status schema. |
Table 3 provides an example of MMC-EDP AIM Conformance Testing.
Table 3 – An example of MMC-EDP AIM Conformance Testing
| Input Data | Data Type | Input Conformance Testing Data |
| Meaning | JSON | All input JSON Emotion files to be drawn from Meaning JSON Files |
| Recognised Text | Unicode | All input Text files to be drawn from Text files. |
| Input Emotion | JSON | All input JSON Emotion files to be drawn from Emotion JSON Files |
| Output Data | Data Type | Output Conformance Testing Criteria |
| Machine Text | Unicode | All Text files produced shall conform with Text. |
| Machine Emotion | JSON | Emotion JSON Files shall validate against Emotion Schema |
The two attributes emotion_Name and emotion_SetName must be present in the output JSON file of Emotion. The value of either of the two attributes may be null.
9 Performance Assessment
