ISSUE-8: Example in C2 contrary to Protocol-2029
Incorrect example, section C2
Example in C2 contrary to Protocol-2029
- State:
- CLOSED
- Product:
- SOAP-JMS Binding specification
- Raised by:
- Eric Johnson
- Opened on:
- 2009-07-29
- Description:
- 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
- Related Actions Items:
ACTION-91 on Eric Johnson to Propose a change to Spec. wording to remedy inconsistency in MIME example vs. Protocol-2029 assertion - due 2009-07-21, closed- Related emails:
- Agenda for 2009-09-08 conference call (from eric@tibco.com on 2009-09-07)
- RE: Agenda for 2009-09-01 conference call (from Derek.Rokicki@softwareag.com on 2009-09-01)
- RE: Agenda for 2009-09-01 conference call (from peaston@progress.com on 2009-09-01)
- Agenda for 2009-09-01 conference call (from eric@tibco.com on 2009-08-31)
- RE: Agenda for 2009-08-25 conference call (from peaston@progress.com on 2009-08-25)
- Agenda for 2009-08-25 conference call (from eric@tibco.com on 2009-08-24)
- ISSUE-8: update available (from phil_adams@us.ibm.com on 2009-08-18)
- Re: ACTION-91 - proposal to resolve ISSUE-8 (from phil_adams@us.ibm.com on 2009-08-11)
- RE: Agenda for 2009-08-11 conference call (from peaston@progress.com on 2009-08-11)
- Agenda for 2009-08-11 conference call (from eric@tibco.com on 2009-08-10)
- ACTION-91 - proposal to resolve ISSUE-8 (from eric@tibco.com on 2009-08-10)
- Re: Agenda for 2009-08-04 conference call (from M8PHILLI@uk.ibm.com on 2009-08-04)
- Re: Agenda for 2009-08-04 conference call (from ylafon@w3.org on 2009-08-04)
- Agenda for 2009-08-04 conference call (from eric@tibco.com on 2009-08-03)
- ISSUE-8 (Incorrect example, section C2): Example in C2 contrary to Protocol-2029 [SOAP-JMS Binding specification] (from sysbot+tracker@w3.org on 2009-07-29)
- Action item 95 complete (from eric@tibco.com on 2009-07-29)
Related notes:
Applied resolution accepted in conf. call of 2009-09-08:
http://www.w3.org/2009/09/08-soap-jms-minutes.html#item07
Display change log