Knowledge base

ebXML Knowledge base pages provide a reliable basis of technical and educational information on the standards. Content is created and maintained by the Editorial Board for ebXML.

Your comments are welcome. Suggestions for editing these pages should be made using the add new comment link at the bottom of each ebXML Knowledge base page. The Editorial Board will periodically review these comments and incorporate them into the main text as appropriate.

ebXML Overview

ebXML (Electronic Business using eXtensible Markup Language), is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet. Using ebXML, companies now have a standard method to exchange business messages, conduct trading relationships, communicate data in common terms and define and register business processes.

ebXML includes five types of specifications, which may be implemented singly or in tandem: Related work includes:


Significant milestones in the development and adoption of ebXML include:

September 1999   
United Nations and OASIS Join Forces to Produce Global XML Framework for Electronic Business

December 1999
Organizations from Around the World Gather to Launch ebXML

March 2000
ebXML Initiative Releases First Technical Specifications for Public Comment

May 2000
ebXML Moves Forward on Defining Global Electronic Business Infrastructure

August 2000
ebXML Showcases Dynamic Trading Network

September 2000
ebXML Sets Standards for Electronic Trading Partner Agreements
850,000 Companies Select ebXML for New Global Commerce Internet Protocol

February 2001
ebXML Integrates SOAP Into Messaging Services Specification
ebXML Technical Architecture Specification Approved

April 2001
ebXML Messaging Services Specification Gains RosettaNet Support

May 2001
ebXML Approved: UN/CEFACT and OASIS Deliver on 18-Month Initiative

June 2001
OASIS Forms ebXML Technical Committees

July 2001
UN/CEFACT Forms e-Business Transition Ad Hoc Working Group

May 2002
ebXML Registry Approved as OASIS Standards

September 2002
ebXML Messaging Service Specification Approved As OASIS Standard

December 2002
ebXML Collaboration Protocol Profile and Agreement Ratified as OASIS Standard

June 2003
UN/CEFACT Plenary Endorses Latest ebXML Specifications

October 2003
ebXML Business Process Specification Advances Within OASIS

March 2004
ISO Approves ebXML OASIS Standards

April 2004
OASIS Members Advance Service Oriented Architecture Based on ebXML and Web Services

10 May 2004
UN/CEFACT and OASIS Cooperate to Strengthen Work on ebXML


Review answers to the frequently asked questions below. Post new questions and additional comments at the FAQ Forum. See also: ebBP FAQ, ebCPPA FAQ, ebMS FAQ, and Registry FAQ.

Are there royalty fees for the use of ebXML?

OASIS provides ebXML specifications free of charge. There are no royalties or fees associated with the use of the ebXML specifications. Openness of the ebXML specifications is a requirement in order to encourage adoption.

How does ebXML address the needs of the small-medium size enterprises?

ebXML's requirements begin with the objective to promote the use of shrink-wrapped, plug-and-play software to support its messages. By keeping that focus paramount, as well as taking advantage of the economies of scale presented by the Internet, ebXML's design and technical architecture remain within the reach of smaller businesses.

How does ebXML affect an existing IT infrastructure?

If a company does not yet exchange electronic business data, ebXML means making the connections to send and receive these messages, authenticating other parties, editing the contents of the messages, and mapping the data to internal systems. If a company already uses EDI or other business data exchange protocols, it may have already established these facilities but may still need to write new routines for ebXML messages. Packaged software often makes these functions transparent to end-users.

How does ebXML impact current EDI investments?

Companies with systems set up for business data exchange will probably have fewer changes in business processes than those starting from scratch. ebXML builds on the lessons learned from EDI, particularly the need to identify trading partners and messages and account for all message traffic. The best practices established for effective EDI apply to ebXML. ebXML also identifies common data objects, called core components, that allow companies to interchange standard EDI data with XML vocabularies compliant with the ebXML specifications.

Is ebXML just for B2B, or can it be applied to business-to-consumer trading?

ebXML supports messages and services among businesses as well as between businesses and consumers. For business-to-consumer exchanges, however, the specifications define only the services and architecture on the business end, not customer screens or interactions.

What development environments does ebXML support?

