This page summarizes the relationships among specifications, whether they are finished standards or drafts. Below, each title
links to the most recent version of a document.
For related introductory information, see: Protocols, Protocols.
Completed Work
W3C Recommendations have
been reviewed by W3C Members, by software developers, and by other
W3C groups and interested parties, and are endorsed by the
Director as Web Standards. Learn more about the W3C Recommendation
Track.
Group Notes are not standards and do not
have the same level of W3C endorsement.
Standards
|
2011-12-13
|
translations
·
errata
This specification defines two WS-Policy assertions that can be
used to advertise the requirement to use a certain version of SOAP
in message exchanges.
|
|
2007-04-27
|
translations
·
errata
SOAP Version 1.2 Part 0: Primer (Second Edition) is a
non-normative document intended to provide an easily understandable
tutorial on the features of SOAP Version 1.2. In particular, it
describes the features through various usage scenarios, and is
intended to complement the normative text contained in Part 1
and Part 2 of
the SOAP 1.2 specifications. This second edition includes
additional material on the SOAP Message Transmission Optimization
Mechanism (MTOM), the XML-binary Optimized Packaging (XOP) and the
Resource Representation SOAP Header Block (RRSHB)
specifications.
|
|
2007-04-27
|
translations
·
errata
SOAP Version 1.2 is a lightweight protocol intended for
exchanging structured information in a decentralized, distributed
environment. "Part 1: Messaging Framework" defines, using XML
technologies, an extensible messaging framework containing a
message construct that can be exchanged over a variety of
underlying protocols.
|
|
2007-04-27
|
translations
·
errata
SOAP Version 1.2 is a lightweight protocol intended for
exchanging structured information in a decentralized, distributed
environment. SOAP Version 1.2 Part 2: Adjuncts defines a set of
adjuncts that may be used with SOAP Version 1.2 Part 1: Messaging
Framework. This specification depends on SOAP Version 1.2 Part 1:
Messaging Framework [SOAP Part 1].
|
|
2007-04-27
|
translations
·
errata
This document draws on assertions found in the SOAP Version 1.2
specifications [SOAP Part 1], [SOAP Part 2], and provides a set of tests in
order to show whether the assertions are implemented in a SOAP
processor.
A SOAP 1.2 implementation that passes all of the tests specified
in this document may claim to conform to the SOAP 1.2 Test Suite,
2007 04 27. It is incorrect to claim to be compliant with the SOAP
Version 1.2 specifications merely by passing successfully all the
tests provided in this test suite. It is also incorrect to claim
that an implementation is non compliant with the SOAP Version 1.2
specifications based on its failure to pass one or more of the
tests in this test suite.
|
|
2005-01-25
|
translations
·
errata
This document describes the semantics and serialization of a SOAP
header block for carrying resource representations in SOAP messages.
|
|
2005-01-25
|
translations
·
errata
This document describes an abstract feature and a concrete
implementation of it for optimizing the transmission and/or wire format
of SOAP messages. The concrete implementation relies on the [XML-binary Optimized Packaging] format for carrying SOAP messages.
|
Group Notes
|
2007-07-02
|
SOAP Version 1.2 Part 2 provides a request-response MEP and a
response-only MEP. This, the SOAP 1.2 Part 3, provides a one-way
MEP.
|
|
2006-03-21
|
SOAP Version 1.1 provides an HTTP binding for exchanging a
request and a response. This binding provides a "request optional
response" refinement that enables an HTTP response with status code
202 to have a SOAP envelope or to be empty.
|
|
2004-06-08
|
This document defines a SOAP feature that represents an abstract model
for SOAP attachments. It provides the basis for the creation of SOAP
bindings that transmit such attachments along with a SOAP envelope, and
provides for reference of those attachments from the envelope. SOAP
attachments are described using the notion of a compound document
structure consisting of a primary SOAP message part and zero or more
related documents parts known as attachments.
|
|
2003-10-08
|
SOAP 1.2 intermediaries have some license when reserializing
messages that pass through them. This document defines a
transformation algorithm that renders all semantically equivalent
SOAP messages identically. The transformation may be used in
conjunction with an XML canonicalization algorithm prior to the
generation of a message digest in producing XML digital signatures
that are sufficiently robust to survive passage through one or more
SOAP intermediaries.
|
|
2003-07-30
|
This document describes the SOAP Usage Scenarios and how they
may be implemented using the SOAP 1.2 specification.
|
|
2003-07-28
|
This document describes the XML Protocol Working Group's
requirements for the XML Protocol (XMLP) specification.
|
|
2002-07-03
|
This document is meant to be an illustration of the SOAP 1.2
Protocol Binding Framework applied to a well known internet
transport mechanism, Email, specifically rfc2822.
|
Drafts
Below are draft documents:
Proposed Recommendations.
Some of these may become Web Standards through the W3C Recommendation Track
process. Others may be published as Group Notes or
become obsolete specifications.
Proposed Recommendations
|
2011-12-08
|
This document specifies how SOAP should bind to a messaging
system that supports the Java Message Service (JMS)
[Java Message Service]. Binding is specified for both SOAP 1.1
[SOAP 1.1] and SOAP 1.2 [SOAP 1.2 Messaging Framework]
using the SOAP 1.2 Protocol Binding Framework.
|
Obsolete Specifications
These specifications have either been superseded by others,
or have been abandoned. They remain available for archival
purposes, but are not intended to be used.
Retired
|
2007-09-18
|
This specification describes a domain-specific policy assertion
that indicates endpoint support of the optimized MIME
multipart/related serialization of SOAP messages defined in section
3 of the SOAP Message Transmission Optimization Mechanism [MTOM] specification. This policy assertion can be
specified within a policy alternative as defined in Web Services
Policy 1.5 - Framework [WS-Policy] and
attached to a WSDL description as defined in Web Services Policy
1.5 - Attachment [WS-PolicyAttachment].
|
|
2004-06-08
|
This document records the use cases and specifies the
requirements for optimizing the processing and serialization of SOAP
messages.
|
|
2003-02-20
|
This document describes an Abstract Model of XML Protocol.
The challenge of crafting a protocol specification is to create
a description of behaviour that is not tied to any particular
approach to implementation. There is a need to abstract away from
some of the messy implementation details of buffer management, data
representation and specific APIs. However, in order to describe the
behaviour of a protocol one has to establish a set of (useful)
concepts that can be used in that description. An abstract model is
one way to establish a consistent set of concepts. An abstract
model is a tool for the description of complex behaviour — it
is not a template for an implementation... although it should not
stray so far away from reality that it is impossible to recognise
how the required behaviours would be implemented.
|
W3C
