2006-05-09 diff-marked version: Web Services Addressing 1.0 - Core

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 the 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 2004 ]. Specifically, each member of an Element Information Item'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 (<xs:any/>). The use of @{any} indicates the presence of an attribute wildcard (<xs:anyAttribute/>).

Where pseudo-schemas are provided for a component, they use BNF-style conventions for attributes and elements: "?" denotes optionality (i.e. zero or one occurrences), "*" denotes zero or more occurrences, "+" one or more occurrences, "[" and "]" are used to form groups, and "|" represents choice. Attributes are conventionally assigned a value which corresponds to their type, as defined in the normative schema. Elements with simple content are conventionally assigned a value which corresponds to the type of their content, as defined in the normative schema. Pseudo schemas do not include extensibility points for brevity.

When defining the cardinality of endpoint reference properties and message addressing properties, this specification uses the following notation: ( n .. m ), where n is the minimum allowed number of occurrences of the property and m is the maximum allowed number of occurrences. When n has the same value as m then exactly that number of occurrences of the property must be present in the associated endpoint reference or message.

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 ]).

WS-Addressing may be used with SOAP [ SOAP 1.2 deleted text: Part 1: Messaging Framework , SOAP 1.1 ] as described in Web Services Addressing 1.0 - SOAP Binding[ WS-Addressing-SOAP WS-Addressing SOAP Binding ]. WS-Addressing may be used with WSDL [ WSDL 2.0 Core Language , WSDL 1.1 ] described services as described in Web Services Addressing 1.0 - WSDL Binding[ WS-Addressing-WSDL WS-Addressing WSDL Binding ]. 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/08/addressing . A normative XML Schema [ XML Schema Structures , XML Schema Datatypes ] document can be obtained by dereferencing the XML namespace URI.

2.1 Information Model for Endpoint References

An endpoint reference is a collection of abstract properties. This specification defines a core set of properties, but it is also possible for other specifications to extend these and/or add other properties. The semantics and XML Infoset representation for any such extension properties will be described in their defining specifications. An endpoint reference consists of the following abstract properties:

[address] : IRI (1..1)

An absolute IRI [ IETF RFC 3987 ] representing the address of the endpoint. This specification introduces two predefined [address] values as shown in Table 2-1 .

Table 2-1. Predefined [address] values

URI	Description
"http://www.w3.org/2005/08/addressing/anonymous"	Some endpoints cannot be located with a meaningful IRI; this URI is used to allow such endpoints to send and receive messages. The precise meaning of this URI is defined by the binding of Addressing to a specific protocol and/or the context in which the EPR is used.
"http://www.w3.org/2005/08/addressing/none"	Messages sent to EPRs whose [address] is this value MUST be discarded (i.e. not sent). This URI is typically used in EPRs that designate a reply or fault endpoint (see section 3.1 Abstract Property Definitions ) to indicate that no reply or fault message should be sent.

[reference parameters] : xs:any (0..unbounded).

A reference may contain a number of individual parameters that are associated with the endpoint to facilitate a particular interaction. Reference parameters are namespace-qualified element information items that are required to properly interact with the endpoint. Reference parameters are provided by the issuer of the endpoint reference and are assumed to be opaque to other users of an endpoint reference. The binding of reference parameters to messages depends upon the protocol binding used to interact with the endpoint - Web Services Addressing 1.0 - SOAP Binding[ WS-Addressing-SOAP WS-Addressing SOAP Binding ] describes the default binding for the SOAP protocol.

The reference parameters are not ordered. No significance can be attributed to any order in which they may appear, because they may be bound to a message in a way which does not preserve that ordering.

[metadata] : xs:any (0..unbounded)

A reference may contain metadata that describes the behavior, policies and capabilities of the endpoint. Metadata may be included in an endpoint reference to facilitate easier processing by a user of an endpoint reference, or because the metadata was dynamically generated.

The metadata embedded in an EPR is not necessarily a complete statement of the metadata pertaining to the endpoint. Moreover, while embedded metadata is necessarily valid at the time the EPR is initially created it may become stale at a later point in time.

