W3C
Web Services Addressing 1.0 - SOAP Binding
W3C Working Draft 31 March 2005
This version:
http://www.w3.org/TR/2005/WD-ws-addr-soap-20050331
Latest version:
http://www.w3.org/TR/ws-addr-soap
Previous versions:
http://www.w3.org/TR/2005/WD-ws-addr-soap-20050215
Editors:
Martin Gudgin, Microsoft Corp
Marc Hadley, Sun Microsystems, Inc
This document is also available in these non-normative formats: postscript, PDF
, XML, and plain text.
Copyright ? 2005 W3C^? (MIT, ERCIM, Keio), All Rights Reserved. W3C liability,
trademark and document use rules apply.
-------------------------------------------------------------------------------
Abstract
Web Services Addressing provides transport-neutral mechanisms to address Web
services and messages. Web Services Addressing 1.0 - SOAP Binding (this
document) defines the binding of the abstract properties defined in Web
Services Addressing 1.0 - Core to SOAP Messages.
Status of this Document
This section describes the status of this document at the time of its
publication. Other documents may supersede this document. A list of current W3C
publications and the latest revision of this technical report can be found in
the W3C technical reports index at http://www.w3.org/TR/.
This is the Last Call Working Draft of the Web Services Addressing 1.0 - SOAP
Binding specification for review by W3C members and other interested parties.
It has been produced by the Web Services Addressing Working Group (WG), which
is part of the W3C Web Services Activity.
If the feedback is positive, the Working Group plans to submit this
specification for consideration as a W3C Candidate Recommendation. Comments on
this document are invited and are to be sent to the public
public-ws-addressing-comments@w3.org mailing list ( public archive). Comments
can be sent until 11 May 2005.
A diff-marked version against the previous version of this document is
available. For a detailed list of changes since the last publication of this
document, please refer to appendix B. Change Log. Issues about this document
are documented in the Last Call issues list maintained by the Working Group.
Discussion of this document takes place on the public-ws-addressing@w3.org
mailing list (public archive).
This document was produced under the 5 February 2004 W3C Patent Policy. The
Working Group maintains a public list of patent disclosures relevant to this
document; that page also includes instructions for disclosing [and excluding] a
patent. An individual who has actual knowledge of a patent which the individual
believes contains Essential Claim(s) with respect to this specification should
disclose the information in accordance with section 6 of the W3C Patent Policy.
Publication as a Working Draft does not imply endorsement by the W3C
Membership. This is a draft document and may be updated, replaced or obsoleted
by other documents at any time. It is inappropriate to cite this document as
other than work in progress.
+-----------------------------------------------------------------------------+
|Editorial note | |
|-----------------------------------------------------------------------------|
|The Web Services Addressing Working Group has decided to use XML Schema, |
|where appropriate, to describe constructs defined in this specification. Note|
|that this restricts use of Web Services Addressing to XML 1.0. |
+-----------------------------------------------------------------------------+
-------------------------------------------------------------------------------
Table of Contents
1. Introduction
1.1 Notational Conventions
1.2 Namespaces
2. SOAP 1.2 Addressing 1.0 Feature
2.1 Feature Name
2.2 Description
2.3 Properties
2.4 Interactions with Other SOAP Features
3. SOAP 1.2 Addressing 1.0 Module
3.1 Module Name
3.2 Description
3.3 Binding Message Addressing Properties
4. SOAP 1.1 Addressing 1.0 Extension
4.1 Extension Name
4.2 Description
5. Faults
5.1 Invalid Message Addressing Property
5.2 Message Addressing Property Required
5.3 Destination Unreachable
5.4 Action Not Supported
5.5 Endpoint Unavailable
6. Security Considerations
6.1 Additional Considerations for SOAP Intermediaries
7. References
Appendices
A. Acknowledgements (Non-Normative)
B. Change Log (Non-Normative)
B.1 Changes Since Second Working Draft
B.2 Changes Since First Working Draft
B.3 Changes Since Submission
-------------------------------------------------------------------------------
1. Introduction
Web Services Addressing 1.0 - Core[WS-Addressing-Core] defines a set of
abstract properties and an XML Infoset [XML Information Set] representation
thereof to reference Web service endpoints and to facilitate end-to-end
addressing of endpoints in messages. Web Services Addressing 1.0 - SOAP Binding
(this document) defines the binding of the abstract properties defined in Web
Services Addressing 1.0 - Core to SOAP Messages.
The following example illustrates the use of these mechanisms in a SOAP 1.2
message being sent from http://example.com/business/client1 to http://
example.com/fabrikam/Purchasing:
Example 1-1. Use of message addressing properties in a SOAP 1.2 message.
(001)
(002)
(003)
(004) http://example.com/6B29FC40-CA47-1067-B31D-00DD010662DA
(005)
(006)
(007) http://example.com/business/client1
(008)
(009) http://example.com/fabrikam/Purchasing
(010) http://example.com/fabrikam/SubmitPO
(011)
(012)
(013) ...
(014)
(015)
Lines (002) to (011) represent the header of the SOAP message where the
mechanisms defined in the specification are used. The body is represented by
lines (012) to (014).
Lines (003) to (010) contain the message addressing properties serialized as
SOAP header blocks. Specifically, lines (003) to (005) specify the identifier
for this message and lines (006) to (008) specify the endpoint to which replies
to this message should be sent as an Endpoint Reference. Line (009) specifies
the address URI of the ultimate receiver of this message. Line (010) specifies
an Action IRI identifying expected semantics.
1.1 Notational Conventions
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
interpreted as described in RFC 2119 [IETF RFC 2119].
When describing abstract data models, this specification uses the notational
convention used by XML Infoset [XML Information Set]. Specifically, abstract
property names always appear in square brackets (e.g., [some property]).
When describing concrete XML schemas [XML Schema Structures, XML Schema
Datatypes], this specification uses the notational convention of WS-Security [
WS-Security]. Specifically, each member of an element's [children] or
[attributes] property is described using an XPath-like notation (e.g., /
x:MyHeader/x:SomeProperty/@value1). The use of {any} indicates the presence of
an element wildcard (). The use of @{any} indicates the presence of an
attribute wildcard ().
1.2 Namespaces
This specification uses a number of namespace prefixes throughout; they are
listed in Table 1-1. Note that the choice of any namespace prefix is arbitrary
and not semantically significant (see [XML Namespaces ]).
Table 1-1. Prefixes and Namespaces used in this
specification
+------------------------------------------------+
|Prefix|Namespace |
|------+-----------------------------------------|
|S |http://www.w3.org/2003/05/soap-envelope |
|------+-----------------------------------------|
|S11 |http://schemas.xmlsoap.org/soap/envelope |
|------+-----------------------------------------|
|wsa |http://www.w3.org/2005/03/addressing |
|------+-----------------------------------------|
|wsaw |http://www.w3.org/2005/03/addressing/wsdl|
|------+-----------------------------------------|
|xs |http://www.w3.org/2001/XMLSchema |
+------------------------------------------------+
WS-Addressing is defined in terms of the XML Information Set [XML Information
Set]. WS-Addressing is conformant to the SOAP 1.2 [SOAP 1.2 Part 1: Messaging
Framework] processing model and is also compatible with SOAP 1.1[SOAP 1.1] for
backwards compatibility. WS-Addressing may be used with WSDL [WSDL 2.0]
described services as described in Web Services Addressing 1.0 - WSDL Binding[
WS-Addressing-WSDL]. The examples in this specification use an XML 1.0 [XML 1.0
] representation but this is not a requirement.
All information items defined by this specification are identified by the XML
namespace URI [XML Namespaces] "http://www.w3.org/2005/03/addressing". A
normative XML Schema [XML Schema Structures, XML Schema Datatypes] document can
be obtained by dereferencing the XML namespace URI.
2. SOAP 1.2 Addressing 1.0 Feature
This section defines the SOAP 1.2 Addressing 1.0 Feature.
2.1 Feature Name
The SOAP 1.2 Addressing 1.0 Feature is named using the following IRI:
* http://www.w3.org/2005/03/addressing/feature
2.2 Description
The SOAP 1.2 Addressing 1.0 Feature provides a SOAP-specific expression of the
abstract message addressing properties defined by Web Services Addressing 1.0 -
Core[WS-Addressing-Core].
This feature may be used with any SOAP MEP. A binding that supports this
feature MUST provide a means to transmit the properties listed above with a
message and to reconstitute their values on receipt of a message.
2.3 Properties
The SOAP 1.2 Addressing 1.0 Feature defines the following properties:
http://www.w3.org/2005/03/addressing/feature/Destination
Corresponds to the abstract [destination] property.
http://www.w3.org/2005/03/addressing/feature/SourceEndpoint
Corresponds to the abstract [source endpoint] property.
http://www.w3.org/2005/03/addressing/feature/ReplyEndpoint
Corresponds to the abstract [reply endpoint] property.
http://www.w3.org/2005/03/addressing/feature/FaultEndpoint
Corresponds to the abstract [fault endpoint] property.
http://www.w3.org/2005/03/addressing/feature/MessageId
Corresponds to the abstract [message id] property.
http://www.w3.org/2005/03/addressing/feature/Relationship
Corresponds to the abstract [relationship] property.
http://www.w3.org/2005/03/addressing/feature/ReferenceParameters
Corresponds to the abstract [reference parameters] property.
http://www.w3.org/2005/03/addressing/feature/Action
Corresponds to the abstract [action] property.
2.4 Interactions with Other SOAP Features
If the http://www.w3.org/2003/05/soap/features/action/Action property of the
SOAP Action featureSOAP 1.2 Part 2: Adjuncts has a value, then the value of the
http://www.w3.org/2005/03/addressing/feature/Action property of the SOAP 1.2
Addressing 1.0 feature MUST be identical to it.
3. SOAP 1.2 Addressing 1.0 Module
The SOAP 1.2 Addressing 1.0 Module defines a set of SOAP header blocks to
support the SOAP 1.2 Addressing 1.0 Feature described in 2. SOAP 1.2 Addressing
1.0 Feature. To ensure interoperability with a broad range of devices, all
conformant implementations that include support for SOAP 1.2 MUST support the
SOAP 1.2 Addressing 1.0 Module.
3.1 Module Name
The SOAP 1.2 Addressing 1.0 Module is identified using the following IRI:
* http://www.w3.org/2005/03/addressing/module
3.2 Description
The SOAP 1.2 Addressing 1.0 Feature (see 2. SOAP 1.2 Addressing 1.0 Feature)
defines a set of SOAP properties and their correspondence to the abstract
message addressing properties defined by Web Services Addressing 1.0 - Core[
WS-Addressing-Core]. The SOAP 1.2 Addressing 1.0 Module uses the XML Infoset
representation of the abstract message addressing properties defined in Web
Services Addressing 1.0 - Core.
When sending a message each property is represented using the appropriate
element information item as a SOAP header block. The resulting header blocks
are targetted at the ultimate recipient in the SOAP message path (note that
extensions to WS-Addressing could be written to specify different targetting).
3.3 Binding Message Addressing Properties describes additional processing
required when binding message addressing properties to SOAP header blocks.
When receiving a message, the abstract properties are populated from their
corresponding element information items in the message. Note that the message
addressing properties gathered by an intermediary when receiving a SOAP message
do not necessarily get replayed as MAPs when resending the message along the
message path.
3.3 Binding Message Addressing Properties
When a message is be addressed to an endpoint, the values of the SOAP 1.2
Addressing 1.0 Feature properties are mapped to the message as SOAP header
blocks with the following additional modifications:
* The value of the http://www.w3.org/2005/03/addressing/feature/
ReferenceParameters property is added to the SOAP message header. The
element information item of each [reference parameter] (including all of
its [children], [attributes] and [in-scope namespaces]) is added as a SOAP
header block in the new message.
* Each header block added as a result of the above rule is annotated with a
wsa:isReferenceParameter attribute whose value is "true".
* Each property that is of type IRI MUST be serialized as an absolute IRI in
the SOAP message.
The following example shows how the SOAP 1.2 Addressing 1.0 Module is used to
construct a message addressed to the endpoint:
Example 3-1. Example endpoint reference.
http://example.com/fabrikam/acct
fabrikam:Inventory
123456789
ABCDEFG
The address value is copied in the "To" header block and the "CustomerKey" and
"ShoppingCart" elements are copied literally as a header blocks in a SOAP
message addressed to this endpoint. The resulting SOAP message would look as
follows:
Example 3-2. Example endpoint reference mapped to SOAP message header blocks.
...
http://example.com/fabrikam/acct
...
123456789
ABCDEFG
...
...
4. SOAP 1.1 Addressing 1.0 Extension
The SOAP 1.1 Addressing 1.0 Extension defines a set of SOAP header blocks to
support the SOAP 1.2 Addressing 1.0 Feature described in 2. SOAP 1.2 Addressing
1.0 Feature. To ensure interoperability with a broad range of devices, all
conformant implementations that include support for SOAP 1.1 MUST support the
SOAP 1.1 Addressing 1.0 Extension. This SOAP 1.1 extension is provided for
backwards compatibility only.
4.1 Extension Name
The SOAP 1.1 Addressing 1.0 Extension is identified using the following IRI:
* http://www.w3.org/2005/03/addressing/module
4.2 Description
The SOAP 1.2 Addressing 1.0 Feature (see 2. SOAP 1.2 Addressing 1.0 Feature)
defines a set of SOAP properties and their correspondence to the abstract
message addressing properties defined by Web Services Addressing 1.0 - Core[
WS-Addressing-Core]. The SOAP 1.1 Addressing 1.0 Extension uses the XML Infoset
representation of the abstract message addressing properties defined in Web
Services Addressing 1.0 - Core and binds each element information item to a
SOAP header block. The SOAP 1.1 Addressing 1.0 Extension operates as described
in 3. SOAP 1.2 Addressing 1.0 Module with the following exceptions:
SOAP Action
Use of the SOAPAction HTTP header is required when using the SOAP 1.1 HTTP
binding. The value of the SOAPAction HTTP header SHOULD be identical to the
value of the http://www.w3.org/2005/03/addressing/feature/Action property
of the Web Services Addressing 1.0 feature.
5. Faults
The faults defined in this section are generated if the condition stated in the
preamble in each subsection is met.
Endpoints compliant with this specification MUST include the required message
addressing properties serialized as SOAP headers in all fault messages. Fault
messages are correlated as replies using the [relationship] property as defined
in Section 3. The [action] property below designates WS-Addressing fault
messages:
http://www.w3.org/2005/03/addressing/fault
The definitions of faults use the following properties:
[Code] The fault code.
[Subcode] The fault subcode.
[Reason] The English language reason element.
[Detail] The detail element. If absent, no detail element is defined for the
fault.
The properties above bind to a SOAP 1.2 fault as follows:
Example 5-1. Binding of fault properties to SOAP 1.2 messages.
http://www.w3.org/2005/03/addressing/fault
[Code]
[Subcode]
[Reason]
[Detail]
The SOAP 1.1 fault is less expressive and map only [Subcode] and [Reason].
These the properties bind to a SOAP 1.1 fault as follows:
Example 5-2. Binding of fault properties to SOAP 1.1 messages.
[Subcode]
[Reason]
5.1 Invalid Message Addressing Property
A message information property cannot be processed.
[Code] S:Sender
[Subcode] wsa:InvalidMessageAddressingProperty
[Reason] A message addressing property is not valid and the message cannot be
processed. The validity failure can be either structural or semantic, e.g. a
[destination] that is not an IRI or a [relationship] to a [message id] that was
never issued.
[Detail] [invalid property]
5.2 Message Addressing Property Required
A required message addressing property is absent.
[Code] S:Sender
[Subcode] wsa:MessageAddressingPropertyRequired
[Reason] A required message addressing property is not present.
[Detail] [Missing Property QName]
5.3 Destination Unreachable
No endpoint can be found capable of acting in the role of the [destination]
property.
[Code] S:Sender
[Subcode] wsa:DestinationUnreachable
[Reason] No route can be determined to reach [destination].
[Detail] empty
5.4 Action Not Supported
The [action] property in the message is not supported at this endpoint.
The contents of this fault are as follows:
[Code] S:Sender
[Subcode] wsa:ActionNotSupported
[Reason] The [action] cannot be processed at the receiver.
[Detail] [action]
5.5 Endpoint Unavailable
The endpoint is unable to process the message at this time either due to some
transient issue or a permanent failure.
The endpoint may optionally include a RetryAfter parameter in the detail. The
source should not retransmit the message until this duration has passed.
[Code] S:Receiver
[Subcode] wsa:EndpointUnavailable
[Reason] The endpoint is unable to process the message at this time.
[Detail] [xs:NonNegativeInteger]
The following describes the attributes and elements listed above:
/wsa:RetryAfter
This element (of type xs:nonNegativeInteger) is a suggested minimum
duration in milliseconds to wait before retransmitting the message. If this
element is omitted from the detail, the value is infinite.
+-------------------------------------------------------------------------+
|Editorial note: M Hadley | |
|-------------------------------------------------------------------------|
|The WG seeks feedback on the choice of nonNegativeInteger for this |
|element. Other types considered included unsignedLong, unsignedInt and |
|duration. |
+-------------------------------------------------------------------------+
/wsa:RetryAfter/@{any}
Optional extensibility attributes that do not affect processing.
6. Security Considerations
WS-Addressing message addressing properties serialized as SOAP headers (wsa:To,
wsa:Action et al.) including those headers present as a result of the
[reference parameters] property SHOULD be integrity protected as explained in
Web Services Addressing 1.0 - Core[WS-Addressing-Core].
When receiving a SOAP message, certain SOAP headers may be resulting from the
serialization of an EPR's [reference parameters] property. The SOAP message
receiver MAY perform additional security and sanity checks to prevent
unintended actions.
6.1 Additional Considerations for SOAP Intermediaries
To avoid breaking signatures, intermediaries MUST NOT change the XML
representation of WS-Addressing headers. Specifically, intermediaries MUST NOT
remove XML content that explicitly indicates otherwise-implied content, and
intermediaries MUST NOT insert XML content to make implied values explicit. For
instance, if a RelationshipType attribute is present with a value of "http://
www.w3.org/2005/03/addressing/reply", an intermediary MUST NOT remove it;
similarly, if there is no RelationshipType attribute, an intermediary MUST NOT
add one.
7. References
[WS-Addressing-Core]
Web Services Addressing 1.0 - Core, M. Gudgin, M. Hadley, Editors.
[WS-Addressing-WSDL]
Web Services Addressing 1.0 - WSDL Binding, M. Gudgin, M. Hadley, Editors.
[WSDL 2.0]
Web Services Description Language 2.0, R. Chinnici, M. Gudgin, J. J.
Moreau, J. Schlimmer, S. Weerawarana, Editors. World Wide Web Consortium, 3
August 2004. This version of the WSDL 2.0 specification is http://
www.w3.org/TR/2004/WD-wsdl20-20040803. The latest version of WSDL 2.0 is
available at http://www.w3.org/TR/wsdl20.
[IETF RFC 2119]
Key words for use in RFCs to Indicate Requirement Levels, S. Bradner,
Author. Internet Engineering Task Force, June 1999. Available at http://
www.ietf.org/rfc/rfc2119.txt.
[RFC 3987]
M. Duerst, M. Suignard, "Internationalized Resource Identifiers (IRIs)",
January 2005. (See http://www.ietf.org/rfc/rfc3987.txt.)
[XML 1.0]
Extensible Markup Language (XML) 1.0 (Third Edition), T. Bray, J. Paoli, C.
M. Sperberg-McQueen, and E. Maler, Editors. World Wide Web Consortium, 4
February 2004. This version of the XML 1.0 Recommendation is http://
www.w3.org/TR/2004/REC-xml-20040204. The latest version of XML 1.0 is
available at http://www.w3.org/TR/REC-xml.
[XML Namespaces]
Namespaces in XML, T. Bray, D. Hollander, and A. Layman, Editors. World
Wide Web Consortium, 14 January 1999. This version of the XML Information
Set Recommendation is http://www.w3.org/TR/1999/REC-xml-names-19990114. The
latest version of Namespaces in XML is available at http://www.w3.org/TR/
REC-xml-names.
[XML Information Set]
XML Information Set, J. Cowan and R. Tobin, Editors. World Wide Web
Consortium, 24 October 2001. This version of the XML Information Set
Recommendation is http://www.w3.org/TR/2001/REC-xml-infoset-20011024. The
latest version of XML Information Set is available at http://www.w3.org/TR/
xml-infoset.
[XML Schema Structures]
XML Schema Part 1: Structures Second Edition, H. Thompson, D. Beech, M.
Maloney, and N. Mendelsohn, Editors. World Wide Web Consortium, 28 October
2004. This version of the XML Schema Part 1 Recommendation is http://
www.w3.org/TR/2004/REC-xmlschema-1-20041028. The latest version of XML
Schema Part 1 is available at http://www.w3.org/TR/xmlschema-1.
[XML Schema Datatypes]
XML Schema Part 2: Datatypes Second Edition, P. Byron and A. Malhotra,
Editors. World Wide Web Consortium, 28 October 2004. This version of the
XML Schema Part 2 Recommendation is http://www.w3.org/TR/2004/
REC-xmlschema-2-20041028. The latest version of XML Schema Part 2 is
available at http://www.w3.org/TR/xmlschema-2.
[SOAP 1.2 Part 1: Messaging Framework]
SOAP Version 1.2 Part 1: Messaging Framework, M. Gudgin, M. Hadley, N.
Mendelsohn, J-J. Moreau, H. Frystyk Nielsen, Editors. World Wide Web
Consortium, 24 June 2003. This version of the "SOAP Version 1.2 Part 1:
Messaging Framework" Recommendation is http://www.w3.org/TR/2003/
REC-soap12-part1-20030624/. The latest version of "SOAP Version 1.2 Part 1:
Messaging Framework" is available at http://www.w3.org/TR/soap12-part1/.
[SOAP 1.2 Part 2: Adjuncts]
SOAP Version 1.2 Part 2: Adjuncts, M. Gudgin, M. Hadley, N. Mendelsohn,
J-J. Moreau, H. Frystyk Nielsen, Editors. World Wide Web Consortium, 24
June 2003. This version of the "SOAP Version 1.2 Part 2: Adjuncts"
Recommendation is http://www.w3.org/TR/2003/REC-soap12-part2-20030624/. The
latest version of "SOAP Version 1.2 Part 2: Adjuncts" is available at http:
//www.w3.org/TR/soap12-part2/.
[SOAP 1.1]
Don Box, et al, Simple Object Access Protocol (SOAP) 1.1, May 2000.
[WS-Security]
OASIS, Web Services Security: SOAP Message Security, March 2004.
A. Acknowledgements (Non-Normative)
This document is the work of the W3C Web Service Addressing Working Group.
Members of the Working Group are (at the time of writing, and by alphabetical
order): Abbie Barbir (Nortel Networks), Rebecca Bergersen (IONA Technologies,
Inc.), Andreas Bj?rlestam (ERICSSON), Ugo Corda (SeeBeyond Technology
Corporation), Francisco Curbera (IBM Corporation), Glen Daniels (Sonic
Software), Paul Downey (BT), Jacques Durand (Fujitsu Limited), Michael Eder
(Nokia), Robert Freund (Hitachi, Ltd.), Yaron Goland (BEA Systems, Inc.),
Martin Gudgin (Microsoft Corporation), Arun Gupta (Sun Microsystems, Inc.),
Hugo Haas (W3C/ERCIM), Marc Hadley (Sun Microsystems, Inc.), David Hull (TIBCO
Software, Inc.), Yin-Leng Husband (HP), Anish Karmarkar (Oracle Corporation),
Paul Knight (Nortel Networks), Philippe Le H?garet (W3C/MIT), Mark Little
(Arjuna Technologies Ltd.), Jonathan Marsh (Microsoft Corporation), Jeff
Mischkinsky (Oracle Corporation), Nilo Mitra (ERICSSON), Eisaku Nishiyama
(Hitachi, Ltd.), Mark Nottingham (BEA Systems, Inc.), Ales Novy (Systinet
Inc.), David Orchard (BEA Systems, Inc.), Mark Peel (Novell, Inc.), Tony Rogers
(Computer Associates), Tom Rutt (Fujitsu Limited), Rich Salz (DataPower
Technology, Inc.), Davanum Srinivas (Computer Associates), Jiri Tejkl (Systinet
Inc.), Greg Truty (IBM Corporation), Steve Vinoski (IONA Technologies, Inc.),
Pete Wenzel (SeeBeyond Technology Corporation), Steve Winkler (SAP AG), ?mit
Yal??nalp (SAP AG), Prasad Yendluri (webMethods, Inc.).
Previous members of the Working Group were: Lisa Bahler (SAIC - Telcordia
Technologies), Marc Goodner (SAP AG), Harris Reynolds (webMethods, Inc.).
The people who have contributed to discussions on public-ws-addressing@w3.org
are also gratefully acknowledged.
B. Change Log (Non-Normative)
B.1 Changes Since Second Working Draft
+-----------------------------------------------------------------------------+
| Date |Editor | Description |
|------------+-------+--------------------------------------------------------|
|2005-03-21 @|mgudgin|Added sentence about SOAP 1.1 to section 4 |
|23:15 | | |
|------------+-------+--------------------------------------------------------|
|2005-03-18 @|mgudgin|s/Addresssing/Addressing |
|23:21 | | |
|------------+-------+--------------------------------------------------------|
|2005-03-10 @|mhadley|Incorporated additional editorial fixes from J. Marsh. |
|03:40 | | |
|------------+-------+--------------------------------------------------------|
|2005-03-10 @|mhadley|Incorporated additional issue resolution text for issues|
|03:16 | |7 and 44 from H. Haas. |
|------------+-------+--------------------------------------------------------|
|2005-03-10 @|mhadley|Incorporated editorial fixes from J. Marsh. |
|02:06 | | |
|------------+-------+--------------------------------------------------------|
|2005-03-09 @|mhadley|Fixed example that didn't reflect the chnage from |
|07:11 | |wsa:Type to wsa:isReferenceParameter |
|------------+-------+--------------------------------------------------------|
|2005-03-08 @|mhadley|Added resolution to issue 53 (schema tweaks) |
|20:50 | | |
|------------+-------+--------------------------------------------------------|
|2005-03-02 @|mhadley|Added resolution to issue 4 |
|21:18 | | |
|------------+-------+--------------------------------------------------------|
|2005-03-02 @|mhadley|Added resolution to issue 7 |
|20:30 | | |
|------------+-------+--------------------------------------------------------|
|2005-03-02 @|mhadley|Added resolution to issues 22 and 51/ |
|19:36 | | |
|------------+-------+--------------------------------------------------------|
|2005-02-28 @|mhadley|Added resolution to issues 24 and 26 |
|22:08 | | |
|------------+-------+--------------------------------------------------------|
|2005-02-27 @|mhadley|Changed URI to IRI where appropriate. |
|19:42 | | |
|------------+-------+--------------------------------------------------------|
|2005-02-17 @|mhadley|Added issue 47 resolution |
|15:37 | | |
|------------+-------+--------------------------------------------------------|
|2005-02-15 @|mhadley|Fixed some references to message information headers to |
|22:06 | |message information properties |
+-----------------------------------------------------------------------------+
B.2 Changes Since First Working Draft
+-----------------------------------------------------------------------------+
| Date |Editor | Description |
|----------+-------+----------------------------------------------------------|
|2005-02-01| |Removed several occurances of the word 'identify' when |
|@ 19:49 |mhadley|used with endpoint references. Replaced with 'reference' |
| | |or 'address' as appropriate. |
|----------+-------+----------------------------------------------------------|
|2005-01-24|mgudgin|Removed spurious reference to section 3.3.2 from Section 3|
|@ 20:22 | | |
|----------+-------+----------------------------------------------------------|
|2005-01-23|mgudgin|Incorporated resolution of issue i008; added wsa:Type |
|@ 21:11 | |attribute to reference parameters |
|----------+-------+----------------------------------------------------------|
|2005-01-20|mgudgin|Removed text from first paragraph of section 3 per |
|@ 13:10 | |resolution of issue i040 |
|----------+-------+----------------------------------------------------------|
|2005-01-16|mgudgin|s/PortType/InterfaceName in certain examples |
|@ 22:41 | | |
|----------+-------+----------------------------------------------------------|
|2004-12-16|mhadley|Added resolution to issue 19 - WSDL version neutrality |
|@ 18:20 | | |
|----------+-------+----------------------------------------------------------|
|2004-12-16|mhadley|Added issue 33 resolution |
|@ 16:50 | | |
|----------+-------+----------------------------------------------------------|
|2004-12-14|mhadley|Switched back to edcopy formatting |
|@ 20:10 | | |
|----------+-------+----------------------------------------------------------|
| | |Enhanced auto-changelog generation to allow specification |
|2004-12-14|mhadley|of data ranges for logs. Split change log to show changes |
|@ 20:02 | |between early draft and first working draft and changes |
| | |since first working draft. |
|----------+-------+----------------------------------------------------------|
|2004-12-14| |Added resolutions for issues 12 (EPR lifecycle), 37 |
|@ 18:13 |mhadley|(relationship from QName to URI) and 39 (spec name |
| | |versioning) |
+-----------------------------------------------------------------------------+
B.3 Changes Since Submission
+-----------------------------------------------------------------------------+
| Date |Editor | Description |
|----------+-------+----------------------------------------------------------|
|2004-11-24|mhadley|Added note that addressing is backwards compatible with |
|@ 15:32 | |SOAP 1.1 |
|----------+-------+----------------------------------------------------------|
|2004-11-23| |Updated titles of examples. Fixed table formatting and |
|@ 21:38 |mhadley|references. Replaced uuid URIs with http URIs in examples.|
| | |Added document status. |
|----------+-------+----------------------------------------------------------|
| | |Second more detailed run through to separate core, SOAP |
|2004-11-07|mhadley|and WSDL document contents. Removed dependency on |
|@ 02:03 | |WS-Policy. Removed references to WS-Trust and |
| | |WS-SecurityPolicy |
|----------+-------+----------------------------------------------------------|
|2004-11-02|mhadley|Removed static change log and added dynamically generated |
|@ 22:25 | |change log from cvs. |
|----------+-------+----------------------------------------------------------|
|2004-10-28|mhadley|Initial cut of separating specification into core, soap |
|@ 17:05 | |and wsdl |
+-----------------------------------------------------------------------------+