Thursday, May 21, 2009

The technical architecture consists of several pieces:

Messaging: ebXML uses SOAP to send messages.

Business processes: ebXML distinguishes itself from other XML frameworks through its emphasis on business processes. Modeling languages and charting tools such as the Unified Modeling Language (UML) are used to standardize and capture the flow of business data among trading partners.

Trading partner profiles and agreements: ebXML defines an XML-based Collaboration Protocol Profile (CPP) to list supported industries, business processes, messages, and data-exchange technologies.

Registries and repositories: Registries contain the industry processes, messages, and vocabularies that define the transactions that occur between trading partners.

Core components: Core components operate at the data level to provide interoperability among industries and identify the data items that businesses use most often across industries, assigning them neutral names and unique identifiers.

ZwiftBooks and ebXML


ZwiftBooks uses ebXML to define a process for doing business.


Figure 5.6, ZwiftBooks first reviews the contents of an ebXML registry to determine the requirements for an ebXML implementation appropriate for the publishing industry. Having determined the appropriateness of relevant ebXML transaction definitions, ZwiftBooks decides to buy rather than internally generate the software needed to support the anticipated ebXML transactions.



No comments:

Post a Comment