xmlp-comments@w3.org from March 2002 by subject

Issue #176 closed

Issue #33 closed : modularity

Issue #41 closed

Issue #44 closed : req/resp correlation over non-HTTP protocols

Issue 103 closed: Precisely describe message path semantics

Issue 110 resolution

Issue 113 Closed: Representing void returns in the presence of o ut/inout params

Issue 137:

Issue 154 closed: Invariance of role

Issue 16 closed: Void return type and no out arg

Issue 167 closed: Support for XML Schema Types

Issue 17 closed

Issue 177 closed: missing elements same as nils

Issue 178 closed: requirements imposed by end-to-end features

Issue 179 closed: One-way messaging in SOAP 1.2

Issue 180 resolution

Issue 181 closed: Inconsistency between section 4.4.3 and section 2

Issue 184 closed: : XML Legacy Types in SOAP Encoding Schema

Issue 186 closed: Uniqueness and reference constraints on id and ref attributes

Issue 189: closed

Issue 48 Re-closed (re:custom data encodings)

Issue 51 closed: Support different message patterns

Issue 54

Issue 57 closed: Usage Scenario over multiple transports

Issue 59 closed: mandating character encodings

Issue 78 closed: ordering of structs

Issue Gudge General a): closed ("split part 2")

Issue with encodingStyle

Maintaining status-quo on question about envelope parameter on SOAP media type

NameValue and NameValueList data types

Resolution of Issue 182: "Fault code restriction."

Resolution of Issue 183: Default values of SOAP header block att ributes"

Resolution of Issue 67: "convey error information."

SOAP Email Binding Meeting - Tuesday, March 26 - 8 AM PST, 11 AM EST - Con-call info

SOAP Primer Review

typo, please forward

Updated example (was Re: RDF response on XMLP Issue #29)

UUID message identifiers

Last message date: Sunday, 31 March 2002 18:35:40 UTC