1. OASIS and Web Services Standards: Patrick J. Gannon President and CEO www.oasis-open.org

2. OASIS drives the development, convergence and adoption of e-business standards. of e-business standards. OASIS Mission

3. Current Members n Software vendors n User companies n Industry organizations n Governments n Universities and Research centres n Individuals n And cooperation with other standards bodies

4. OASIS Members Represent the Marketplace

5. Why OASIS and Semantic Web Services?

6. OASIS & Semantic Web Services OASIS is where convergence happens l OASIS has history of applying foundational methods from W3C and others to building accessible standards for practical eBusiness methods l OASIS has a history of successfully hosting converging efforts n e.g., WSDM and the recently-submitted GGF and Globus work

7. OASIS & Semantic Web Services OASIS is where the use cases are l OASIS hosts the two dominant standardized methods for SOA data discovery, UDDI and ebXML Registry -- both actively exploring semantic method interfaces l OASIS has over 14 TCs working on web services work, including the core methods for: n service management, n security, n access control and n transactional contracting and negotiation

8. OASIS & Semantic Web Services OASIS is where the use cases are l Semantic Standards (RDF, OWL) and emerging specs (WSMO, WSMX) need to be integrated into actual e-Business frameworks, many of which are developed through OASIS l OASIS creates composable, modular standards that can be aggregated into recognizable e- Business functions n CDC Epidemiology demos in Fall 2003 n SAML and WS-Security access and security demos in early 2004 n etc.

9. OASIS Technical Committees & Semantic Web Services n UDDI Specification TC l OWL as the UDDI Taxonomy Language n ebXML Registry TC l Semantic content registries provide a federated registry for the semantics of schemas, ontologies, and applications. Moving towards an OWL/RDF vision n Product Life Cycle Support TC l Manufacturing lifecycle ontologies soon to be OWL ready

10. Semantic Web Services Architecture n Dynamic Service Discovery n Service Selection and Composition n Negotiation and Contracting n Semantic Web Community Support Services n Semantic Web Service Lifecycle and Resource Management Services

11. OASIS Opportunities with Semantic Web Services n Discussion on new TC for practical eBusiness applications of SWS n Liaisons with other WS TCs and Semantic TCs (DITA, Topic Maps) n Liaisons with industry consortia (RosettaNet, HL7, AIAG, ACORD, ISM, HR-XML, OAGi, OGC, WfMC, …)

12. Clearly, the time to forge a common framework based on Semantic interoperability standards and e- Business web services standards is now. Patrick Gannon, CEO and President, OASIS Adaptive Information: Improving Business Through Semantic Interoperability, Grid Computing & Enterprise Integration – Book Forward What is OASIS Saying about Semantic Web Services?

13. Web Services Standards: OASIS is Leading the Way for Widespread Adoption

14. Dependencies for Web Services Deployment n Advances & coordination in infrastructure standards: security, reliable messaging, transactions, business process and management n Collaboration on implementation standards for specific communities and cross-industries n Maturity of key security standards n User demands for compatibility n Standards developed through an open and neutral process

15. Approved OASIS Standards for Web Services n UDDI: Universal Description, Discovery & Integration l Defining a standard method for enterprises to dynamically discover and invoke Web services. n WSRP: Web Services for Remote Portlets l Standardizing the consumption of Web services in portal front ends. n WSS: Web Services Security l Delivering a technical foundation for implementing integrity and confidentiality in higher-level Web services applications.

16. OASIS Web Services Infrastructure Work 14+ OASIS Technical Committees, including: n ASAP: Asynchronous Service Access Protocol Enabling the control of asynchronous or long-running Web services. n WSBPEL: Business Process Execution Language Enabling users to describe business process activities as Web services and define how they can be connected to accomplish specific tasks. n WS-CAF: Composite Application Framework Defining an open framework for supporting applications that contain multiple Web services used in combination. n WSDM: Distributed Management Defining Web services architecture to manage distributed resources.

17. OASIS Web Services Infrastructure Work n WSN: Notification Advancing a pattern-based approach to allow Web services to disseminate information to one another. n WSRM: Reliable Messaging Establishing a standard, interoperable way to guarantee message delivery to applications or Web services. n WSRF: Resource Framework Defining an open framework for modeling and accessing stateful resources.

18. Standardizing Web Services Implementations For communities and across industries: n ebSOA: e-Business Service Oriented Architecture Advancing an e-business architecture that builds on ebXML and other Web services technology. n FWSI: Framework for WS Implementation Defining methods for broad, multi-platform, vendor-neutral implementation. n oBIX: Open Building Information Xchange Enabling mechanical and electrical systems in buildings to communicate with enterprise applications. n Translation WS Automating the translation and localization process as a Web service.

19. Identifying End User Solutions n OASIS e-Government TC Providing a forum for governments internationally to: l Voice needs and requirements l Recommend work for relevant OASIS TCs l Create best practice documents, l Promote the adoption of OASIS specs/standards within Governments

20. OASIS Standards for Security n SAML: Security Services Defining the exchange of authentication and authorization information to enable single sign-on. n SPML: Provisioning Services Providing an XML framework for managing the allocation of system resources within and between organizations. n XACML: Access Control Expressing and enforcing authorization policies for information access over the Internet. n XCBF: Common Biometric Format Providing a standard way to describe information that verifies identity based on human characteristics such as DNA, fingerprints, iris scans, and hand geometry. n WSS: Web Services Security Advancing a technical foundation for implementing integrity and confidentiality in higher-level Web services applications. n AVDL: Application Vulnerability Standardizing the exchange of information on security vulnerabilities of applications exposed to networks.

21. OASIS Security Work n DSS: Digital Signature Services Defining an XML interface to process digital signatures for Web services and other applications. n PKI: Public Key Infrastructure Advancing the use of digital certificates as a foundation for managing access to network resources and conducting electronic transactions. n Rights Language Defining digital rights for resources that include digital content and Web services. n WAS: Web Application Security Creating an open data format to describe Web application security vulnerabilities, providing guidance for initial threat and risk ratings.

22. Compatibility and Convergence n Industry groups call for a migration/convergence path for WS, ebXML, and related standards. n Web services enters phase where business requirements and measurable interoperability drive standards development and convergence. n User participation in standards drives convergence that will prevail over centrifugal pull of competitive positions.

23. Open Standards Process: Essential to WS Adoption n Enables collaboration n Assures fairness n Provides for transparency n Embraces full participation n Ensures a level playing field for all n Prevents unfair first-to-market advantage for any one participant n Meets government requirements

24. OASIS Open Process n Hosts a variety of projects to standardize methods from multiple groups n Encourages convergence but does not mandate it n Provides fair data about projects being standardized, but doesnt pick winners

25. Web Services Standards: Leading the Way for Widespread Adoption n Advances in infrastructure standards--security, transactions, messaging, management OASIS is the home for a very significant portion of this work. n Collaboration on implementation standards for & across industries Communities define standards & identify requirements at OASIS. n Maturity of key security standards The majority of these are work products of OASIS. n User demands for compatibility User requirements drive OASIS development. n Standards developed through an open and neutral process OASIS enables open collaboration, providing for fairness, transparency, and full participation from vendors, users, and governments.

26. Contact Information: Patrick Gannon President & CEO patrick.gannon@oasis-open.org +1.978.761.3546 n www.oasis-open.org n www.xml.org n www.xml.coverpages.org

27. Patrick J. Gannon n OASIS – C.E.O., President, Board Director (2001-Present) n UNECE – Chair, Team of Specialists for Internet Enterprise Development (2000-2002, 2004-Present) Prior positions … n BEA Systems – Sr. VP Strategic Marketing n Netfish Technologies – VP Industry Standards n Open Buying on the Internet (OBI) – Executive Director n RosettaNet – First Project Leader (1998) n CommerceNet – VP Strategic Programs l XML eCommerce Evangelist (1997-1999) l Interoperable Catalog WG (1995-1998) n PIDX, CIAG, PVF Roundtable, CIMIS (1988-1995)