3952 2006-11-04 16:01:41 +0000 Change optional example from MTOM to security (Guidelines and Primer) 2006-12-06 17:52:18 +0000 1 1 1 Unclassified WS-Policy Primer FPWD Macintosh All RESOLVED FIXED P2 normal --- 1 w3c w3c public-ws-policy-qa oldest_to_newest 12825 0 w3c 2006-11-04 16:01:41 +0000 Target: Guidelines, primer Justification: MTOM is a very bad example for optionality since it raises ambiguities depending on message flow. Best practices might suggest using different endpoints for with and without MTOM. Reason is that MTOM assertion mandates usage of MTOM on both requests and responses, so request without MTOM is ambiguous, is it a message that wouldn't naturally use MTOM, is it in error, or does it signal desire not to use MTOM. Proposal: Change to example using WS-SecurityPolicy, for example that messages optionally may need timestamp using Timestamp assertion. Test: review guidelines and primer. 13087 1 Daniel.Roth 2006-12-06 17:52:18 +0000 Proposal updated as attached to http://lists.w3.org/Archives/Public/public-ws-policy/2006Dec/0018.html. See resolution at http://www.w3.org/2006/12/06-ws-policy-irc#T17-37-30.