ebXML was designed to be independent of equipment, software platforms or communication networks. As long as a system supports standard Internet transport protocols and XML, it should also support ebXML.

Who is using ebXML?

ebXML is being used around the globe by a wide variety of industries. Review (and add to) the list of deployments and learn more about available case studies.

Why ebXML?

ebXML supports electronic interchange by parties in a peer-to-peer relationship when the interchange crosses domains of control. The specifications enable the composition of distinct components that can be used individually, together with the other specifications in the framework, or with other emerging technologies to accomplish a larger activity or business goal.

Five capabilities were identified as part of the initial objective for ebXML, and remain important to conduct electronic trading relationships among business parties. They are:

  • Well-understood business semantics and guiding principles
  • Framework and operational semantics for assembling business transactions and complex activities
  • A secure and reliable transport
  • Defined framework for publishing, discovery and availability of needed artifacts and services
  • Framework to configure a contract between business parties, and to associate or link the business process with the underlying transport

ebXML Webinar Week Generates Interest

Get to know all the standards and their practical application for eBusiness - see this summary on the News page where we show you how ebXML Webinars Generate Community Interest.

Business Process

The ebXML Business Process (ebBP) OASIS Standard provides a business process foundation that promotes the automation and predictable exchange of business collaboration definitions using XML. The specification is advanced by the OASIS ebXML Business Process Technical Committee, a group that remains open to new participation.

Getting to know ebBP

Collaborative business processes using ebBP encompass some basic premises and include:

  1. Activities

  2. Partners or parties

  3. Roles that partners or parties assume

  4. Conditions whereby they interact

  5. Business transaction patterns that support the activities and the conditions expected

The ebBP defines a standard language to configure business systems for business collaboration execution between collaborating parties or business partners.  It is targeted for monitoring of collaborative business processes these entities.  Today, ebBP has evolved from previous versions to integrate the use of other emerging technologies as part of eBusiness solutions focused on SOA.


  • Integrates internationally defined or partner-specified business transaction patterns.
  • Allows infrastructure flexibility for underlying messaging protocols used while providing computable quality of service and conditional constructs.
  • Handles complex activities, choreographies and business collaborations including multi-party relationships that involve role binding changes.
  • Is monitoring focused.
  • Is primarily targeted for eBusiness and collaborating partners rather than enterprise applications.
  • Has gained more attention in user communities than with technology vendors.

ebBP interest and adoption

In its current iteration, the ebBP has garned interest across several industries and user communities including:
Communication has been fostered with groups such as those that support or plan to use Universal Business Language proponents such as with open source freeubl and Health Level 7.

Note: Links are provided to emerging process definitions used by or of interest to these communities.

The freebxmlbp Editor from METU

An open source project on Source Forge using ebBP provides a start for user communities to engage business collaborations. Middle East Technical University in Turkey has created and provided the tools while significant work continues in the health care domain.

The ebBP team appreciates the strong effort by METU and those in the health care domain.

ebBP OASIS Standard

The ebBP v2.0.4 set of packages are an OASIS Standard. The packages include:
  • Technical specification and appendices
  • Core and business signal schemas with documentation
  • A transformation snippet to enable previous versions, and other supporting details
Take a look at the ebBP OASIS Standard:

Also see the link at the OASIS Open home page for ebBP.


Review answers to the frequently asked questions below on ebBP. Post new questions and additional comments at the FAQ Forum. See also: ebXML FAQ, ebCPPA FAQ, ebMS FAQ, and Registry FAQ.

For five core facts - What you always wanted to know about ebBP in five simple questions...

What is ebBP?

The ebBP OASIS Standard is a technical business process specification. It defines a standard language so that business systems can be configured to support the execution of business collaborations between partners or collaborating parties rather than the processing accomplished from the perspective of one business partner. The formal designation has been eBusiness Extensible Markup Language (ebXML) Business Process Specification Schema (BPSS). It is more commonly known as ebBP (after the OASIS ebXML Business Process Technical Committee).

What is a Business Transaction?

A Business Transaction is realized as Business Document Flows between Requesting and Responding parties performing roles. A Business Transaction is a specialized protocol used to achieve and support enforceable transaction semantics and state alignment between collaborating parties. The patterns listed in the technical specification provide semantic guidance, and options for a Business Transaction. One or more Business Signals can be exchanged as part of a Business Transaction to ensure state alignment of the respective parties.

When is the ebBP technical specification used?

The ebBP technical specification can be used to specify any shared collaboration. The specification may be effectively used with the other specifications in the ebXML framework, and with other technologies, for example when Web Services software components are being specified to execute Business Collaborations. Or, the ebBP business semantics and syntax are well-suited to enable definition of modular process building blocks that are combined in complex collaboration activities. The ebBP technical specification is also used to specify the business process related configuration parameters for configuring a software component to execute and monitor the collaborations.

What is an ebBP definition?

A business process definition created using the semantics and syntax provided in the ebBP technical specification is referred to as an ebBP definition. ebBP definitions describe interoperable business processes that allow business partners, or collaborating parties, to cooperate and achieve a given business goal. It contains the specification of the Business Transaction, the choreography for using the Business Transaction(s) that comprise a Business Collaboration, and the Business Collaborations themselves. An ebBP definition is a machine computable and interpretable specification. The software component that manages these activities on behalf of a business partner is termed a Business Service Interface (BSI).

What is a Business Signal?

Business signals have a specific business purpose and are separate from lower protocol and transport signals. One or more Business Signals can be exchanged as part of a Business Transaction to ensure state alignment between both parties. Evaluation of business signals enable the state of a Business Collaboration to be explicitly calculated at run time. The ebBP technical specification provides both the structure and choreography of Business Signals, including allowing for user defined signals.

What function does a Business Signal provide?

A Business Signal is computable. This provides the collaborating parties with a mutual understanding of the business activity. This function allows the parties to know if their expectations in a Business Transaction are realized. This is state alignment, and is important in order for the ebBP specification to have commercial viability. The ebBP specification provides the ability to conduct intended transactions if that is the intent of the collaborating parties.

What is Business Collaboration?

A Business Collaboration is a set of roles interacting through a set of choreographed Business Transactions by exchanging Business Documents. A Business Collaboration is defined by the parties in the collaboration; it can be simple or complex, it can include expected and unexpected (but contingent) actions and the collaboration can allow for other than eBusiness options. The ebBP technical specification is used to specify the business process parameters to configure the Business Service Interface (BSI) needed to execute and to monitor the collaborations, including the capability to transition to human interactions or decisions that may be important to eBusiness activity, e.g. a phone call.

How is the ebBP technical specification used?

The ebBP technical specification provides the structure and semantics for ebBP process definitions. The goal of the ebBP technical specification is to provide the bridge between eBusiness process modeling and the execution of eBusiness software components.

All the parameters of the ebBP definition are intended to be specified at design time or, where applicable, acquired at deployment or runtime. This can be done by creating a business process and information model although modeling is optional. The ebBP definition expresses the expectations of the collaborating parties or business partners and provides the mechanisms to support state alignment. The ebBP technical specification provides the capability to leverage international business transaction patterns and the operational semantics that enable their use; and, well defined business signals to compute state alignment. The ebBP definition and a CPA may be used to configure a BSI.

What is included in the ebBP Version 2.0.X series?

The ebBP Versions 2.0.X includes normative documents, and non normative examples and artifacts to better inform users. The approved standard is Version 2.0.4. The documents and artifacts included are:


  • the technical specification and designated appendices
  • the core ebBP schema and documentation
  • the standard Business Signal schema and documentation
  • description of the Business Service Interface
  • other important guidance including the pattern matrices included in the specification

Non normative

  • transformation functions for v1.05 => 2.0.1
  • CPA — ebBP mapping
  • a glossary
  • the Public Review comments
  • other relevant use cases and guidelines
  • all examples

