1 / 27

OASIS and Web Services Standards:

www.oasis-open.org. OASIS and Web Services Standards:. Patrick J. Gannon President and CEO. OASIS Mission. OASIS drives the development, convergence and adoption of e-business standards. Current Members. Software vendors User companies Industry organizations Governments

nerice
Download Presentation

OASIS and Web Services Standards:

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


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

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

  3. Current Members • Software vendors • User companies • Industry organizations • Governments • Universities and Research centres • Individuals • 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 • OASIS has history of applying foundational methods from W3C and others to building accessible standards for practical eBusiness methods • OASIS has a history of successfully hosting converging efforts • e.g., WSDM and the recently-submitted GGF and Globus work

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

  8. OASIS & Semantic Web Services • OASIS is where the use cases are • 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 • OASIS creates composable, modular standards that can be aggregated into recognizable e-Business functions • CDC Epidemiology demos in Fall 2003 • SAML and WS-Security access and security demos in early 2004 • etc.

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

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

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

  12. What is OASIS Saying about Semantic Web Services? “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

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

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

  15. Approved OASIS Standards for Web Services • UDDI: Universal Description, Discovery & Integration • Defining a standard method for enterprises to dynamically discover and invoke Web services. • WSRP: Web Services for Remote Portlets • Standardizing the consumption of Web services in portal front ends. • WSS: Web Services Security • 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: • ASAP: Asynchronous Service Access ProtocolEnabling the control of asynchronous or long-running Web services. • WSBPEL: Business Process Execution LanguageEnabling users to describe business process activities as Web services and define how they can be connected to accomplish specific tasks. • WS-CAF: Composite Application FrameworkDefining an open framework for supporting applications that contain multiple Web services used in combination. • WSDM: Distributed ManagementDefining Web services architecture to manage distributed resources.

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

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

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

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

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

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

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

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

  25. Web Services Standards: Leading the Way for Widespread Adoption • Advances in infrastructure standards--security, transactions, messaging, managementOASIS is the home for a very significant portion of this work. • Collaboration on implementation standards for & across industriesCommunities define standards & identify requirements at OASIS. • Maturity of key security standardsThe majority of these are work products of OASIS. • User demands for compatibilityUser requirements drive OASIS development. • 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 • www.oasis-open.org • www.xml.org • www.xml.coverpages.org

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

More Related