Description of Model

The model operates as follows:

1. Company A has become aware of an ebXML registry accessible on the Internet.

2. Company A, after reviewing the contents of ebXML registry, decides to build and deploy its own ebXML-compliant application.

   Custom software development is not a necessary prerequisite for ebXML participation. ebXML-compliant applications and components that provide necessary solutions are commercially available and easily found.

3. Company A then submits its own business profile information (including implementation details and reference links) to ebXML registry.

   The business profile submitted to ebXML registry describes the company’s ebXML capabilities and constraints, as well as its supported business scenarios. These business scenarios are XML versions of the B2B Protocols and associated information bundles (for example, a sales tax calculation) in which the company is able to engage. After receiving verification that the format and usage of a business scenario is correct, ebXML registry sends an acknowledgment to Company A.

4. After additional communication is established, Company B accesses, in ebXML registry, the business scenarios supported by Company A.

   If they decide they want to, Company B sends a request to Company A stating they want to engage in a business scenario using ebXML. Company B acquires the necessary ebXML-compliant applications in the same way as Company A.

5. Before starting the scenario, Company B submits a proposed business arrangement directly to Company A’s ebXML-compliant software interface. The proposed business arrangement outlines the mutually agreed-upon business scenarios and specific agreements.

   The business arrangement also contains information pertaining to the messaging requirements for transactions to take place, contingency plans, and security-related requirements. Company A then accepts the business agreement.

6. Company A and B are now ready to engage in eBusiness transactions using ebXML.