What are the major features and capabilities that have been added or significantly expanded in the ebBP v2.0.X series?

  1. The six business transaction patterns specified by the UN/CEFACT Modeling Methodology (UMM Revision 10, Chapters 8 & 9) for business messaging exchanges have been further articulated. Concrete parameters have more fully defined and operational semantic spelled out. These six patterns could enable the majority of business transactions in eBusiness or other shared collaborations. In addition, an extensible pattern has been specified to enable anticipated industry or partner specific business transactions. This pattern is the Data Exchange pattern.
  2. Enabled the use of hybrid, ebXML or Web Services in the business message exchange. Done by creating an Operational Mapping for the business messages and signals used in the business transaction patterns to abstract operations used in the WSDL message exchange patterns.
  3. Enable an ebBP definition to reference a set of logical Business Documents. Logical business documents can be specified from multiple sources or namespaces. The actual Business Document can be realized by using external specifications to include ebXML CC and Universal Business Language (UBL) Small Business Subset (SBS), Domain specific business documents can also be defined.
  4. Business partners can assume different roles throughout the collaboration. These roles can be attached to the Business Collaboration definition as it is composed so as to understand how the role change enables the business message exchange in a business transaction whether it is binary or has multiple parties. These expanded role binding capabilities support communities such as RosettaNet.
  5. A status visibility function has been provided. This allows third parties to be visible in a business transaction although they do not have a first class role in the business transaction but their activities are important to one of the collaborating (first class) parties.
  6. Use of semantic information to support the capability to take a generic business process and specialize it for a specific use.
  7. Improved linking constructs and transition capabilities to support the process definition as they are composed.

What is the status of ebBP?

ebBP v 2.0.4 has been approved as an OASIS Standard. The OASIS eBusiness Business Process Technical Committee plans to promote the ebBP to ISO 15000 status as soon as practical while encouraging and promoting adoption. Future collaboration with UN/CEFACT and Object Management Group (OMG) is anticipated.

Errata are included as non normative artifacts and found on the public web site:

Are there tools that use ebBP?

Yes, there is an open source editor, freebxmlbp, which was developed at Middle East Technical University (METU). The tool is under development with an initial user's guide recently circulated.

See ebXML deployments for more information.

What known user communities are using or interested in ebBP?

  • Textiles
  • Transport
  • Local government
  • High technology
  • Health care
  • Financial Services
  • Agencies/departments of National Governments

How does ebBP relate to BPSS?

Briefly and simply, ebBP is a short name, or alias, for the technical specification that realizes business collaboration, ebXML BPSS. They are one and the same. The objective is to define business processes in a standard way to allow interoperability between systems, organizations, business partners and collaborating parties. This will enable eBusiness. Labeling the latest and more substantive version ebBP focuses on the objective rather than the mechanism for achieving the objective which is the technical specification.

What you always wanted to know about ebBP in five simple questions...

1. How does ebBP relate to other process standards?
ebBP is a standard process definition language for eBusiness collaboration to configure eBusiness and monitor business expectations of the business quality of service contract. It could be used in a complementary way with other process standards such as WS-Choreography Description Language (WS-CDL) for web services choreography, and/or WS-Business Process Execution Language (WS-BPEL) for orchestration. ebBP provides the business quality of service and semantics important for business stakeholders, particularly the conditions, constraints, and visibility criteria needed. ebBP could be used when leveraging WS-BPEL for managing enterprise applications that support the eBusiness exchanges. ebBP can also be mapped to the Business Process Definition Metamodel interaction protocol and represented in Business Process Modeling Notation as these latter two efforts converge to provide a flexible modeling environment for business processes, their semantics, and visualization.

2. What value add does ebBP provide for eBusiness stakeholders and when compared to other process languages?
ebBP's origin began with the UN/CEFACT Modeling Methodology and the international business transaction patterns that support eBusiness. Those patterns, and the business quality of service expectations defined to support them are key to the successful use of ebBP.  ebBP provides a level of business abstraction independent of any platform, software or services, which also adds flexibility to its use with web services and other XML based technologies.  ebBP also allows mapping semantic details and content to business documents and business transactions. Coupled with the use of business signals, business stakeholders can effectively manage their eBusiness document exchanges.

3. What general applications are targeted for the use of ebBP?
ebBP documents the document-based, business message exchanges important to eBusiness automation.  It therefore provides a basis for and supports the business monitoring of those messages exchanges. When represented in BPMN and mapped to BPDM, ebBP provides a computable abstraction from  business modeling views and links to the technical contract or other drivers or guides to enterprise processes.  ebBP definitions, such as the modular descriptions developed by Universal Business Language (UBL), a library of business process modules can be developed to speed the definition of, consistent application using and other domain aspects important to many domains.

4. What use cases are met by ebBP? What tools are available or can be used?ebBP practically can be used with many XML based design tools, including Oxygen, XMLSpy and other editors. A freebxmlbp editor is available on Source Forge. In addition, another collaborative effort is underway to support use of ebBP with other modeling languages using Eclipse.  Visual Studio also supports ebBP. ebBP has  been applied in domains such as textiles, transport, health care, financial services, and eGovernment.

5. Where is ebBP going?
The focus is adoption and promotion of this ebBP OASIS Standard v2.0.4 to ISO to join the ISO 15000 set.  Future efforts are under discussion with several organizations.

Collaboration Protocol Profile and Agreement

The ebXML Collaboration Protocol Profile and Agreement (CPPA) OASIS Standard (ISO 15000-1) defines how trading partners engage in electronic business collaborations through the exchange of electronic messages. The specification is advanced by the OASIS ebXML CPPA Technical Committee, a group that remains open to new participation.


Review answers to the frequently asked questions below on the ebXML Collaboration Protocol Profile and Agreement. Post new questions and additional comments at the FAQ Forum. See also: ebXML FAQ, ebBP FAQ, ebMS FAQ, and Registry FAQ.

What is the need for ebXML CPPA?

The ebXML Collaboration Protocol Profile and Agreement OASIS Standard provides definitions for the sets of information used in business collaborations. One set of information (the Profile) contains data about the business partners' technical capabilities to engage in electronic business collaborations with other partners. The second set of information (the Agreement) contains data that has been agreed to configure the public, shared aspects of the protocols used in the business collaboration protocols. Version 2.0 of the specification is highly aligned with ebXML business process descriptions (ebBPSS) and the ebXML Messaging protocol (ebMS). Future versions will accommodate extensions that provide support for other business process notations and other business messaging protocols. A specification of the Negotiation protocol for Collaboration Protocol Agreements is nearing completion in 2003.

Who should be involved in this development?

The maintenance and enhancement of this OASIS Standard should be of interest to ISVs seeking interoperable and standardized approaches to the configuration of heterogeneous yet interoperable software for enabling business collaboration. It should be of interest to end users concerned with automation of the management of configuration information over the lifetime of a business collaboration community. It should also be of interest to those seeking documented configurations suitable for monitoring compliance of collaborators' performance in areas such as data confidentiality, reliability, authentication, acknowledgment, and timely response.

Who will benefit from ebXML CPPA and how?

This technology can benefit end users now in reducing the costs of initial collaboration setup and in the management of the lifecycle of the configuration information. Monitored agreements may also be of value in reducing costs of operation and in resolving service problems.

How does this work compare with related efforts at other standards organizations?

This work presumes that exchanges of business information in business collaborations will tend to be conducted in relatively static modes, with slowly changing configurations. Options and functionality will be deliberately changed, rather than dynamically reconfigured on a message-by-message basis. It also presumes that many businesses will be interested in monitoring the "messaging communications channel" parameters to see that agreed-upon levels of compliance and performance are maintained. It is also problematic how enthusiastically extremely dynamic modes of configuration (spontaneous collaboration) will be embraced by those interested in verification of agreed upon-behavior in business collaboration. Finally, the Negotiation protocol is to provide a highly automatic way to set up agreements for collaboration protocols, largely realizing the business advantages (lower management costs) promised by highly dynamic ("spontaneous") collaboration technologies.

In addition, many businesses tend to confine the supported technical interactions to the smallest number of profiles permitting secure and reliable connectivity. Security, reliability, diagnostic visibility, and change management are core concerns for business collaboration protocols, but are either neglected or specialized topics in basic technology or general purpose web services standards organizations.

When will ebXML CPPA be completed?

ebXML CPPA Versions 1.0 and 2.0 are complete. Version 2.0 is an approved OASIS Standard. An ebXML CPPA Negotiation specification is currently under development. A maintenance 2.1 version will fix several minor errors that have been detected and resolved and add enhanced extensibility points to the schema. Plans for a version 3.x will emerge as other ebXML specifications (ebXML Messaging and ebXML Business Process) move forward.

Who uses ebCPPA?

