Go to MPAI-MMC V2.5 AI Modules
Function
Ref. Model
I/O Data
SubAIMs
JSON MData
Profiles
Ref. Software
Conformance
Performance
1 Functions
The Entity Dialogue Processing (MMC‑EDP) AIM provides a text in response to an input text. The MMC‑EDP AIM may also receive some or all of the following inputs: the descriptors (Meaning) of the input text, the ID of the speaker who produced the input text and the identifier of a face, a Personal Status, the Summary data type of the conversation being held in the scene, the Geometry of the objects of an audio‑visual scene, the Identifiers of some of the objects in the scene. MMC‑EDP may also produce the Personal Status of the 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 – The Entity Dialogue Processing (MMC‑EDP) AIM
3 I/O 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 Identifier | ID of the Audio or Visual Object the Entity refers to. |
| Audio-Visual Scene Geometry | The Geometry of the AV Scene. |
| Speaker Identifier | The ID of the Speaker. |
| Face Identifier | The ID of the Face. |
| Output | Description |
| Machine Text Object | 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.5/AIMs/EntityDialogueProcessing.json
6 Profiles
Profiles of Entity Dialogue Processing are specified.
7 Reference Software
Not part of this specification.
8 Conformance Testing
Table 2 provides the Conformance Testing Method for the 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 – Conformance Testing Method for the MMC‑EDP AIM
| 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 Instance 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 Format | Input Conformance Testing Data |
|---|---|---|
| Meaning | JSON | All input JSON Meaning files to be drawn from Meaning JSON Files. |
| Recognised Text | Unicode | All input Text files to be drawn from Text files. |
| Input Personal Status | JSON | All input JSON Personal Status files to be drawn from Personal Status JSON Files. |
| Output Data | Data Format | Output Conformance Testing Criteria |
| Machine Text | Unicode | All Text files produced shall conform with Text. |
| Machine Personal Status | JSON | Personal Status JSON files shall validate against Personal Status schema. |
The two attributes personalStatus_Name and personalStatus_SetName must be present in the output JSON file of Personal Status. The value of either of the two attributes may be null.
9 Performance Assessment
Not part of this specification.
