Project news

15-day Public Review for ebCore Agreement Update Specification V1.0 – ends July 18th

The OASIS ebXML Core (ebCore) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

ebCore Agreement Update Specification Version 1.0
Committee Specification Draft 02 / Public Review Draft 02
31 May 2016

What is ebCore Agreement and why is it important?

The ebCore Agreement Update specification defines message exchanges and an XML schema to support the exchange of messaging service communication agreement update requests and the associated responses to such requests.

The schema offers extensibility for various types of updates. The main initial application of the specification is the exchange of X.509 certificates for certificate rollover, for which a separate extension schema is provided.

The specification is based on the concept of messaging service communication agreements and the creation of new agreements as independently identified updated copies of existing agreements. The specification also provides an Agreement Termination feature. The specification supports ebMS2, ebMS3 and AS4 but can also be used with other protocols that have a concept of communication agreement. The specification is independent of storage or interchange formats for configuration information.

About the TC:

The ebXML Core TC maintains ebXML specifications transitioned from other Technical Committees. TCs eligible for maintenance by the ebXML Core TC are ebXML Messaging, ebXML CPPA, ebXML ebBP, ebXML IIC, and ebXML RegRep. The ebXML Core TC manages clarifications, modifications, and enhancements for the specifications through the OASIS standards process.

Public Review Period:

The public review starts 04 July 2016 at 00:00 UTC and ends 18 July 2016 at 11:59 UTC. The specification was previously submitted for public review [2]. This 15-day review is limited in scope to changes made from the previous review. Changes are highlighted in red-lined DIFF file included in the package [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.

The prose specification document and related files are available here:

Editable source (Authoritative):



XML schemas:

Schema data dictionary:

XML document samples:

ZIP distribution files (complete):

For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:

Additional information about this specification and the ebCore TC may be found on 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 ‘ebCore Agreement Update Specification Version 1.0’, 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.

========== Additional references:

[1] OASIS ebXML Core (ebCore) TC

[2] Previous public reviews:

30-day public review, 10 November 2015:
– Comment resolution log:

[3] Red-lined DIFF file:


RF on Limited Terms Mode