I verified that our resolution regd. SAPAction that we adopted today is
not a problem from SAP 1.1, WS-I BP and implementation perspective (a
whole bunch of impl. traces are available at [1]).
I think the only issue is wrt to WS-Addressing SAP binding [2], which
does not qualify the statement (quoted below) as applicable to HTTP
Request only:
"The value of the SAPAction HTTP header MUST either be identical to the
value of the wsa:Action header, or be empty."
I'll raise that as an ed. issue in WS-Addr WG.
Thx.
-Anish