RE: TAG requests help with examples of WS-Addressing

WS-RM, under standardization at OASIS, also uses WS-A heavily including
EPRs. In particular look to the wsrm:AcksTo element which is of type
wsa:EndpointReferenceType. This is a required element in WS-RM messages
such as wsrm:CreateSequence. There are many message examples in the
appendix of the specification.

The first CD of WS-RM is here:

There are many more examples in the WS-* specs as Eric notes below.

Marc Goodner
(425) 703-1903

-----Original Message-----
[] On Behalf Of Newcomer, Eric
Sent: Thursday, December 01, 2005 6:23 AM
To: Cahill, Conor P;;
Subject: RE: TAG requests help with examples of WS-Addressing

EPRs are also used in the WS-Transactions specifications (under
standardization at the WS-TX TC in Oasis).   


Several other proposed WS-* specifications depend upon WSA constructs,
including the EPR.  The point is that even if end users don't see them,
they are important for use in SOAP headers for various features.

Eric, WS-TX TC co-chair
+1 781 902 8366
fax: +1 781 902 8009
Making Software Work Together (TM)

-----Original Message-----
From: Cahill, Conor P [] 
Sent: Wednesday, November 30, 2005 8:30 AM
Subject: RE: TAG requests help with examples of WS-Addressing


The Liberty Alliance is making heavy use of EPRs both in 
message headers as well as in our Discovery Service 
responses (used to describe how to invoke web services).

The current draft specifications are available at:

An interesting extension that we have done as well is defined
a new header for responses (EPRUpdate) to update the EPR that
was used to invoke the service (such as redirecting the request
to a different endpoint, adding additional reference parameters,
etc.)  Details on that usage is within the SOAP Bindings 

I believe this is a good example of a complete system 
making concrete use of the WS-Addressing specifications.


Received on Thursday, 1 December 2005 18:21:38 UTC