1 Definition
An Item that a Source Process sends to a Destination Process requesting the performance of a Process Action.
2 Functional Requirements
An IPP Message may be a Process Action Request (PA Request) or Process Action Response (PA Response) composed of the following elements. Additional Details at Protocols.
IPP Message Elements | Description |
Message ID | ID of PA Request or PA Response. |
Response ID | ID of the Message to which this Message is a response. Absent when the Message is a request. |
Source Process ID | ID of Process issuing Message. |
Process Action | Combination of Action, Items/Processes and Complement (see below). |
Resolution Service ID | Resolution Service to which the Message must be sent. Absent when the two Processes are in the same M-Instance. |
Destination Process ID | ID of Process to which the Message is sent. |
Acknowledgement | Acknowledgement = Y, if successful, or Error message, if failure. |
3 Syntax
https://schemas.mpai.community/MMM4/V2.0/data/IPPMessage.json
4 Semantics
Label | Size | Description |
Header | N1 Bytes | IPP Message Header |
– Standard-IPPMessage | 9 Bytes | The characters “MMM-MSG-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 |
IPPMessageID | N4 Bytes | Identifier of Message. |
IPPMessage | N5 Bytes | Number of Bytes in Message Data |
– MessageID | N6 Bytes | As specified in Functional Requirements. |
– ResponseID | N7 Bytes | As specified in Functional Requirements. |
– SourceProcessID | N8 Byte | As specified in Functional Requirements. |
– ProcessAction | N9 Bytes | As specified in Functional Requirements. |
– ResolutionServiceID | N10 Bytes | As specified in Functional Requirements. |
– DestinationProcessID | N11 Bytes | As specified in Functional Requirements. |
– Acknowledgement | N12 Bytes | As specified in Functional Requirements. |
DescrMetadata | N13 Bytes | Descriptive Metadata. |