1. © OASIS 2003 Achieving Sustainable Business Benefits with Web Services Standards Patrick Gannon President & CEO eGovernment & Web Services Moscow 21 July 2003

2. oasis-open.org © OASIS 2003 Patrick J. Gannon zOASIS – C.E.O., President, Board Director zUNECE – Chair, Team of Specialists for Internet Enterprise Development (2000-2002) zBEA Systems – Sr. VP Strategic Marketing zNetfish Technologies – VP Industry Standards zOpen Buying on the Internet (OBI) – Exec. Dir. zRosettaNet – First Project Leader (1998) zCommerceNet – VP Strategic Programs yXML eCommerce Evangelist (1997-99) yInteroperable Catalog WG (1995-1998) zPIDX, CIAG, PVF Roundtable, CIMIS (1988-95)

3. oasis-open.org © OASIS 2003 Agenda zTechnology Trends zBusiness Benefits zIssues Impacting Web Services zValue Proposition for Standards zOASIS Role in Standards Adoption

4. © OASIS 2003 Information Technology Trends Technology & Business

5. oasis-open.org © OASIS 2003 Consumer Services Supply Chain Distribution Internet Based Delivery Business-to-BusinessProcesses The eBusiness Tidal Wave

6. oasis-open.org © OASIS 2003 B2C Integration Directory Services XML Web Services Sales and Distribution B2B iMarketPlaces / Hubs ASP’s (App’ Srvc Provider) Information Mining The eBusiness Technologies

7. oasis-open.org © OASIS 2003 The Challenge: How to Take an Architecture That Has Withstood the Test of Time…

8. oasis-open.org © OASIS 2003 Keep it from being marginalized…

9. oasis-open.org © OASIS 2003 Keep it from being washed away in the technology tidal wave …

10. oasis-open.org © OASIS 2003 And turn it into the centerpiece of a thriving marketplace …

11. © OASIS 2003 Business Benefits from a Service Oriented Architecture

12. oasis-open.org © OASIS 2003 The Dawn of a New Era Built on Service Oriented Architecture

13. oasis-open.org © OASIS 2003 Vision of a Service-Oriented Architecture zA place where services are ubiquitous and organically integrated into the way we think and work. zA place where both users and providers of information interact through a common focus on services. zA world where technology is implemented within industry frameworks that operate on a global scale, enabled by open, interoperable standards.

14. oasis-open.org © OASIS 2003 A Common Web Service Framework Is Essential z To provide a sustainable foundation, z That will allow end-user companies to achieve the payback they require, z To invest widely in the service- oriented architecture.

15. oasis-open.org © OASIS 2003 Achieving Sustainable Business Benefits through a Common Web Service Framework In this post-dot-com era, end user companies are expecting more liquidity and longevity of their assets. To achieve the ROI, Cost Reduction and Service Expansion benefits expected; the widespread deployment of standards-based Web services is essential.

16. © OASIS 2003 What is a Web Service? Architectural Definition Core Protocols

17. oasis-open.org © OASIS 2003 Some Days Its Hard to Know Which Way is Up or Down

18. oasis-open.org © OASIS 2003 A Web service is a software application identified by a URI, whose interfaces and bindings are capable of being defined, described and discovered as XML artifacts. A Web service supports direct interactions with other software agents using XML- based messages via Internet-based protocols. --W3C Web Services Architecture Working Group © W3C 2002. Web Services Definition

19. © OASIS 2003 Web Services Issues

20. oasis-open.org © OASIS 2003 Fundamental Issues that Must Be Addressed 1.A common framework for Web service interactions based on open standards must occur. 2.An agreed set of vocabularies and interactions for specific industries or common functions must be adopted.

21. oasis-open.org © OASIS 2003 “for this service-oriented scenario to happen, there needs to be standardization of the types of messages and data exchanges” Douglas Barry Web Services and Service-Oriented Architectures - The Savvy Manager ’ s Guide

22. oasis-open.org © OASIS 2003 Greatest Concern Preventing Adoption of Web services “There's a sordid history in the technology world of everybody trying to get a little leverage over somebody else by developing proprietary extensions or vendor-specific add-ons to the core technology. In general, those have been bad, because they don't end up being sustainable over time and that costs companies like us a lot of money.” CIO of a Fortune 100 corporation

23. oasis-open.org © OASIS 2003 Issues Impacting Web Services for the Global Business Market zMoving proprietary WS specifications through an open standards process yCore specifications (SOAP, WSDL) at W3C yInfrastructure specifications (security, management, business process, etc.) at OASIS zCoordinating and demonstrating related infrastructure standards zAdapting industry business vocabularies and business scenarios to WS framework

24. © OASIS 2003 Value Proposition for Open Standards

25. oasis-open.org © OASIS 2003 Formula for Sustainable Standards Market Adoption Open Standardization Traction Sanction ProprietaryJCVConsortiaSDO SGML ISO XML W3C SOAP v1.1 SOAP v1.2 W3C UDDI v2,3 UDDI.org WSDL v1.2 W3C ebMSG v2 OASIS WSDL v1.1 UDDI v2,3 OASIS eb Reg v2 OASIS

26. oasis-open.org © OASIS 2003 Why Are Software Standards Important?CompatibilityExtensibility Predictability Interoperability Leverage Existing Skills Rapid Development

27. oasis-open.org © OASIS 2003 Why Do Vendors Comply? zDeliver customer value yFaster customization yEasier integration with other customer applications zSecure broader adoption of technology yMore developers means broader deployment yMore companies can easily build applications zGain competitive edge yLeadership role in the formulation of standards yLarger developer community grows adoption

28. oasis-open.org © OASIS 2003 What Does It Take for Software Vendors? zActive participation in standards bodies zDrive standards development to further industry, interoperability, adoption zAnalysis of standards in software development zBalance of innovation with standards support zFocus on compliance & interoperability testing

29. oasis-open.org © OASIS 2003 So Why Don’t Vendors Always Support Standards? zToo easy to “do your own thing” yQuickness to delivery, shortcuts available zLock-in customers to proprietary solutions yIntegration with other systems means more consulting zLack of top-level priority ySupporting multiple standards requires specific expertise and resource commitment zCompliance not always possible yMany standards do not have compliance testing

30. oasis-open.org © OASIS 2003 How Can Users Influence Vendors? zExamine and understand standards that are pertinent to your industry zParticipate in standards bodies that relate to your business practices zHelp vendors understand the importance of your requirements for interoperability zHelp vendors understand what standards you rely upon today and in the future … and why zDo not purchase products from vendors who do not support the standards you need

31. oasis-open.org © OASIS 2003 Delphi Group Research on the Value of Open Software Standards zGreatest benefit to support open standards 1.Increases the value of existing and future investments in information systems 2.Provides greater software re-usability 3.Enables greater data portability zFactors driving participation in standards 1.Vendor neutral environment 2.Access to a community of developers 3.Membership comprised of both end-users and software developers

32. oasis-open.org © OASIS 2003 Delphi Group Research on the Value of Open Software Standards “Compliance with standards in software development is not simply a strategic direction, but a business imperative.” “Even those who took a very practical approach and stated that standards might slow down their efforts initially, agreed that in the long run the presence of a standard represented a much more secure investment.”

33. oasis-open.org © OASIS 2003 What Should an Open Standards Process Provide? zOpportunity to pursue technical work in a neutral environment – level playing field zBalanced participation by technology vendors, end users & governmental agencies zOpportunity to set the technical agenda – member driven zActive support from relevant industry associations zVisibility and sanction by an internationally recognized standards body

34. © OASIS 2003 ebXML Electronic Business using eXtensible Markup Language The Global Standard for Electronic Business Achieving International Support & Adoption

35. oasis-open.org © OASIS 2003 zUnited Nations Center for Trade Facilitation and Electronic Business zDevelopers of EDIFACT zOne of four organizations in the world that can set de jure standards zWorld’s largest independent, non- profit organization dedicated to the standardization of XML applications zMore than 600 members

36. oasis-open.org © OASIS 2003 ebXML Industry Adoption zAutomotive (AIAG) zComputers, Electronic Components (RosettaNet) zConstruction ze-Government zFinancial Services (SWIFT) zHealthcare (HL7) zHuman Resources (HR-XML) zInsurance (ACORD) zLaw Enforcement zPetroleum - Oil & Gas (PIDX) zPulp, Paper, Printing & Publishing zSteel zTelecommunications zTrading Networks zTransportation – Aerospace, Shipping zTravel – Airlines

37. © OASIS 2003 IDA Interchange of Data between Administrations XML Europe 2003 5 th May, London Paul E Murphy IDA, Enterprise Directorate General European Commission

38. oasis-open.org © OASIS 2003 Interoperability activities Architecture Guidelines Interoperability Framework for pan-European e-government services Business Models XML / ebXML / Web Services

39. oasis-open.org © OASIS 2003 Business Models ebXMLWeb Services Generic B2B data exchange Generic B2B data exchange XML / SOAP Highly regulated B2B Not highly regulated B2B Merge or Parallel development? Parallel

40. oasis-open.org © OASIS 2003 Electronic Business Technologies

41. © OASIS 2003 OASIS Role in Standards Adoption

42. oasis-open.org © OASIS 2003 OASIS drives the development, convergence and adoption of e-business standards. of e-business standards.

43. oasis-open.org © OASIS 2003 OASIS Relationships zAttempt to cooperate and liaise with other standards organizations as much as possible yAvoid duplication, promote interoperability yGain sanction/authority for OASIS work zFormal working relationships with: yW3C, OMG, IDEAlliance, RosettaNet, CommerceNet yACORD, HL7, LISA, SWIFT, VCA, UCC, ONCE, etc. yISO/IEC JTC SC34, ISO TC154 (Cat. A Liaison) yITU-T A.4 and A.5 Recognition yISO, IEC, ITU, UN-ECE Memorandum of Understanding (MoU) for E-Business

44. oasis-open.org © OASIS 2003 Balanced Member Representation

45. oasis-open.org © OASIS 2003 Quality of Services Conceptual Model for Standards M a n a g e m e n tS e c u r i t y XML Syntax Network Transport Vertical Industry XML and WS Generalized Processes Specialized Processes Generalized Content Specialized Content Messaging Service Description Language Presentation Description Transaction Patterns Transaction Instance Repository Registry / Directory Process Description Language Content Definition Language C o n f o r m a n c e / I n t e r o p e r a b I l I t y

46. oasis-open.org © OASIS 2003 Quality of Services Conceptual Model For OASIS Management S e c u r i t y XML Syntax Network Transport Vertical Industry Area Generalized Processes Specialized Processes Generalized Content Specialized Content Messaging Service Description Language Presentation Description Transaction Patterns Transaction Instance Repository Registry / Directory Process Description Language Content Definition Language Conformance and Interoperability

47. oasis-open.org © OASIS 2003 OASIS TCs: Vertical zAutomotive Repair Information z Controlled Trade z Docbook z Education XML z e-Government z e-Procurement Standardization z Election and Voter Services z Emergency Management z Human Markup z Tax XML

48. oasis-open.org © OASIS 2003 OASIS TCs: Vertical (cont.) zLegalXML y Court Filing y eContracts y eNotarization y Integrated Justice y Lawful Intercept y Legislative Information y Online Dispute Resolution (ODR) y Transcripts

49. oasis-open.org © OASIS 2003 OASIS TCs: Vertical (cont.) zGeneralized Content Definition yCustomer Information Quality (CIQ) yOpen Office XML zGeneralized Processes yebXML CPPA yLocalization Interchange Format (XLIFF) yProvisioning Services (SPML) yTranslation Web Services yContent Assembly Mechanism (CAM)

50. oasis-open.org © OASIS 2003 Quality of Services Conceptual Model For OASIS Management S e c u r i t y XML Syntax Network Transport XML and Web Services Area Generalized Processes Specialized Processes Generalized Content Specialized Content Messaging Service Description Language Presentation Description Transaction Patterns Transaction Instance Repository Registry / Directory Process Description Language Content Definition Language Conformance and Interoperability

51. oasis-open.org © OASIS 2003 OASIS TCs: XML and Web Services zRegistries, Repositories, and Directories yDirectory Services (DSML) yebXML Registry yUDDI Specification zMessaging yebXML Messaging yWeb Services Reliable Messaging zContent Definition Language yUniversal Business Language (UBL)

52. oasis-open.org © OASIS 2003 OASIS TCs: XML and Web Services (cont.) z XML Syntax y Entity Resolution y RELAX NG y Topic Maps Published Subjects y Topic Maps PS Geography /Languages y Topic Maps PS XML Standards Vocabulary

53. oasis-open.org © OASIS 2003 OASIS TCs: XML and Web Services (cont.) z Security y Access Control (XACML) y Application Vulnerability Description Lang. (AVDL) y Common Biometric Format (XCBF) y Digital Signature Services (DSS) y Extensible Resource Identifier (XRI) y Provisioning Services (SPML) y Public Key Infrastructure (PKI) y Rights Language (RLTC) y Security Services (SAML) y Web Application Security (WAS) y Web Services Security (WSS)

54. oasis-open.org © OASIS 2003 OASIS TCs: XML and Web Services (cont.) z Process Description Language y Business Transaction Protocol (BTP) y Web Services Business Process Execution Language (WSBPEL) z Presentation Description y User Interface (UIML) y Web Services for Interactive Applications (WSIA) y Web Services Remote Portal (WSRP) z Management yManagement Protocol yWeb Services Distributed Management (WSDM)

55. oasis-open.org © OASIS 2003 OASIS Member Sections zA group of technical committees or OASIS members, with its own identify and governance zLegalXML zUDDI zPublic Key Infrastructure (PKI) zAuto Repair Information

56. oasis-open.org © OASIS 2003 OASIS Value zSanction x Traction = Adoption zTen years demonstrated success zNeutral and independent zTechnical and procedural competence zWorldwide visibility and outreach zClose coordination with peer standards organizations on a global level zRelevance, Openness, Implement-ability

57. oasis-open.org © OASIS 2003 Thinking is easy, acting is difficult, and to put one's thoughts into action is the most difficult thing in the world. Johann Wolfgang Von Goethe ” “

58. zwww.xml.orgzwww.xml.coverpages.org zwww.oasis-open.org patrick.gannon@oasis-open.org