2.2.2 SRMP Message Structure

  • Article

All SRMP messages MUST conform to the basic structure of a SOAP 1.1 message, as specified in [SOAP1.1] section 4, as follows:

  • The SOAP Envelope element <se:Envelope>, as defined in namespace http://schemas.xmlsoap.org/soap/envelope, MUST be present as the top-level element of the SRMP message.

  • The SOAP Header element <se:Header>, as defined in namespace http://schemas.xmlsoap.org/soap/envelope, MUST be present as the first immediate child element of the SOAP Envelope element.

  • The SOAP Body element <se:Body>, as defined in http://schemas.xmlsoap.org/soap/envelope, MUST be present and MUST be an immediate child element of a SOAP Envelope element. It MUST directly follow the SOAP Header element. The <se:Body> element MUST be empty and MUST be ignored.

The application message payload that the QM on the receiving computer delivers to the receiving application MUST be encoded as a multipart MIME attachment (see [RFC2387]) by the sending QM.

Internal receipt messages (delivery, commitment, and stream receipts) MUST NOT contain a multipart MIME payload attachment.