1. Interoperability at the Business Layer ISWC Industry Day – Information Juggernaut National University of Ireland - Galway 7 November 2005 Patrick Gannon President & CEO Patrick Gannon President & CEO

2. n Vision for Service Oriented Architecture n Key Directions in SOA and Web Services Standards n What your company can do Open Standards for Semantics and Service Oriented Architecture

3. Vision for Future Global eBusiness built on a Service Oriented Architecture

4. The Dawn of a New Era Built on Service Oriented Architecture

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

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

7. Achieving Sustainable Business Benefits through a Open Standards for Web Services 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.

8. 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.

9. Whats the problem? n Industry-specific vocabularies have all too often been developed in a stove-pipe fashion n Industry sectors lack a unified approach to creating XML vocabularies n This creates a barrier to achieving service expansion benefits into cross-sectoral lines of business n Governments are realizing the shortcomings of a departmental approach which hampers attempts to share information between agencies and between different levels of government

10. Whats the solution? Interoperability at the Business Layer

11. What are some ways forward? A.UBL OASIS Standard provides a common point of reference against which existing industry business languages can map their vocabularies B.Semantic interoperability and reasoning tools can attempt to map common elements C.Industry sectors should adopt common SOA elements and common SOA methodology D.Industry associations are building their Web Service interaction specifications within OASIS in order to take advantage of the many (24) SOA and WS committees already at OASIS

12. Cross-Sectoral Approach to SOA Foundation Adoption n Link open standards development processes closer to university and government sponsored research efforts n Active involvement of technology vendors in Proof-of- Concept efforts and open standards development n Industry associations and end-user businesses taking an active role in setting requirements and priorities n Governments collaborating in the process to provide public policy requirements and drive adoption n Open source software developers participating to build implementations based on the open standards for the SME markets and smaller governments

13. Leading the Adoption of Service Oriented Architecture and Web Services Standards

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

15. n OASIS is a member-led, international non-profit standards consortium concentrating on structured information and global e-business standards. n Over 650 Members with 5,000+ participants of OASIS are: l Vendors, users, academics and governments l Organizations, individuals and industry groups n Best known for web services, e-business, security and document format standards. n Supports over 65 committees producing royalty- free and RAND standards in an open process.

16. OASIS Relationships n Cooperate and liaise with other standards organizations l Working to reduce duplication, promote interoperability l Gaining sanction/authority & adoption for OASIS Standards n Formal working relationships with: l ISO, IEC, ITU, UN-ECE MoU for E-Business l ISO/IEC JTC1 SC34, ISO TC154 (Cat. A Liaison) l ITU-T A.4 and A.5 Recognition l IBFD, IEEE-ITO, IPTC, LISA, SITA, SWIFT, UPU l BPMI, CommerceNet, GGF, IDEAlliance, Liberty Alliance, OAGi, OGC, OMA, OMG, GS1-US/RosettaNet, W3C, WfMC, WSCC, WS-i l ABA, ACORD, AIAG, CABA, HL7, HR-XML, ISM, MBAA-MISMO, NASPO, NIGP, NNA l BASDA, European ICTSB, CEN/ISSS, EC SEEM, LRC, PISCES l Asia PKI, CNNIC, EA-ECA, ECIF, ETRI, III, KIEC, KNCA, NII-EPA, PSLX, Standards-AU

17. OASIS Members Represent the Marketplace

18. International Representation

19. OASIS Open Standards and Open Source Software n Open Standards create a larger market to encourage Open Source Software development n Open Source Software built on Open Standards provides a broader range of implementation tools & solutions n Open Source Software projects can spawn Open Standards

20. OASIS Standards with Open Source Implementations n OpenDocument Format for Office Applications l OpenOffice http://www.openoffice.orghttp://www.openoffice.org n WS-Remote Portlets in Apache: l WSRP4J http://ws.apache.org/wsrp4j/http://ws.apache.org/wsrp4j/ n Registry: l ebXML RegRep in Sourceforge: http://sourceforge.net/projects/ebxmlrr/http://sourceforge.net/projects/ebxmlrr/ l UDDI in Apache: http://ws.apache.org/juddi/http://ws.apache.org/juddi/ n Access Control: XACML in Sourceforge: l http://sunxacml.sourceforge.net/ http://sunxacml.sourceforge.net/ n Message Reliability: ebXML Messaging in SourceForge (multiple): l http://sourceforge.net/projects/ebxmlms/ http://sourceforge.net/projects/ebxmlms/ l http://sourceforge.net/projects/openebxml/ http://sourceforge.net/projects/openebxml/ l http://sourceforge.net/projects/ebmail/ http://sourceforge.net/projects/ebmail/ n Documentation Enterprise l Outsourcing http://sourceforge.net/projects/deo/http://sourceforge.net/projects/deo/ l Core components http://sourceforge.net/projects/corecomponents/http://sourceforge.net/projects/corecomponents/ n Business Content Assembly: CAM in open Java: http://jcam.org.uk http://jcam.org.uk

21. OASIS Standards

22. Common transport (HTTP, etc.) Service Discovery Service Description Orchestration & Management Security & Access Messaging Data Content Common language (XML)

23. Common transport (HTTP, etc.) Service Discovery Service Description Orchestration & Management Security & Access Messaging Data Content OASIS Work Common language (XML)

