- From: Eric Johnson <eric@tibco.com>
- Date: Wed, 29 Jul 2009 13:25:35 -0700
- To: SOAP-JMS <public-soap-jms@w3.org>
Title: Example in C2 contrary to Protocol-2029
Description:
------------
in the example, the text of the example starts with this:
MIME-Version: 1.0
Content-Type: Multipart/Related;boundary=MIME_boundary;
type="application/xop+xml";
start="<945414389.1092086011970>";
startinfo="application/soap+xml"
This, of course, is contrary to Protocol-2029, which reads:
Note also that if the payload is formatted as a MIME multipart message,
then the first byte or character encountered in the JMS Message body
MUST be the start of the MIME boundary for the start of the first part —
what MIME Part One [IETF RFC 2045] section 2.5 calls a "Body Part".
Justification:
--------------
Example should match the normative text
Proposal:
---------
Remove all the text in the example that comes before the first MIME
boundary.
(Note that this is a formal filing of an issue from the email
http://lists.w3.org/Archives/Public/public-soap-jms/2009Jul/0001.html )
-Eric Johnson
Received on Wednesday, 29 July 2009 20:24:49 UTC