Home > Articles

  • Print
  • + Share This
This chapter is from the book

This chapter is from the book

3 Introduction

3.1 Summary

The vision of ebXML is to create a single global electronic marketplace where enterprises of any size and in any geographical location can meet and conduct business with each other through the exchange of XML based messages. ebXML enables anyone, anywhere, to do electronic business with anyone else, however, it is anticipated that compliance with and adoption of the various ebXML components will be incremental, over time.

In order for enterprises to conduct electronic business with each other, they must first discover each other and the products and services they have to offer. They then must determine which business processes and documents are necessary to obtain those products and services. After that, they need to determine how the exchange of information will take place and then agree on contractual terms and conditions. Once all of this is accomplished, they can then exchange information and products/services according to these agreements.

To facilitate this, ebXML provides an infrastructure for data communication interoperability, a semantic framework for commercial interoperability, and a mechanism that allows enterprises to find, establish a relationship, and conduct business with each other.

Data communication interoperability is ensured by a standard message transport mechanism with a well-defined interface, packaging rules, and a predictable delivery model, as well as an interface to handle incoming and outgoing messages at either end.

Commercial interoperability is provided by means of a specification schema for defining business processes and a core components and context model for defining Business Documents. ebXML recommends a methodology and provides a set of worksheets and guidelines for creating those models. A business library (catalog) of business process and information models promotes business efficiency by encouraging reuse of business processes or parts of predefined business processes.

In order for the actual conduct of business to take place, ebXML provides a shared repository where businesses can discover each other's business offering by means of partner profile information, a process for establishing an agreement to do business (Collaboration Protocol Agreement, or CPA), and a shared repository for company profiles, business-process-specifications, and relevant business messages.

3.2 Scope and audience

This document deals with aspects of commercial interoperability, specifically the process by which enterprises can analyze, identify, and define those business processes and business documents necessary for the conduct of electronic business with other enterprises, within the ebXML framework.

The audience for this document will typically comprise representatives of any of a number of different functional areas within an enterprise, including marketing, business development, executive management, procurement, software development, IT, etc.

3.3 Related documents

[ebTA] ebXML Technical Architecture Specification. Version 1.0.4. 16 February 2001. ebXML Technical Architecture Project Team.

UN/CEFACT Modelling Methodology. CEFACT/TMWG/N090R9. February 2001. UN/CEFACT Technical Modeling Working Group.

Information Technologies - Open-EDI Reference Model. ISO/IEC 14662:1997(E). International Organization for Standardization (ISO) and International Electrotechnical Commission (IEC).

[bpWS] ebXML Business Process Analysis Worksheets and Guidelines v1.0. May 11, 2001. ebXML Business Process Project Team.

[bpPROC] ebXML Catalog of Business Processes. Version 1.0. Date May 11, 2001. ebXML Business Process Project Team.

[bpPATT] ebXML Business Process and Simple Negotiation Patterns. Version 1.0, May 11 2001. ebXML Business Process Project Team.

[ebBPSS] ebXML Business Process Specification Schema. Version 1.0 May 11 2001. Context/Meta Model Group of the CC/BP Joint Delivery Team.

[ebCCD&A] ebXML Methodology for the Discovery and Analysis of Core Components. V1.0, May 11 2001. ebXML Core Components Project Team.

[enCNTXT] ebXML The role of context in the re-usability of Core Components and Business Processes ebXML Core Components. Version 1.0, May 11 2001. ebXML Core Components Project Team.

[ebCCDOC] ebXML specification for the application of XML based assembly and context rules. Version 1.0, May 11 2001. ebXML Core Components.

[ebGLOSS] ebXML TA Glossary. Version 1.0, May 11 2001. Technical Architecture Project Team.

[ebRIM] ebXML Registry Information Model. Version 1.0, 11 May 2001. ebXML Registry Project Team.

[ebRS] ebXML Registry Services. Version 1.0, May 11 2001. ebXML Registry Project Team.

[ebCPP] ebXML Collaboration-Protocol Profile and Agreement Specification. Version 1.0, May 11 2001

[secRISK] ebXML Technical Architecture Risk Assessment Report. Version 1.0, May 11 2001

3.4 Document conventions

The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHALL NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this document, are to be interpreted as described in RFC 2119 [Bra97].

When the term Meta Model is used, it refers to the e-Business Process Meta Model as defined in the UN/CEFACT Modeling Methodology .

When the term Specification Schema is used, it refers to the Meta Model and its DTD form as defined in the ebXML Business Process Specification Schema .

  • + Share This
  • 🔖 Save To Your Account