To deal with conflicts between the embedded metadata of two EPRs that have the same [address], or between embedded metadata and metadata obtained from a different source, or to ascertain the current validity of embedded metadata, mechanisms that are outside of the scope of this specification, such as EPR life cycle information (see 2.4 Endpoint Reference Lifecycle ) or retrieval of metadata from an authoritative source, SHOULD be used.

2.2 Endpoint Reference XML Infoset Representation

This section defines an XML Infoset-based representation for an endpoint reference as both an XML type (wsa:EndpointReferenceType) and as an XML element (<wsa:EndpointReference>). For brevity simple XML terms are used, e.g. 'element' instead of 'element information item' - this is not intended to constrain use of the constructs defined in this section to textual XML representations.

The wsa:EndpointReferenceType type is used wherever a Web service endpoint is referenced. The following describes the contents of this type:

<wsa:EndpointReference>
    <wsa:Address>xs:anyURI</wsa:Address>
    <wsa:ReferenceParameters>xs:any*</wsa:ReferenceParameters> ?
    <wsa:Metadata>xs:any*</wsa:Metadata>?
</wsa:EndpointReference>

The following describes the attributes and elements listed in the schema overview above:

/wsa:EndpointReference

This represents some element of type wsa:EndpointReferenceType. This example uses the predefined <wsa:EndpointReference> element, but any element of type wsa:EndpointReferenceType may be used.

/wsa:EndpointReference/wsa:Address

This REQUIRED element (whose content is of type xs:anyURI) specifies the [address] property of the endpoint reference.

/wsa:EndpointReference/wsa:Address/@{any}

This is an extensibility mechanism to allow additional attributes to be specified.

/wsa:EndpointReference/wsa:ReferenceParameters

This OPTIONAL element may contain elements from any namespace. Such elements form the [reference parameters] of the reference.

/wsa:EndpointReference/wsa:ReferenceParameters/@{any}

This is an extensibility mechanism to allow additional attributes to be specified.

/wsa:EndpointReference/wsa:ReferenceParameters/{any}

Each element information item found in [reference parameters] (including all of that elements [children], [attributes] and [in-scope namespaces]) is represented as is.

/wsa:EndpointReference/wsa:Metadata

This OPTIONAL element may contain elements from any namespace. Such elements form the metadata that is relevant to the interaction with the endpoint.

/wsa:EndpointReference/wsa:Metadata/{any}

Each child element of Metadata represents an individual piece of metadata.

/wsa:EndpointReference/wsa:Metadata/{@any}

This is an extensibility mechanism to allow additional attributes to be specified. Some examples in this specification show use of this extensibility point to include a wsdlLocation[ WSDL 2.0 Core Language ] attribute to provide a hint for the location of a WSDL description of the service deployed at the endpoint.

/wsa:EndpointReference/{any}

This is an extensibility mechanism to allow additional elements to be specified.

/wsa:EndpointReference/@{any}

This is an extensibility mechanism to allow additional attributes to be specified.

The following shows an example endpoint reference. This element references the the endpoint at the URI "http://example.com/fabrikam/acct".

<wsa:EndpointReference xmlns:wsa="http://www.w3.org/2005/08/addressing">
   <wsa:Address>http://example.com/fabrikam/acct</wsa:Address>
</wsa:EndpointReference>
      

2.3 Endpoint Reference Comparison

This specification provides no concept of endpoint identity and therefore does not provide any mechanism to determine equality or inequality of EPRs and does not specify the consequences of their equality or inequality. However, note that it is possible for other specifications to provide a comparison function that is applicable within a limited scope.

2.4 Endpoint Reference Lifecycle

This specification does not define a lifecycle model for endpoint references and does not address the question of time-to-live for endpoint references. Other specifications that build on or use WS-Addressing may define a lifecycle model for endpoint references created according to that specification.

2.5 Endpoint Reference Extensibility

As noted in 2.2 Endpoint Reference XML Infoset Representation endpoint references are extensible. When extension attributes or elements appear as part of an endpoint reference, the processing model for such extensions is defined by the specification for those extensions. Software that processes endpoint references can safely ignore any such extensions that it does not recognize or understand.

