1. Copyright OASIS, 2002 Challenges and Successes in Interoperability Scott McGrath OASIS

2. Copyright OASIS, 2002 Greatest challenges to interoperability Too many, incompatible industry vocabularies or specifications No broad, industry-wide input to and support for specifications JCV “standards” or vendor-proprietary implementations and extensions Those using the spec don’t have input

3. Copyright OASIS, 2002 Who makes Standards: Consortia vs SDO Domain Experts Market awareness Fast development Uncertain process JCV limits & confusion Evolving/ unenforceable standards Recognized process Thorough process Lack speed to market Uncertain market relevance Permanent/ enforceable standards

4. Copyright OASIS, 2002 Highest Value= Lowest Development Cost Widest Implementation Greatest Interoperability Lowest Value= Conflicting non-Standards Expensive Implementations & Use Proprietary Designs Market Traction Formal Sanction Standards Value:

5. Copyright OASIS, 2002 OASIS Standards: Open and Adopted Market Adoption Open Standardization Traction Sanction ProprietaryJCVConsortia SDO- Gov’t SGML ISO XML W3C SOAP v1.1 SOAP v1.2 W3C UDDI v2 UDDI.org WSDL WG W3C eb MS v2 OASIS eb Reg v2 OASIS WSDL v1.1 Standards:

6. Copyright OASIS, 2002 OASIS- part consortia, part SDO Open member organization Market awareness Very low cost for participation Domain experts Fast process Recognized process Enforceable results OASIS is a Class A Liaison to ISO TC 154, the international standards body for electronic commerce syntax OASIS is a member of the Management Group for the ISO IEC ITU UN/CEFACT Memo of Understanding on Electronic Commerce Standards

7. Copyright OASIS, 2002 The OASIS solution for Interoperability Convergence Coordination Harmonization

8. Copyright OASIS, 2002 Convergence at OASIS AuthXML and S2ML converge in the SAML TC TREX and RELAX converge in the RELAX NG TC WSUI and WSXL converge in the WSIA TC XRPM, ADpr, ITML converge in the PSML TC AND Global Address, MSI NAML converge in the CIQ TC Recent announcement Web Services Security

9. Copyright OASIS, 2002 Dot-orgs have moved to OASIS ADpr Initiative AuthXML.Org ITML.Org LegalXML.org S2ML.Org TopicMaps.org WSUI.Org XRPM Working Group

10. Copyright OASIS, 2002 Vendors have submitted specs to OASIS TCs Work such as – WSXL from IBM – XOCP from BEA Systems – xCBL from Commerce One – ITML from Jamcracker – CRML, others from MSI – XrML from ContentGuard

11. Copyright OASIS, 2002 Coordination European Parliament European Commission Business Registry CTML LegalXML Others– Election & Voter Services, Open Education Standards, etc

12. Copyright OASIS, 2002 European Parliament RFP will require implementations based on open standards Contractor selection will focus on those companies with experience in standards development “We will no longer fund development of proprietary or non-standards based systems. Interoperability must prevail.” Peter Pappamikail

13. Copyright OASIS, 2002 European Commission DG Information Society – Single European Electronic Marketplace Providing funding Providing vision Expects use of ebXML DG Enterprise – Auto Repair Information Response to consumer and aftermarket needs for information Requiring standard format of manufacturers’ information Allowing users and providers to create standard via OASIS TC Process Results will be enforced

14. Copyright OASIS, 2002 Controlled Trade Mark-up Language Sponsored by US Dept of State – Scholarships for emerging economies Government agencies globally Documentation systems providers Controlled goods manufacturers Transportation & logistic experts Localization industry

15. Copyright OASIS, 2002 User community drives LegalXML US Dept of Justice 12 state, county, local agencies Dozens of Individuals These users are driving expectations These users are guiding their technology partners

16. Copyright OASIS, 2002 OASIS leads Harmonization ebXML UBL

17. Copyright OASIS, 2002 ebXML The Global Standard for Electronic Business

18. Copyright OASIS, 2002 ebXML Provides a Standard Way to: Exchange business messages Conduct trading relationships Communicate data in common terms Define and register business processes

