I find myself agreeing with Steve on this

In addition to defining addressing-related information headers for SOAP messages, WS-Addressing introduces the concept of an EndpointReference (EPR) which is used as the means of capturing the addressing-related information of a service endpoint. I don’t see why an EPR couldn’t be of the form:


<!- Protocol-specific addresses ->




<!- And a logical address ->



If a service wishes to make available EPRs that advertise the service’s accessibility over a number of transports, why shouldn’t we allow it to? So, I agree with Steve‘s arguments on this one.

The alternative, of course, is to have separate EPRs for each of the above <wsa:Address> elements.