1 Definition
An Item containing executable code, e.g., application program.
2 Functional Requirements
- The Data of a Program shall have a format enabling it to be executed in the target M-Instance.
- A Program may be subject to certification before it can be imported into an M-Instance.
- Certification may be carried out by or on behalf of the M-Instance Manager.
3 Syntax
https://schemas.mpai.community/MMM4/V1.0/data/Program.json
4 Semantics
Label | Size | Description |
Header | N1 Bytes | Program Header |
– Standard | 9 Bytes | The characters “MMM-PRG-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 |
MInstanceID | N4 Bytes | Identifier of M-Instance. |
ProgramID | N5 Bytes | Identifier of Program. |
ProgramData | N6 Bytes | Number of Bytes composing the Program. |
– ProgramFormatID | N7 Bytes | The Identifier of the Program Format. |
– ProgramLength | N8 Bytes | N is the number of Bytes composing the Program. |
– ProgramDataURI | N9 Bytes | Where Program Data is found. |
DescrMetadata | N10 Bytes | Descriptive Metadata |
DescrMetadata | N11 Bytes | Descriptive Metadata |
5 Data Formats
MPAI expects that different entities may develop and wish to import different Programs into an M-Instance. An M-Instance may require that a Program be certified before being imported.
6 To Respondents
MPAI requests:
- Comments on
- Functional Requirements.
- JSON Syntax and Semantics of Program.
- Program certification.
- Proposals for an initial list of Program Formats.