David:
What if the CPA says ackRequested is "perMessage" and actor is "nextMSH"? In
this case, the sender desires an intermediate Ack rather than an end-to-end
Ack. An AckRequested targeted to the next intermediary must be included in
the message because the intermediary is not privy to information in the CPA.
I don't think we want to make the AckRequested required or prohibited
depending on the setting of the actor attribute. Instead, it is simpler to
require that each of the properties that have "per message semantics" be
present in the SOAP Heaer in order to get the desired effect.
Regards,
-Arvola