ISSUE-1: Assertion Protocol-2013 is missing RFC 2119 language

Assert Protocol-2013 is spurious

Assertion Protocol-2013 is missing RFC 2119 language

State:
CLOSED
Product:
SOAP-JMS Binding specification
Raised by:
Eric Johnson
Opened on:
2009-07-27
Description:
Description:
------------
We have this paragraph: "if the charset parameter is specified it is checked to ensure that it matches the encoding value from the supplied XML. If there is a mismatch then a fault MUST be generated.† [Definition: Use fault subcode contentTypeMismatch in the event that the values do not match.†]

Protocol-2012 captures the first sentence, and Protocol-2013 covers the [Definition:]. Notice that the definition doesn't have any RFC 2119 language.

Justification:
--------------
It is impossible to test Protocol-2013 without also testing 2012. Further, Protocol-2013 does not contain any RFC 2119 language. Yet it is clearly subsidiary to Protocol-2012, and the absence of this language leaves it unclear as to what MUST be done. Combining the two statements will clarify the possible confusion.

Proposal:
---------

Change the paragraph that reads:
"if the charset parameter is specified it is checked to ensure that it matches the encoding value from the supplied XML. If there is a mismatch then a fault MUST be generated.† [Definition: Use fault subcode contentTypeMismatch in the event that the values do not match.†]

to this:

"If the charset parameter is specified it is checked to ensure that it matches the encoding value from the supplied XML. A fault MUST be generated with [Definition: subcode *contentTypeMismatch* if the encoding values do not match.]†"

Related Actions Items:
No related actions
Related emails:
  1. Minutes 2009/08/11 (from M8PHILLI@uk.ibm.com on 2009-08-11)
  2. RE: Agenda for 2009-08-11 conference call (from peaston@progress.com on 2009-08-11)
  3. Agenda for 2009-08-11 conference call (from eric@tibco.com on 2009-08-10)
  4. Re: ISSUE-1: update available (from eric@tibco.com on 2009-08-10)
  5. ISSUE-1: update available (from phil_adams@us.ibm.com on 2009-08-10)
  6. Re: Agenda for 2009-08-04 conference call (from M8PHILLI@uk.ibm.com on 2009-08-04)
  7. Re: Agenda for 2009-08-04 conference call (from ylafon@w3.org on 2009-08-04)
  8. Agenda for 2009-08-04 conference call (from eric@tibco.com on 2009-08-03)
  9. Action item 95 complete (from eric@tibco.com on 2009-07-29)
  10. RE: Agenda for 2009-07-28 conference call (from peaston@progress.com on 2009-07-28)
  11. Agenda for 2009-07-28 conference call (from eric@tibco.com on 2009-07-27)
  12. ISSUE-1 (Assert Protocol-2013 is spurious): Assertion Protocol-2013 is missing RFC 2119 language [SOAP-JMS Binding specification] (from sysbot+tracker@w3.org on 2009-07-27)

Related notes:

Conf. call 2009-08-11 - agreed with application of the resolution:

http://www.w3.org/2009/08/11-soap-jms-minutes.html

Eric Johnson, 17 Aug 2009, 20:46:09

Amending issue: opened on 2009-08-04:
http://www.w3.org/2009/08/04-soap-jms-minutes.html

Eric Johnson, 6 Oct 2010, 01:23:58

Amending issue record:
http://www.w3.org/2009/08/04-soap-jms-minutes.html
Accepted proposal as written in issue tracker.

Eric Johnson, 6 Oct 2010, 01:27:22

Amending issue record:
XML diff:
http://dev.w3.org/cvsweb/2008/ws/soapjms/soapjms.xml.diff?r1=1.53&r2=1.54&f=h
HTML diff:
http://dev.w3.org/cvsweb/2008/ws/soapjms/soapjms.html.diff?r1=1.52&r2=1.53&f=h

Eric Johnson, 6 Oct 2010, 01:47:36

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: 1.html,v 1.1 2013-09-16 14:06:33 carine Exp $