Extension elements and attributes MAY add additional properties to an endpoint reference in addition to those specified in 2.1 Information Model for Endpoint References . Endpoint reference extensions MAY modify the value of one or more existing properties of an endpoint reference. Extensions MAY modify the rules for binding endpoint reference properties to message addressing properties, or otherwise indicate that a different binding be used.

Note that this ability to modify existing properties and binding behavior, when coupled with the fact that software can ignore unknown or unrecognized extensions, may result in a difference in behavior depending on whether such an extended endpoint reference is processed by software that understands the extension(s). When designing endpoint reference extensions designers should consider that standard processing per this specification will prevail in cases where their extension is not recognized or understood.

2.6 Identifying Resources in an Endpoint Reference

The Architecture of the World Wide Web, Volume One [ AoWWW ] recommends [ AoWWW , Section 2] the use of URIs to identify resources. Using abstract properties of an EPR other than [destination] to identify resources is contrary to this recommendation. In certain circumstances, such a use of additional properties may be convenient or beneficial; however, when building systems, the benefits or convenience of identifying a resource using reference parameters should be carefully weighed against the benefits of identifying a resource solely by URI as explained in [ AoWWW , Section 2.1] of the Web Architecture.

3.1 Abstract Property Definitions

Message addressing properties collectively augment a message with the following abstract properties to support one-way, request-response, and other interaction patterns:

[destination] : IRI (1..1)

An absolute IRI representing the address of the intended receiver of this message.

[source endpoint] : endpoint reference (0..1)

Reference to the endpoint from which the message originated.

[reply endpoint] : endpoint reference (0..1)

An endpoint reference for the intended receiver for replies to this message.

[fault endpoint] : endpoint reference (0..1)

An endpoint reference for the intended receiver for faults related to this message.

[action] : IRI (1..1)

An absolute IRI that uniquely identifies the semantics implied by this message.

It is RECOMMENDED that the value of the [action] property is an IRI identifying an input, output, or fault message within a WSDL interface or port type. An action may be explicitly or implicitly associated with the corresponding WSDL definition. Web Services Addressing 1.0 - WSDL Binding[ WS-Addressing-WSDL WS-Addressing WSDL Binding ] describes the mechanisms of association.

[message id] : IRI (0..1)

An absolute IRI that uniquely identifies the message. When present, it is the responsibility of the sender to ensure that each message is uniquely identified. The behavior of a receiver when receiving a message that contains the same [message id] as a previously received message is unconstrained by this specification.

[relationship] : (IRI, IRI) (0..unbounded)

A pair of values that indicate how this message relates to another message. The type of the relationship is identified by an absolute IRI. The related message is identified by an absolute IRI that corresponds to the related message's [message id] property. The message identifier IRI may refer to a specific message, or be the following pre-defined URI that means "unspecified message": "http://www.w3.org/2005/08/addressing/unspecified"

This specification has one predefined relationship type as shown in Table 3-1 .

Table 3-1. Predefined [relationship] values

URI	Description
"http://www.w3.org/2005/08/addressing/reply"	Indicates that this is a reply to the message identified by the [message id] IRI.

[reference parameters] : xs:any (0..unbounded).

Corresponds to the value of the [reference parameters] property of the endpoint reference to which the message is addressed.

The [destination] and [action] properties indicate the target processing location and the verb or intent of the message respectively. The values of these properties can be used to facilitate the dispatch of messages.

A binding of WS-Addressing message addressing properties MUST reflect the property cardinality shown above. Web Services Addressing 1.0 - SOAP Binding[ WS-Addressing-SOAP WS-Addressing SOAP Binding ] defines such a binding for the SOAP [ SOAP 1.2 deleted text: Part 1: Messaging Framework , SOAP 1.1 ] protocol.

3.2 XML Infoset Representation of Message Addressing Properties

The following shows the XML Infoset representation of the message addressing properties defined in 3.1 Abstract Property Definitions :

