Operation names and self-description

From the Feb 12 minutes;
> 11. Issue 120: Operation Name feature proposal [.1, .2]
[snip]
> Jeff: Rather than doing an exegesis on MB's proposal, we ought to say we don't understand MB's issues
> and we can not make any changes until we understand.

I think my comments stand on their own, but perhaps I could provide
an as-brief-as-possible description of the requirement I'm trying to
meet with those comments.

I want to see SOAP messages be more self-descriptive regarding operation
names.

What that means is that I want any party which sees that message
(ultimate recipient, intermediary, gateway, etc..), to be able to locate
the operation name in the message.

The problem - which is why I think this requires a more complex
solution than Umit's proposal - is that there are several ways that
people use to identify the operation in a SOAP message; SOAPAction,
wsa:Action, root element of SOAP body, implicitly, and inherited from
an underlying application protocol (if any).  That means we need a way
of declaring, in the message, which one of those is in effect for that
message.

Does that help?

Mark.
-- 
Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca