Web Services Standards

An overview of the Web services standards landscape

This page provides an overview of existing Web Services standards; it has last been updated on 16 October 2006. Please let us know your feedback about problems, missing or obsolete standards via email to ws-standards@innoq.com .


3.0 17.11.2006 al

Standards Bodies

Web Services Interoperability Organization [ WS-I ] 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.

[top]

World Wide Web Consortium [ W3C ] 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.

[top]

Internet Engineering Task Force [ IETF ] 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.

[top]

Organization for the Advancement of Structured Information Standards [ OASIS ] 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.

[top]

XML Standards

XML 1.0 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.

Dependencies:

[top]

XML 1.1 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.

Dependencies:

[top]

Namespaces in XML provide a simple method for qualifying element and attribute names used in XML documents by associating them with namespaces identified by IRI references.

Dependencies:

[top]

XML Information Set (Second Edition) 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.

Dependencies:

[top]

XML Schema is an XML language for describing and constraining the content of XML documents.

Dependencies:

[top]

XML binary Optimized Packaging (XOP) is an XML language for describing and constraining the content of XML documents.

Dependencies:

[top]

Describing Media Content of Binary Data in XML (DMCBDX) 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.

Dependencies:

[top]

Messaging Specifications

SOAP 1.1 is a lightweight, xml-based protocol for exchange of information in a decentralized, distributed environment.

Dependencies: > resources > security > metadata

[top]

SOAP 1.2 is a lightweight, xml-based protocol for exchange of information in a decentralized, distributed environment.

Dependencies: > resources > security > metadata

[top]

SOAP Message Transmission Optimization Mechanism (MTOM) describes an abstract feature for optimizing the transmission and/or wire format of a SOAP message.

Dependencies: > resources > security > metadata

[top]

Resource Representation SOAP Header Block (RRSHB) complements MTOM by defining mechanisms for describing and conveying non-XML resource representations in a SOAP 1.2 message.

Dependencies: > resources > security > metadata

[top]

WS-Addressing - Core 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.

Dependencies: > resources > security > metadata

[top]

WS Addressing - WSDL Binding defines how the abstract properties defined in Web Services Addressing - Core are described using WSDL.

Dependencies: > resources > security > metadata

[top]

WS Addressing - SOAP Binding provides transport-neutral mechanisms to address Web services and messages.

Dependencies: > resources > security > metadata

[top]

WS-Eventing defines a baseline set of operations that allow Web services to provide asynchronous notifications to interested parties.

Dependencies: > resources > security > metadata

[top]

WS-Notification (WSN) 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.

Dependencies: > resources > security > metadata

[top]

WS-BaseNotification 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.

Dependencies: > resources > security > metadata

[top]

WS-Topics defines three topic expression dialects that can be used as subscription expressions in subscribe request messages and other parts of the WS-Notification system.

Dependencies: > resources > security > metadata

[top]

WS-BrokeredNotification 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.

Dependencies: > resources > security > metadata

[top]

WS-Enumeration 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.

Dependencies: > resources > security > metadata

[top]

Meta Data Standards

Universal Description, Discovery and Integration 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.

Dependencies: > security > messaging

[top]

Web Services Description Language 1.1 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.

Dependencies: > messaging

[top]

Web Services Description Language 2.0 Core 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.

Dependencies: > messaging

[top]

Web Services Description Language 2.0 SOAP Binding describes the concrete details for using WSDL 2.0 in conjunction with SOAP 1.1 protocol.

Dependencies: > messaging

[top]

WS-MetadataExchange 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.

Dependencies: > security > messaging

[top]

WS-Policy describes the capabilities and constraints of the policies on intermediaries and endpoints (e.g. business rules, required security tokens, supported encryption algorithms, privacy rules).

Dependencies: > security > messaging

[top]

WS-PolicyAssertions provides an initial set of assertions to address some common needs of Web services applications.

Dependencies: > security > messaging

[top]

WS-PolicyAttachment 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.

Dependencies: > security > messaging

[top]

WS-Discovery defines a multicast discovery protocol for dynamic discovery of services on ad-hoc and managed networks.

Dependencies: > security > messaging

[top]

Attachments

WS-Attachments 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

Dependencies:

[top]

Direct Internet Message Encapsulation 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

Dependencies:

[top]

Reliable Messaging

WS-ReliableMessaging 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.

Dependencies: > transaction > basic profile > security > metadata

[top]

WS-Reliability 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.

Dependencies: > transaction > basic profile > security > metadata

[top]

