Web Services Standards Overview Dependencies Messaging Specifications SOAP 1.1 SOAP 1.2 Interoperability Business Process Specifications Management Specifications Presentation SOAP Message Transmission Optimization Mechanism WS-Notification the trademarks of their respective owners. of their respective the trademarks Management Using Web Management Of WS-BaseNotification Issues Business Process Execution WS-Choreography Model Web Service Choreography Web Service Choreography WS-Management Specifications Services (WSDM-MUWS) Web Services (WSDM-MOWS) Language for Web Services 1.1 Overview Interface Description Language AMD, Dell, Intel, Microsoft and Sun WS-Topics (BPEL4WS) · 1.1 · BEA Systems, IBM, (WSCI) · 1.0 · W3C 1.0 1.0 1.0 · W3C (CDL4WS) · 1.0 · W3C Microsystems Microsoft, SAP, Sun Microsystems, SAP, BEA Systems WS-BrokeredNotification Working Draft Candidate Recommendation OASIS OASIS Published Specification Web Services for Remote Security Resource Basic Profile Siebel Systems · OASIS-Standard and Intalio · Note OASIS-Standard OASIS-Standard Metadata Portlets (WSRP) WS-Addressing – Core 1.1 ̆ ̆ ̆ ̆ ̆ ̆ ̆ 2.0 WS-I Business Process Execution Language for Web Services WS-Choreography Model Overview defines the format Web Service Choreography Interface (WSCI) describes Web Service Choreography Description Language Web Service Distributed Management: Management Using Web Service Distributed Management: Management Of WS-Management describes a general SOAP-based WS-Addressing – WSDL Binding 1.1(BPEL4WS) provides a language for the formal and structure of the (SOAP) messages that are exchanged, how Web Service operations can be choreographed in the (CDL4WS) is to specify a declarative, XML based language Web Services (WSDM-MUWS) defines how an IT resource Web Services (WSDM-MOWS) addresses management of protocol for managing systems such as PCs, servers, OASIS Final Specification specification of business processes and business interaction and the sequence and conditions in which the messages context of a message exchange in which the Web Service that defines from a global viewpoint the common and connected to a network provides manageability interfaces the components that form the network, the Web services devices, Web services and other applications, and other protocols using Web Services. are exchanged. participates. complementary observable behaviour, where message such that the IT resource can be managed locally and from endpoints, using Web services protocols. manageable entities. Committee Draft WS-Addressing – SOAP Binding exchanges occur, and when the jointly agreed ordering remote locations using Web services technologies. ̆ Basic Profile – The Basic Profile 1.1 provides rules are satisfied. ̈ Web Services for Remote Portlets (WSRP) defines a WS-Eventing implementation guidelines for how related set of non- set of interfaces and related semantics which standardize proprietary Web Service specifications should be used Business Process Execution Business Process Management XML Process Definition interactions with components providing user-facing WS-Enumeration together for best interoperability. Language for Web Services 2.0 Language (BPML) markup, including the processing of user interactions with Language (XPDL) Service Modeling Language that markup. (BPEL4WS) · 2.0 1.1 2.0 IBM, BEA, BMC, Cisco, Dell, HP, Intel, OASIS, BEA Systems, IBM, Microsoft, SAP, BPMI.org Final Microsoft, Sun Siebel Systems · Committee Draft Final Draft Draft Specification Metadata Specifications Basic Profile 1.2 ̆ Business Process Execution Language for Web Services ̆ Business Process Management Language (BPML) ̆ XML Process Definition Language (XPDL) provides an WS-Policy ̆ WS-I 2.0 (BPEL4WS) provides a language for the formal provides a meta-language for expressing business XML file format that can be used to interchange process Servcie Modeling Language (SML) is used to model specification of business processes and business interaction processes and supporting entities. models between tools. complex IT services and systems, including their structure, WS-PolicyAssertions Working Group Draft protocols using Web Services. constraints, policies, and best practices. WS-PolicyAttachment ̆ Basic Profile – The Basic Profile 1.2 builds on Basic Profile 1.1 by incorporating Basic Profile 1.1 errata, requirements WS-Discovery from Simple SOAP Binding Profile 1.0, and adding support Security for WS-Addressing and MTOM. WS-MetadataExchange Universal Description, Discovery and Integration Messaging Web Service Description Language 1.1 Basic Profile 2.0 Web Service Description Language 2.0 Core WS-I Working Group Draft Metadata Specifications Reliability Security Specifications Transaction Resource Web Service Description Language 2.0 SOAP Binding ̆ Basic Profile – The Basic Profile 2.0 is an update of WS-I Security Specifications BP that includes a profile of SOAP 1.2. WS-PolicyAssertions Specifications WS-SecurityPolicy Specifications Specifications WS-Policy WS-Security for identification purposes only and may be used herein names are and product brand organisation, names. These company, roduct 1.1 1.1 1.5 1.1 WS-Security BEA Systems, IBM, Microsoft, W3C OASIS IBM, Microsoft, SAP RSA Security, VeriSign Web Services Working Draft OASIS-Standard WS-Coordination WS-Security: SOAP Message Security Attachments Profile Public Draft WS-ReliableMessaging Public Draft 1.1 Resource Framework (WSRF) 1.0 1.1 OASIS 1.2 WS-Security: Kerberos Binding WS-I ̆ WS-Policy describes the capabilities and constraints of ̆ WS-PolicyAssertions provides an initial set of assertions OASIS ̆ WS-Security is a communications protocol providing a ̆ WS-SecurityPolicy defines how to describe policies related Working Draft OASIS Final Specification WS-Security: SAML Token Profile the policies on intermediaries and endpoints (e.g. business to address some common needs of Web Services Committee Draft means for applying security to Web Services. to various features defined in the WS-Security specification. OASIS-Standard rules, required security tokens, supported encryption applications. ̆ WS-Coordination describes an extensible framework for providing algorithms, privacy rules). protocols that coordinate the actions of distributed applications. ̆ Web Services Resource Framework (WSRF) defines a family of WS-Security: X.509 Certificate Token Profile ̆ Attachments Profile – The Attachment Profile 1.0 specifications for accessing stateful resources using Web Services. complements the Basic Profile 1.1 to add support ̆ WS-ReliableMessaging describes a protocol that allows WS-Security: Username Token Profile for interoperable SOAP Messages with attachments-based Web services to communicate reliable in the presence of WS-Business Activity WS-Security: WS-Security: 1.1 (WSRF) Metadata software component, system, or network failures. It defines WS-BaseFaults Reliability Web Services. WS-SecurityPolicy Messaging a SOAP binding that is required for interoperability. SOAP Message Security Username Token Profile OASIS 1.2 WS-PolicyAttachment WS-Discovery 1.1 1.1 Working Draft OASIS WS-Trust Working Draft 1.2 Microsoft, BEA Systems, Canon, OASIS OASIS ̆ WS-Business Activity provides the definition of the business activity Simple SOAP Public Review Draft Public Review Draft WS-Federation W3C Intel and webMethods WS-Reliable Messaging coordination type that is to be used with the extensible coordination ̆ WS-BaseFaults (WSRF) defines a base set of information Binding Profile W3C Member Submission Draft Policy Assertion (WS-RM Policy) framework described in the WS-Coordination specification. that may appear in fault messages. WS-BaseFaults defines an ̆ WS-Security: SOAP Message Security describes ̆ WS-Security: Username Token Profile describes how WS-SecureConversation 1.0 1.1 XML schema type for base faults, along with rules for how WS-I enhancements to SOAP messaging to provide message a Web Service consumer can supply a Username Token as a this base fault type is used and extended by Web Services. ̆ ̆ OASIS WS-Atomic Transaction Final Specification WS-PolicyAttachment defines two general-purpose WS-Discovery defines a multicast discovery protocol for integrity and confidentiality. Specifically, this specification means of identifying the requestor by username, and mechanisms for associating policies with the subjects to dynamic discovery of services on ad-hoc and managed Committee Draft provides support for multiple security token formats, trust optionally using a password (or shared secret, etc.) to 1.1 which they apply; the policies may be defined as part networks. domains, signature formats and encryption technologies. authenticate that identity to the Web Service producer. OASIS WS-ServiceGroup (WSRF) Reliability Specifications ̆ Simple SOAP Binding Profile – The Simple SOAP Binding of existing metadata about the subject or the policies may ̆ Web Services ReliableMessaging Policy Assertion The token formats and semantics for using these are Committee Draft 1.2 Profile consists of those Basic Profile 1.0 requirements be defined independently and associated through an defined in the associated profile documents. (WS-RM Policy) describes a domain-specific policy assertion ̆ OASIS WS-ReliableMessaging related to the serialization of the envelope and its external binding to the subject. for WS-ReliableMessaging that that can be specified within WS-Atomic Transaction defines protocols that enable existing Working Draft representation in the message. a policy alternative as defined in WS-Policy