OASIS ebXML Core (ebCore) TC

Join TC     TC Page     Send a comment to this TC

Managing modifications and maintenance for several ratified ebXML specifications

Pim van der Eijk, Chair
Sander Fieten, sander@chasquis-consulting.com, Chair

Table of Contents

Announcements

18 September 2016: ebCore Agreement Update Specification Version 1.0 has been approved as a Committee Specification. For more information, see the announcement at https://www.oasis-open.org/news/announcements/ebcore-agreement-update-specification-v1-0-published-by-the-oasis-ebxml-core-ebco.

Participation in the OASIS ebXML Core TC is open to all interested parties. Contact member-services@oasis-open.org for more information on joining the TC.


Overview

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.

For more information, see the TC Charter.


Technical Work Produced by the Committee

ebCore Agreement Update Specification Version 1.0. Edited by Pim van der Eijk and Theo Kramer. 18 September 2016. OASIS Committee Specification 01. http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/cs01/ebcore-au-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/ebcore-au-v1.0.html.

OASIS ebCore Party Id Type Technical Specification Version 1.0. Edited by Dale Moberg and Pim van der Eijk. 28 September 2016. OASIS Committee Specification 01. http://docs.oasis-open.org/ebcore/PartyIdType/v1.0/PartyIdType-1.0.html. Latest version: http://docs.oasis-open.org/ebcore/PartyIdType/v1.0/PartyIdType-1.0.html.



Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.