Message Service Specification (MSS) is a communications-protocol neutral method for exchanging electronic business messages. It supports reliable, secure delivery of business information and a flexible enveloping technique. This flexible enveloping technique is being used to incorporate features of SOAP (new window) and RosettaNet Business Message (new window) messages.
The Message Service Specification contains two parts:
-
Header container. This is the first MIME part, containing One SOAP message. The SOAP message is an XML document consisting of a SOAP Envelope element. The SOAP Envelope element consists of:
SOAP-ENV:Header. This is a generic mechanism for adding features to SOAP message, including ebXML specific header elements.
SOAP-ENV:Body. This is a container for message service handler control data and information related to the payload parts of the message.
-
Payload containers. There can be zero or more additional MIME parts containing application specific payloads. See RosettaNet Business Message payloads (new window).
MSS can use HTTP, but other protocols such as HTTPS, and Simple Mail Transfer Protocol (SMTP) may by used.
Organization: ebXML
More information: MSS page on the OASIS website (new window)
More on the general topic: Messaging specifications
- Asynchronous Application Service Protocol (ASAP) for SOAP
- Representational State Transfer (REST)
- RosettaNet Business Message
- SOAP
- Web Distributed Data Exchange (WDDX)
- Web Services Addressing (WS-Addressing)
- Web Services Eventing (WS-Eventing)
- Web Services Notification (WSN)
- Web Services Reliability (WS-Reliability)
- Web Services Reliable Messaging (WS-ReliableMessaging)
- XML Protocol (XMLP)
