The current specification contains <operation/> elements which appear as child elements of both interface elements and
of binding elements. The purpose of these operation elements is to provide a mechanism to attach policy (intents and/or
policySets) to operations within an interface.

This is producing a parallel interface definition language, alongside WSDL, Java interfaces and so on, but at the moment
it is not an adequate interface definition language as it does not provide means to identify the message elements flowing
into and out of each operation. This parallel interface definition language is adding complexity.

With the proposal for Issue 15, a mechanism is provided to externally attach policy to interfaces, operations and messages
in a single uniform way. Once the Issue 15 mechanism is agreed, the second mechanism to attach policy to operations
is completely redundant and unnecessary.


PROPOSAL:

Remove <operation/> elements from the specification entirely.

<Dependent on the resolution to Issue 15>