OASIS Week of ebXML Standards Webinars

June 4 – June 7, 2007

ebXML origin and context UN/CEFACT

United Nations Centre for Trade Facilitation and Electronic Business

Created and maintains the UN/EDIFACT standards for Electronic Data Interchange (EDI)

1998/1999 analysis on EDI use

OASIS Organization for Advancement of

Structured Information Standards Consortium hosting XML and related

standards work

ebXML initiative, then.. Phase 1, joint initiative by OASIS and UN/CEFACT

9/1999 open invitation to e-business community to join 18 month project from 11/1999 to 5/2001; specifications delivered, on time

Vision: “Create a single global electronic marketplace where enterprises

of any size and in any geographical location can meet and conduct business with each other”

Provide a “modular, yet complete electronic business framework” Approach

Semantic and Technical interoperability Modular framework leveraging EDI, XML, Internet, Web

technologies

ebXML standards today.. ebXML Messaging (ebMS)

Secure, Reliable messaging, binding to CPA Version 2 certified interoperable messaging since 2002

Collaboration Protocols Agreements (CPA) Bilateral message service and partner configuration Binding to the ebXML Messaging Service (ebMS)

Business Process (ebBP) Support for complex business interactions Choreography (public process) Binding to message protocols via CPA

Registry Information Model and Services

Core Components Information model for vocabularies and business documents

Speakers Dale Moberg, Axway (TC Chair) Sacha Schlegel (TC Member)

Thursday, June 7

OASIS ebXML Collaboration Protocol Profile and Agreement (ebCPPA) v3.0

Overview Architectural Context and Function User Value

Registries/Repositories

CoreComponents

CoreComponents

BusinessDocumentsBusiness

Documents

CP AgreementCP Agreement

Des

ign

Tim

e BusinessProcess

BusinessProcess

CollaborationProtocolProfile

CollaborationProtocolProfile

CollaborationProtocolProfile

CollaborationProtocolProfile

Transport

Package

BusinessService

Interface

BusinessServices/App’s

Ru

nti

me Business

ServiceInterface

BusinessServices/App’s

XML based: XMI, Specification Schema, Document Schemas

Register & Discover

CPA Glues the Business Process’s Business Transactions to DeliveryChannels

Assigns Parties to BP Roles & Connects PKI for Party Identities

Maps BusinessCollaborations to ebMS Services, and BusinessTransactionActivities to Actions.

Supply metadata values for agreed delivery channel parameters and features of MSHs.

Map BP QOS to technologies and parameters. Enumerate options for transfer, security,

reliability, and document envelope details

End User Values Rapid collaboration community ramp up and

lifecycle management. Incremental CPP or CPA templates possible.

Delivery Channels define IT allowed ways for partners to collaborate

Common format enables different vendors to interoperate; end users can migrate collaboration information if needed

Templates can constrain choices. Supports collaboratin community portal designs.

CPP and Negotiation for Advanced Peer to Peer community designs.

Design Choices Delivery channel features are static and fixed

between participants. Some features can be “dynamic” (per message), but most are agreed upon and provide a service agreement for the BP specified contract.

Offloads much metadata from being carried in message.

Preferences and negotiation allowed. Variety of ways to implement formation of CPAs,

from web forms for template editing to automated process involving negotiation.

Version 2.0 Deployed for ebMS 2 Configuration

But v 2.0 omitted an extensible approach to cover other Messaging Protocols, Business Process Descriptions, and Channel features.

V 2.0 also omitted detailed specifications for standardization of aspects of the formation of CPAs from CPPs and CPA templates.

Roll up of approved errata and additions. Extensibility model adopted using substitution

groups. Applies to collaboration protocols other than

ebMS 2.0. Including EDIINT, ebMS 3.0, WS (WSDL and WS-Policy), BPSS 2.0, RNIF 2.0, MMS-AS2, MMS-ebMS, MMS-WSI.

Portal technology for CPA template edits producing a CPA based community (in progress)

Start at support of libraries for message sets, such as UBL SBS. Example by Sacha Schlegel follows.

Collaboration Community Ramp Up and Libraries

CPPA Collaboration Community Support Today we often find static business

collaborations. Business have long and real-world relationships with their trading partners.

When they move their information exchange to the ebusiness world then the ebXML CPPA provides a good way to handle the necessary technical information between these relationships.

Relation to Negotiation Dynamic, ad-hoc, and spontaneous

electronic commerce is the future. The ebXML CPPA provides guidance with

“the Automated negotiation of Collaboration Protocol Agreements” work.

But more important is to solve today's problem.

ebXML CPPA for UBL SBS

The Universal Business Language (UBL) 1.0 Small Business Subset (SBS) provides a set of basic business processes.

The business processes were used to generate ebXML Collaboration Protocol Agreement 'building blocks'.

Technical details were left to be filled out by the trading partners.

Other Aspects of Configuration The components of the business process

(such as ebXML Business Process) are independent of the technical details and can be generated in advance.

The ebXML IIC deployment profile for CPA can be used by a community to profile the technical details.

Illustrations and Examples Imagine a library (could be in the

ebXML Registry Repository, of course) that we browse.