Bug / Issue Tracking Service Full Text Bug Listing Bug 4509 - editorial: WS-Policy 1.5 should be Web Services Policy 1.5 Bug#: 4509 Product:  XMLP WG Version: unspecified Platform: All OS/Version: All Status: RESOLVED Severity: normal Priority: P2 Resolution: FIXED Assigned To: chrisfer@us.ibm.com Reported By: chrisfer@us.ibm.com QA Contact: chrisfer@us.ibm.com Component: mtom policy assertion Target Milestone: --- URL:  Summary: editorial: WS-Policy 1.5 should be Web Services Policy 1.5 Keywords:   Status Whiteboard:  Opened: 2007-04-27 20:23 Description:   Opened: 2007-04-27 20:23 editorial: WS-Policy 1.5 should be Web Services Policy 1.5 ------- Comment #1 >From Christopher Ferris 2007-06-20 19:39:08 ------- RESOLUTION: tentatively close issue 4509 by changing the reference to Policy 1.5 as suggested in the issue, wit hthe reference to the 1.5 Recommendation when it is published See http://www.w3.org/2007/06/20-xmlprotocol-irc#T19-38-53 ------- Comment #2 From Christopher Ferris 2007-09-12 19:28:56 ------- done Bug 5173 - garbled text Bug#: 5173 Product:  XMLP WG Version: unspecified Platform: All OS/Version: All Status: RESOLVED Severity: normal Priority: P2 Resolution: FIXED Assigned To: chrisfer@us.ibm.com Reported By: chrisfer@us.ibm.com QA Contact: chrisfer@us.ibm.com Component: mtom policy assertion Target Milestone: --- URL:  Summary: garbled text Keywords:   Status Whiteboard:  Opened: 2007-10-10 14:25 Description:   Opened: 2007-10-10 14:25 http://lists.w3.org/Archives/Public/xml-dist-app/2007Oct/0005.html ------- Comment #1 From Christopher Ferris 2007-10-10 19:23:54 ------- RESOLUTION: close issue 5173 by adding "To" to the garbled sentence and move to 4th paragraph as in the original issue resolution for 4506 See http://www.w3.org/2007/10/10-xmlprotocol-irc#T19-23-30-1 Bug 5174 - editorial comments Bug#: 5174 Product:  XMLP WG Version: unspecified Platform: All OS/Version: All Status: RESOLVED Severity: normal Priority: P2 Resolution: FIXED Assigned To: chrisfer@us.ibm.com Reported By: chrisfer@us.ibm.com QA Contact: chrisfer@us.ibm.com Component: mtom policy assertion Target Milestone: --- URL:  Summary: editorial comments Keywords:   Status Whiteboard:  Opened: 2007-10-10 14:26 Description:   Opened: 2007-10-10 14:26 http://lists.w3.org/Archives/Public/xmlp-comments/2007Sep/0000.html ------- Comment #1 From Christopher Ferris 2007-10-10 19:27:54 ------- RESOLUTION: agree that citations should be consistent and that we need to recheck all the links to ensure that they are all current See http://www.w3.org/2007/10/10-xmlprotocol-irc#T19-26-39 Bug 5175 - Changes to Section 1 (Last Call comment - editorial) Bug#: 5175 Product:  XMLP WG Version: unspecified Platform: PC OS/Version: Windows NT Status: RESOLVED Severity: normal Priority: P2 Resolution: FIXED Assigned To: chrisfer@us.ibm.com Reported By: ram.jeyaraman@microsoft.com QA Contact: chrisfer@us.ibm.com Component: mtom policy assertion Target Milestone: --- URL:  Summary: Changes to Section 1 (Last Call comment - editorial) Keywords:   Status Whiteboard:  Opened: 2007-10-10 16:00 Description:   Opened: 2007-10-10 16:00 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 From Christopher Ferris 2007-10-10 19:57:38 ------- 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 Bug 5176 - Namespace URI (LC comment - editorial) Bug#: 5176 Product:  XMLP WG Version: unspecified Platform: PC OS/Version: Windows NT Status: RESOLVED Severity: normal Priority: P2 Resolution: WONTFIX Assigned To: chrisfer@us.ibm.com Reported By: ram.jeyaraman@microsoft.com QA Contact: chrisfer@us.ibm.com Component: mtom policy assertion Target Milestone: --- URL:  Summary: Namespace URI (LC comment - editorial) Keywords:   Status Whiteboard:  Opened: 2007-10-10 16:04 Description:   Opened: 2007-10-10 16:04 The Last Call version [1] uses the namespace URI http://www.w3.org/2007/08/soap12-mtom-policy. Is there a reason why this namespace or the expected stable namespace URI http://www.w3.org/ns/soap12-mtom-policy contains the phrase ?soap12? in it? Is this policy assertion linked to a particular version of SOAP? [1] http://www.w3.org/TR/2007/WD-soap12-mtom-policy-20070918/ ------- Comment #1 From Christopher Ferris 2007-10-17 19:13:55 ------- RESOLUTION: close issue 5176 with no action and respond to commentor that the assertion is in fact not specific to soap12 See http://www.w3.org/2007/10/17-xmlprotocol-irc#T19-13-23 Bug 5205 - reinforce sect 3.3 to make it clear it is specific to binding protocol Bug#: 5205 Product:  XMLP WG Version: unspecified Platform: All OS/Version: All Status: RESOLVED Severity: normal Priority: P2 Resolution: FIXED Assigned To: chrisfer@us.ibm.com Reported By: chrisfer@us.ibm.com QA Contact: chrisfer@us.ibm.com Component: mtom policy assertion Target Milestone: --- URL:  Summary: reinforce sect 3.3 to make it clear it is specific to binding protocol Keywords:   Status Whiteboard:  Opened: 2007-10-17 13:39 Description:   Opened: 2007-10-17 13:39 Essentially, we need to make it clear that what the assertion says is "use MTOM" as appropriate to the specific transport protocol binding to which the assertion applies. See minutes from WG telcon [1]. [1] http://www.w3.org/2007/10/10-xmlprotocol-minutes.html ------- Comment #1 From Christopher Ferris 2008-04-16 13:11:44 ------- closed with proposal from Anish[1], as tweaked by Chris [2] [1] http://lists.w3.org/Archives/Public/xml-dist-app/2007Nov/0008.html [2] http://lists.w3.org/Archives/Public/xml-dist-app/2007Dec/0000.html Actions: Home | New | Search | | Reports | My Requests | My Votes | Log out chrisfer@us.ibm.com Edit: Prefs | Users Saved Searches: My Bugs   bugs to the new saved search: