Issues

Apply the following changes to selected issues:

There are 20 issues listed in the system.

↓ID ↓State Title Raised on ↓Product Open Actions
ISSUE-1 (edit)
Assert Protocol-2013 is spurious		 CLOSED Assertion Protocol-2013 is missing RFC 2119 language 2009-07-27 SOAP-JMS Binding specification 0
ISSUE-2 (edit)
Protocol-2020 is spurious		 CLOSED Assertion Protocol-2020 missing RFC 2119 language 2009-07-27 SOAP-JMS Binding specification 0
ISSUE-3 (edit)
Protocol-2023 is spurious		 CLOSED Assertion Protocol-2023 missing RFC 2119 language 2009-07-27 SOAP-JMS Binding specification 0
ISSUE-4 (edit)
Protocol-2024 needs restructuring		 OPEN Protocol-2024 does not include RFC-2119 language, has large associated table 2009-07-27 SOAP-JMS Binding specification 0
ISSUE-5 (edit)
Protocol-2035 is redundant		 CLOSED Protocol-2035 is redundant 2009-07-27 SOAP-JMS Binding specification 0
ISSUE-6 (edit)
Protocol 2039 redundant		 CLOSED Protocol 2039 redundant, missing RFC 2119 language 2009-07-28 SOAP-JMS Binding specification 0
ISSUE-7 (edit)
Protocol-2041 is spurious		 CLOSED Protocol-2041 is spurious 2009-07-29 SOAP-JMS Binding specification 0
ISSUE-8 (edit)
Incorrect example, section C2		 CLOSED Example in C2 contrary to Protocol-2029 2009-07-29 SOAP-JMS Binding specification 0
ISSUE-9 (edit) CLOSED Clarify wording of assertions that deal with fault subcodes 2009-08-10 SOAP-JMS Binding specification 0
ISSUE-10 (edit)
redundant assertions 2016 and 2017		 CLOSED Combine redundant assertions 2016 and 2017 2009-08-10 SOAP-JMS Binding specification 0
ISSUE-11 (edit)
requestURI in response message?		 CLOSED Should SOAPJMS_requestURI be in the response message? 2009-08-24 SOAP-JMS Binding specification 0
ISSUE-12 (edit)
Bad MIME terminating boundary		 CLOSED MIME multipart terminating boundary incorrect in Example C2 2009-09-15 SOAP-JMS Binding specification 0
ISSUE-13 (edit)
Extra space in Schema		 CLOSED Soapjms schema issue 2009-09-23 SOAP-JMS Binding specification 0
ISSUE-14 (edit)
WSDL conformance statements missing		 OPEN Apparently normative statements about WSDL are not written that way. 2009-09-29 SOAP-JMS Binding specification 0
ISSUE-15 (edit)
Incorrect use of RFC keywords		 OPEN WSDL section of spec uses RFC 2119 keywords inappropriately 2009-09-29 SOAP-JMS Binding specification 0
ISSUE-16 (edit)
non-existent "soap" prefix		 OPEN Section 3.4.5 refers to a non-existent "soap" prefix 2009-10-20 SOAP-JMS Binding specification 0
ISSUE-17 (edit)
References to RFC 3987		 OPEN References to RFC 3987 are incorrect, not consistent with expected use 2009-10-26 SOAP-JMS Binding specification 0
ISSUE-18 (edit)
consistency of references, acronyms		 OPEN consistency of references, acronyms 2009-10-26 SOAP-JMS Binding specification 0
ISSUE-19 (edit)
3001, 3002, 3003 overlap		 OPEN Normative statements 3001, 3002, 3003 overlap and/or are redundant 2009-10-26 0
ISSUE-20 (edit)
Statement 3004 lacks context, RFC 2119 keywords		 OPEN Statement 3004 lacks context, RFC 2119 keywords 2009-10-26 SOAP-JMS Binding specification 0

Raise an issue .

Eric Johnson <eric@tibco.com>, Chair, Yves Lafon <ylafon@w3.org>, Staff Contact
Tracker, originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: issues.php,v 1.10 2009/08/06 13:54:53 dom Exp $