Achieving Sustainable Business Benefits with Web Services Standards

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

2. Patrick J. Gannon • OASIS – C.E.O., President, Board Director • UNECE – Chair, Team of Specialists for Internet Enterprise Development (2000-2002) • BEA Systems – Sr. VP Strategic Marketing • Netfish Technologies – VP Industry Standards • Open Buying on the Internet (OBI) – Exec. Dir. • RosettaNet – First Project Leader (1998) • CommerceNet – VP Strategic Programs • XML eCommerce Evangelist (1997-99) • Interoperable Catalog WG (1995-1998) • PIDX, CIAG, PVF Roundtable, CIMIS (1988-95) © OASIS 2003

3. Agenda • Technology Trends • Business Benefits • Issues Impacting Web Services • Value Proposition for Standards • OASIS Role in Standards Adoption © OASIS 2003

4. Information Technology Trends Technology & Business © OASIS 2003

5. The eBusiness Tidal Wave Cultural Shift Business-to-Business Processes Supply Chain Distribution Consumer Services Internet Based Delivery © OASIS 2003

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

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

8. Keep it from being marginalized… © OASIS 2003

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

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

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

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

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

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

15. 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. © OASIS 2003

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

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

18. Web Services Definition 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 © OASIS 2003 © W3C 2002.

19. Web Services Issues © OASIS 2003

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

21. Issues Impacting Web Services for the Global Business Market • Moving proprietary WS specifications through an open standards process • Core specifications (SOAP, WSDL) at W3C • Infrastructure specifications (security, management, business process, etc.) at OASIS • Coordinating and demonstrating related infrastructure standards • Adapting industry business vocabularies and business scenarios to WS framework © OASIS 2003

22. Value Proposition for Open Standards © OASIS 2003

23. Formula for Sustainable Standards Traction XML W3C SOAP v1.1 SOAP v1.2 W3C ebMSG v2 OASIS Market Adoption WSDL v1.1 WSDL v1.2 W3C eb Reg v2 OASIS UDDI v2,3 UDDI.org UDDI v2,3 OASIS SGML ISO Proprietary JCV Consortia SDO Sanction Open Standardization © OASIS 2003

24. Why Are Software Standards Important? Compatibility Extensibility Predictability Interoperability Rapid Development Leverage Existing Skills © OASIS 2003

25. Why Do Vendors Comply? • Deliver customer value • Faster customization • Easier integration with other customer applications • Secure broader adoption of technology • More developers means broader deployment • More companies can easily build applications • Gain competitive edge • Leadership role in the formulation of standards • Larger developer community grows adoption © OASIS 2003

26. How Can Users Influence Vendors? • Examine and understand standards that are pertinent to your industry • Participate in standards bodies that relate to your business practices • Help vendors understand the importance of your requirements for interoperability • Help vendors understand what standards you rely upon today and in the future … and why • Do not purchase products from vendors who do not support the standards you need © OASIS 2003

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

28. 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.” © OASIS 2003

29. What Should an Open Standards Process Provide? • Opportunity to pursue technical work in a neutral environment – level playing field • Balanced participation by technology vendors, end users & governmental agencies • Opportunity to set the technical agenda – member driven • Active support from relevant industry associations • Visibility and sanction by an internationally recognized standards body © OASIS 2003

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

31. United Nations Center for Trade Facilitation and Electronic Business Developers of EDIFACT One of four organizations in the world that can set de jure standards World’s largest independent, non-profit organization dedicated to the standardization of XML applications More than 600 members © OASIS 2003

32. ebXML Industry Adoption • Automotive (AIAG) • Computers, Electronic Components (RosettaNet) • Construction • e-Government • Financial Services (SWIFT) • Healthcare (HL7) • Human Resources (HR-XML) • Insurance (ACORD) • Law Enforcement • Petroleum - Oil & Gas (PIDX) • Pulp, Paper, Printing & Publishing • Steel • Telecommunications • Trading Networks • Transportation – Aerospace, Shipping • Travel – Airlines © OASIS 2003

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

34. Interoperability activities Architecture Guidelines XML / ebXML / Web Services Interoperability Framework for pan-European e-government services BusinessModels © OASIS 2003

35. Business Models ebXML Web Services Generic B2B data exchange Generic B2B data exchange XML / SOAP XML / SOAP Parallel Merge or Parallel development? Highly regulated B2B Not highly regulated B2B © OASIS 2003

36. Electronic Business Technologies © OASIS 2003

37. OASIS Role in Standards Adoption © OASIS 2003

38. OASIS drives the development, convergence and adoption of e-business standards. © OASIS 2003

39. OASIS Relationships • Attempt to cooperate and liaise with other standards organizations as much as possible • Avoid duplication, promote interoperability • Gain sanction/authority for OASIS work • Formal working relationships with: • W3C, OMG, IDEAlliance, RosettaNet, CommerceNet • ACORD, HL7, LISA, SWIFT, VCA, UCC, ONCE, etc. • ISO/IEC JTC SC34, ISO TC154 (Cat. A Liaison) • ITU-T A.4 and A.5 Recognition • ISO, IEC, ITU, UN-ECE Memorandum of Understanding (MoU) for E-Business © OASIS 2003

40. Balanced Member Representation © OASIS 2003

41. Conceptual Model for Standards Transaction Instance Vertical Industry Transaction Patterns Specialized Content Specialized Processes Generalized Content Generalized Processes Content Definition Language Process Description Language Registry / Directory 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 S e c u r i t y M a n a g e m e n t Quality of Services XML and WS Repository Presentation Description Service Description Language Messaging XML Syntax Transport © OASIS 2003 Network

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

43. OASIS TCs: Vertical • Automotive Repair Information • Controlled Trade • Docbook • Education XML • e-Government • e-Procurement Standardization • Election and Voter Services • Emergency Management • Human Markup • Tax XML © OASIS 2003

44. OASIS TCs: Vertical (cont.) • LegalXML • Court Filing • eContracts • eNotarization • Integrated Justice • Lawful Intercept • Legislative Information • Online Dispute Resolution (ODR) • Transcripts © OASIS 2003

45. OASIS TCs: Vertical (cont.) • Generalized Content Definition • Customer Information Quality (CIQ) • Open Office XML • Generalized Processes • ebXML CPPA • Localization Interchange Format (XLIFF) • Provisioning Services (SPML) • Translation Web Services • Content Assembly Mechanism (CAM) © OASIS 2003

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

47. OASIS TCs: XML and Web Services • Registries, Repositories, and Directories • Directory Services (DSML) • ebXML Registry • UDDI Specification • Messaging • ebXML Messaging • Web Services Reliable Messaging • Content Definition Language • Universal Business Language (UBL) © OASIS 2003

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

49. OASIS TCs: XML and Web Services (cont.) • Process Description Language • Business Transaction Protocol (BTP) • Web Services Business Process Execution Language (WSBPEL) • Presentation Description • User Interface (UIML) • Web Services for Interactive Applications (WSIA) • Web Services Remote Portal (WSRP) • Management • Management Protocol • Web Services Distributed Management (WSDM) © OASIS 2003

50. OASIS Value • Sanctionx Traction = Adoption • Ten years demonstrated success • Neutral and independent • Technical and procedural competence • Worldwide visibility and outreach • Close coordination with peer standards organizations on a global level • Relevance, Openness, Implement-ability © OASIS 2003