3.0 17.11.2006 al Standards Bodies Web Services Interoperability Organization WS-I http://www.ws-i.org/ is an open industry organization chartered to promote Web services interoperability across platforms, operating systems and programming languages. The organization's diverse community of Web services leaders helps customers to develop interoperable Web services by providing guidance, recommended practices and supporting resources. Specifically, WS-I creates, promotes and supports generic protocols for the interoperable exchange of messages between Web services. World Wide Web Consortium W3C http://www.w3.org/ was created in October 1994 to lead the World Wide Web to its full potential by developing common protocols that promote its evolution and ensure its interoperability. W3C has over 350 Member organizations from all over the world and has earned international recognition for its contributions to the growth of the Web. W3C is designing the infrastructure, and defining the architecture and the core technologies for Web services. In September 2000, W3C started the XML Protocol Activity to address the need for an XML-based protocol for application-to-application messaging. In January 2002, the Web Services Activity was launched, subsuming the XML Protocol Activity and extending its scope. Internet Engineering Task Force IETF http://www.ietf.org/ is a large open international community of network designers, operators, vendors, and researchers concerned with the evolution of the Internet architecture and the smooth operation of the Internet. Organization for the Advancement of Structured Information Standards OASIS http://www.oasis-open.org/ is a not-for-profit, international consortium that drives the development, convergence, and adoption of e-business standards. The consortium produces more Web services standards than any other organization along with standards for security, e-business, and standardization efforts in the public sector and for application-specific markets. Founded in 1993, OASIS has more than 4,000 participants representing over 600 organizations and individual members in 100 countries. XML Standards http://www.w3.org/TR/xml/ W3C 1.0 Recommendation is a pared-down version of SGML, designed especially for Web documents. It allows one to create own customized tags, enabling the definition, transmission, validation, and interpretation of data between applications and between organizations. http://www.w3.org/TR/xml11/ W3C 1.1 Recommendation is a pared-down version of SGML, designed especially for Web documents. It allows one to create own customized tags, enabling the definition, transmission, validation, and interpretation of data between applications and between organizations. http://www.w3.org/TR/xml-names11/ W3C 1.1 Recommendation provide a simple method for qualifying element and attribute names used in XML documents by associating them with namespaces identified by IRI references. http://www.w3.org/TR/xml-infoset W3C 1.0 Recommendation is an abstract data set to provide a consistent set of definitions for use in other specifications that need to refer to the information in a well-formed XML document. http://www.w3.org/TR/xmlschema11-1/ W3C 1.1 Working Draft is an XML language for describing and constraining the content of XML documents. http://www.w3.org/TR/xop10/ W3C 1.0 Recommendation is an XML language for describing and constraining the content of XML documents. http://www.w3.org/TR/xml-media-types/ W3C Note specifies how to indicate the content-type associated with binary element content in an XML document and to specify, in XML Schema, the expected content-type(s) associated with binary element content. Messaging Specifications http://www.w3.org/TR/2000/NOTE-SOAP-20000508/ W3C 1.1 Note is a lightweight, xml-based protocol for exchange of information in a decentralized, distributed environment. 1 resources 2 security 3 metadata http://www.w3.org/TR/soap12-part1/ W3C 1.2 Recommendation is a lightweight, xml-based protocol for exchange of information in a decentralized, distributed environment. 1 resources 2 security 3 metadata http://www.w3.org/TR/soap12-mtom/ W3C Recommendation describes an abstract feature for optimizing the transmission and/or wire format of a SOAP message. 1 resources 2 security 3 metadata http://www.w3.org/TR/soap12-rep/ W3C Recommendation complements MTOM by defining mechanisms for describing and conveying non-XML resource representations in a SOAP 1.2 message. 1 resources 2 security 3 metadata http://www.w3.org/TR/ws-addr-core W3C 1.0 Recommendation provides transport-neutral mechanisms to address Web services and messages. This specification defines XML elements to identify Web service endpoints and to secure end-to-end endpoint identification in messages. 1 resources 2 security 3 metadata http://www.w3.org/TR/ws-addr-wsdl/ W3C 1.0 Candidate Recommendation defines how the abstract properties defined in Web Services Addressing - Core are described using WSDL. 1 resources 2 security 3 metadata http://www.w3.org/TR/ws-addr-soap/ W3C 1.0 Recommendation provides transport-neutral mechanisms to address Web services and messages. 1 resources 2 security 3 metadata http://www.w3.org/Submission/WS-Eventing W3C http://www.w3.org/TR/ws-addr-core/ W3C Member Submission defines a baseline set of operations that allow Web services to provide asynchronous notifications to interested parties. 1 resources 2 security 3 metadata http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsn OASIS 1.3 OASIS-Standard is a family of related white papers and specifications that define a standard Web services approach to notification using a topic-based publish/subscribe pattern. 1 resources 2 security 3 metadata http://docs.oasis-open.org/wsn/wsn-ws_base_notification-1.3-spec-os.htm OASIS 1.3 OASIS-Standard standardizes the terminology, concepts, operations, WSDL and XML needed to express the basic roles involved in Web services publish and subscribe for notification message exchange. 1 resources 2 security 3 metadata http://docs.oasis-open.org/wsn/wsn-ws_topics-1.3-spec-pr-02.htm OASIS 1.3 OASIS-Standard defines three topic expression dialects that can be used as subscription expressions in subscribe request messages and other parts of the WS-Notification system. 1 resources 2 security 3 metadata http://docs.oasis-open.org/wsn/wsn-ws_brokered_notification-1.3-spec-os.htm OASIS 1.3 OASIS-Standard defines the interface for the NotificationBroker. A NotificationBroker is an intermediary, which, among other things, allows publication of messages from entities that are not themselves service providers. 1 resources 2 security 3 metadata http://www.w3.org/Submission/WS-Enumeration/ W3C Public Draft describes a general SOAP-based protocol for enumerating a sequence of XML elements that is suitable for traversing logs, message queues, or other linear information models. 1 resources 2 security 3 metadata Meta Data Standards http://www.oasis-open.org/committees/uddi-spec/doc/spec/v3/uddi-v3.0.2-20041019.htm OASIS 3.0.2 OASIS-Standard defines a set of services supporting the description and discovery of businesses, organizations, and other Web services providers, the Web services they make available, and the technical interfaces which may be used to access those services. 1 security 2 messaging http://www.w3.org/TR/wsdl W3C 1.1 Note is an XML-based language for describing Web services and how to access them. It specifies the location of the service and the operations (or methods) the service exposes. 1 messaging http://www.w3.org/TR/wsdl20/ W3C 2.0 Candidate Recommendation is an XML-based language for describing Web services and how to access them. It specifies the location of the service and the operations (or methods) the service exposes. 1 messaging http://www.w3.org/TR/wsdl20-soap11-binding W3C 2.0 Working Draft describes the concrete details for using WSDL 2.0 in conjunction with SOAP 1.1 protocol. 1 messaging http://specs.xmlsoap.org/ws/2004/09/mex/WS-MetadataExchange.pdf BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems, and webMethods 1.1 Public Draft enables a service to provide metadata to others through a Web services interface. Given only a reference to a Web service, an user can access a set of WSDL/SOAP operations to retrieve the metadata that describes the service. 1 security 2 messaging http://www.w3.org/TR/2006/WD-ws-policy-primer-20061018/ W3C 1.5 Working Draft describes the capabilities and constraints of the policies on intermediaries and endpoints (e.g. business rules, required security tokens, supported encryption algorithms, privacy rules). 1 security 2 messaging http://xml.coverpages.org/ws-policyassertionsV11.pdf BEA Systems, IBM, Microsoft, SAP 1.1 Public Draft provides an initial set of assertions to address some common needs of Web services applications. 1 security 2 messaging http://www.w3.org/Submission/WS-PolicyAttachment/ W3C 1.2 W3C Member Submission defines two general-purpose mechanisms for associating policies with the subjects to which they apply; the policies may be defined as part of existing metadata about the subject or the policies may be defined independently and associated through an external binding to the subject. 1 security 2 messaging http://msdn.microsoft.com/library/en-us/dnglobspec/html/WS-Discovery.pdf Microsoft, BEA Systems, Canon, Intel, and webMethods Draft defines a multicast discovery protocol for dynamic discovery of services on ad-hoc and managed networks. 1 security 2 messaging Attachments http://www-106.ibm.com/developerworks/webservices/library/ws-attach.html Microsoft, IBM Internet-Draft defines an abstract model for SOAP attachments and based on this model defines a mechanism for encapsulating a SOAP message and zero or more attachments in a DIME message http://msdn.microsoft.com/library/en-us/dnglobspec/html/draft-nielsen-dime-02.txt (IETF) Microsoft, IBM Internet-Draft is a lightweight, binary message format that can be used to encapsulate one or more application-defined payloads of arbitrary type and size into a single message construct Reliable Messaging http://docs.oasis-open.org/ws-rx/wsrm/200608/wsrm-1.1-spec-cd-04.html OASIS 1.1 Committe draft describes a protocol that allows Web services to communicate reliable in the presence of software component, system, or network failures. It defines a SOAP binding that is required for interoperability. 1 transaction 2 basic profile 3 security 4 metadata http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrm OASIS 1.1 OASIS-Standard is a SOAP-based protocol for exchanging SOAP messages with guaranteed delivery, no duplicates, and guaranteed message ordering. WS-Reliability is defined as SOAP header extensions and is independent of the underlying protocol. This specification contains a binding to HTTP. 1 transaction 2 basic profile 3 security 4 metadata http://docs.oasis-open.org/ws-rx/wsrmp/200608/wsrmp-1.1-spec-cd-04.html OASIS 1.1 Committee Draft (WS-RM Policy) describes a domain-specific policy assertion for WS-ReliableMessaging that that can be specified within a policy alternative as defined in WS-Policy Framework. 1 transaction 2 basic profile 3 security 4 metadata Transactions and Coordination http://www.oasis-open.org/committees/download.php/15738/WS-Coordination- OASIS 1.1 Working Draft describes an extensible framework for providing protocols that coordinate the actions of distributed applications. 1 metadata 2 messaging 3 security http://www.oasis-open.org/apps/group_public/download.php/16447/Microsoft%20Word%20-%20wstx-wsba-1.1-spec-wd-02.pdf OASIS 1.1 Working Draft provides the definition of the business activity coordination type that is to be used with the extensible coordination framework described in the WS-Coordination specification. 1 metadata 2 messaging 3 security http://docs.oasis-open.org/ws-tx/wstx-wsat-1.1-spec-cd-01.pdf OASIS 1.1 Committee Draft defines protocols that enable existing transaction processing systems to wrap their proprietary protocols and interoperate across different hardware and software vendors. 1 metadata 2 messaging 3 security http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ws-caf Arjuna Technologies, Fujitsu, IONA , Oracle, and Sun Microsystems 1.0 Committee Specification is a collection of three specifications aimed at solving problems that arise when multiple Web services are used in combination. It proposes standard, interoperable mechanisms for managing shared context and ensuring business processes achieve predictable results and recovery from failure. 1 reliability 2 security http://www.arjuna.com/library/specs/ws_caf_1-0/WS-CTX.pdf Arjuna Technologies, Fujitsu, IONA, Oracle and Sun Microsystems 1.0 Committee Draft is intended as a lightweight mechanism for allowing multiple Web services to share a common context. 1 reliability 2 security http://www.arjuna.com/library/specs/ws_caf_1-0/WS-CF.pdf Arjuna Technologies, Fujitsu, IONA, Oracle and Sun Microsystems 1.0 Committee Draft allows the management and coordination in a Web services interaction of a number of activities related to an overall application. 1 reliability 2 security http://www.arjuna.com/library/specs/ws_caf_1-0/WS-TXM.pdf Arjuna Technologies, Fujitsu, IONA, Oracle and Sun Microsystems 1.0 Committee Draft defines a core infrastructure service consisting of a Transaction Service for Web services. 1 reliability 2 security Business Processes http://www.ebpml.org/bpml_1_0_june_02.htm BPMI.org 1.1 Final Draft provides a meta-language for expressing business processes and supporting entities. 1 reliability 2 security 3 messaging 4 transaction http://www-106.ibm.com/developerworks/webservices/library/ws-bpel/ BEA Systems , IBM, Microsoft, SAP, Siebel Systems 1.1 OASIS-Standard provides a language for the formal specification of business processes and business interaction protocols using Web services. 1 reliability 2 security 3 messaging 4 transaction http://www.oasis-open.org/committees/download.php/16024/wsbpel-specification-draft-Dec-22-2005.htm OASIS 2.0 Committee Draft provides a language for the formal specification of business processes and business interaction protocols using Web services. 1 reliability 2 security 3 messaging 4 transaction http://www.wfmc.org/standards/docs.htm 2.0 Final provides an XML file format that can be used to interchange process models between tools. 1 reliability 2 security 3 messaging 4 transaction http://www.w3.org/TR/ws-chor-model/ W3C 1.0 Working Draft defines the format and structure of the (SOAP) messages that are exchanged, and the sequence and conditions in which the messages are exchanged. 1 reliability 2 security 3 messaging 4 transaction http://www.w3.org/TR/wsci/ W3C 1.0 Candidate Recommendation specifies a declarative, XML-based language that defines from a global viewpoint the common and complementary observable behaviour, where message exchanges occur, and when the jointly agreed ordering rules are satisfied. 1 reliability 2 security 3 messaging 4 transaction http://www.w3.org/TR/wsci W3C ; Sun Microsystems, SAP, BEA Systems, and Intalio 1.0 Note describes how Web service operations can be choreographed in the context of a message exchange in which the Web service participates. 1 reliability 2 security 3 messaging 4 transaction Security http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss OASIS 1.1 OASIS standard is a communications protocol providing a means for applying security to Web Services. 1 reliability 2 messaging 3 metadata http://www.oasis-open.org/committees/download.php/16790/wss-v1.1-spec-os-SOAPMessageSecurity.pdf OASIS 1.1 Public Review Draft describes enhancements to SOAP messaging to provide message integrity and confidentiality. Specifically, this specification provides support for multiple security token formats, trust domains, signature formats, and encryption technologies. The token formats and semantics for using these are defined in the associated profile documents. 1 reliability 2 messaging 3 metadata http://www.oasis-open.org/archives/wss/200209/pdf00002.pdf Microsoft, IBM, OASIS 1.0 Working Draft defines how to encode Kerberos tickets and attach them to SOAP messages. As well, it specifies how to add signatures and encryption to the SOAP message, in accordance with WS-Security, which uses and references the Kerberos tokens. 1 reliability 2 messaging 3 metadata http://docs.oasis-open.org/wss/v1.1/wss-v1.1-spec-pr-x509TokenProfile-01.htm OASIS 1.1 Public Review Draft defines the use of Security Assertion Markup Language (SAML) v1.1 assertions in the context of WSS: SOAP Message Security including for the purpose of securing SOAP messages and SOAP message exchanges. 1 reliability 2 messaging 3 metadata http://docs.oasis-open.org/wss/v1.1/wss-v1.1-spec-pr-x509TokenProfile-01.htm OASIS 1.1 Public Review Draft describes the use of the X.509 authentication framework with the WS-Security: SOAP Message Security specification. 1 reliability 2 messaging 3 metadata http://docs.oasis-open.org/wss/v1.1/wss-v1.1-spec-pr-UsernameTokenProfile-01.htm OASIS 1.1 Public Review Draft describes how a Web service consumer can supply a UsernameToken as a means of identifying the requestor by username, and optionally using a password (or shared secret, etc.) to authenticate that identity to the Web service producer. 1 reliability 2 messaging 3 metadata http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf IBM, Microsoft, RSA Security, VeriSign 1.1 Public Draft defines how to describe policies related to various features defined in the WS-Security specification. 1 reliability 2 messaging 3 metadata ftp://www6.software.ibm.com/software/developer/library/ws-trust.pdf BEA Systems , Computer Associates, IBM, Layer 7 Technologies, Microsoft, Netegrity, Oblix, OpenNetwork, Ping Identity Corporation, Reactivity, RSA Security, VeriSign, and Westbridge Technology Initial Draft describes a framework for trust models that enables Web services to securely interoperate. It uses WS-Security base mechanisms and defines additional primitives and extensions for security token exchange to enable the issuance and dissemination of credentials within different trust domains. 1 reliability 2 messaging 3 metadata http://msdn.microsoft.com/ws/2003/07/ws-federation IBM, Microsoft, BEA Systems, RSA Security, VeriSign 1.0 Initial Draft describes how to manage and broker the trust relationships in a heterogeneous federated environment including support for federated identities. 1 reliability 2 messaging 3 metadata ftp://www6.software.ibm.com/software/developer/library/ws-secureconversation.pdf BEA Systems , Computer Associates, IBM, Layer 7 Technologies, Microsoft , Netegrity, Oblix, OpenNetwork , Ping Identity Corporation, Reactivity, RSA Security, VeriSign, and Westbridge Technology Public Draft specifies how to manage and authenticate message exchanges between parties including security context exchange and establishing and deriving session keys. 1 reliability 2 messaging 3 metadata Interoperability http://www.ws-i.org/Profiles/BasicProfile-1.1.html WS-I 1.1 Final Specification provides implementation guidelines for how related set of non-proprietary Web service specifications should be used together for best interoperability. http://www.ws-i.org/Profiles/BasicProfile-1.2.html WS-I 1.2 Working Group Draft builds on Basic Profile 1.1 by incorporating Basic Profile 1.1 errata, requirements from Simple SOAP Binding Profile 1.0, and adding support for WS-Addressing and MTOM. http://www.ws-i.org/docs/charters/WSBasic_Profile_Charter2-1.pdf WS-I 2.0 is an update of WS-I BP that includes a profile of SOAP 1.2. http://www.ws-i.org/Profiles/AttachmentsProfile-1.0.html WS-I 1.0 Final Specification complements the Basic Profile 1.1 to add support for interoperable SOAP Messages with attachments-based Web services. http://www.ws-i.org/Profiles/BasicSecurityProfile-1.0.html WS-I Working Group Draft defines the WS-I Basic Security Profile 1.0, based on a set of non-proprietary Web services specifications, along with clarifications and amendments to those specifications which promote interoperability http://www.ws-i.org/Profiles/SimpleSoapBindingProfile-1.0.html WS-I 1.0 Final Specification consists of those Basic Profile 1.0 requirements related to the serialization of the envelope and its representation in the message. http://www.ws-i.org/Profiles/RELTokenProfile-1.0.html WS-I 1.0 Working Group Draft based on a non-proprietary Web services specification, along with clarifications and amendments to that specification which promote interoperability. http://www.ws-i.org/Profiles/SAMLTokenProfile-1.0.html WS-I 1.0 Working Group Draft based on a non-proprietary Web services specification, along with clarifications and amendments to that specification which promote interoperability. http://www.ws-i.org/Profiles/ConformanceClaims-1.0-2004-11-15.html WS-I 1.0 Final Specification catalogues mechanisms that can be used to attach WS-I Profile Conformance Claims to Web services artefacts (e.g., WSDL descriptions, UDDI registries). http://www-128.ibm.com/developerworks/webservices/library/specification/ws-ramp/ WS-I 1.0 is a profile, in the fashion of the WS-I profiles, that enables, among other things, basic B2B integration scenarios using Web services technologies. Resources http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm is an abstraction of the architectural elements within a distributed hypermedia system. REST ignores the details of component implementation and protocol syntax in order to focus on the roles of components, the constraints upon their interaction with other components, and their interpretation of significant data elements. It encompasses the fundamental constraints upon components, connectors, and data that define the basis of the Web architecture, and thus the essence of its behavior as a network-based application. 1 transaction 2 security 3 messaging http://www.w3.org/TR/soap12-rep/ W3C allows SOAP message recipients to access cached representations of resources. 1 transaction 2 security 3 messaging http://www.w3.org/Submission/WS-Transfer/ W3C W3C Member Submission describes a general SOAP-based protocol for accessing XML representations of Web service-based resources. 1 transaction 2 security 3 messaging http://w3.org/Submission/WS-Enumeration BEA Systems, Computer Associates, Microsoft, Sonic Software, and Systinet W3C Member Submission describes a general SOAP-based protocol for enumerating a sequence of XML elements that is suitable for traversing logs, message queues, or other linear information models. 1 transaction 2 security 3 messaging http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrf OASIS 1.2 OASIS standard defines a family of specifications for accessing stateful resources using Web services. 1 transaction 2 security 3 messaging http://docs.oasis-open.org/wsrf/2005/03/wsrf-WS-BaseFaults-1.2-draft-04.pdf OASIS 1.2 Working Draft defines a base set of information that may appear in fault messages. WS-BaseFaults defines an XML Schema type for base faults, along with rules for how this base fault type is used and extended by Web services. 1 transaction 2 security 3 messaging http://docs.oasis-open.org/wsrf/2005/03/wsrf-WS-ServiceGroup-1.2-draft-04.pdf OASIS 1.2 Working Draft defines a means by which Web services and WS-Resources can be aggregated or grouped together for a domain specific purpose. 1 transaction 2 security 3 messaging http://docs.oasis-open.org/wsrf/2005/03/wsrf-WS-ResourceProperties-1.2-draft-06.pdf OASIS 1.2 Working Draft specifies the means by which the definition of the properties of a WS-Resource may be declared as part of the Web service interface. The declaration of the WS-Resource properties represents a projection of or a view on the WS-Resource state. 1 transaction 2 security 3 messaging http://docs.oasis-open.org/wsrf/2005/03/wsrf-WS-ResourceLifetime-1.2-draft-05.pdf OASIS 1.2 Working Draft is to standardize the terminology, concepts, message exchanges, WSDL and XML needed to monitor the lifetime of, and destroy WS-Resources. Additionally, it defines resource properties that may be used to inspect and monitor the lifetime of a WS-Resource. 1 transaction 2 security 3 messaging Management http://docs.oasis-open.org/wsdm/2004/12/wsdm-muws-part1-1.0.pdf OASIS 1.0 OASIS-Standard defines how an IT resource connected to a network provides manageability interfaces such that the IT resource can be managed locally and from remote locations using Web services technologies. 1 resource 2 security 3 messaging http://docs.oasis-open.org/wsdm/2004/12/wsdm-mows-1.0.pdf OASIS 1.0 OASIS-Standard addresses management of the components that form the network, the Web services endpoints, using Web services protocols. 1 resource 2 security 3 messaging http://xml.coverpages.org/ni2005-09-17-a.html AMD, Dell, Intel, Microsoft, and Sun Microsystems Published Specification describes a general SOAP-based protocol for managing systems such as PCs, servers, devices, Web services and other applications, and other manageable entities. 1 metadata 2 security 3 messaging http://www-03.ibm.com/autonomic/service_modeling_language_spec.html IBM, BEA, BMC, Cisco, Dell, HP, Intel, Microsoft, Sun 0.5 Draft Specification is used to model complex IT services and systems, including their structure, constraints, policies, and best practices. 1 resource 2 security 3 messaging Presentation http://docs.oasis-open.org/wsrp/v2/wsrp-2.0-spec-cd-03-highlight.html OASIS 2.0 Committee Draft defines a set of interfaces and related semantics which standardize interactions with components providing user-facing markup, including the processing of user interactions with that markup. 1 reliablity 2 security 3 messaging