David Fallside
- Re: Updated example (was Re: RDF response on XMLP Issue #29)
- Re: SOAP Primer Review
- Re: typo, please forward
- Issue 110 resolution
- Issue 180 resolution
Doug Davis
Gaertner, Dietmar
Glen Daniels
Henrik Frystyk Nielsen
- Maintaining status-quo on question about envelope parameter on SOAP media type
- RE: Issue #176 closed
- RE: Issue 189: closed
- Issue #176 closed
- Issue #41 closed
Herve Ruellan
Hoelzing, Gerd
Jacek Kopecky
- Re: Issue Gudge General a): closed ("split part 2")
- Issue 78 closed: ordering of structs
- Issue 59 closed: mandating character encodings
- Issue 177 closed: missing elements same as nils
Jean-Jacques Moreau
John Ibbotson
Marc Hadley
- Issue 48 Re-closed (re:custom data encodings)
- Re: Resolution of Issue 182: "Fault code restriction."
- Re: Issue 179 closed: One-way messaging in SOAP 1.2
Mark Baker
Martin Gudgin
- 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 137:
- Issue 181 closed: Inconsistency between section 4.4.3 and section 2
- Issue 184 closed: : XML Legacy Types in SOAP Encoding Schema
Mountain, Highland M
Murali Janakiraman
- Issue 57 closed: Usage Scenario over multiple transports
- Issue 16 closed: Void return type and no out arg
- Issue 113 Closed: Representing void returns in the presence of o ut/inout params
noah_mendelsohn@us.ibm.com
- RE: Issue 189: closed
- Re: Issue 189: closed
- Re: Issue #176 closed
- Re: Issue 103 closed: Precisely describe message path semantics