Sunday, 31 March 2002
Friday, 29 March 2002
Thursday, 28 March 2002
Wednesday, 27 March 2002
- Issue 110 resolution
- Re: Issue 189: closed
- Re: Issue Gudge General a): closed ("split part 2")
- Re: Issue Gudge General a): closed ("split part 2")
Monday, 25 March 2002
Friday, 22 March 2002
- RE: Issue #176 closed
- RE: Issue 189: closed
- Re: Issue 189: closed
- Re: Issue #176 closed
- RE: SOAP Email Binding Meeting - Tuesday, March 26 - 8 AM PST, 11 AM EST - Con-call info
- Issue #176 closed
- Fw: UUID message identifiers
- Re: Issue with encodingStyle
- Re: NameValue and NameValueList data types
- Issue 186 closed: Uniqueness and reference constraints on id and ref attributes
- Issue 167 closed: Support for XML Schema Types
- Issue 189: closed
Thursday, 21 March 2002
Friday, 15 March 2002
Tuesday, 12 March 2002
- Issue 48 Re-closed (re:custom data encodings)
- Re: Resolution of Issue 182: "Fault code restriction."
- Resolution of Issue 67: "convey error information."
- Resolution of Issue 182: "Fault code restriction."
- Resolution of Issue 183: Default values of SOAP header block att ributes"
- Issue 51 closed: Support different message patterns
Friday, 8 March 2002
Thursday, 7 March 2002
- Issue 57 closed: Usage Scenario over multiple transports
- FW: Issue 17 closed
- Re: Issue 154 closed: Invariance of role
- Issue 154 closed: Invariance of role
- Re: Issue 179 closed: One-way messaging in SOAP 1.2
Wednesday, 6 March 2002
- Issue 137:
- Issue 181 closed: Inconsistency between section 4.4.3 and section 2
- Issue 184 closed: : XML Legacy Types in SOAP Encoding Schema
- Issue #44 closed : req/resp correlation over non-HTTP protocols
- Issue #33 closed : modularity
Tuesday, 5 March 2002
- Re: Issue 103 closed: Precisely describe message path semantics
- Issue 179 closed: One-way messaging in SOAP 1.2
Monday, 4 March 2002
- Issue 16 closed: Void return type and no out arg
- Issue 113 Closed: Representing void returns in the presence of o ut/inout params
- Issue 178 closed: requirements imposed by end-to-end features
- Issue 103 closed: Precisely describe message path semantics