19. Copyright OASIS, 2002 ebXML History Begun as 18-month initiative in November 1999 Specifications delivered on schedule in May 2001 Developed in an open process by more than 4500 participants representing 2000 organizations in 150 countries on virtually every continent

20. Copyright OASIS, 2002 What does ebXML do? Lowers the cost/complexity of electronic business Facilitates global trade and puts SMEs and developing nations in the picture Expands electronic business to new and existing trading partners Converges current and emerging XML efforts Eliminates dependence by supporting any language, any payload, any transport

21. Copyright OASIS, 2002 Main ebXML concepts Business Processes – Defined as models, Expressed in XML Business Messages – Expressed in XML Trading Partner Agreement – Specifies parameters for businesses to interface with each other – Expressed in XML Business Service Interface – Implements Trading Partner Agreement – Expressed in XML Transport and Routing Layer – Moves the actual XML data between trading partners Registry/Repository - Provides a “container” for process models, vocabularies, and partner profiles.

22. Copyright OASIS, 2002 Continuing ebXML Work Specifications available at www.ebxml.orgwww.ebxml.org Infrastructure work continuing at OASIS – Messaging- V2.0 OASIS Standard vote now underway. – Collaborative Partner – Interoperability, Implementation, Conformance – Registry & Repository RIM v 2.0 OASIS Standard, 2.1 TC specification RS x2.0 OASIS Standard, v2.1 TC specification Content-related work continuing at UN/CEFACT – Business Process – Core Components

23. Copyright OASIS, 2002 ebXML Implementations highlighted at ebXML Day, May 2002 Open Source ebXML Registry Implementation, CECID U-Hong Kong ebXML Messaging in Insurance, Innovation Process Technology ebXML and IFX, XT-I Pan Asian E-Commerce Alliance's Global e- Trade Platform Based on ebXML, KTNET See OASIS & ebXML web sites for complete list

24. Copyright OASIS, 2002 “ebXML provides a platform on which to build standards... that are developed faster and yet supported by a rich set of software tools.”

25. Copyright OASIS, 2002 “It is clear that ebXML will soon become the standard for all global trade. By implementing ebXML, GCI takes advantage of the excellent work that’s being accomplished to streamline many EDI processes and remove waste and redundancy from supply chains.”

26. Copyright OASIS, 2002 Industry Groups Support ebXML The Open Healthcare Group

27. Copyright OASIS, 2002 UBL Summary UBL is “the real deal” – actual standard XML business schemas –Completes the ebXML stack –Combines the experience of XML and business experts UBL is dedicated to vendor-neutral interoperability –Open process –Unencumbered IP –Cross-industry semantic harmonization UBL can enable the “B2B web” –HTML + HTTP = web publishing –UBL + ebXML = web commerce

28. Copyright OASIS, 2002 UBL- industry interoperability Chemical Mfr C C’s industry partners CIDX Auto Mfr B B’s industry partners OAGIS Electronics Mfr A A’s industry partners RosettaNet

29. Copyright OASIS, 2002 UBL Liaisons ACORD (insurance industry) EIDX (electronics industry) ARTS (retail sales) RosettaNet (information technology) XBRL (accounting) X12 (EDI) UN/EDIFACT (EDI)

30. Copyright OASIS, 2002 Security - A Real Success Story SAML Access Control - XACML Provisioning – PSTC Biometrics Format- XCBF Rights Language XrML Web Services Security

31. Copyright OASIS, 2002 OASIS portals for information sharing XML.org – Open, vendor neutral, portal for sharing real XML developments – Expect a new focus on industry sectors Industry specific pages--compilation of relevant standards, best practices, architecture etc. Content driven by users XML Cover Pages

32. Copyright OASIS, 2002 Future Steps for OASIS Technical Architecture Board Greater convergence More liaisons with more organizations More opportunities for government and vendor partnering in a neutral way

33. Copyright OASIS, 2002 Future steps for you Decide which existing standards are meaningful Expect implementations around these standards Identify and lead development of additional standards in your domain Support development where development is appropriate

34. Copyright OASIS, 2002 More information Scott McGrath – Scott.mcgrath@oasis-open.org Scott.mcgrath@oasis-open.org – 1 978-667-5115 www.oasis-open.org