This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 5175 - Changes to Section 1 (Last Call comment - editorial)
Summary: Changes to Section 1 (Last Call comment - editorial)
Status: RESOLVED FIXED
Alias: None
Product: XMLP WG
Classification: Unclassified
Component: mtom policy assertion (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Christopher Ferris
QA Contact: Christopher Ferris
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-10 16:00 UTC by Ram Jeyaraman
Modified: 2007-10-10 19:57 UTC (History)
0 users

See Also:


Attachments

Description Ram Jeyaraman 2007-10-10 16:00:32 UTC
The current text in section 1 [1] does not clearly explain the meaning of this policy assertion  including this informational content [2] will help clarify the semantics of this policy assertion. 
  
Specifically, the first paragraph of section 1 [1] may be modified as follows:

This specification describes a domain-specific policy assertion for the SOAP Message Transmission Optimization Mechanism W3C Recommentation [MTOM] that can be specified within a policy alternative as defined in Web Services Policy 1.5 - Framework [WS-Policy]. This policy assertion indicates that messages are encoded as described in section 3 of the SOAP Message Transmission Optimization Mechanism [MTOM] using MIME multipart/related [RFC2387] and XML-binary Optimized Packaging [XOP]. For backwards compatibility, the policy assertion can also be used in conjunction with the SOAP 1.1 Binding for MTOM 1.0 [MTOMS11] Member Submission. 

[1] http://www.w3.org/TR/2007/WD-soap12-mtom-policy-20070918/
[2] Informational content: "This policy assertion indicates that messages are encoded as described in section 3 of the SOAP Message Transmission Optimization Mechanism [MTOM] using MIME multipart/related [RFC2387] and XML-binary Optimized Packaging [XOP]."
Comment 1 Christopher Ferris 2007-10-10 19:57:38 UTC
RESOLUTION: issue 5175 closed with proposal from Ram as described in issue
See http://www.w3.org/2007/10/10-xmlprotocol-irc#T19-57-14