Review: MTOM Serialization Policy Assertion 1.1

Asir S Vedamuthu, Microsoft Corporation

September 26th, 2007

The WS-Policy Working Group used the best practices in the Guidelines document to review the MTOM Serialization Policy Assertion 1.1 Last Call Working Draft. The assertion follows 23 of the 23 applicable best practices (see the table below). That is an A+!

The WS-Policy Working Group does not have any negative comments on the Last Call Working Draft.

Best Practices Does the best practice apply to the MTOM Serialization Policy Assertion? Does the MTOM Serialization Policy Assertion follow the best practice?
1. Semantics Independent of Attachment Mechanisms Y Y
2. Define assertions relevant to compatibility tests Y Y

3. Mark Ignorable Assertions not related to compatibility

N  
4. Semantics Independent of the Form Y Y

5. Start with a Simple Assertion

Y Y

6. Use Unique QNames

Y Y
7. Provide an XML definition Y Y
8. Specify Semantics Clearly Y Y
9. Document Ignorable Behavior Y Y
10. Document Use of the Ignorable Attribute in XML Y Y
11. Assertion Authors should allow use of wsp:Optional Y Y
12. Define message format only Y Y
13. Avoid Duplication of Assertions Y Y
14. Use Parameters for Useful Information N  

15. Use Nested Assertions for Dependent Behaviors

N  

16. Enumerate Nested Assertions

N  
17. Discourage Domain Specific Intersection Y Y
18. Limit use of Optional Assertions N  

19. Consider entire message exchange pattern when specifying Assertions that may be optional

Y Y
20. Indicate use of an Optional Assertion Y Y

21. Reusable Assertions

Y Y

22. Describe Semantics of Multiple Assertions of Same Type

N  

23. Leverage Defined Attachment Mechanisms

Y Y

24. Use Defined Policy Subjects

Y Y
25. Identify Policy Subjects Y Y
26. Specify WSDL Policy Subject(s) Y Y
27. Consider Scope of Attachment Points Y Y
28. Choose the Most Granular WSDL Policy Subject Y Y

29. Define Rules for Attachment of an Assertion type to Multiple WSDL policy subjects

N  
30. Specify Preferred WSDL Attachment Point Y Y

31. Use defined tModels when appropriate

N  

32. Specify Composition with Related Assertions

N  
33. Independent Assertions for Different Versions of a Behavior N  

34. Document changes to policy subject

N