Web Services ReliableMessaging Policy Assertion (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.

Dependencies: > transaction > basic profile > security > metadata

[top]

Transactions and Coordination

WS-Coordination describes an extensible framework for providing protocols that coordinate the actions of distributed applications.

Dependencies: > metadata > messaging > security

[top]

WS-Business Activity 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.

Dependencies: > metadata > messaging > security

[top]

WS-Atomic Transaction defines protocols that enable existing transaction processing systems to wrap their proprietary protocols and interoperate across different hardware and software vendors.

Dependencies: > metadata > messaging > security

[top]

WS-Composite Application Framework 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.

Dependencies: > reliability > security

[top]

WS-Context is intended as a lightweight mechanism for allowing multiple Web services to share a common context.

Dependencies: > reliability > security

[top]

WS-Coordination Framework allows the management and coordination in a Web services interaction of a number of activities related to an overall application.

Dependencies: > reliability > security

[top]

WS-Transaction Management defines a core infrastructure service consisting of a Transaction Service for Web services.

Dependencies: > reliability > security

[top]

Business Processes

Business Process Management Language provides a meta-language for expressing business processes and supporting entities.

Dependencies: > reliability > security > messaging > transaction

[top]

Business Process Execution Language for Web Services 1.1 provides a language for the formal specification of business processes and business interaction protocols using Web services.

Dependencies: > reliability > security > messaging > transaction

[top]

Business Process Execution Language for Web Services 2.0 provides a language for the formal specification of business processes and business interaction protocols using Web services.

Dependencies: > reliability > security > messaging > transaction

[top]

XML Process Definition Language (XPDL) - 2.0 provides an XML file format that can be used to interchange process models between tools.

Dependencies: > reliability > security > messaging > transaction

[top]

WS-Choreography Model Overview defines the format and structure of the (SOAP) messages that are exchanged, and the sequence and conditions in which the messages are exchanged.

Dependencies: > reliability > security > messaging > transaction

[top]

Web Service Choreography Description Language 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.

Dependencies: > reliability > security > messaging > transaction

[top]

Web Service Choreography Interface describes how Web service operations can be choreographed in the context of a message exchange in which the Web service participates.

Dependencies: > reliability > security > messaging > transaction

[top]

Security

WS-Security is a communications protocol providing a means for applying security to Web Services.

Dependencies: > reliability > messaging > metadata

[top]

WS-Security : SOAP Message Security 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.

Dependencies: > reliability > messaging > metadata

[top]

WS-Security : Kerberos Binding 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.

Dependencies: > reliability > messaging > metadata

[top]

WS-Security : SAML Token Profile 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.

Dependencies: > reliability > messaging > metadata

[top]

WS-Security : X.509 Certificate Token Profile describes the use of the X.509 authentication framework with the WS-Security: SOAP Message Security specification.

Dependencies: > reliability > messaging > metadata

[top]

WS-Security Username Token Profile 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.

Dependencies: > reliability > messaging > metadata

[top]

WS-SecurityPolicy defines how to describe policies related to various features defined in the WS-Security specification.

Dependencies: > reliability > messaging > metadata

[top]

WS-Trust 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.

Dependencies: > reliability > messaging > metadata

[top]

WS-Federation describes how to manage and broker the trust relationships in a heterogeneous federated environment including support for federated identities.

Dependencies: > reliability > messaging > metadata

[top]

WS-SecureConversation specifies how to manage and authenticate message exchanges between parties including security context exchange and establishing and deriving session keys.

Dependencies: > reliability > messaging > metadata

[top]

Interoperability

Basic Profile 1.1 provides implementation guidelines for how related set of non-proprietary Web service specifications should be used together for best interoperability.

Dependencies:

[top]

Basic Profile 1.2 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.

Dependencies:

[top]

Basic Profile 2.0 is an update of WS-I BP that includes a profile of SOAP 1.2.

Dependencies:

[top]

Attachments Profile complements the Basic Profile 1.1 to add support for interoperable SOAP Messages with attachments-based Web services.

Dependencies:

[top]

Basic Security Profile 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

Dependencies:

[top]

Simple SOAP Binding Profile consists of those Basic Profile 1.0 requirements related to the serialization of the envelope and its representation in the message.

Dependencies:

[top]

REL Token Profile based on a non-proprietary Web services specification, along with clarifications and amendments to that specification which promote interoperability.

Dependencies:

[top]

SAML Token Profile based on a non-proprietary Web services specification, along with clarifications and amendments to that specification which promote interoperability.

Dependencies:

[top]

Conformance Claim Attachment Mechanisms catalogues mechanisms that can be used to attach WS-I Profile Conformance Claims to Web services artefacts (e.g., WSDL descriptions, UDDI registries).

Dependencies:

[top]

Reliable Asynchronous Messaging Profile is a profile, in the fashion of the WS-I profiles, that enables, among other things, basic B2B integration scenarios using Web services technologies.

Dependencies:

[top]

Resources

Representational State Transfer 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.

Dependencies: > transaction > security > messaging

[top]

Resource Representation SOAP Header Block allows SOAP message recipients to access cached representations of resources.

Dependencies: > transaction > security > messaging

[top]

WS-Transfer describes a general SOAP-based protocol for accessing XML representations of Web service-based resources.

Dependencies: > transaction > security > messaging

[top]

WS-Enumeration 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.

Dependencies: > transaction > security > messaging

[top]

Web Services Resource Framework defines a family of specifications for accessing stateful resources using Web services.

Dependencies: > transaction > security > messaging

[top]

WS-BaseFaults 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.

Dependencies: > transaction > security > messaging

[top]

WS-ServiceGroup defines a means by which Web services and WS-Resources can be aggregated or grouped together for a domain specific purpose.

Dependencies: > transaction > security > messaging

[top]

WS-ResourceProperties 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.

Dependencies: > transaction > security > messaging

[top]

WS-ResourceLifetime 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.

Dependencies: > transaction > security > messaging

[top]

Management

Web Service Distibuted Management: Management Using Web Services (WSDM-MUWS) 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.

Dependencies: > resource > security > messaging

[top]

Web Service Distibuted Management: Management Of Web Services (WSDM-MOWS) addresses management of the components that form the network, the Web services endpoints, using Web services protocols.

Dependencies: > resource > security > messaging

[top]

WS-Management describes a general SOAP-based protocol for managing systems such as PCs, servers, devices, Web services and other applications, and other manageable entities.

Dependencies: > metadata > security > messaging

[top]

Servcie Modeling Language (SML) is used to model complex IT services and systems, including their structure, constraints, policies, and best practices.

Dependencies: > resource > security > messaging

[top]

Presentation

Web Services for Remote Portlets (WSRP) 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.

Dependencies: > reliablity > security > messaging

[top]