<wsa:To>xs:anyURI</wsa:To> ?
<wsa:From>wsa:EndpointReferenceType</wsa:From> ?
<wsa:ReplyTo>wsa:EndpointReferenceType</wsa:ReplyTo> ?
<wsa:FaultTo>wsa:EndpointReferenceType</wsa:FaultTo> ?
<wsa:Action>xs:anyURI</wsa:Action>
<wsa:MessageID>xs:anyURI</wsa:MessageID> ?
<wsa:RelatesTo RelationshipType="xs:anyURI"?>xs:anyURI</wsa:RelatesTo> *
<wsa:ReferenceParameters>xs:any*</wsa:ReferenceParameters> ?
                    

The following describes the attributes and elements listed in the schema overview above:

/wsa:To

This OPTIONAL element (whose content is of type xs:anyURI) provides the value for the [destination] property. If this element is NOT present then the value of the [destination] property is "http://www.w3.org/2005/08/addressing/anonymous".

/wsa:From

This OPTIONAL element (of type wsa:EndpointReferenceType) provides the value for the [source endpoint] property.

/wsa:ReplyTo

This OPTIONAL element (of type wsa:EndpointReferenceType) provides the value for the [reply endpoint] property. If this element is NOT present then the value of the [address] property of the [reply endpoint] EPR is "http://www.w3.org/2005/08/addressing/anonymous".

/wsa:FaultTo

This OPTIONAL element (of type wsa:EndpointReferenceType) provides the value for the [fault endpoint] property.

/wsa:Action

This REQUIRED element (whose content is of type xs:anyURI) conveys the value of the [action] property.

/wsa:MessageID

This OPTIONAL element (whose content is of type xs:anyURI) conveys the [message id] property.

/wsa:RelatesTo

This OPTIONAL (repeating) element information item contributes one abstract [relationship] property value, in the form of an (IRI, IRI) pair. The content of this element (of type xs:anyURI) conveys the [message id] of the related message.

/wsa:RelatesTo/@RelationshipType

This OPTIONAL attribute (of type xs:anyURI) conveys the relationship type as an IRI. When absent, the implied value of this attribute is "http://www.w3.org/2005/08/addressing/reply".

/[reference parameters]*

Each element information item found in [reference parameters] (including all of that elements [children], [attributes] and [in-scope namespaces]) is represented as is.

Note that each of the element information items described above allows attribute wildcards for future extensibility. A message processor may safely ignore any extension attribute it does not recognize. Attribute extensibility allows use of xml:id[ xml:id ] for identification of these elements if desired.

3.3 Sending a Message to an EPR

This section describes the process of constructing a message in accordance to an EPR.

1. If the EPR's [address] property is "http://www.w3.org/2005/08/addressing/none" the message is discarded, if not then populate the message's message addressing properties:

   • [action]: this property is required, but is not populated from the EPR.

   • [destination]: this property takes the value of the EPR's [address] property.

   • [reference parameters]: this property takes the value of the selected EPR's [reference parameters] property

3.4 Formulating a Reply Message

This section specifies the WS-Addressing-specific rules for creating a reply or fault message related to another message.

1. Select the appropriate EPR:

   • If the reply is a normal message, select the EPR from the related message's [reply endpoint] message addressing property.

     Note:

     The [reply endpoint] message addressing property will always be present when using the XML Infoset representation since, in the absence of a wsa:ReplyTo element, the value of the [reply endpoint] message addressing property defaults to an EPR with an [address] property of "http://www.w3.org/2005/08/addressing/anonymous" - see section 3.2 XML Infoset Representation of Message Addressing Properties .

     If the [reply endpoint] message addressing property is not present the processor MUST fault. This could only occur when using an alternate representation of message addressing properties.

   • Otherwise, if the reply is a fault message and the related message's [fault endpoint] message addressing property is not empty, select the EPR from that property. If the [fault endpoint] property is empty, select the EPR from the related message's [reply endpoint] message addressing property. Otherwise, if the [reply endpoint] property is empty, the behavior of the recipient of the related message is unconstrained by this specification.

   • In either of the above cases, if the related message lacks a [message id] property, the processor MUST fault.

2. Send the message according to the previous section, but also including:

   • [relationship]: this property MUST include a pair of IRIs as follows; the relationship type is the predefined reply URI "http://www.w3.org/2005/08/addressing/reply" and the related message's identifier is the [message id] property value from the message being replied to; other relationships MAY be expressed in this property

