- From: <noah_mendelsohn@us.ibm.com>
- Date: Mon, 26 Jan 2004 14:57:13 -0500
- To: "Martin Gudgin" <mgudgin@microsoft.com>
- Cc: xmlp-comments@w3.org
Martin Gudgin writes: > I trust the resolves the issue to your satisfaction. In this case, I would like the record to show that I believe we have probably made a mistake here, at least in the case of allowing the HTTP binding to carry unreferenced parts. I think this is unnecessary and a potential back-door threat to interoperability. That said, I do not wish to formally contest this decision but merely to log my opinion in the record. I therefore agree to accept the resolution as you've summarized it. BTW: your email to me included a cc: to Noah_Mendelsohn@lotus.com. That address is no longer valid and mail sent to it may (or may not) bounce. My correct business email address is Noah_Mendelsohn@us.ibm.com. Thank you! -------------------------------------- Noah Mendelsohn IBM Corporation One Rogers Street Cambridge, MA 02142 1-617-693-4036 -------------------------------------- "Martin Gudgin" <mgudgin@microsoft.com> Sent by: xmlp-comments-request@w3.org 01/26/2004 06:26 AM To: <xmlp-comments@w3.org> cc: "Mendelsohn, Noah" <Noah_Mendelsohn@lotus.com>, (bcc: Noah Mendelsohn/Cambridge/IBM) Subject: RE: Resolution for Issue 440 And heres the reference [1] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x440 > -----Original Message----- > From: Martin Gudgin > Sent: 26 January 2004 11:26 > To: 'xmlp-comments@w3.org' > Cc: Mendelsohn, Noah > Subject: Resolution for Issue 440 > > Noah, > > You raised Issue 440[1] regarding multiple references to a > single MIME part and unreferenced MIME parts in MTOM/XOP. > > The XMLP WG has resolved this issue as follows: > > XOP will allow unreferenced MIME parts > MTOM and HTTP binding will allow unreferenced MIME parts but > such MIME parts play no part in SOAP processing. > > XOP will allow multiple refs per binary part MTOM will allow > multiple refs per binary part HTTP binding will allow only > one ref per binary part > > I trust the resolves the issue to your satisfaction. > > Regards > > Martin Gudgin > For the W3C XMLP WG >
Received on Monday, 26 January 2004 14:58:54 UTC