OASIS Week of ebXML Standards Webinars June 4 – June 7, 2007

ebXML origin and context n UN/CEFACT l United Nations Centre for Trade Facilitation and Electronic Business l Created and maintains the UN/EDIFACT standards for Electronic Data Interchange (EDI) l 1998/1999 analysis on EDI use n OASIS l Organization for Advancement of Structured Information Standards l Consortium hosting XML and related standards work

ebXML initiative, then.. n Phase 1, joint initiative by OASIS and UN/CEFACT l 9/1999 open invitation to e-business community to join l 18 month project from 11/1999 to 5/2001; l specifications delivered, on time n Vision: l “Create a single global electronic marketplace where enterprises of any size and in any geographical location can meet and conduct business with each other” l Provide a “modular, yet complete electronic business framework” n Approach l Semantic and Technical interoperability l Modular framework leveraging EDI, XML, Internet, Web technologies

ebXML standards today.. n ebXML Messaging (ebMS) l Secure, Reliable messaging, binding to CPA l Version 2 certified interoperable messaging since 2002 n Collaboration Protocols Agreements (CPA) l Bilateral message service and partner configuration l Binding to the ebXML Messaging Service (ebMS) n Business Process (ebBP) l Support for complex business interactions l Choreography (public process) l Binding to message protocols via CPA n Registry l Information Model and Services n Core Components l Information model for vocabularies and business documents

n Speakers l Dale Moberg, Axway (TC Chair) l Sacha Schlegel (TC Member) Thursday, June 7 OASIS ebXML Collaboration Protocol Profile and Agreement (ebCPPA) v3.0

Overview n Architectural Context and Function n User Value

Registries/ Repositories Core Components Business Documents CP Agreement Design Time Business Process Collaboration Protocol Profile Transport Package Business Service Interface Business Services/App’s Runtime Business Service Interface Business Services/App’s XML based: XMI, Specification Schema, Document Schemas Register & Discover

CPA Glues the Business Process’s Business Transactions to DeliveryChannels n Assigns Parties to BP Roles & Connects PKI for Party Identities n Maps BusinessCollaborations to ebMS Services, and BusinessTransactionActivities to Actions. n Supply metadata values for agreed delivery channel parameters and features of MSHs. n Map BP QOS to technologies and parameters. n Enumerate options for transfer, security, reliability, and document envelope details

End User Values n Rapid collaboration community ramp up and lifecycle management. Incremental CPP or CPA templates possible. n Delivery Channels define IT allowed ways for partners to collaborate n Common format enables different vendors to interoperate; end users can migrate collaboration information if needed n Templates can constrain choices. Supports collaboratin community portal designs. n CPP and Negotiation for Advanced Peer to Peer community designs.

Design Choices n 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. n Offloads much metadata from being carried in message. n Preferences and negotiation allowed. n 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 n But v 2.0 omitted an extensible approach to cover other Messaging Protocols, Business Process Descriptions, and Channel features. n V 2.0 also omitted detailed specifications for standardization of aspects of the formation of CPAs from CPPs and CPA templates.

n Roll up of approved errata and additions. n Extensibility model adopted using substitution groups. n 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. n Portal technology for CPA template edits producing a CPA based community (in progress) n 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 n Today we often find static business collaborations. Business have long and real-world relationships with their trading partners. n 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 n Dynamic, ad-hoc, and spontaneous electronic commerce is the future. n n The ebXML CPPA provides guidance with “the Automated negotiation of Collaboration Protocol Agreements” work. n But more important is to solve today's problem.

ebXML CPPA for UBL SBS n The Universal Business Language (UBL) 1.0 Small Business Subset (SBS) provides a set of basic business processes. n The business processes were used to generate ebXML Collaboration Protocol Agreement 'building blocks'. n Technical details were left to be filled out by the trading partners.

Other Aspects of Configuration n The components of the business process (such as ebXML Business Process) are independent of the technical details and can be generated in advance. n The ebXML IIC deployment profile for CPA can be used by a community to profile the technical details.

Illustrations and Examples n Imagine a library (could be in the ebXML Registry Repository, of course) that we browse.