The following example illustrates a message containing message addressing properties serialized as header blocks in a SOAP 1.2 message:

<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
  xmlns:wsa="http://www.w3.org/2005/08/addressing">
  <S:Header> 
  <wsa:MessageID>http://example.com/someuniquestring</wsa:MessageID>
    <wsa:ReplyTo>
      <wsa:Address>http://example.com/business/client1</wsa:Address>
    </wsa:ReplyTo>
    <wsa:To>mailto:fabrikam@example.com</wsa:To>
    <wsa:Action>http://example.com/fabrikam/mail/Delete</wsa:Action>
  </S:Header>
  <S:Body>
    <f:Delete xmlns:f="http://example.com/fabrikam">     
       <maxCount>42</maxCount>
    </f:Delete>
  </S:Body>
</S:Envelope>
      

This message would have the following property values:

• [destination]: "mailto:fabrikam@example.com"

• [reply endpoint]: The endpoint with [address] "http://example.com/business/client1"

• [action]: "http://example.com/fabrikam/mail/Delete"

• [message id]: "http://example.com/someuniquestring"

The following example illustrates a reply to the above message:

<S:Envelope
  xmlns:S="http://www.w3.org/2003/05/soap-envelope" 
  xmlns:wsa="http://www.w3.org/2005/08/addressing">
  <S:Header>
    <wsa:MessageID>http://example.com/someotheruniquestring</wsa:MessageID>
    <wsa:RelatesTo>http://example.com/someuniquestring</wsa:RelatesTo>
    <wsa:To>http://example.com/business/client1</wsa:To>
    <wsa:Action>http://example.com/fabrikam/mail/DeleteAck</wsa:Action>
  </S:Header>
  <S:Body>
    <f:DeleteAck xmlns:f="http://example.com/fabrikam"/>
  </S:Body>
</S:Envelope>
      

This message would have the following property values:

• [destination]: "http://example.com/business/client1"

• [action]: "http://example.com/fabrikam/mail/DeleteAck"

• [message id]: "http://example.com/someotheruniquestring"

• [relationship]: ("http://www.w3.org/2005/08/addressing/reply", "http://example.com/someuniquestring")

4.1 Additional Security Considerations

To prevent information disclosure, EPR issuers should not put sensitive information into the [address] or [reference parameters] properties unless it has been adequately protected against arbitrary disclosure.

Some processors may use [message id] as part of a uniqueness metric in order to detect message replay. Care should be taken to ensure that, for purposes of replay detection, [message id] is composed from data, such as a timestamp, such that a legitimate retransmission of the message is not confused with a replay attack. It is also advisable to use a [message id] that is not predictable, to prevent attackers from constructing and sending an unsolicited reply to a message without having to see the actual message.

<cite> deleted text: <a href= "http://www.w3.org/TR/2004/REC-webarch-20041215/"> Architecture of the World Wide Web, Volume One </cite>, I. Jacobs, N. Walsh, Editors. W3C Recommendation, World Wide Web Consortium, 15 December 2004. This version of the Architecture of the World Wide Web, Volume One Recommendation is at http://www.w3.org/TR/2004/REC-webarch-20041215/. The latest version is available at http://www.w3.org/TR/webarch/ </dd> 5.1 Normative References

[IETF RFC 2119]

Key words for use in RFCs to Indicate Requirement Levels , S. Bradner. RFC, Bradner, Author. Internet Engineering Task Force, June 1999. Available at http://www.ietf.org/rfc/rfc2119.txt.

[IETF RFC 3987]

Internationalized Resource Identifiers (IRIs) M. Duerst, and M. Suignard. RFC, Suignard, Authors. Internet Engineering Task Force, January 2005. Available at 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. deleted text: W3C Recommendation, 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. deleted text: W3C Recommendation, 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]

<a href= "http://www.w3.org/TR/2004/REC-xml-infoset-20040204"> XML Information Set (Second Edition) , J. Cowan and R. Tobin, Editors. deleted text: W3C Recommendation, World Wide Web Consortium, 4 February 2004. This version of the XML Information Set Recommendation is http://www.w3.org/TR/2004/REC-xml-infoset-20040204. The <a href= "http://www.w3.org/TR/xml-infoset"> 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. deleted text: W3C Recommendation, 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. deleted text: W3C Recommendation, 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.

