1 Definition
An Item containing the ID or the Item to be Interpreted.
2 Functional Requirements
Interpret should support:
- The needs of humans and Processes to communicate to a Service their needs to Interpret Processes and Items.
- Rich form of Interpret requests and responses.
- Interpret requests and responses shall use the same Qualifiers.
3 Syntax
https://schemas.mpai.community/MMM4/V1.0/data/Interpret.json
4 Semantics
Label | Size | Description |
Header | N1 Bytes | Interpret Header |
– Standard | 9 Bytes | The characters “MMM-DIS-V” |
– Version | N2 Bytes | Major version – 1 or 2 characters |
– Dot-separator | 1 Byte | The character “.” |
– Subversion | N3 Byte | Minor version – 1 or 2 characters |
M-InstanceID | N4 Bytes | Identifier of M-Instance. |
InterpretID | N5 Bytes | Identifier of Interpret Item. |
InterpretData | N6 Bytes | Set of Interpret Data |
– InterpretFormatID | N7 Bytes | ID of Interpret Format |
– InterpretDataLength | N8 Bytes | Length of Interpret Data |
– InterpretDataURI | N9 Bytes | URI of Interpret Data |
DescrMetadata | N11 Bytes | Descriptive Metadata |
5 Data Formats
MPAI assumes that different Discover Services will use different Interpret Formats.
6 To Respondents
MPAI requests:
- Comments on Functional Requirements of the Interpret Item.
- Proposals for an initial list of Interpret Formats.