That's just the problem. There are too many ways of doing the same thing. We're not proposing to move the semantics of WS-E to SOAP. Extensions should appear as children of wse:Subscribe. The optional use of SOAP headers is to enforce the "don't create a subscription if you don't understand this extension" semantics.

- gp

Chou, Wu (Wu) wrote:

I don't think anything broken with Mode attribute of WS-E. The current WS-E specs fully support using all the options including SOAP header. It is an implementation choice and it can choose to use one or both. I am also concerned about moving semantics of WS-E to SOAP. Details are in [1],[2] and related link.

[1] http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Apr/0061.html

[2] http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Apr/0083.html

Thanks,

- Wu Chou.