Andrew Layman
- RE: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. (Saturday, 23 February)
- RE: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. (Saturday, 23 February)
- RE: Soap Message Canonicalization (SM-C14N) (Sunday, 17 February)
- RE: SOAP Encoding and Schema (Sunday, 17 February)
- RE: Issue with soap-rpc:result (Sunday, 17 February)
- RE: Soap Message Canonicalization (SM-C14N) (Sunday, 17 February)
- RE: SOAP Encoding: Default values (Sunday, 17 February)
- Possibly defaulted (was RE: Minutes for Thurs 7th Feb 2002 Telcon) (Friday, 8 February)
- RE: Issue with soap-rpc:result (Friday, 8 February)
- RE: Issue with soap-rpc:result (Thursday, 7 February)
- RE: Issue with encodingStyle (Thursday, 7 February)
- RE: Issue with encodingStyle (Thursday, 7 February)
Asir S Vedamuthu
bill palmer
Bob Cunnings
Champion, Mike
Christopher Ferris
- Re: Issue 182: Fault Code restriction: "At Most One Fault Proposal" (Thursday, 21 February)
- Re: XMLP/XMLE Use cases and processing models (Thursday, 21 February)
- Re: Issue 182: Fault Code restriction: "At Most One Fault Proposal" (Thursday, 21 February)
- Re: Soap Message Canonicalization (SM-C14N) (Monday, 18 February)
- Re: Soap Message Canonicalization (SM-C14N) (Friday, 15 February)
- oops! Re: Resolving the ednote in part 1 section 5.1 (Friday, 15 February)
- Re: Resolving the ednote in part 1 section 5.1 (Friday, 15 February)
- Re: TBTF: Proposed resolution issue 179 (Tuesday, 12 February)
- Re: Proposal for resolution of issue 176 (Tuesday, 12 February)
- Re: Proposal for resolution of issue 176 (Tuesday, 12 February)
- Re: Proposal for resolution of issue 176 (Monday, 11 February)
- Re: Proposal for resolution of issue 176 (Monday, 11 February)
- Re: Proposal for resolution of issue 176 (Monday, 11 February)
- TBTF: revised proposed resolution for i178 (Friday, 8 February)
- Re: Proposed rewrite of Part 1, section 2 (long) (Wednesday, 6 February)
- Re: TBTF: security considerations proposed text (Tuesday, 5 February)
- TBTF: proposal for issue #57 (Tuesday, 5 February)
- TBTF: proposed resolution for i178 (Tuesday, 5 February)
- TBTF: security considerations proposed text (Monday, 4 February)
- Re: TBTF: SOAP MEP vs TMEP (Monday, 4 February)
- Re: Who Faulted (was RE: Proposed rewrite of Part 1, section 2 (l ong) ) (Friday, 1 February)
CSC@w3.org
David E. Cleary
David Orchard
dirkx@covalent.net
Don Box
Eastlake III Donald-LDE008
Eugene Kuznetsov
Fred Carter
Glen Daniels
Handoko
Henrik Frystyk Nielsen
- RE: Issue 182: Fault Code restriction: "At Most One Fault Proposa l" (Saturday, 23 February)
- RE: Soap Message Canonicalization (SM-C14N) (Saturday, 23 February)
- RE: Issue 182: Fault Code restriction: "At Most One Fault Proposal" (Saturday, 23 February)
- RE: Issue 182: Fault Code restriction: "At Most One Fault Proposal" (Saturday, 23 February)
- RE: Issue 182: Fault Code restriction: "At Most One Fault Proposal" (Thursday, 21 February)
- RE: Issue 182: Fault Code restriction: "At Most One Fault Proposal" (Thursday, 21 February)
- RE: Soap Message Canonicalization (SM-C14N) (Thursday, 21 February)
- RE: Issue 182: Fault Code restriction: "At Most One Fault Proposal" (Thursday, 21 February)
- RE: Soap Message Canonicalization (SM-C14N) (Thursday, 21 February)
- RE: Soap Message Canonicalization (SM-C14N) (Wednesday, 20 February)
- RE: Soap Message Canonicalization (SM-C14N) (Wednesday, 20 February)
- RE: Soap Message Canonicalization (SM-C14N) (Wednesday, 20 February)
- Proposal for resolving issue 180 (Tuesday, 19 February)
- ETF and editors: Issue 17 and 48: Proposal for describing when to use SOAP encoding (Tuesday, 19 February)
- RE: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. (Monday, 18 February)
- RE: SOAP Encoding: Default values (Monday, 18 February)
- RE: New Issue: Fault Code Restrictions (Saturday, 16 February)
- Proposed resolution for issue 103 (Saturday, 16 February)
- RE: Soap Message Canonicalization (SM-C14N) (Friday, 15 February)
- RE: Resolving the ednote in part 1 section 5.1 (Thursday, 14 February)
- Resolving the ednote in part 1 section 5.1 (Wednesday, 13 February)
- RE: TBTF: Proposed resolution issue 179 (Tuesday, 12 February)
- RE: New issue: Default values of SOAP header block attributes (Tuesday, 12 February)
- Issues 16 and 113: Proposed resolution (Tuesday, 12 February)
- RE: Proposal for resolution of issue 176 (Tuesday, 12 February)
- RE: Proposal for resolution of issue 176 (Tuesday, 12 February)
- Issue 55: Proposed resolution (Tuesday, 12 February)
- RE: Proposal for resolution of issue 176 (Monday, 11 February)
- Proposal for resolution of issue 176 (Monday, 11 February)
- New issue: Default values of SOAP header block attributes (Sunday, 10 February)
- RE: RPC Mapping (Friday, 8 February)
- RE: RPC Mapping (Friday, 8 February)
- RE: Issue 177: missing elements same as nils? (Wednesday, 6 February)
- Issue 177: missing elements same as nils? (Wednesday, 6 February)
- XML name encoding examples (Monday, 4 February)
- RE: DIME and SOAP in DIME specs submitted as IETF Internet Drafts (Monday, 4 February)
- DIME and SOAP in DIME specs submitted as IETF Internet Drafts (Saturday, 2 February)
- RE: Issue 133, and permitting no body (Friday, 1 February)
- RE: Who Faulted (was RE: Proposed rewrite of Part 1, section 2 (l ong) ) (Friday, 1 February)
Hugo Haas
Ibhar Software
Jacek Kopecky
- Draft resolution for issue 59 (Friday, 22 February)
- RE: Issue with soap-rpc:result (Friday, 22 February)
- Re: SOAP Encoding multistructs (Wednesday, 20 February)
- SOAP Encoding multistructs (Wednesday, 20 February)
- ETF's proposal for issue 78: RPC structs and Encoding root attribute (Wednesday, 20 February)
- Re: ETF and editors: Issue 17 and 48: Proposal for describing when to use SOAP encoding (Tuesday, 19 February)
- Re: Proposal for issue 78: RPC structs and Encoding root attribute (Tuesday, 19 February)
- Re: Proposal for issue 78: RPC structs and Encoding root attribute (Tuesday, 19 February)
- Proposal for issue 78: RPC structs and Encoding root attribute (Monday, 18 February)
- Re: RPC/Encoding dependency (Monday, 18 February)
- Re: RPC/Encoding dependency (Monday, 18 February)
- RE: Issue with soap-rpc:result (Friday, 15 February)
- RE: Issue with soap-rpc:result (Friday, 15 February)
- RE: Issue with soap-rpc:result (Friday, 15 February)
- RE: Issue with soap-rpc:result (Friday, 15 February)
- RE: Issue with soap-rpc:result (Friday, 15 February)
- RE: Issue with soap-rpc:result (Thursday, 14 February)
- Re: Possibly defaulted (was RE: Minutes for Thurs 7th Feb 2002 Telcon) (Wednesday, 13 February)
- RE: Issue with soap-rpc:result (Wednesday, 13 February)
- Re: Issue with soap-rpc:result (Tuesday, 12 February)
- Re: Updated Proposal for Rewrite of Part 1 Section 2 (Tuesday, 12 February)
- Re: Possibly defaulted (was RE: Minutes for Thurs 7th Feb 2002 Telcon) (Tuesday, 12 February)
- Re: RPC/Encoding dependency (Tuesday, 12 February)
- Re: RPC Mapping (Tuesday, 12 February)
- RE: Issue with soap-rpc:result (Tuesday, 12 February)
- RE: Issue with soap-rpc:result (Tuesday, 12 February)
- RE: Issue with soap-rpc:result (Friday, 8 February)
- RE: Issue with soap-rpc:result (Friday, 8 February)
- RE: Issue with encodingStyle (Thursday, 7 February)
- RE: Issue with soap-rpc:result (Thursday, 7 February)
- RE: Issue with soap-rpc:result (Thursday, 7 February)
- Re: Issue with soap-rpc:result (Wednesday, 6 February)
- Re: Issue 177: missing elements same as nils? (Wednesday, 6 February)
- Re: SOAP Encoding - Arrays (Wednesday, 6 February)
- array dimension zero? (Tuesday, 5 February)
- Re: SOAP Encoding - Arrays (Tuesday, 5 February)
- Re: SOAP Encoding - Arrays (Friday, 1 February)
Jean-Jacques Moreau
- Re: Issue 182: Fault Code restriction: "At Most One Fault Proposal" (Thursday, 21 February)
- Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTT P binding preamble. (Thursday, 21 February)
- Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. (Wednesday, 20 February)
- Re: Proposal for resolution of issue 176 (Tuesday, 12 February)
- Re: Proposal for resolution of issue 176 (Tuesday, 12 February)
- Re: New issue: Default values of SOAP header block attributes (Tuesday, 12 February)
- Re: Email binding (Friday, 8 February)
- Re: Email binding (Friday, 8 February)
- Re: XMLP/XMLE Use cases and processing models (Wednesday, 6 February)
- Re: NOTATION attribute invalid in soap-encoding (Wednesday, 6 February)
- Re: NOTATION attribute invalid in soap-encoding (Tuesday, 5 February)
- Re: NOTATION attribute invalid in soap-encoding (Tuesday, 5 February)
- Re: TBTF: security considerations proposed text (Tuesday, 5 February)
- Re: DIME and SOAP in DIME specs submitted as IETF Internet Drafts (Monday, 4 February)
- Re: Who Faulted (was RE: Proposed rewrite of Part 1, section 2 (l ong) ) (Friday, 1 February)
- Re: Who Faulted (was RE: Proposed rewrite of Part 1, section 2 (l ong) ) (Friday, 1 February)
- Re: Who Faulted (was RE: Proposed rewrite of Part 1, section 2 (l ong) ) (Friday, 1 February)
John Ibbotson
John J. Barton
Joseph Reagle
Kirill Gavrylyuk
Kurt Cagle
Larry Masinter
Marc Hadley
- Revised Issue 137 Proposed Resolution (Thursday, 28 February)
- Issue 154: Role invariance - proposed resolution (Friday, 22 February)
- Re: ETF and editors: Issue 17 and 48: Proposal for describing when to use SOAP encoding (Tuesday, 19 February)
- Re: Proposal for issue 78: RPC structs and Encoding root attribute (Tuesday, 19 February)
- Re: Proposal for issue 78: RPC structs and Encoding root attribute (Tuesday, 19 February)
- Re: Soap Message Canonicalization (SM-C14N) (Tuesday, 19 February)
- Re: SOAP Encoding: Default values (Monday, 18 February)
- Re: TBTF: Proposed resolution issue 179 (Wednesday, 13 February)
- ETF: Telcon Minutes Tues 12th Feb 2002 (Tuesday, 12 February)
- New Issue: Fault Code Restrictions (Tuesday, 12 February)
- Re: Updated Proposal for Rewrite of Part 1 Section 2 (Tuesday, 12 February)
- Re: Proposal for resolution of issue 176 (Tuesday, 12 February)
- Re: TBTF: Proposed resolution issue 179 (Tuesday, 12 February)
- Re: Updated Proposal for Rewrite of Part 1 Section 2 (Monday, 11 February)
- TBTF: Proposed resolution issue 179 (Monday, 11 February)
- Re: Possibly defaulted (was RE: Minutes for Thurs 7th Feb 2002 Telcon) (Monday, 11 February)
- Updated Proposal for Rewrite of Part 1 Section 2 (Monday, 11 February)
- ETF: Minutes for Thurs 7th Feb 2002 Telcon (Friday, 8 February)
- Re: TBTF: SOAP MEP vs TMEP (Monday, 4 February)
- Re: Who Faulted (was RE: Proposed rewrite of Part 1, section 2 (l ong) ) (Monday, 4 February)
mario.jeckle@daimlerchrysler.com
Mark Baker
- Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. (Monday, 25 February)
- Re: SOAP & REST (Thursday, 7 February)
- Re: SOAP & REST (Thursday, 7 February)
- Re: SOAP & REST (Thursday, 7 February)
- Re: Issue 133, and permitting no body (Thursday, 7 February)
- Re: SOAP & REST (Wednesday, 6 February)
- Re: Issue 133, and permitting no body (Wednesday, 6 February)
- Re: Reflective systems (Wednesday, 6 February)
- SOAP & REST (Wednesday, 6 February)
- Re: TBTF: security considerations proposed text (Tuesday, 5 February)
- Re: Issue 133, and permitting no body (Tuesday, 5 February)
- Reflective systems (Monday, 4 February)
- Re: Issue 133, and permitting no body (Monday, 4 February)
- Re: Issue 133, and permitting no body (Monday, 4 February)
- Re: Issue 133, and permitting no body (Monday, 4 February)
- Re: Issue 133, and permitting no body (Monday, 4 February)
- Re: Issue 133, and permitting no body (Sunday, 3 February)
- Re: Issue 133, and permitting no body (Saturday, 2 February)
- Re: Issue 133, and permitting no body (Saturday, 2 February)
- Re: Issue 133, and permitting no body (Saturday, 2 February)
- Re: Issue 133, and permitting no body (Friday, 1 February)
- Re: Issue 133, and permitting no body (Friday, 1 February)
- Re: Issue 133, and permitting no body (Friday, 1 February)
- Re: Issue 133, and permitting no body (Friday, 1 February)
- Re: Issue 133, and permitting no body (Friday, 1 February)
Mark Nottingham
- Re: Issue 133: multple methods per URI (Friday, 22 February)
- Issue 133: multple methods per URI (Thursday, 21 February)
- Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. (Thursday, 21 February)
- Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTT P bi nding preamble. (Wednesday, 20 February)
- Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTT P bi nding preamble. (Wednesday, 20 February)
- Re: Soap Message Canonicalization (SM-C14N) (Wednesday, 20 February)
- Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTT P bi nding preamble. (Wednesday, 20 February)
- Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. (Tuesday, 19 February)
- Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. (Tuesday, 19 February)
- Re: Soap Message Canonicalization (SM-C14N) (Sunday, 17 February)
- Re: Soap Message Canonicalization (SM-C14N) (Saturday, 16 February)
- Re: Soap Message Canonicalization (SM-C14N) (Saturday, 16 February)
- Re: FYI: BCP 56, RFC 3205 on HTTP Layering (Thursday, 14 February)
- Re: SOAP & REST (Thursday, 7 February)
- Re: Issue 133, and permitting no body (Wednesday, 6 February)
- Re: Issue 133, and permitting no body (Tuesday, 5 February)
- Re: Issue 133, and permitting no body (Tuesday, 5 February)
- Re: Issue 133, and permitting no body (Monday, 4 February)
- Re: Issue 133, and permitting no body (Monday, 4 February)
- Re: Issue 133, and permitting no body (Saturday, 2 February)
- Re: Issue 133, and permitting no body (Friday, 1 February)
- Re: Issue 133, and permitting no body (Friday, 1 February)
- Re: Rules for intermediaries handling of PIs, whitespace, etc. (Friday, 1 February)
Martin Gudgin
- Re: Draft resolution text for Issue 181 ( Revised ) (Tuesday, 26 February)
- Re: XML Schema list simple type (Sunday, 24 February)
- Draft resolution text for Issue 181 (Saturday, 23 February)
- Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. (Tuesday, 19 February)
- Re: Proposal for issue 78: RPC structs and Encoding root attribute (Tuesday, 19 February)
- Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. (Tuesday, 19 February)
- SOAP Encoding: Default values (Friday, 15 February)
- SOAP Encoding and Schema (Thursday, 14 February)
- Re: RPC/Encoding dependency (Tuesday, 12 February)
- Re: RPC Mapping (Saturday, 9 February)
- Re: RPC Mapping (Friday, 8 February)
- Re: RPC Mapping (Friday, 8 February)
- RPC/Encoding dependency (Friday, 8 February)
- RPC Mapping (Friday, 8 February)
- ETF: NOTATION in soap-encoding schema (Friday, 8 February)
- Re: NOTATION attribute invalid in soap-encoding (Tuesday, 5 February)
- Re: NOTATION attribute invalid in soap-encoding (Tuesday, 5 February)
Marwan Sabbouh
Matt Long
Max Johnson
Mike Dierken
Mountain, Highland M
Noah Mendelsohn
noah_mendelsohn@us.ibm.com
- xsi:type for multiref targets. (Thursday, 28 February)
- Re: using xsi:type with the SOAP encoding rules (Friday, 1 March)
- Re: Issue 154: Role invariance - proposed resolution (Wednesday, 27 February)
- Re: Draft resolution for issue 59 (Sunday, 24 February)
- RE: Issue 182: Fault Code restriction: "At Most One Fault Proposa l" (Saturday, 23 February)
- RE: Soap Message Canonicalization (SM-C14N) (Friday, 22 February)
- RE: Issue 182: Fault Code restriction: "At Most One Fault Proposal" (Thursday, 21 February)
- Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. (Thursday, 21 February)
- RE: Soap Message Canonicalization (SM-C14N) (Thursday, 21 February)
- RE: Soap Message Canonicalization (SM-C14N) (Wednesday, 20 February)
- RE: Soap Message Canonicalization (SM-C14N) (Wednesday, 20 February)
- RE: Soap Message Canonicalization (SM-C14N) (Wednesday, 20 February)
- Re: ETF and editors: Issue 17 and 48: Proposal for describing when to use SOAP encoding (Wednesday, 20 February)
- RE: XMLP/XMLE Use cases and processing models (Wednesday, 20 February)
- Re: Soap Message Canonicalization (SM-C14N) (Tuesday, 19 February)
- RE: XMLP/XMLE Use cases and processing models (Tuesday, 19 February)
- Re: Soap Message Canonicalization (SM-C14N) (Tuesday, 19 February)
- Re: SOAP Encoding: Default values (Tuesday, 19 February)
- RE: XMLP/XMLE Use cases and processing models (Tuesday, 19 February)
- RE: Issue with soap-rpc:result (Thursday, 14 February)
- RE: Issue with soap-rpc:result (Thursday, 14 February)
- Re: Resolving the ednote in part 1 section 5.1 (Thursday, 14 February)
- Re: TBTF: Proposed resolution issue 179 (Wednesday, 13 February)
- Re: TBTF: Proposed resolution issue 179 (Tuesday, 12 February)
- RE: Issue with soap-rpc:result (Tuesday, 12 February)
- Re: Proposal for resolution of issue 176 (Monday, 11 February)
- Re: Proposal for resolution of issue 176 (Monday, 11 February)
- Re: TBTF: Proposed resolution issue 179 (Monday, 11 February)
- Re: Proposal for resolution of issue 176 (Monday, 11 February)
- Re: New issue: Default values of SOAP header block attributes (Monday, 11 February)
- Re: TBTF: revised proposed resolution for i178 (Monday, 11 February)
- Re: RPC Mapping (Saturday, 9 February)
- Re: Issue with encodingStyle (Saturday, 9 February)
- Re: XMLP/XMLE Use cases and processing models (Saturday, 9 February)
- RE: Issue with soap-rpc:result (Friday, 8 February)
- Re: SOAP & REST (Thursday, 7 February)
- RE: Issue with soap-rpc:result (Thursday, 7 February)
- RE: Issue 133, and permitting no body (Thursday, 7 February)
- RE: Issue with encodingStyle (Thursday, 7 February)
- RE: Issue with encodingStyle (Wednesday, 6 February)
- Re: Issue with soap-rpc:result (Wednesday, 6 February)
- RE: Proposed rewrite of Part 1, section 2 (long) (Wednesday, 6 February)
- Re: Issue 133: SOAP and The Web Architecture (Wednesday, 6 February)
- Re: Issue 133, and permitting no body (Wednesday, 6 February)
- Re: Reflective systems (Tuesday, 5 February)
- Re: Issue 133, and permitting no body (Tuesday, 5 February)
- RE: TBTF: SOAP MEP vs TMEP (Friday, 1 February)
- RE: One-way messaging in SOAP 1.2 (Friday, 1 February)
- Re: Issue 133, and permitting no body (Friday, 1 February)
- Re: Issue 133, and permitting no body (Friday, 1 February)
- Re: Who Faulted (was RE: Proposed rewrite of Part 1, section 2 (l ong) ) (Friday, 1 February)
Paul Cotton
Paul Prescod
Rich Salz
- Re: xsi:type for multiref targets. (Friday, 1 March)
- Re: xsi:type for multiref targets. (Friday, 1 March)
- Re: Soap Message Canonicalization (SM-C14N) (Wednesday, 20 February)
- Re: Soap Message Canonicalization (SM-C14N) (Wednesday, 20 February)
- Re: Soap Message Canonicalization (SM-C14N) (Tuesday, 19 February)
- Re: Soap Message Canonicalization (SM-C14N) (Monday, 18 February)
- Re: Soap Message Canonicalization (SM-C14N) (Monday, 18 February)
- Re: Soap Message Canonicalization (SM-C14N) (Saturday, 16 February)
- Re: Soap Message Canonicalization (SM-C14N) (Saturday, 16 February)
- Re: Soap Message Canonicalization (SM-C14N) (Friday, 15 February)
- Re: Soap Message Canonicalization (SM-C14N) (Friday, 15 February)
- Re: Soap Message Canonicalization (SM-C14N) (Friday, 15 February)
- Soap Message Canonicalization (SM-C14N) (Friday, 15 February)
- Re: Issue with soap-rpc:result (Tuesday, 12 February)
- Re: Proposal for resolution of issue 176 (Tuesday, 12 February)
- Re: Proposal for resolution of issue 176 (Tuesday, 12 February)
- Re: Proposal for resolution of issue 176 (Monday, 11 February)
- Re: Issue with soap-rpc:result (Monday, 11 February)
- Re: Reflective systems (Saturday, 9 February)
- Re: Reflective systems (Wednesday, 6 February)
- Re: Issue 133, and permitting no body (Monday, 4 February)
S. Alexander Jacobson
Scott Cantor
Simon Fell
Takeshi Imamura
Tim Ewald
- RE: Issue with soap-rpc:result (Saturday, 23 February)
- using xsi:type with the SOAP encoding rules (Saturday, 23 February)
- RE: Issue with soap-rpc:result (Wednesday, 20 February)
- RE: Issue with soap-rpc:result (Wednesday, 20 February)
- RE: Issue with soap-rpc:result (Thursday, 14 February)
- RE: Issue with soap-rpc:result (Thursday, 14 February)
- RE: Issue with soap-rpc:result (Wednesday, 13 February)
- RE: Issue with soap-rpc:result (Wednesday, 13 February)
- RE: Issue with soap-rpc:result (Saturday, 9 February)
- RE: Issue with soap-rpc:result (Friday, 8 February)
- Sorry for the duplicate posts (Thursday, 7 February)
- RE: Issue with soap-rpc:result (Thursday, 7 February)
- RE: Issue with encodingStyle (Thursday, 7 February)
- RE: Issue with soap-rpc:result (Thursday, 7 February)
- Issue with soap-rpc:result (Thursday, 7 February)
- Issue with soap-rpc:result (Thursday, 7 February)
- Issue with encodingStyle (Thursday, 7 February)
- RE: Issue with soap-rpc:result (Thursday, 7 February)
- RE: Issue with soap-rpc:result (Thursday, 7 February)
- RE: Issue with soap-rpc:result (Wednesday, 6 February)
- Issue with encodingStyle (Wednesday, 6 February)
- Issue with soap-rpc:result (Wednesday, 6 February)
Vinoski, Stephen
Williams, Stuart
- RE: Issue 182: Fault Code restriction: "At Most One Fault Proposa l" (Sunday, 24 February)
- Issue 67: convey error information (Friday, 22 February)
- RE: Issue 182: Fault Code restriction: "At Most One Fault Proposa l" (Friday, 22 February)
- RE: Issue 133: multple methods per URI (Friday, 22 February)
- RE: Issue 182: Fault Code restriction: "At Most One Fault Proposa l" (Friday, 22 February)
- RE: Issue 182: Fault Code restriction: "At Most One Fault Proposa l" (Friday, 22 February)
- RE: Issue 182: Fault Code restriction: "At Most One Fault Proposa l" (Friday, 22 February)
- RE: Issue 182: Fault Code restriction: "At Most One Fault Proposa l" (Thursday, 21 February)
- Issue 182: Fault Code restriction: "At Most One Fault Proposal" (Thursday, 21 February)
- RE: Issue 133: SOAP and Web Architecture: Draft sentences for HTT P bi nding preamble. (Wednesday, 20 February)
- RE: Issue 133: SOAP and Web Architecture: Draft sentences for HTT P binding preamble. (Wednesday, 20 February)
- RE: Issue 133: SOAP and Web Architecture: Draft sentences for HTT P bi nding preamble. (Wednesday, 20 February)
- RE: Issue 133: SOAP and Web Architecture: Draft sentences for HTT P bi nding preamble. (Wednesday, 20 February)
- Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. (Monday, 18 February)
- RE: SOAP & REST (Thursday, 7 February)
- RE: Issue 133, and permitting no body (Thursday, 7 February)
- RE: SOAP & REST (Thursday, 7 February)
- RE: Issue 133, and permitting no body (Wednesday, 6 February)
- RE: Issue 133, and permitting no body (Tuesday, 5 February)
- RE: Issue 133, and permitting no body (Monday, 4 February)
- RE: Issue 133, and permitting no body (Monday, 4 February)
- RE: Issue 133, and permitting no body (Monday, 4 February)
- Issue 102: Clarify Rules for Delivering Fault Messages (Saturday, 2 February)
- RE: TBTF: SOAP MEP vs TMEP (Saturday, 2 February)
- RE: Who Faulted (was RE: Proposed rewrite of Part 1, section 2 (l ong) ) (Friday, 1 February)
- RE: One-way messaging in SOAP 1.2 (Friday, 1 February)
- RE: Who Faulted (was RE: Proposed rewrite of Part 1, section 2 (l ong) ) (Friday, 1 February)
Yves Lafon
- minutes of 13 feb 2002 (Wednesday, 20 February)
- minutes (Wednesday, 13 February)
- Re: SOAP & REST (Thursday, 7 February)
- Email binding (Thursday, 7 February)
- Re: Issue 133, and permitting no body (Wednesday, 6 February)
- Re: SOAP & REST (Wednesday, 6 February)
- minutes of 23/01/2002 teleconference (Tuesday, 5 February)
- Re: Issue 133, and permitting no body (Friday, 1 February)
- Re: Issue 133, and permitting no body (Friday, 1 February)
- Re: Issue 133, and permitting no body (Friday, 1 February)
Last message date: Thursday, 28 February 2002 21:58:15 UTC