5.2 Other References

[AoWWW]

Architecture of the World Wide Web, Volume One ,I. Jacobs, and N. Walsh, Editors. World Wide Web Consortium, 15 December 2004. This version of the Architecture of the World Wide Web, Volume One Recommendation is at http://www.w3.org/TR/2004/REC-webarch-20041215/. The latest version is available at http://www.w3.org/TR/webarch/

[SOAP 1.1]

Simple Object Access Protocol (SOAP) 1.1 ,D. Box, et al, Editors. World Wide Web Consortium, 8 May 2000. Available at http://www.w3.org/TR/2000/NOTE-SOAP-20000508/.

[SOAP 1.2 deleted text: Part 1: Messaging Framework]

SOAP Version 1.2 Part 1: Messaging Framework , M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, and H. Frystyk Nielsen, Editors. W3C Recommendation, World Wide Web Consortium, 24 June 2003. This version of the "SOAP SOAP Version 1.2 Part 1: Messaging Framework" Framework Recommendation is http://www.w3.org/TR/2003/REC-soap12-part1-20030624/. The latest version of "SOAP SOAP Version 1.2 Part 1: Messaging Framework" Framework is available at http://www.w3.org/TR/soap12-part1/.

[SOAP 1.1] [WS-Addressing SOAP Binding]

<a href= "http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"> Simple Object Access Protocol (SOAP) 1.1 Web Services Addressing 1.0 - SOAP Binding , D. Box, D. Ehnebuske, G. Kakivaya, A. Layman, N. Mendelsohn, H Frystyk Nielsen, S. Thatte, D. Winer, M. Gudgin, M. Hadley, and T. Rogers, Editors. W3C Member Submission, 8 World Wide Web Consortium, 9 May 2000. 2006. This version of the WS-Addressing SOAP Binding Recommendation is http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509. The latest version of WS-Addressing SOAP Binding is available at http://www.w3.org/TR/ws-addr-soap.

[WS-Addressing WSDL Binding]

Web Services Addressing 1.0 - WSDL Binding ,M. Gudgin, M. Hadley, T. Rogers, and Ü. Yalçinalp, Editors. World Wide Web Consortium, 16 February 2006. This version of the WS-Addressing WSDL Binding specification is http://www.w3.org/TR/2006/WD-ws-addr-wsdl-20060216. The latest version of WS-Addressing WSDL Binding is available at http://www.w3.org/TR/ws-addr-wsdl.

[WSDL 1.1]

Web Services Description Language (WSDL) 1.1 , E. Christensen, F. Curbera, G. Meredith, et al, Authors. World Wide Web Consortium, March 2001. Available at http://www.w3.org/TR/2001/NOTE-wsdl-20010315.

[WSDL 2.0 Core Language]

Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language ,R. Chinnici, J. J. Moreau, A. Ryman, and S. Weerawarana, Editors. W3C Member Submission, 15 World Wide Web Consortium, 27 March 2001. 2006. This version of the WSDL 2.0 specification is http://www.w3.org/TR/2006/CR-wsdl20-20060327. The latest version of WSDL 2.0 is available at http://www.w3.org/TR/wsdl20.

[WS-Security] [WS-Security 2004]

Web Services Security: SOAP Message Security 1.0 (WS-Security 2004) , A. Nadalin, C. Kaler, P. Hallam-Baker, and R. Monzillo, Editors. OASIS Standard, OASIS, Organization for the Advancement of Structured Information Standards, March 2004. Available at http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf.

[xml:id]

xml:id Version 1.0 , J. Marsh, D. Veillard, and N. Walsh, Editors. deleted text: W3C Recommendation, World Wide Web Consortium, 9 September 2005. This version of the "xml:id" xml:id Version 1.0 Recommendation is http://www.w3.org/TR/2005/REC-xml-id-20050909/. The latest version of "xml:id" xml:id is available at http://www.w3.org/TR/xml-id/.