ISSUE-48: Unflagged assertions about message body and content type

unflagged message body assertions

Unflagged assertions about message body and content type

State:
CLOSED
Product:
SOAP-JMS Binding specification
Raised by:
Eric Johnson
Opened on:
2010-07-16
Description:
From email: http://lists.w3.org/Archives/Public/public-soap-jms/2010Jul/0013.html

Section 2.4: Four "MUST" statements not flagged as normative assertions:
First pair: "Based on the sending node's use of SOAP 1.1, SOAP 1.2, SOAP Messages with Attachments, and MTOM, the contentType property MUST be set as it would be for SOAP/HTTP, and the message body MUST use the corresponding format. "

Second pair: "For example, if the SOAP payload is formatted as a simple SOAP envelope, the contentType property value MUST be specified as "text/xml" for SOAP 1.1 or "application/soap+xml" for SOAP 1.2. On the other hand, if the SOAP payload is formatted as a MIME multipart message, the contentType property value MUST be specified as "multipart/related". "

The above are not flagged as normative assertions.

In addition, the assertions about the contentType property are more appropriate to put with the definition of that property, and stated somewhat differently from what is already under the definition for that property.

Proposal:
Overall, the easiest way to fix this issue, it seems is to defer to the definition of the "contentType" property.

Details:
Remove the two paragraphs noted above. Add a new sentence at the beginning of the current paragraph #4 (which currently starts "In this way...") that reads:

The bytes or characters of the JMS Message payload correspond to the MIME format as indicated by the definition of the contentType property.

Also in the same paragraph (#4), for slightly more clarity, replace the words "Note also that" with "Specifically, "
Related Actions Items:
Related emails:
  1. Applied resolution of issue 48, completing action 204 (from eric@tibco.com on 2010-08-30)
  2. Agenda for the 2010-08-31 conference call (from eric@tibco.com on 2010-08-30)
  3. Agenda for the 2010-08-24 conference call (from eric@tibco.com on 2010-08-23)
  4. ACTION 199 (from M8PHILLI@uk.ibm.com on 2010-08-23)
  5. RE: Agenda for the 2010-08-17 conference call (from Derek.Rokicki@softwareag.com on 2010-08-17)
  6. Agenda for the 2010-08-17 conference call (from eric@tibco.com on 2010-08-16)
  7. Agenda for the 2010-08-03 conference call (from eric@tibco.com on 2010-08-02)
  8. Agenda for the 2010-07-27 conference call (from eric@tibco.com on 2010-07-26)
  9. Re: Agenda for the 2010-07-20 conference call (from eric@tibco.com on 2010-07-20)
  10. RE: Agenda for the 2010-07-20 conference call (from Derek.Rokicki@softwareag.com on 2010-07-20)
  11. Re: Agenda for the 2010-07-20 conference call (from phil_adams@us.ibm.com on 2010-07-20)
  12. Agenda for the 2010-07-20 conference call (from eric@tibco.com on 2010-07-19)
  13. Re: ACTION 186 - top to bottom review of current copy of spec (from eric@tibco.com on 2010-07-16)
  14. ISSUE-48 (unflagged message body assertions): Unflagged assertions about message body and content type [SOAP-JMS Binding specification] (from sysbot+tracker@w3.org on 2010-07-16)

Related notes:

Opened as per conf. call of 2010-07-27:
http://www.w3.org/2010/07/27-soap-jms-minutes.html

Eric Johnson, 3 Aug 2010, 00:02:51

Resolved as per: http://www.w3.org/2010/08/24-soap-jms-minutes.html

Eric Johnson, 30 Aug 2010, 21:28:44

Application of resolution accepted as per 2010-08-31 conf call:
http://www.w3.org/2010/08/31-soap-jms-minutes.html

Eric Johnson, 7 Sep 2010, 15:27:49

Display change log ATOM feed


Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 48.html,v 1.1 2013-09-16 14:06:36 carine Exp $