| 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
PS-Text Interpretation (MMC-PRI):
| Receives | Text Descriptors, either from Text Description or as a direct input to PS-Text Interpretation. |
| Produces | PS-Text, the Personal Status of the Text Modality. |
2 Reference Model
Figure 1 depicts the Reference Model of the PS-Text Interpretation (MMC-PRI) AIM.
Figure 1 – The PS-Text Interpretation (MMC-PRI) AIM Reference Model
3 Input/Output Data
Table 1 specifies the Input and Output Data of the PS-Text Interpretation (MMC-PRI) AIM.
Table 1 – I/O Data of the PS-Text Interpretation (MMC-PRI) AIM
| Input | Description |
| Text Descriptors | Descriptors of Text |
| Output | Description |
| Text Personal Status | Personal Status of Text |
4 SubAIMs
No SubAIMs.
5 JSON Metadata
https://schemas.mpai.community/MMC/V2.2/AIMs/PSTextInterpretation.json
6 Profiles
No Profiles
7 Reference Software
8 Conformance Testing
| Input Data | Data Type | Input Conformance Testing Data |
| Meaning | JSON | All input Meaning JSON files to be drawn from Emotion JSON Files |
| Output Data | Data Type | Output Conformance Testing Criteria |
| Emotion (Text) | JSON | All Emotion JSON File 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
