Web Services Addressing provides transport-neutral mechanisms to address Web services and messages. Web Services Addressing 1.0 - Metadata (this document) defines how the abstract properties defined in Web Services Addressing 1.0 - Core are described using WSDL, how to include WSDL metadata in endpoint references, and how WS-Policy can be used to indicate the support of WS-Addressing by a Web service.
This is the Last Call Working Draft of the Web Services Addressing 1.0 - Metadata
specification for review by W3C members and other interested
parties. It has been produced by the
The Working Group plans to submit this specification for
consideration as a
The Working Group plans to submit this specification for
consideration as a
Two interoperable implementations of each optional and required feature of the specifications have been produced.
The Working Group releases a test suite along with an
The sections
No significant change has been made to this document since its
previous version. The detailed disposition of those comments can
be found in the
Discussion of this document takes place on the
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.
This document was produced by a group operating under the
Last Modified: $Date: 2007/06/27 19:31:45 $
Web Services Addressing 1.0 - Core [
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 [
When describing abstract data models, this specification uses the notational
convention used by the XML Infoset [
When describing concrete XML schemas [
This specification uses a number of namespace prefixes throughout; they are
listed in
| Prefix | Namespace |
|---|---|
| S | http://www.w3.org/2003/05/soap-envelope |
| S11 | http://schemas.xmlsoap.org/soap/envelope |
| wsa | http://www.w3.org/2005/08/addressing |
| wsam | http://www.w3.org/2007/05/addressing/metadata |
| wsoap | http://www.w3.org/ns/wsdl/soap |
| xs | http://www.w3.org/2001/XMLSchema |
| wsdl | Either http://www.w3.org/ns/wsdl or http://schemas.xmlsoap.org/wsdl/ depending on context |
| wsdl20 | http://www.w3.org/ns/wsdl |
| wsdl11 | http://schemas.xmlsoap.org/wsdl/ |
| soap11 | http://schemas.xmlsoap.org/wsdl/soap/ |
| wsp | http://www.w3.org/ns/ws-policy |
The working group intends to update the value of the Web Services Addressing 1.0 - Metadata namespace URI each time a new version of this document is published until such time that the document reaches Candidate Recommendation status. Once it has reached Candidate Recommendation status, the working group intends to maintain the value of the Web Services Addressing 1.0 - Metadata namespace URI that was assigned in the Candidate Recommendation unless significant changes are made that impact the implementation of the specification.
WS-Addressing is defined in terms of the XML Information Set [
All information items defined by this specification are identified by the XML
namespace URI [
An EPR's metadata section can contain a reference to WSDL metadata, can include embedded WSDL metadata, or both.
The WSDL binding of Web Services Addressing introduces the following element and attribute information items for referencing WSDL metadata from an EPR's metadata section:
A QName identifying a description of the sequences of messages that a service sends and/or receives. This corresponds to a WSDL 2.0 interface or, for backwards compatibility, a WSDL 1.1 port type. When this element is included in an EPR, the EPR is considered to be specific to the interface or port type it identifies.
A QName that identifies the set of endpoints at which a particular Web service is deployed. The set of endpoints is represented by a service in WSDL 2.0 or, for backwards compatibility, a WSDL 1.1 service.
An NCName that identifies one endpoint amongst the set identified by the service name above. An endpoint is represented by an endpoint in WSDL 2.0 or, for backwards compatibility, a port in WSDL 1.1. When this attribute is specified, the EPR is considered to be specific to the endpoint or port it identifies.
The element information items defined above are used in an EPR's metadata
section. The following shows an example endpoint reference. This references the
interface named "ghns:reservationInterface" at the endpoint IRI
"http://greath.example.com/2004/reservation". Note the use of the WSDL[
WSDL 2.0 or, for backwards compatibility, 1.1 definitions can be embedded in the metadata section of an EPR to provide a consuming application with WSDL information that applies to the referenced endpoint. To do so, the creator of an EPR MAY include a WSDL 2.0 description element (or a WSDL 1.1 definitions element) in the metadata property of the EPR. The semantics of the embedded WSDL is as defined by the WSDL 2.0 or 1.1 specifications.
In particular, embedding a WSDL service component description MAY be used by EPR issuers to indicate the presence of alternative addresses and protocol bindings to access the referenced endpoint. The alternatives are provided by the different endpoints of the embedded service. In the case of WSDL 1.1, additional ports can be conveyed by the WSDL 1.1 service definition which are not alternative access channels to the endpoint. In that case, if the InterfaceName or ServiceName elements are also included in the metadata section of the EPR, only the ports with the same interface as that specified are to be considered alternative access channels.
If the ServiceName element appears in the EPR’s [metadata] and an embedded WSDL service component is also provided inside a descriptions or definitions component, then the ServiceName SHOULD match the name of (one or more of) the WSDL service(s) included therein; the endpoint (port) name SHOULD match as well if present. The behavior of an EPR consumer when the ServiceName doesn’t match an embedded description is undefined.
This specification supports a mechanism for indicating, in a WSDL description, that
the endpoint conforms to the WS-Addressing specification. That mechanism uses
WS-Policy Framework [
The mechanism for indicating that a binding or endpoint conforms to the
WS-Addressing specification is through the use of the Web Services Policy -
Framework [
The wsam:Addressing policy assertion applies to the endpoint policy subject.
For WSDL 1.1, these assertions may be attached
to wsdl11:port or
wsdl11:binding. For WSDL 2.0,
they may be attached to
wsdl20:endpoint or
wsdl20:binding. A policy
expression containing the wsam:Addressing
policy assertion MUST NOT be attached to a
wsdl:portType or
wsdl20:interface. The
wsam:Addressing policy assertion specifies a
concrete behavior whereas the
wsdl:portType or
wsdl20:interface is an abstract
construct.
The wsam:Addressing policy assertion is a nested policy
container assertion. The meaning of this assertion, when present in a policy
alternative, is that WS-Addressing is required to communicate with the
subject. The wsam:Addressing assertion indicates that there are
no restrictions on the use of WS-Addressing unless otherwise qualified by
assertions in its nested policy expression. In order to indicate that the
subject supports WS-Addressing but does not require its use, an additional
policy alternative should be provided which does not contain this assertion;
the compact authoring style for an optional policy assertion provided by
WS-Policy V1.5 [wsp:Optional attribute, as a syntactic shortcut, can be
used with the wsam:Addressing assertion. This indicates two
policy alternatives, one which contains the policy assertion, and another
which does not.
The inclusion of this assertion implies
support for the Web Services Addressing 1.0 - Core [
The wsam:AnonymousResponses element MAY be used as a policy assertion nested
within the wsam:Addressing assertion in accordance with the rules laid down
by
The appearance of this element within the wsam:Addressing policy assertion indicates that
the endpoint requires request messages to use response
endpoint EPRs that contain the anonymous URI
("http://www.w3.org/2005/08/addressing/anonymous") as the value of
[address]. In other words, the endpoint requires the use of anonymous responses.
The None URI ("http://www.w3.org/2005/08/addressing/none") may appear as the
value of [address] in place of the anonymous URI; this value MUST be
accepted.
The wsam:NonAnonymousResponses element MAY be used as a policy assertion
nested within the Addressing assertion in accordance with the rules laid
down by wsam:NonAnonymousResponses policy assertion
MUST NOT be used in the same policy alternative as the wsam:AnonymousResponses policy assertion.
The appearance of this element within the wsam:Addressing assertion indicates that
the endpoint expresses requires request messages to use response
endpoint EPRs that contain something other than the anonymous URI as the
value of [address]. In other words, the endpoint requires the use of
non-anonymous responses. This assertion is deliberately vague; its presence
indicates that some non-anonymous addresses will be accepted but doesn't
constrain what such an address might look like. A receiver can still reject
a request that contains an address that it doesn't understand or that
requires a binding it doesn't support.
The None URI ("http://www.w3.org/2005/08/addressing/none") may appear as the
value of [address] in place of a non-anonymous address; this value MUST be
accepted.
When a client is looking for an endpoint with compatible policy, one common method used is to take the policy intersection between the policy which the client is looking for, and the policy asserted in the WSDL document; a non-empty intersection is sought. The policy used by the client must be written carefully to avoid unexpected results. This is most obvious when the client is not looking for explicit support of a particular kind of response; failing to take care could mean missing a compatible policy.
For more detailed descriptions of the use of
wsp:Optional, wsp:Ignorable, and strict and lax intersection, please refer
to the WS-Policy Primer [
This section describes how the values of certain message addressing properties can be specified in WSDL. In some cases the values of message addressing properties are specified using existing WSDL constructs, in other cases new WSDL extensions are defined for that purpose.
A wsdl20:endpoint or wsdl11:port element MAY be extended using a child wsa:EndpointReference element. When extended this way, the [address] property of the child EPR MUST match the {address} property of the endpoint component (WSDL 2.0) or the address value provided by the relevant port extension (WSDL 1.1). For example, in a SOAP 1.1 port described using WSDL 1.1, the location attribute of a soap11:address element (if present) would have the same value as the wsa:Address child element of the wsa:EndpointReference element.
Use of WS-Addressing adds the following OPTIONAL properties to the WSDL 2.0 component model:
A property of the Endpoint component, named {endpoint reference}. This property is of type wsa:EndpointReference, with a cardinality of 1. The property has the value of the wsa:EndpointReference element used as a child of wsdl20:endpoint, if any. If no such extension exists, this property is absent.
The value of the [destination] message addressing property for a message sent to
an endpoint typically matches the value of the {address} property of the
endpoint component (WSDL 2.0) or the address value (if any) provided by the
relevant port extension (WSDL 1.1). For a SOAP 1.1 port described using WSDL
1.1, the value is provided by the location attribute of the soap11:address
extension element. For an endpoint or port extended with an EPR (see
Additional runtime information could override the value of the [destination] message addressing property for messages sent to an endpoint, e.g. a runtime exchange might result in a redirection to a different EPR. Note that WS-Addressing does not define any normative mechanism for such redirection.
When a wsa:EndpointReference element is present in a wsdl20:endpoint or a
wsdl11:port element (see
WS-Addressing defines two mechanisms to associate a value of the [action]
property with input, output and fault elements within a WSDL description:
explicit and defaulting. Explicit association is described in section
Ensuring that there is sufficient information within a message to distinguish
which WSDL operation it is associated with is specified as a best practice in
WSDL 2.0
WS-Addressing defines a global attribute, wsam:Action, that can be used to
explicitly define the value of the [action] property for messages in a WSDL
description. The type of the attribute is xs:anyURI and it is used as an
extension on the WSDL input, output and fault elements. A SOAP binding can
specify SOAPAction values for the input messages of operations. In the
absence of a wsam:Action attribute on a WSDL input element where a non-empty
SOAPAction value is specified, the value of the [action] property for the
input message is the value of the SOAPAction specified. If the wsam:Action
attribute is absent, and SOAPAction is not specified, or is empty, then the
default pattern is used. Note that the SOAPAction value is not required to
be an absolute IRI, but the [action] property is required to be an absolute
IRI; if WS-Addressing is required (the wsam:Addressing assertion is
present), wsam:Action is not specified, and the SOAPAction value is not
empty or an absolute IRI, then the document MUST be considered invalid.
Web Services Addressing 1.0 - SOAP Binding[
The inclusion of wsam:Action without the inclusion of the wsam:Addressing assertion has no normative intent and is only informational. In other words, the inclusion of wsam:Action attributes in WSDL alone does not imply a requirement on clients to use Message Addressing Properties in messages it sends to the service. A client, however, MAY include Message Addressing Properties in the messages it sends, either on its own initiative or as described by other elements of the service contract, regardless of the presence or absence of the wsam:Addressing assertion. Other specifications defining the value of [action] are under no constraint to be consistent with wsam:Action.
For example consider the following WSDL excerpt:
The action for the input of the opCheckAvailability operation within the reservationInterface is explicitly defined to be http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability. The action for the output of this same operation is http://greath.example.com/2004/wsdl/resSvc/opCheckAvailabilityResponse.
The action for the input of the opCheckAvailability operation within the reservationInterface port type is explicitly defined to be http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability. The action for the output of this same operation is http://greath.example.com/2004/wsdl/resSvc/opCheckAvailabilityResponse.
In the absence of an explicitly specified value for the [action] property
(see section
For fault messages, the general form of an action IRI is as follows:
Where:
is ":" when the [target namespace] is a URN, otherwise "/". Note that for IRI schemes other than URNs which aren't path-based (i.e. those that outlaw the "/" character), the default action value might not conform to the rules of the IRI scheme. Authors are advised to specify explicit values in the WSDL in this case.
is the {target namespace} of the interface. If [target namespace] ends with a "/" an additional "/" is not added.
is the {name} of the interface.
is the {name} of the operation.
is the {name} of the fault.
Empty ("") where the operation's {message exchange
pattern} is
"Request" where the operation's {message exchange
pattern} is
"Solicit" where the operation's {message exchange
pattern} is
"Response" where the operation's {message exchange
pattern} is
"Response" where the operation's {message exchange
pattern} is
{message label} where the {message exchange pattern} is not one of the MEP IRIs defined in WSDL 2.0 Part 2.
For example consider the following WSDL excerpt:
[targetNamespace] = http://greath.example.com/2004/wsdl/resSvc
[interface name] = reservationInterface
[operation name] = opCheckAvailability
[direction token] for input is Request
[direction token] for output is Response
Applying the patterns above with these values we have:
input action = http://greath.example.com/2004/wsdl/resSvc/reservationInterface/opCheckAvailabilityRequest
output action = http://greath.example.com/2004/wsdl/resSvc/reservationInterface/opCheckAvailabilityResponse
fault action for a fault named AvailabilityNotAvailableFault = http://greath.example.com/2004/wsdl/resSvc/reservationInterface/opCheckAvailabilityResponse/AvailabilityNotAvailableFault
Use of WS-Addressing adds the following REQUIRED properties to the WSDL 2.0 component model:
A property of the Interface Message Reference and Interface Operation InFault/OutFault
components named {action}. The property is of type xs:anyURI. The
property value is either explicitly specified, as described in
section
A default pattern is also defined for backwards compatibility with WSDL 1.1.
In the absence of an explicitly specified value for the [action] property
(see section
For fault messages, the general form of an action IRI is as follows:
Where:
is ":" when the [target namespace] is a URN, otherwise "/". Note that for IRI schemes other than URNs which aren't path-based (i.e. those that outlaw the "/" character), the default action value might not conform to the rules of the IRI scheme. Authors are advised to specify explicit values in the WSDL in this case.
is a literal character string to be included in the action.
is the target namespace (/definition/@targetNamespace). If [target namespace] ends with a "/" an additional "/" is not added.
is the name of the port type (/definition/portType/@name).
is the {name} of the operation.
is the name of the element as defined in
is the name of the fault (/definition/porttype/operation/fault/@name).
For example consider the following WSDL excerpt:
[targetNamespace] = http://greath.example.com/2004/wsdl/resSvc
[port type name] = reservationInterface
[input name] = CheckAvailability
[output name] = CheckAvailabilityResponse
[fault name] = InvalidDate
Applying the pattern above with these values we have:
input action = http://greath.example.com/2004/wsdl/resSvc/reservationInterface/CheckAvailability
output action = http://greath.example.com/2004/wsdl/resSvc/reservationInterface/Availability
fault action = http://greath.example.com/2004/wsdl/resSvc/reservationInterface/opCheckAvailability/Fault/InvalidDate
WSDL defines rules for a default input or output name if the name attribute is not present. Consider the following example:
[targetNamespace] = http://greath.example.com/2004/wsdl/resSvc
[port type name] = reservationInterface
According to the rules defined in
[input name] = opCheckAvailabilityRequest
Likewise, the output defaults to the operation name with "Response" appended.
[output name] = opCheckAvailabilityResponse
Applying the pattern above with these values we have:
input action = http://greath.example.com/2004/wsdl/resSvc/reservationInterface/opCheckAvailabilityRequest
output action = http://greath.example.com/2004/wsdl/resSvc/reservationInterface/opCheckAvailabilityResponse
This section describes which of the core message properties are mandatory for messages in the various MEPs defined by WSDL.
For backwards compatibility, this section describes which of the core message properties are mandatory for messages in the various MEPs defined by WSDL 1.1.
This is a straightforward one-way message. No responses are expected but related messages could be sent as part of other message exchanges.
| Property | Mandatory | Description |
|---|---|---|
| [destination] | Y | Provides the address of the intended receiver of this message |
| [action] | Y | Identifies the semantics implied by this message |
| [source endpoint] | N | Message origin. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| [reply endpoint] | N | Intended receiver for replies to this message. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| [fault endpoint] | N | Intended receiver for faults related to this message. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| [message id] | N | Unique identifier for this message. Unused in this MEP, but may be included to facilitate longer running message exchanges. |
| [relationship] | N | Indicates relationship to a prior message. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
This is request-response. A reply is expected hence mandating [reply endpoint] in the request message. The response message might be a fault.
| Property | Mandatory | Description |
|---|---|---|
| [destination] | Y | Provides the address of the intended receiver of this message |
| [action] | Y | Identifies the semantics implied by this message |
| [source endpoint] | N | Message origin. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| [reply endpoint] | Y | Intended receiver for the reply to this message. |
| [fault endpoint] | N | Intended receiver for faults related to this message. May be included to direct fault messages to a different endpoint than [reply endpoint]. |
| [message id] | Y | Unique identifier for this message. Used in the [relationship] property of the reply message. |
| [relationship] | N | Indicates relationship to a prior message. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| Property | Mandatory | Description |
|---|---|---|
| [destination] | Y | Provides the address of the intended receiver of this message |
| [action] | Y | Identifies the semantics implied by this message |
| [source endpoint] | N | Message origin. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| [reply endpoint] | N | Intended receiver for replies to this message. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| [fault endpoint] | N | Intended receiver for faults related to this message. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| [message id] | N | Unique identifier for this message. Unused in this MEP, but may be included to facilitate longer running message exchanges. |
| [relationship] | Y | Indicates that this message is a reply to the request message
using the request message [message id] value and the predefined
http://www.w3.org/2005/08/addressing/reply IRI. |
From the WS-Addressing perspective this MEP is the same as One-way. The
properties defined in
From the WS-Addressing perspective this MEP is the same as Request-response.
The properties defined in
This section describes which of the core message properties are mandatory for
messages in the various MEPs defined by WSDL 2.0 [
This is a straightforward one-way message. No responses are expected but related messages could be sent as part of other message exchanges.
| Property | Mandatory | Description |
|---|---|---|
| [destination] | Y | Provides the address of the intended receiver of this message |
| [action] | Y | Identifies the semantics implied by this message |
| [source endpoint] | N | Message origin. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| [reply endpoint] | N | Intended receiver for replies to this message. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| [fault endpoint] | N | Intended receiver for faults related to this message. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| [message id] | N | Unique identifier for this message. Unused in this MEP, but may be included to facilitate longer running message exchanges. |
| [relationship] | N | Indicates relationship to a prior message. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
This one-way MEP allows fault messages. The [message id] property is needed in the initial message in order to be able to correlate any fault with that message.
| Property | Mandatory | Description |
|---|---|---|
| [destination] | Y | Provides the address of the intended receiver of this message |
| [action] | Y | Identifies the semantics implied by this message |
| [source endpoint] | N | Message origin. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| [reply endpoint] | N* | Intended receiver for replies to this message. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| [fault endpoint] | N* | Intended receiver for faults related to this message. |
| [message id] | Y | Unique identifier for this message. Used in the [relationship] property of any resulting fault message. |
| [relationship] | N | Indicates relationship to a prior message. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
* Note that at least one of [fault endpoint] or [reply endpoint] is required for this MEP, so that a fault can be sent if necessary.
| Property | Mandatory | Description |
|---|---|---|
| [destination] | Y | Provides the address of the intended receiver of this message |
| [action] | Y | Identifies the semantics implied by this message |
| [source endpoint] | N | Message origin. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| [reply endpoint] | N | Intended receiver for replies to this message. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| [fault endpoint] | N | Intended receiver for faults related to this message. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| [message id] | N | Unique identifier for this message. Unused in this MEP, but may be included to facilitate longer running message exchanges. |
| [relationship] | Y | Indicates that this message is a response to the in message
using the in message [message id] value and the predefined
http://www.w3.org/2005/08/addressing/reply IRI. |
This is a two-way MEP. A reply is expected hence mandating [reply endpoint] in the request message. The response message might be a fault.
| Property | Mandatory | Description |
|---|---|---|
| [destination] | Y | Provides the address of the intended receiver of this message |
| [action] | Y | Identifies the semantics implied by this message |
| [source endpoint] | N | Message origin. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| [reply endpoint] | Y | Intended receiver for the reply to this message. |
| [fault endpoint] | N | Intended receiver for faults related to this message. May be included to direct fault messages to a different endpoint than [reply endpoint]. |
| [message id] | Y | Unique identifier for this message. Used in the [relationship] property of the out message. |
| [relationship] | N | Indicates relationship to a prior message. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| Property | Mandatory | Description |
|---|---|---|
| [destination] | Y | Provides the address of the intended receiver of this message |
| [action] | Y | Identifies the semantics implied by this message |
| [source endpoint] | N | Message origin. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| [reply endpoint] | N | Intended receiver for replies to this message. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| [fault endpoint] | N | Intended receiver for faults related to this message. Unused in this MEP, but could be included to facilitate longer running message exchanges. |
| [message id] | N | Unique identifier for this message. Unused in this MEP, but may be included to facilitate longer running message exchanges. |
| [relationship] | Y | Indicates that this message is a response to the in message
using the in message [message id] value and the predefined
http://www.w3.org/2005/08/addressing/reply IRI. |
This MEP differs from the In-out MEP in that the subsequent message is
optional. This difference doesn't affect the message properties so the
properties defined in
From the WS-Addressing perspective this MEP is the same as In-only. The
properties defined in
From the WS-Addressing perspective this MEP is the same as Robust In-only.
The properties defined in
From the WS-Addressing perspective this MEP is the same as In-out. The
properties defined in
This MEP differs from the Out-in MEP in that the subsequent message is
optional. This difference doesn't affect the message properties so the
properties defined in
An endpoint reference whose wsa:Metadata element has among its children the elements
defined in
A WSDL description conforms to this specification when it incorporates directly or
indirectly the
An endpoint conforms to this specification if it has a conformant WSDL description
associated with it, and receives and emits messages in accordance with the
constraints defined in sections
This document is the work of the
Members of the Working Group are (at the time of writing, and by alphabetical order): Abbie Barbir (Nortel Networks), Andreas Bjärlestam (ERICSSON), Eran Chinthaka (WSO2), Francisco Curbera (IBM Corporation), Glen Daniels (Sonic Software), Vikas Deolaliker (Sonoa Systems, Inc.), Paul Downey (BT), Jacques Durand (Fujitsu Limited), Robert Freund (Hitachi, Ltd.), Marc Goodner (Microsoft Corporation), David Hull (TIBCO Software, Inc.), Yin-Leng Husband (HP), David Illsley (IBM Corporation), Ram Jeyaraman (Microsoft Corporation), Anish Karmarkar (Oracle Corporation), Paul Knight (Nortel Networks), Philippe Le Hégaret (W3C/MIT), Amelia Lewis (TIBCO Software, Inc.), Bozhong Lin (IONA Technologies, Inc.), Mark Little (JBoss Inc.), Jeganathan Markandu (Nortel Networks), Jeff Mischkinsky (Oracle Corporation), Nilo Mitra (ERICSSON), Eisaku Nishiyama (Hitachi, Ltd.), Ales Novy (Systinet Inc.), David Orchard (BEA Systems, Inc.), Gilbert Pilz (BEA Systems, Inc.), Rama Pulavarthi (Sun Microsystems, Inc.), Alain Regnier (Ricoh Company, Ltd.), Tony Rogers (CA), Tom Rutt (Fujitsu Limited), Davanum Srinivas (WSO2), Jiri Tejkl (Systinet Inc.), Katy Warr (IBM Corporation), Steve Winkler (SAP AG), Ümit Yalçinalp (SAP AG), Prasad Yendluri (webMethods, Inc.).
Previous members of the Working Group were: Lisa Bahler (SAIC - Telcordia Technologies), Rebecca Bergersen (IONA Technologies, Inc.), Vladislav Bezrukov (SAP AG), Dave Chappell (Sonic Software), Ugo Corda (Sun Microsystems, Inc.), Michael Eder (Nokia), Yaron Goland (BEA Systems, Inc.), Martin Gudgin (Microsoft Corporation), Arun Gupta (Sun Microsystems, Inc.), Hugo Haas (W3C), Marc Hadley (Sun Microsystems, Inc), Jonathan Marsh (Microsoft Corporation), Mark Nottingham (BEA Systems, Inc.), Mark Peel (Novell, Inc.), Harris Reynolds (webMethods, Inc.), Rich Salz (IBM Corporation), Davanum Srinivas (Computer Associates), Greg Truty (IBM Corporation), Mike Vernal (Microsoft Corporation), Steve Vinoski (IONA Technologies, Inc.), Pete Wenzel (Sun Microsystems, Inc.).
The people who have contributed to
This section describes strategies for choosing [action] values consistent between this specification and the WS-Addressing Member Submission published 10 August 2004 (hereafter called "2004-08"). The wsa200408 namespace prefix below refers to the "http://schemas.xmlsoap.org/ws/2004/08/addressing" namespace defined in the 2004-08 version.
The WS-Addressing 1.0 [action] property, which identifies the semantics implied by a message, is semantically equivalent to the [action] message information header defined in the 2004-08 version. Authors are therefore advised to use the same value for 1.0 [action] and 2004-08 [action].
However, when describing services in WSDL, the namespace of the Action attribute used to associate values with WSDL operations differs in the two versions (wsam:Action versus wsa200408:Action), and the default action pattern in WS-Addressing 1.0 differs in two respects from that in the 2004-08 version: the [delimiter] can be either "/" or ":" in 1.0 while in 2004-08 it is always "/", and the default action pattern for faults is closer to that of other messages instead of a constant URI.
If a default action pattern is desired, this specification recommends the 1.0 default action pattern. The 200408 [action] can be made consistent with the 1.0 default by:
specifying wsa200408:Action explicitly when the targetNamespace is a URN, and
specifying wsa200408:Action explicitly when the message is a fault.
If the targetNamespace is a URN, it is not advisable to use the 2004-08 default action pattern, as it leads to malformed IRIs. If the targetNamespace is not a URN, and the 2004-08 default action pattern is in use, the 1.0 [action] value can be made consistent by:
specifying wsam:Action explicitly when the message is a fault.
Placeholder for auto change log generation.
Placeholder for auto change log generation.
Placeholder for auto change log generation.
Placeholder for auto change log generation.
Placeholder for auto change log generation.
Placeholder for auto change log generation.