Re: LC 76 - What makes a msg WS-A?

The underlying question is whether WS-A compliance is a property of a
message, or whether it is a matter of context.  I think the current spec
leans toward context.  For example, a message without a [reply endpoint]
is not compliant if it's being sent as a request in an in-out MEP, but
the exact same message might be compliant if sent in an in-only MEP
(e.g., if an operation was changed from in-only to in-out or vice versa
-- maybe not good practice, but possible).

So I would answer that a message is subject to the appropriate
WS-Addressing validation when the endpoint receiving the message
requires it.

Katy Warr wrote:

>
> Please could we discuss the following in the context of LC76?
>
> When is an incoming message deemed to be a WS-Addressing message and
> therefore subject to the appropriate WS-Addressing validation?   Is it
> based on the presence of any WS-addressing Message Addressing
> Property?  For example, does a message containing a reference
> parameter (but no other WS-Addressing information) need to result in a
> MessageAddressingHeaderRequired?    Or, for example, does the
> declaration of the wsa namespace rendor the message WS-Addressing?
>
> Thanks
> Katy