World Library  
Flag as Inappropriate
Email this Article


Article Id: WHEBN0030873555
Reproduction Date:

Title: EbXML  
Author: World Heritage Encyclopedia
Language: English
Subject: UN/CEFACT, Content Assembly Mechanism, UN/CEFACT's Modeling Methodology, Resources, events, agents (accounting model), Computer appliance
Publisher: World Heritage Encyclopedia


Electronic Business using eXtensible Markup Language, commonly known as e-business XML, or ebXML (pronounced ee-bee-ex-em-el, [i'bi,eks,em'el]) as it is typically referred to, is a family of OASIS and UN/CEFACT whose mission is to provide an open, XML-based infrastructure that enables the global use of electronic business information in an interoperable, secure, and consistent manner by all trading partners.

The ebXML architecture is a unique set of concepts; part theoretical and part implemented in the existing ebXML standards work.

The ebXML work stemmed from earlier work on ooEDI (object oriented EDI), UML / UMM, XML markup technologies and the X12 EDI "Future Vision" work sponsored by ANSI X12 EDI.

The melding of these components began in the original ebXML work and the theoretical discussion continues today. Other work relates, such as the Object Management Group work and the OASIS BCM (Business-Centric Methodology) standard (2006).

Conceptual overview of ebXML architecture

While the ebXML standards adopted by ISO and OASIS seek to provide formal XML-enabled mechanisms that can be implemented directly, the ebXML architecture is on concepts and methodologies that can be more broadly applied to allow practitioners to better implement e-business solutions.

A particular instance is the Core Components Technical Specification (CCTS) work that continues within UN/CEFACT, whereas its cousin - UBL - Universal Business Language - specification is used within OASIS that implements specific XML transactions by applying the principles of CCTS to typical supply chain transactions such as invoice, purchase order, ship notice and so on.


ebXML was started in 1999 as a joint initiative between the Organization for the Advancement of Structured Information Standards (OASIS). A joint coordinating committee composed of representatives from each of the two organizations led the effort. Quarterly meetings of the working groups were held between November 1999 and May 2001. At the final plenary a Memorandum of Understanding was signed by the two organizations, splitting up responsibility for the various specifications but continuing oversight by the joint coordinating committee.

The original project envisioned five layers of data specification, including XML standards for:

  • Business processes,
  • Collaboration protocol agreements,
  • Core data components,
  • Messaging,
  • Registries and repositories

All work was completed based on a normative requirements document and the ebXML Technical Architecture Specification.

After completion of the 6 specifications by the two organizations, 5 parts of the work were submitted to ISO TC 154 for approval. The International Organization for Standardization (ISO) has approved the following five ebXML specifications as the ISO 15000 standard, under the general title, Electronic business eXtensible markup language:

  • ISO 15000-1: ebXML Collaborative Partner Profile Agreement
  • ISO 15000-2: ebXML Messaging Service Specification
  • ISO 15000-3: ebXML Registry Information Model
  • ISO 15000-4: ebXML Registry Services Specification
  • ISO 15000-5: ebXML Core Components Technical Specification, Version 2.01.

OASIS technical committees and UN/CEFACT retain the responsibility for maintaining and advancing the above specifications. The initiative was established to promote development and adoption of ebXML-based open-source software.

Collaborative Partner Profile Agreement

Collaborative Partner Profile Agreements are XML based documents specifying a trading agreement between trading partners. Each trading partner will have their own Collaboration Protocol Profile (CPP) document that describes their abilities in an XML format. For instance, this can include the messaging protocols they support, or the security capabilities they support. A CPA (Collaboration Protocol Agreement) document is the intersection of two CPP documents, and describes the formal relationship between two parties. The following information will typically be contained in a CPA document:

  • Identification information: the unique identifiers for each party and their roles within the trading relationship
  • Security information: for instance, are digital signatures required, and what algorithms do they use & communication information: the protocols that will be used when exchanging documents
  • Endpoint locations: the URL, service and action messages should be sent to
  • Rules to follow when acknowledgments are not received for messages, including how long to wait before resending, and how many times to resend
  • Whether duplicate messages should be ignored
  • Whether acknowledgments are required for all messages

Messaging Service Specification

The Message Service Specification (ebMS) describes a communication-neutral mechanism Message Service Handlers (MSH) must implement in order to exchange business documents. ebMS3.0 is the current version of the specification. ebMS3.0 is built as an extension on top of the SOAP with Attachments specification. The SOAP message contains the meta-data required to exchange the business document in a secure and reliable manner, while the business payload is attached to the SOAP message. Multiple business payloads may be attached to a single message, and the format of the payloads is beyond the scope of the ebXML specifications. The information trading partners place in ebMS messages is largely dictated by the CPA agreement that defines the relationship between them. The following information is typically contained within ebMS messages:

  • Unique message id
  • Who the message is for
  • Who sent the message
  • A conversation id for linking related messages
  • A digital signature based on the XML Signature specification
  • An indication for whether duplicate messages should be ignored
  • An indication for whether acknowledgments are required

ebMS is communication protocol neutral, although the most common underlying protocols are HTTP and SMTP.

See also


External links

  • ebXML community
  • ebXML BPSS/ebBP business process specification
  • ebXML CORE steering committee
  • ebMS 2.0 Specification
  • ebXML Messaging Services 3.0: Part 1, Core Features Specification
  • ebXML Messaging Services Technical Committee


  • ebXML Messaging - The direction of secure Internet communications for interoperable, global business
  • OASIS News: ISO Approves ebXML OASIS Standards
  • Simple introduction to ebXML

Open source projects

  • freebXML Registry open source project
  • The Hermes Messaging Gateway is an open-source software commonly deployed in messaging applications to support the AS2/ebMS2 standard.
  • Holodeck B2B is an open-source implementation of the AS4/ebMS3 standard.
  • Jentrata Message Gateway - Open Source gateway leveraging new technology frameworks and standards
  • Webswell Connect - Ebxml open source integration tool

Other tools

  • Cisdal Message Gateway
  • ebXML Messaging Products - Drummond Certified Interoperable
  • eLife Coupler ebXML Messaging Tool
  • MOREBIZ B2B ebXML gateway based on open source frameworks

This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.

Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.