This article has multiple issues. Please helpimprove it or discuss these issues on thetalk page.(Learn how and when to remove these messages) The topic of this articlemay not meet Wikipedia'sgeneral notability guideline. Please help to demonstrate the notability of the topic by citingreliable secondary sources that areindependent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to bemerged,redirected, ordeleted. Find sources: "WS-Addressing" – news ·newspapers ·books ·scholar ·JSTOR(July 2013) (Learn how and when to remove this message) This article includes alist of references,related reading, orexternal links,but its sources remain unclear because it lacksinline citations. Please helpimprove this article byintroducing more precise citations.(July 2013) (Learn how and when to remove this message) (Learn how and when to remove this message)

Web Services Addressing (WS-Addressing) is a specification of transport-neutral mechanism that allowsweb services to communicate addressing information. It essentially consists of two parts: a structure for communicating a reference to a Web service endpoint, and a set of message addressing properties which associate addressing information with a particular message.

WS-Addressing is a standardized way of including message routing data withinSOAP headers. Instead of relying on network-level transport to convey routing information, a message utilizing WS-Addressing may contain its own dispatch metadata in a standardized SOAP header. The network-level transport is only responsible for delivering that message to a dispatcher capable of reading the WS-Addressing metadata. Once that message arrives at the dispatcher specified in the URI, the job of the network-level transport is done.

WS-Addressing supports the use of asynchronous interactions by specifying a common SOAP header (wsa:ReplyTo) that contains the endpoint reference (EPR) to which the response is to be sent. The service provider transmits the response message over a separate connection to the wsa:ReplyTo endpoint. This decouples the lifetime of the SOAP request/response interaction from the lifetime of the HTTP request/response protocol, thus enabling long-running interactions that can span arbitrary periods of time.

An endpoint reference (EPR) is anXML structure encapsulating information useful for addressing a message to a Web service. This includes the destination address of the message, any additional parameters (called reference parameters) necessary to route the message to the destination, and optional metadata (such asWSDL orWS-Policy) about the service.

Message addressing properties communicate addressing information relating to the delivery of a message to a Web service:

• Message destinationURI
• Source endpoint -- the endpoint of the service that dispatched this message (EPR)
• Reply endpoint -- the endpoint to which reply messages should be dispatched (EPR)
• Fault endpoint -- the endpoint to which fault messages should be dispatched (EPR)
• Action -- an action value indicating the semantics of the message (may assist with routing the message)URI
• Unique message IDURI
• Relationship to previous messages (A pair ofURIs)

WS-Addressing was originally authored byMicrosoft,IBM,BEA,Sun Microsystems, andSAP and submitted toW3C for standardization.^[1] The W3C WS-Addressing Working Group has refined and augmented the specification in the process of standardization.

WS-Addressing is currently specified in three parts:

• TheCore specification of Endpoint References and Message Addressing Properties.
• Abinding of these properties toSOAP.
• TheMetadata specification defines how the abstract properties defined inCore are described usingWSDL, how to include WSDL metadata in endpoint references, and howWS-Policy can be used to indicate the support of WS-Addressing by a Web service.

Web Services Policy Attachment for Endpoint Reference (WS-PAEPR) specifies the mechanism and meaning of includingWS-Policy expressions in Endpoint References. WS-PAEPR is a W3C Member Submission.

• Web Services Addressing Working Group
• WS-Addressing - Submission Request to W3C
• Team Comment on the WS-Addressing Submission

• Web service specifications

• Articles with topics of unclear notability from July 2013
• All articles with topics of unclear notability
• Articles lacking in-text citations from July 2013
• All articles lacking in-text citations
• Articles with multiple maintenance issues