1. B2B e-commerce standards for document exchange In350: week 13: Nov. 19,2001 Judith A. Molka-Danielsen

2. Document Exchange and e-commerce Companies need to exchange data with business partners to conduct business. Many B2B processes have automated application programs running at both ends. EDI was the first data exchange standard for this running over private VANs. EDI was developed by United Nations Electronic Data Interchange for Administration, Commerce and Transport (UN/EDIFACT) group, 25 years ago.

3. Problems with EDI It was expensive, only for big businesses. High infrastructure setup and running costs. Imposed proprietary integration approaches on trading partners. SME could not set up add hoc trading agreements. Changes can occur: adoption of Internet technologies, and use of XML as a data exchange format.

4. What XML doesn’t do XML provides a notation for developing tags. But if every business develops its own tags, there is not interoperability. We need the following: Common standard vocabulary between partners Common message exchange sequences between trading partners Security and acknowledgment of correct message exchange

5. B2B interoperability standards Description of message formats exchanged (purchase orders) Binding to transport protocols (http) Sequencing (after sending a purchase order an acknowledgement must be received) Business Process (tie it to real life, after a purchase order is accepted the goods must be delivered to the buyer) Security (encryption, authentication, non- repudiation)

6. Standards for B2B e-commerce XML Common Business Library (xCBL) – for common tagging in industries, used with DTDs Business forms, catalogs, purchas orders, invoices Standard measures, date, time, location, etc. Simple Object Access Protocol (SOAP) – an XML based RPC mechanism for invoking methods, binding. Envelop – what is in message and how to process Encoding rules – express instances of application defined datatypes Convention – for representing RPCs (calls and responses) Web Service Description Language (WSDL) – can share interface descriptions. Info on data being exchanged, sequence of messages, locations of the service and the description of the bindings (ie. SOAP).

7. E-commerce frameworks CommerceNet’s eCo architecture – interoperability framework. Businesses agree on a common method of describing what they do. Architectural specification – info about the e- commerce system in layers. Networks Markets Buinesses Services Interactions Documents Information items Semantic specification – sample set of business docs. xCBL can be used at the Doc and item layers.

8. E-commerce frameworks RosettaNet (1998) is an independent, non-profit consortium to develop XML based standard e- commerce interfaces, to align processes between supply chain partners on a global basis. It uses Partner Interface Processes (PIPs) and PIP Development Methodology RosettaNet Business Dictionary, RosettaNet Technical Dictionary RosettaNet Implementation Framework (Networked Application Architecture) Members are IBM, Microsoft, EDS, Netscape, Oracle, SAP, Cisco systems, Compaq and Intel.

9. E-commerce frameworks Electronic Business XML (ebXML) by OASIS and United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT). Vision is to create a single global electronic marketplace, for businesses of any size, from any location. The architecture has: Registory/repository, uses a ebXML Core Library (core components for documents), repository has defined business processes, registory has set of services that manage the repository and enable sharing of information between partners. Business Process Specification Schema (BPSS),(On how partners take roles, responsibilities, and the interaction of roles as a choreographed set of business transactions.)(written in a DTD or Schema) ebXML Collaboration Protocol Profile (CPP) and Agreement (CPA) agreement of trading partner informations.

10. UDDI(Universal Description, Discovery, Integration) UDDI by IBM, Microsoft and Ariba. More than 175 companies (HP, Boeing,Ford, CommerceOne, Sun Microsystems) agree to support it in the furture. Is a registory architecture to build a registory and interact over the Internet. Registory has white pages, yellow pages (on business info) and green pages (on technical info on services). Defines 5 core types through XML schemas: buisness, service, binding, services specifications information, and relationship info between two parties.

11. BizTalk BizTalk is an XML based application integration framework. Contains a technical specification, a set of XML documents, BizTalk Web portal, BizTalk 2000 Server. BizTalk Web portal has XML schemas suggested by businesses and a globally accessible document library. Schemas are validated, versioned, regisitered in a repository at the web portal site. Partners can choose to conform, to use what is there. Can download ”eShop Offers” schema from BizTalk.org and build an application that uses it. BizTalk 2000 Server – by Microsoft, Orchestration service and Messaging service. Support distributed business models between orgs.Uses gui Visio, generate process definition in XLANG. XLANG provides workflow defintion features (sequence, branch, transaction support, persistance, monitor)

12. Comparing Frameworks Registory/Repository Support Electronic Catalog Support Business Process Support Messaging Protocols Security Other issues: how do we live with multiple frameworks? Are there any commercial off-the-shelf products for implementing specifications?