[Bug 3952] Change optional example from MTOM to security (Guidelines and Primer)

http://www.w3.org/Bugs/Public/show_bug.cgi?id=3952

           Summary: Change optional example from MTOM to security
                    (Guidelines and Primer)
           Product: WS-Policy
           Version: FPWD
          Platform: Macintosh
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Primer
        AssignedTo: frederick.hirsch@nokia.com
        ReportedBy: frederick.hirsch@nokia.com
         QAContact: public-ws-policy-qa@w3.org


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.

Received on Saturday, 4 November 2006 16:01:50 UTC