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 JSON Interface (MMC‑JSI) AIM stands between what a person says, as text, and an application that is driven by commands (User Commands). It is the JSON Interface of the Voice Command Interface, a Composite AIM that enables a person to issue vocal commands to an application. It is the same for every application: the application is known to it by its Application Context, the standing description of the application, which is data of its Access: the schema of the commands, the schema of the responses and the rest of what the two schemas do not say. The AIM does not decide what is said to the person: the Response Hint goes to the dialogue AIM.
| Receives | Basic Text Object (OSD-BTO) | The request of the person, as text. |
| User Command RS (CAE-UCM) #1 | The response of the application, which names the command it answers. | |
| Application Context (MMC-APC) | The Application Context, when the application supplies it. | |
| Produces | User Command RQ (CAE-UCM) #1 | The command for the application, which conforms to the schema of the commands of the application. |
| Basic Text Object (OSD-BTO) | The Response Hint, a text. |
The AIM works in two directions:
- Request to command – a request in words, with what the AIM remembers of the state of the application and of the commands it sent, becomes a command that conforms to the schema of the commands, checked against it before it leaves. A request that is not for the application, or that does not become a valid command, gives no command. A command carries every amount as a number; a request that lacks a number the schema requires does not become a command, and the Response Hint says what is missing, so that the person can be asked.
- Response to Response Hint – a response of the application, which conforms to the schema of the responses and names the command it answers, becomes, from the descriptions in the schema, the Response Hint: a text that tells what the application did and with which values, or what it did not do and why, or why no command was formed. A Response Hint is given for every request.
2 Reference Model
Figure 1 depicts the Reference Model of the JSON Interface (MMC‑JSI) AIM.
Figure 1 – The JSON Interface (MMC‑JSI) AIM
The Application Context (MMC-APC) is received on the Application Context Port; when the application supplies none, it is data of Access. The Metadata of the AIM declares in AccessSources, each by the URI it is published at and its SHA-256: the schema of the commands of the application (CommandSchema), the schema of the responses of the application (ResponseSchema), and the rest of the Application Context (ApplicationContext, whose structure is specified by https://schemas.mpai.community/MMC/V2.5/data/ApplicationContext.json). The descriptions in the two schemas tell the AIM what each field means; that rest says what the two schemas do not say about the application, as data: the conventions the commands rely on (units, axes, orientations, which field a verb is for, how a change by an amount is made, other words for an object), the paths of the command schema that a request may fill, the names the application has, and examples of requests with the commands they come to. The AIM knows no application: these entries are the application. The weights, the chat template and the default parameters of the language model that understands the request are optional entries too (llm-weights, llm-template, llm-parameters).
3 I/O Data
Table 1 specifies the Input and Output Data of the JSON Interface (MMC‑JSI) AIM. A Port is addressed by its Data Type and its Port Number (#); where the metadata gives none, none is shown.
| Input | Description |
|---|---|
| Basic Text Object (OSD-BTO) | The request of the person, as text. |
| User Command RS (CAE-UCM) #1 | The response of the application: a User Command response, which conforms to the schema of the responses of the application and carries the UserCommandID of the command it answers. |
| Application Context (MMC-APC) | The Application Context: the standing description of the application, when the application supplies it. Optional. |
| Output | Description |
| User Command RQ (CAE-UCM) #1 | The command for the application: a User Command request that conforms to the schema of the commands of the application. |
| Basic Text Object (OSD-BTO) | The Response Hint: a text that tells what the application did and with which values, or what it did not do and why, or why no command was formed. |
4 SubAIMs
No SubAIMs.
5 JSON Metadata
https://schemas.mpai.community/MMC/V2.5/AIMs/JSONInterface.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 MMC‑JSI 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.
| Receives | Basic Text Object (OSD-BTO) | Shall validate against Basic Text Object schema. Text Data shall conform with Text Qualifier. |
| User Command RS (CAE-UCM) #1 | Shall validate against the User Command schema and contain a UserCommandRS that conforms to the schema of the responses of the application and whose UserCommandID is that of the command answered. | |
| Application Context (MMC-APC) | Shall validate against the Application Context schema. | |
| Produces | User Command RQ (CAE-UCM) #1 | Shall validate against the User Command schema, contain a UserCommandRQ, and conform to the schema of the commands of the application. |
| Basic Text Object (OSD-BTO) | Shall validate against Basic Text Object schema. Text Data shall conform with Text Qualifier. |
9 Performance Assessment
Not part of this specification.