ebCPPA is being used around the world.

See ebXML deployments for more information.

Messaging Services

The ebXML Messaging Services (ebMS) OASIS Standard (ISO 15000-2) defines the transport, routing and packaging of e-business transactions using standard Internet technologies. The specification is advanced by the OASIS ebXML Messaging Services Technical Committee, a group that remains open to new participation.

ebMS describes a communication-protocol neutral method for exchanging electronic business
messages. It defines specific enveloping constructs supporting reliable, secure delivery of business information. The specification defines a flexible enveloping technique, permitting messages to contain payloads of any format type. This versatility ensures that legacy electronic business systems employing traditional syntaxes (i.e. UN/EDIFACT, ASC X12, or HL7) can leverage the advantages of the ebXML infrastructure along with users of emerging technologies.

The prime objective of ebMS is to facilitate the exchange of electronic business messages within an XML framework that leverages common Internet standards, without making any assumption on the integration and consumption model these messages will follow on the back end. These messages may be consumed in different ways that are out of scope of the specification: they may bind to a legacy application, to a service, be queued, enter a message workflow process, be expected by an already-running business process, be batched for delayed processing, be routed over an Enterprise Service Bus before reaching their consumer application, or be dispatched based on header data or payload data, etc.

The ebXML messaging framework is not a restrictive one: business messages, identified as the 'payloads' of ebXML messages, are not limited to XML documents. Traditional EDI formats may also be transported by ebMS. These payloads can take any digital form–XML, ASC X12, HL7, AIAG E5, database tables, binary image files, etc. Multiple payloads, possibly of different MIME types, can be transported in a single ebMS message. An objective of the ebXML Messaging protocol is to be capable of being carried over any available transfer protocol. The specification provides bindings to HTTP and SMTP, but other protocols to which SOAP may bind can also be used. The choice of an XML framework rather reflects confidence in a growing XML-based Web infrastructure and development tools infrastructure, the components of which can be leveraged and reused by developers.

For more information, see the OASIS ebXML Messaging Service Technical Committee homepage and TC Charter.


Review answers to the frequently asked questions below on the ebXML Messaging Services specification. Post new questions and additional comments at the FAQ Forum. See also: ebXML FAQ, ebBP FAQ, ebCPPA FAQ, and ebXML Registry FAQ.

How does ebMS v3.0 differ from v2.0?

It is becoming critical for broad adoption among all partners – large or small - of a supply-chain, to handle differences in message flow capacity, intermittent connectivity, lack of static IP addresses or firewall restrictions. Such new capabilities played an important role in the motivation that led to ebMS 3.0, along with the need to integrate and profile the emerging SOAP-based QoS-supporting standards. The message header profiling that provided, in ebMS 2.0, a standard business-level header, has also been extended to better address the diversity of back-end binding models, as well as the emerging trend in business activity monitoring, the eBusiness side of which a message handler should be able to support.

Why is ebMS 3.0 being developed in two parts?

A number of OASIS members and supporters wanted the basic functionality as soon as possible (especially the pull functionality) as they have large user bases in the SME arena that need a lightweight intermittently connectable client to deal with major corporations. The OASIS ebMS Technical Committee decided to deliver the base mandatory functionality as soon as possible and to deliver the optional more complex/advanced/less-used functionality later.

Part 1 is mainly the mandatory functionality that we would expect all major vendor Gateway products to support (although some functionality will be optional on a relationship-by-relationship basis.

Part 2 will have all the more specialised functionality that will probably only be used in major organisations inter-trading e.g. large message handling, messaging routing/forwarding, multiple message bundling and additional transport level support. Although some of the functionality may be applied to the simpler trading environment such as the potential to ask for an individual message as part of a message pull request, this will likely be a special function to address a particular problem and not used as the normal general B2B solution.

Who uses ebMS?

ebMS is being used around the world. See ebXML deployments for more information.


The ebXML Registry Information Model OASIS Standard (ISO 15000-3) and the ebXML Registry Services Specification OASIS Standard (ISO 15000-4) define interoperable registries and repositories, with an interface that enables submission, query and retrieval of contents. The specifications are advanced by the OASIS ebXML Registry Technical Committee, a group that remains open to new participation.

For more information, see the TC Charter and FAQ.


ebXML Registry Standards

The version 3.0 standards and related materials are included in a ZIP file available for public download.

The ZIP file contains:
1. The OASIS ebXML Registry Information Model (RIM) Standard, v3.0, as "regrep-rim-3.0-os.pdf".
2. The OASIS ebXML Registry Services (RS) Standard, v3.0, as "regrep-rs-3.0-os.pdf".
3. Supporting files and documentation including:

  • 10 WSDL description files,
  • 20 XML scheme files, and
  • 5 XSD files

These and additional documents can be viewed from the OASIS ebXML Registry Technical Committee homepage under the documents link.

ebXML Registry Webinar

The OASIS ebXML Registry TC held an open webinar event on September 15, 2005 to help developers understand more about how ebXML Registry enables secure, federated information management within and across enterprises. The presentation included an overview of ebXML Registry v3.0 key features, and details on production implementations. A Q&A session with members of the OASIS ebXML Registry TC was included in the event. The presentation materials are available for download OASIS ebXML Registry Webinar

Registry FAQ

Review answers to the frequently asked questions below on the ebXML Registry and Repository specifications. Post new questions and additional comments at the FAQ Forum. See also: ebXML FAQ, ebBP FAQ, ebCPPA FAQ, and ebMS FAQ.

What is an XML Registry?

An XML registry is an information system that stores XML artifacts (e.g., XML schemas, data elements, etc.) and non-XML artifacts (e.g. supporting documents), as well as details (metadata) about the artifacts. The storage facility (e.g., a filesystem or database) that holds registered objects is known as a repository, while the part of the information system that maintains the metadata for the registered objects is known as a registry.

What are the benefits of an XML Registry?

The benefits of an XML Registry are numerous and include:

  • Promotes efficient discovery and maintenance of registered objects
  • Enables efficient version control for registered objects
  • Promotes unified understanding of registered objects. Because metadata for registered objects is accessible from a single location, a unified understanding of the purpose of the registered objects will be promoted
  • Ensures availability and reuse of authoritative XML. A controlled registration and validation of XML artifacts from authoritative sources promotes interoperability between trading partners, and facilitates greater reuse
  • Enables collaborative development. Users can create XML artifacts and submit them to an XML registry for use and potential enhancement by authorized parties. The enhanced versions can then be made available for access by other authorized parties.

Who uses ebXML Registry standards?

ebXML Registry standards are being used around the world. See ebXML deployments for more information.

Core Components

The ebXML Core Components Technical Specification (ISO 15000-5)  presents a methodology for developing a common set of semantic building blocks to represent the general types of business data in use today. It also provides for the creation of new business vocabularies and restructuring of existing business vocabularies. ebXML CCTS is advanced by the Techniques and Methodologies Group (TMG) of the United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT).

ebXML CCTS describes and specifies a new approach to the well-understood problem of the lack of information interoperability between applications in the e-business arena. Traditionally, standards for the exchange of business data have been focused on static message definitions that have not enabled a sufficient degree of interoperability or flexibility. ebXML CCTS addresses the need for a more flexible and interoperable way of standardising business semantics.

Implementation, interoperability, and conformance

The ongoing work of the OASIS ebXML Implementation, Interoperability and Conformance (IIC) Technical Committee enables software providers to create infrastructure and applications which interoperate with and adhere to the ebXML specifications. The Committee provides coordination and specification alignment across the ebXML solution components, ensuring that the ebMS envelopes are compatible with ebCPPA and ebBP, including the XML mechanisms and content they are using. The IIC ensures that each piece of the ebXML solutions stack continues to be compatible with one another. The Committee remains open to new participation.

Work of the OASIS IIC Technical Committee includes:

Initiative Archive (1999-2001)

ebXML began in the fall of 1999 as effort by UN/CEFACT and OASIS to initiate a worldwide project to enable the consistent use of XML for the exchange of all electronic business data.

The ebXML Initiative was an 18-month endeavor in which industry groups, standards bodies, vendors, consultants and users from virtually every continent on the globe participated. In May 2001, ebXML met its deadline by delivering a suite of specifications, white papers and other related documents.

This ebXML Initiative Archive contains: