15-day Public Review for ebMS v3.0 Advanced Features, ends 18 Apr

The OASIS ebXML Messaging Services TC members have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

OASIS ebXML Messaging Services Version 3.0: Part 2, Advanced Features
Committee Specification Draft 03 / Public Review Draft 02
16 February 2011

Specification Overview:

This specification complements the ebMS 3.0 Core Specification by specifying advanced messaging functionality for message service configuration, message bundling, messaging across intermediaries (multi-hop) and transfer of (compressed) messages as series of smaller message fragments.

The main function of intermediaries as defined in this specification is to provide message routing and forwarding based on standardized SOAP message headers, allowing a sending MSH to ignore the ultimate message destination and abstract away from lower-level transport parameters such as the URL of the ultimate receiving MSH and message exchange pattern bindings. The intermediary functionality defined here supports message relaying across segmented networks, synchronous and asynchronous bindings and both active (push) and passive (pull message stores) forwarding styles. Multi-hop paths may consist of any number of intermediaries.

This second review of the specification contains editorial changes to correct and clarify issues raised during its first review period. No changes to the functionality described in the specification have been made as part of these changes.

The OASIS ebXML Messaging Services TC [1] was chartered to develop and recommend technology for the transport, routing and packaging of business transactions using standard Internet technologies.

Public Review Period: The public review starts today, 03 April 2011 and ends 18 April 2011. The specification was previously submitted for a 60-day public review on 13 August 2010 [2]. This 15-day review is limited in scope to changes made from the previous review of 13 August 2010. Changes are highlighted in the diff-marked PDF and editable source files [3].

This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

URIs: The prose specification document and related files are available here:

Editable Source (Authoritative): http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/part2/201004/csprd02/ebms...
HTML: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/part2/201004/csprd02/ebms...
PDF: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/part2/201004/csprd02/ebms...

XML Schemas: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/part2/201004/csprd02/ebms...

ZIP distribution file (complete): http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/part2/201004/csprd02/ebms...

Additional information about the specification and the OASIS ebXML Messaging Services TC may be found at the TC's public home page located at:


Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be accessed via the button labeled "Send A Comment" at the top of the TC public home page, or directly at:


Feedback submitted by TC non-members for this work and for other work of this TC is publicly archived and can be viewed at:


All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of 'OASIS ebXML Messaging Services Version 3.0: Part 2, Advanced Features', we call your attention to the OASIS IPR Policy [4] applicable especially [5] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member's patent, copyright, trademark and license rights that read on an approved OASIS specification. OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC's work.