EbXML

• ebXML is stand for Electronic Business Extensible Markup Language.
• ebXML can be pronounce as " electronic business XML," "e-biz XML," "e-business XML," or "e-b-x-m-l".
• It is a set of specification that put together to enables modular electronics business framwork.
• The ebXML is not a newly formed organisation, it's a joint effort undertaken by OASIS and UN/CEFACT.
• A key aspect for the success of the ebXML initiative is adherence to the use of the W3C suite of XML and related Web technical specifications to the maximum extent practical. A certain key elements of the ebXML technical framework may require adopting alternative technologies and technical specifications— such as those of the Internet Engineering Task Force (IETF), International Organization for Standardization (ISO), Institute of Electrical and Electronics Engineers (IEEE), International Electrotechnical Commission (IEC), UN/CEFACT, OASIS, and the Object Management Group (OMG).

Purpose

• ebXML initiative is to research and identify the open technical framework upon the global implementation of XML. Therefore, to utilized in a consistent and uniform manner for the exchange of electronic business (eb) data in application to application, application to human, and human to application environments—thus creating a single global electronic market.
• and to achieve Electronic Data Interchange (EDI)

Terminology

Registry

A central server that stores a variety of data necessary to make ebXML work. Amongst the information a Registry makes available in XML form are: Business Process & Information Meta Models, Core Library, Collaboration Protocol Profiles, and Business Library. Basically, when a business wants to start an ebXML relationship with another business, it queries a Registry in order to locate a suitable partner and to find information about requirements for dealing with that partner.

Business Processes

Activities that a business can engage in (and for which it would generally want one or more partners). A Business Process is formally described by the Business Process Specification Schema (a W3C XML Schema and also a DTD), but may also be modeled in UML.

Collaboration Protocol Profile (CPP)

A profile filed with a Registry by a business wishing to engage in ebXML transactions. The CPP will specify some Business Processes of the business, as well as some Business Service Interfaces it supports.

Business Service Interface

The ways that a business is able to carry out the transactions necessary in its Business Processes. The Business Service Interface also includes the kinds of Business Messages the business supports and the protocols over which these messages might travel.

Business Messages

The actual information communicated as part of a business transaction. A message will contain multiple layers. At the outside layer, an actual communication protocol must be used (such as HTTP or SMTP). SOAP is an ebXML recommendation as an envelope for a message "payload." Other layers may deal with encryption or authentication.

Core Library

A set of standard "parts" that may be used in larger ebXML elements. For example, Core Processes may be referenced by Business Processes. The Core Library is contributed by the ebXML initiative itself, while larger elements may be contributed by specific industries or businesses.

Collaboration Protocol Agreement (CPA)

In essence, a contract between two or more businesses that can be derived automatically from the CPPs of the respective companies. If a CPP says "I can do X," a CPA says "We will do X together."

Simple Object Access Protocol (SOAP)

A W3C protocol for exchange of information in a distributed environment endorsed by the ebXML initiative. Of interest for ebXML is SOAP's function as an envelope that defines a framework for describing what is in a message and how to process it.

How does it work

1. The company A will find the requirements for their own ebXML implementation on the Registry.
   - Company A can build their own or buy ebXML implementation that suitable for ebXML trasactions
   - ebXML initiative hope that vendors will support all element of ebXML
2. Company A create Collaboration Protocol Profile (CPP) - CPP will contain necessary information for potential partner to determine the business role in which Company A interest.
   - necessary information such as protocol type that are available to engage for the role.
   
3. Register CPP in ebXML registry.
4. Company B look at CPP that Company A had registered to see the compatible.
   
5. Company B negotiate a Collaboration Protocol Agreement (CPA) automatically for start the business process.
   
6. Companies begin to send business messages and start their transaction which involve business message conforming to further ebXML.
   - ebXML will have helped in agreeing to monitoring and verifying these real would activities.