ISSUE-32: Protocol-2015 too vaguely worded, probably unnecessary

Protocol-2015 too vague

Protocol-2015 too vaguely worded, probably unnecessary

State:

CLOSED

Product:

SOAP-JMS Binding specification

Raised by:

Eric Johnson

Opened on:

2010-03-15

Description:

At the moment, Protocol-2015 (http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?content-type=text/html;%20charset=utf-8#Protocol-2015)

states: "The contentType parameter MUST reflect the value specified in the Content-type part header for the first part (the SOAP body, so text/xml or application/xop+xml)"

Items:
#1) Vague: "reflect" is a completely vague word with unclear meaning.

#2) Incorrect: "first part" - should the message be MIME multi-part, the "first part" could be a binary attachment - it does not need to be the actual SOAP message (as we've discussed in previous conference calls and email threads)

#3) Incomplete: "so text/xml or..." - is an incomplete list of possibilities, but its presence in a normative statement implies it is exhaustive.

Particularly on the last item (#3), I don't see that it is actually useful to be exhaustive - if someone comes up with a new SOAP specification that somehow affects the "contentType" parameter, it would be better for everyone if our spec is not overly prescriptive.

Proposal:

Remove the normative statement, as it is not clarifying anything, and it isn't adding any useful normative requirements.

Related Actions Items:

No related actions

Related emails:

1. Issue-30, Issue-31: update available (from phil_adams@us.ibm.com on 2010-04-26)
2. Agenda for the 2010-04-13 conference call (from eric@tibco.com on 2010-04-26)
3. Issue-32, Issue-33: update available (from phil_adams@us.ibm.com on 2010-04-26)
4. Updated: Agenda for the 2010-04-13 conference call (from eric@tibco.com on 2010-04-12)
5. Agenda for the 2010-04-13 conference call (from eric@tibco.com on 2010-04-12)
6. Agenda for the 2010-04-06 conference call (from eric@tibco.com on 2010-04-05)
7. Re: Agenda for 2010-03-30 conference call (from eric@tibco.com on 2010-03-29)
8. Agenda for 2010-03-30 conference call (from eric@tibco.com on 2010-03-29)
9. Re: Agenda for 2010-03-16 conference call (from eric@tibco.com on 2010-03-15)
10. Agenda for 2010-03-16 conference call (from eric@tibco.com on 2010-03-15)
11. Re: ISSUE-32 (Protocol-2015 too vague): Protocol-2015 too vaguely worded, probably unnecessary [SOAP-JMS Binding specification] (from eric@tibco.com on 2010-03-15)
12. ISSUE-32 (Protocol-2015 too vague): Protocol-2015 too vaguely worded, probably unnecessary [SOAP-JMS Binding specification] (from sysbot+tracker@w3.org on 2010-03-15)

Related notes:

Display change log