24. Common transport (HTTP, etc.) Common language (XML) Service Discovery Service Description Orchestration & Management Security & Access Messaging Data Content ebXML MSG, WS-Reliability [Conformance], ebXML IIC, XSLT Conf, DSS, PKI, SAML, WS-Security, XCBF [DSML], SPML, XACML, DCML (x5), WSDM, WSRF, WSN ASAP, BTP, CAM, ebXML-BP, WSBPEL, WSCAF [Auto Repair], AVDL, eGov, Election, eProc, Emerg, Legal XML(4), Materials, PLCS, PPS, TaxML, WAS CIQ, CGM, DocBook, OpenDocument,, UBL, XLIFF ebXML CPPA HumanML, UIML, WSRP ebXML RegRep, UDDI BCM, ebSOA, FWSI, TransWS, SOA-RM DITA, EntityRes, RELAX-NG, Published Subjects, XDI, XRI

25. Standardizing SOA & Web Services Cross-Functionally 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 implementation methods and common functional elements for broad, multi-platform, vendor-neutral implementations of Web services for e Business applications. n Service Oriented Architecture Adoption Blueprints Developing concrete examples of business requirements for SOA implementations. n SOA-RM: SOA Reference Model Developing a core reference model to guide and foster the creation of specific, service-oriented architectures. n Semantic Execution Environment Developing guidelines, justifications, and implementation directions for deploying Semantic Web services in SOA.

26. Semantic Execution Environment TC n First Meeting: 11 Nov 2005 n Charter: Provide guidelines, justifications and implementation directions for an execution environment for Semantic Web services in service-oriented systems; building on the Web Service Modeling eXecution environment (WSMX) work. n Proposed Co-Chairs: l Michal Zaremba, DERI Ireland l Dieter Fensel, DERI Austria n Deliverables: l Semantic Web Services Architecture and Information Model l Execution Semantics for Semantics-Enabled systems n Related Activities: l OASIS SOA-RM, ebSOA, SOA Adoption Blueprints, & WS TCs l W3C RDF, WS Description WG, WS Choreography WG l SWSI, Meteor-S, OWL-S

27. Semantic Execution Environment TC Proposers n DERI – Digital Enterprise Research Institute (Ireland) n CEFRIEL - ICT Center of Excellence For Research, Innovation, Education and industrial Labs partnership (Italy) n INRIA - Institut National de Recherche en Informatique (France) n Open University (UK) n Software Research & Development Center (Turkey) n Adobe Systems n Booz Allen Hamilton n Fidelity n Nortel n NASA (USA) n NCA – National Computerization Agency (Korea) n … plus many more international participants

28. 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 WSDM: Web Services Distributed Management l Management Using WS (MUWS), Management of WS (MOWS). n WS-Reliability: Web Services Reliability l Establishing a standard, interoperable way to guarantee message delivery to applications or Web services. n WSRP: Web Services for Remote Portlets l Standardizing presentation-oriented Web services for use by aggregation intermediaries, such as portals. n WSS: Web Services Security l Delivering a technical foundation for implementing integrity and confidentiality in higher-level Web services applications.

29. OASIS Web Services Infrastructure Work 24+ OASIS SOA & WS 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 WSN: Notification Advancing a pattern-based approach to allow Web services to disseminate information to one another. n WSQM: Quality Model Preparing a quality model in the context of contracting for Web services between associates conceptually, in order to secure Web services at a specific level of service quality.

30. OASIS Web Services Infrastructure Work n WS-RX: Reliable Exchange Advancing a protocol for reliable message exchange using Web services. n WSRF: Resource Framework Defining an open framework for modeling and accessing stateful resources. n WS-SX: Secure Exchange Define extensions to OASIS Web Services Security to enable trusted SOAP message exchanges involving multiple message exchanges and to define security policies that govern the formats and tokens of such messages [WS SecureConversation, WS Trust, WS SecurityPolicy]. n WS-TX: Transaction Define a set of protocols to coordinate the outcomes of distributed application actions [WS Coordination, WS AtomicTransaction, WS BusinessActivity].

31. 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 n OASIS International Health Continuum TC Providing a forum for the global healthcare industry community to articulate and coordinate requirements for XML and Web services standards: l Promote the adoption of OASIS specs/standards within healthcare community l Create best practice documents n OASIS Tax XML TC Promoting interoperability of XML tax-related information: l Create best practice documents, advising OECD Tax Committee.

32. Standardizing Web Services Implementations For communities to build their Web services: n oBIX: Open Building Information Xchange Enabling mechanical and electrical systems in buildings to communicate with enterprise applications. n RCXML: Remote Control XML Developing a set of XML standards to support control of devices to be accessed and controlled remotely. n Translation WS Automating the translation and localization process as a Web service. l OASIS supporting launch of Localisation Testing Lab at Localisation Research Centre at University of Limerick, Ireland

33. 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.

34. 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 WAS: Web Application Security Creating an open data format to describe Web application security vulnerabilities, providing guidance for initial threat and risk ratings. n WS-SX: Web Services Secure Exchange Creating an open data format to describe Web application security vulnerabilities, providing guidance for initial threat and risk ratings.

35. SOA & 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 (24+). 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.

36. Reducing Risk Reducing Risk in new e-business technologies n Avoid reinventing the wheel l Stay current with emerging technologies n Influence industry direction l Ensure consideration of own needs n Realize impact of interoperability and network effects n Reduce development cost & time l save development on new technologies l share cost/time with other participants

37. What can your company do? n Participate l Understand the ground rules l Contribute actively Or… n Be a good observer In any case… n Make your needs known l Use cases, functions, platforms, IPR, priorities, availability, tooling n Be pragmatic: standardization is a voluntary process

38. 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