ISSUE-4 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 |
SOAP-JMS Binding Working Group |
ISSUE-14 WSDL conformance statements missing |
OPEN |
Apparently normative statements about WSDL are not written that way. |
2009-09-29 |
SOAP-JMS Binding specification |
0 |
SOAP-JMS Binding Working Group |
ISSUE-15 Incorrect use of RFC keywords |
OPEN |
WSDL section of spec uses RFC 2119 keywords inappropriately |
2009-09-29 |
SOAP-JMS Binding specification |
0 |
SOAP-JMS Binding Working Group |
ISSUE-16 non-existent "soap" prefix |
OPEN |
Section 3.4.5 refers to a non-existent "soap" prefix |
2009-10-20 |
SOAP-JMS Binding specification |
0 |
SOAP-JMS Binding Working Group |
ISSUE-17 References to RFC 3987 |
OPEN |
References to RFC 3987 are incorrect, not consistent with expected use |
2009-10-26 |
SOAP-JMS Binding specification |
0 |
SOAP-JMS Binding Working Group |
ISSUE-18 consistency of references, acronyms |
OPEN |
consistency of references, acronyms |
2009-10-26 |
SOAP-JMS Binding specification |
0 |
SOAP-JMS Binding Working Group |
ISSUE-19 3001, 3002, 3003 overlap |
OPEN |
Normative statements 3001, 3002, 3003 overlap and/or are redundant |
2009-10-26 |
|
0 |
SOAP-JMS Binding Working Group |
ISSUE-20 Statement 3004 lacks context, RFC 2119 keywords |
OPEN |
Statement 3004 lacks context, RFC 2119 keywords |
2009-10-26 |
SOAP-JMS Binding specification |
0 |
SOAP-JMS Binding Working Group |