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 4885 - should 4506 have been resolved differently?
Summary: should 4506 have been resolved differently?
Status: RESOLVED WONTFIX
Alias: None
Product: XMLP WG
Classification: Unclassified
Component: mtom policy assertion (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Christopher Ferris
QA Contact: Christopher Ferris
URL: http://lists.w3.org/Archives/Public/x...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-26 11:36 UTC by Christopher Ferris
Modified: 2007-07-26 11:41 UTC (History)
0 users

See Also:


Attachments

Description Christopher Ferris 2007-07-26 11:36:03 UTC
See note from Mark baker at http://lists.w3.org/Archives/Public/xml-dist-app/2007Jul/0004.html.
Comment 1 Christopher Ferris 2007-07-26 11:41:21 UTC
See meeting minutes at: http://www.w3.org/2007/07/25-xmlprotocol-minutes.html#action06

WG resolved to open and close with no action. The WG felt that while Mark's point was possibly technically correct absent the context of the MTOM Policy assertion that using the application/xop+xml media type did not in fact represent an endpoint's ability to support MTOM, but rather the XOP media type, which is not what the MTOM policy assertion is about. The WG also noted that in fact the multipart/related; type=application/xop+xml did not technically represent support for MTOM, but could, in fact, represent another serialization of a multipart message that had, as its root body, an application/xop+xml serialized entity. However, in the context of use of the MTOM policy assertion, one could reasonably infer that it meant support for MTOM if the receiving endpoint of the ACCEPT header had exposed a policy that included the MTOM policy assertion.