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. It carries nothing that belongs to one application: whatever an application needs to say is given to it as text. The AIM may also receive some or all of the following inputs: the descriptors (Text Descriptors) of the input text, the Personal Status, the identifier of the user, the identifiers of Visual and Audio Objects of the scene, the Geometry of the scene, the Summary of the conversation. It may also produce the Personal Status of the machine, and the HCI Memory Data:
| Receives | Text Object | Text of the entity upstream to be processed; the Refined Text, which in the Voice Command Interface is the Response Hint of JSON Interface. |
| Text Descriptors | Descriptors of input Text Object. | |
| Personal Status | Of the entity upstream. | |
| Instance Identifiers | The user, and the Visual and Audio Objects of the scene. | |
| Scene Geometry | Visual and Audio, and the Basic Multimodal Scene Descriptors. | |
| Summary | A summary of the discussions being held in the environment. | |
| Handles | One Text Object at a time | From an entity upstream. |
| Takes into account | Past Text Objects | And their spatial arrangement. |
| Produces | Text Object | Of Machine. |
| Personal Status | Of Machine. | |
| Summary | Edited summary based on input data, and the Output Summary. | |
| Machine Avatar Model, HCI Memory Data | As in Table 1. |
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
The language model of the Entity Dialogue Processing (MMC‑EDP) AIM is data of Access. The Metadata of the AIM declares its weights, its chat template and its default parameters in AccessSources (llm-weights, llm-template, llm-parameters) by the URI they are published at and their SHA-256. The software that runs the model is part of the Implementation of the AIM: it is given the weights from Access and creates the model from them.
3 I/O Data
Table 1 specifies the Input and Output Data of the Entity Dialogue Processing (MMC‑EDP) AIM. A Port is addressed by its Data Type and its Port Number (#); where the metadata gives none, none is shown.
| Input | Description |
|---|---|
| Summary (MMC-SUM) | Summary: the summary in the current state. |
| Basic Text Object (OSD-BTO) #1 | Text Object: the text, from the entity the AIM is communicating with. |
| Text Descriptors Object (MMC-TDO) | Text Descriptors: the descriptors of the input Text Object. |
| Personal Status (MMC-EPS) #1 | Personal Status: the Personal Status of the entity the AIM is communicating with. |
| Instance Identifier (OSD-IID) #1 | User ID: the identifier of the user. |
| Instance Identifier (OSD-IID) #2 | Visual Object IDs: the identifiers of Visual Objects in the scene. |
| Instance Identifier (OSD-IID) #3 | Audio Object IDs: the identifiers of Audio Objects in the scene. |
| Basic Visual Scene Geometry (OSD-BVG) | Visual Scene Geometry: the Basic Visual Scene Geometry. |
| Basic Audio Scene Geometry (OSD-BAG) | Audio Scene Geometry: the Basic Audio Scene Geometry. |
| Basic Multimodal Scene Descriptors (OSD-BMS) | Basic Multimodal Scene Descriptors. |
| Basic Text Object (OSD-BTO) #3 | Refined Text: the text as refined upstream; in the Voice Command Interface, the Response Hint that JSON Interface gives it. |
| Output | Description |
| Basic 3D Model Object (OSD-B3O) | Machine Avatar Model. |
| Summary (MMC-SUM) #2 | Output Summary. |
| Basic Text Object (OSD-BTO) | Machine Text Object: the text produced in response to the input. |
| Personal Status (MMC-EPS) | Machine Personal Status: the Personal Status the AIM intends to add to its modalities. |
| Summary (MMC-SUM) | Edited Summary: the result of refining the input Summary. |
| HCI Memory Data (MMC-HMD) | HCI Memory Data. |
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.
| Input | Basic Text Object (OSD-BTO) #1 | Shall validate against Basic Text Object schema. Text Data shall conform with Text Qualifier. |
| Basic Text Object (OSD-BTO) #3 | Shall validate against Basic Text Object schema. Text Data shall conform with Text Qualifier. | |
| Text Descriptors Object (MMC-TDO) | Shall validate against Text Descriptors Object schema. | |
| Personal Status (MMC-EPS) #1 | Shall validate against Personal Status schema. | |
| Instance Identifier (OSD-IID) #1, Instance Identifier (OSD-IID) #2, Instance Identifier (OSD-IID) #3 | Shall validate against Instance Identifier schema. | |
| Basic Visual Scene Geometry (OSD-BVG), Basic Audio Scene Geometry (OSD-BAG), Basic Multimodal Scene Descriptors (OSD-BMS) | Shall validate against the schema of the Data Type. | |
| Summary (MMC-SUM) | Shall validate against Summary schema. | |
| Output | Basic Text Object (OSD-BTO) | Shall validate against Basic Text Object schema. Text Data shall conform with Text Qualifier. |
| Personal Status (MMC-EPS) | Shall validate against Personal Status schema. | |
| Summary (MMC-SUM), Summary (MMC-SUM) #2 | Shall validate against Summary schema. | |
| Basic 3D Model Object (OSD-B3O), HCI Memory Data (MMC-HMD) | Shall validate against the schema of the Data Type. |
9 Performance Assessment
Not part of this specification.
