1. Promoting Web services interoperability across platforms, applications and programming languages Overview Presentation September, 2003

2. THE CONTEXT

3. 3  Businesses need to innovate at an ever increasing pace  Success requires broad interoperability  Within an enterprise  Between business partners  Across a heterogeneous set of platforms, applications and programming languages  Internet technologies are assumed, interoperability is required

4. 4 THE CONTEXT  The shift to Web services is underway  An Internet-native distributed computing model based on XML standards has emerged  Early implementations are solving problems today and generating new requirements  The Web services standards stack is increasing in size and complexity to meet these requirements  The fundamental characteristic of Web services is interoperability

5. THE CHALLENGE

6. 6  “[the] architecture of Web services is not fully crystallized. Without guidance, standards may fragment” Gartner Group  “Inevitably, companies involved with Web services will define them in their own way. The term Web services will be a messy catchall phrase.” Intelligent Enterprise  “standards…allow Web services to overcome the barriers of different programming languages, operating systems, and vendor platforms so multiple applications can interact.” eWeek

7. 7 THE OPPORTUNITY HTTP, HTMLXML Web Services Market Impact 199519971999200120032005 WS-I formed

8. 8 WHAT IS NEEDED?  Guidance  A common definition for Web services  Implementation guidance and support for Web services adoption  Interoperability  Across platforms, applications, and languages  Consistent, reliable interoperability between Web services technologies from multiple vendors  A standards integrator to help Web services advance in a structured, coherent manner

9. 9 GOALS  Achieve Web services interoperability  Across platforms, applications and languages  Encourage Web services adoption  Among customers, industries and end users  Accelerate Web services deployment

10. 10 ACHIEVE INTEROPERABILITY  Promote a common, clear definition for Web services  Integrate specifications from various standards bodies  Provide a visible representation of conformance through use of WS-I logo

11. 11 ENCOURAGE ADOPTION  Build industry consensus to reduce early adopter risks  Provide a forum for end users to communicate requirements  Act as a customer advocate to raise awareness of business requirements

12. 12 ACCELERATE DEPLOYMENT  Offer implementation guidance and best practices  Deliver tools and sample applications  Provide a forum for Web services developers to collaborate and share expertise

13. 13 ORGANIZATION  Board of directors  Management and administration body  Ensure the organization and its working groups adhere to their defined scope  Working groups  Develop materials and other deliverables to aid Web services interoperability  Membership  Vote to approve adoption and distribution of any materials developed by the working groups

14. 14 TECHNICAL WORKING GROUPS  Basic Profile  Chris Ferris, IBM  Scenarios and Sample Applications  Sinisa Zimek, SAP  Testing Tools and Materials  Jacques Durand, Fujitsu  Basic Security Profile  Paul Cotton, Microsoft

15. THE DELIVERABLES

16. 16 WORKING GROUP DELIVERABLES  Profiles  Named groups of specifications at given version levels with conventions about how they work together  Use cases and usage scenarios  Solution scenarios based on customer requirements  Sample code and applications  Test suites and supporting materials  Conformance testing tools  Supporting documentation and white papers

17. 17 SAMPLE DIAGRAM usage scenarios sample applications scenarios and sample applications use cases web services basic profile testing tools other test materials testing tools and materials profiles

18. 18 PROFILES  Provide guidance on general purpose Web services functionality  Address interoperability at a level above specification-by- specification  Supporting specifications and standards will be considered from multiple industry sources  Profile development will reflect market needs and requirements

19. 19 USE CASES AND USAGE SCENARIOS  Capture requirements  Use cases capture business requirements  Usage scenarios capture technical requirements needed for Web services to meet these business requirements  Drive profile creation  Prompt revision to an existing profile  Become the requirements statement for a new profile  Drive sample application creation  Sample applications represent a solution to a use case

20. 20 TESTING TOOLS  Test tools and materials  Designed to test Web service implementations for errors and to ensure conformance with the profiles  Final materials available to all Web service developers  Sample applications  Implementation of one or more use cases  Built in multiple languages to run on many platforms  Validate correct functioning of test tools  Demonstrate profile-based interoperability  Source code for the implementations will be available

21. 21 TESTING RESOURCES  Web Services Communication Monitor  Captures messages exchanged between Web services and the software that invokes them and stores the messages for later analysis  Web Services Profile Analyzer  Evaluates messages captured by Monitor  Validates the description and registration artifacts of the Web service  Output of Analyzer tool will be used as the basis for WS-I conformance claims  Tools can be used by any Web services developer  Source code will be available

22. 22 USE OF DELIVERABLES  The public is free (and encouraged) to  Download, use, and display the Basic Profile  Download and use test tools and material to test their applications  Download, use, modify, and redistribute WS-I sample applications  Adopters may (in addition to the above)  Reproduce and redistribute specifications with their products  Members may (in addition to all of the above)  Ship test tools and material (as is or modified) within their products

23. 23 CONFORMANCE  Logo represents a claim that the product or service can pass the required tests using the WS-I Test Tools  Reports generated by the tools must be made publicly available  WS-I logo is a label for customers to look for  Enforcement is market driven  Expected review by competitors and trade media  Use must reference specific profile  WS-I logo on a company’s Web site must link to the specific profile to which conformance is claimed  For shipped products, the specific profile must be referenced in documentation (e.g. ReadMe file)

24. 24 WS-I IN THE MARKETPLACE  Tool developers will advertise that their products support development and deployment of conformant services  Middleware vendors will advertise that their products support conformant service hosting  Customers will look for WS-I conformance on products

25. 25 KEY MILESTONES 2.6.02: WS-I Founded 4.18.02: First Community Meeting 10.17.02: WS-I Approves Board Expansion 10.29.02: Availability of Basic Profile 1.0 Working Draft 1.30.03: Availability of Draft Sample Application Materials 3.26.03: Sun and webMethods Elected to Board 2002 2003 4.16.03: Availability of Draft Testing Tools 4.1.03: Basic Security Profile WG Chartered 8.12.03: Basic Profile 1.0 Delivered! 2004

26. 26 WS-I, STANDARDS AND INDUSTRY Businesses, Industry Consortia, Developers, End-Users Requirements Standards and Specifications Requirements Implementation Guidance

27. 27 WS-I AND STANDARDS BODIES  Web services standards come from a variety of bodies  W3C, OASIS, IETF, ISO, ECMA, etc.  WS-I is a standards integrator  Downstream from standards organizations  Upstream from industry and industry consortia  Ensure interoperability of implementations  Collaboration with other bodies is a requirement

28. 28 WS-I AND STANDARDS BODIES  Support relationships with standards bodies who own specifications referenced by WS-I profiles  Ensure consistency  Minimize redundancy  Foster communication and cooperation with industry consortia and other organizations

29. 29 JOIN WS-I TODAY  Join  Join a community of more than 150 industry leaders and visionaries with a shared vision for Web services interoperability  Foster commitment across the community  Participate  Encourage customer participation and buy-in  Commit to an aggressive schedule for delivering resources to aid Web services implementations  Conform  Ensure implementations conform with WS-I profiles  Promote conformance to customers and partners