xml-dist-app@w3.org from February 2002 by date

Friday, 1 March 2002

• RE: xsi:type for multiref targets. Scott Cantor
• Re: xsi:type for multiref targets. Rich Salz
• RE: xsi:type for multiref targets. Scott Cantor
• Re: xsi:type for multiref targets. Rich Salz

Thursday, 28 February 2002

• xsi:type for multiref targets. noah_mendelsohn@us.ibm.com

Friday, 1 March 2002

• Re: using xsi:type with the SOAP encoding rules noah_mendelsohn@us.ibm.com

Thursday, 28 February 2002

• RE: Proposal for issue 78: RPC structs and Encoding root attribute Don Box
• Revised Issue 137 Proposed Resolution Marc Hadley

Wednesday, 27 February 2002

• Re: Issue 154: Role invariance - proposed resolution noah_mendelsohn@us.ibm.com

Tuesday, 26 February 2002

• Re: Draft resolution text for Issue 181 ( Revised ) Martin Gudgin

Monday, 25 February 2002

• RE: XMLP/XMLE Use cases and processing models Eastlake III Donald-LDE008
• Draft Resolution for issue 57 Mountain, Highland M
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. Mark Baker

Sunday, 24 February 2002

• RE: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP binding preamble. Larry Masinter
• Re: Draft resolution for issue 59 noah_mendelsohn@us.ibm.com
• RE: Issue 182: Fault Code restriction: "At Most One Fault Proposa l" Williams, Stuart
• Re: XML Schema list simple type Martin Gudgin
• RE: Issue with encodingStyle Don Box
• RE: Reflective systems Don Box

Saturday, 23 February 2002

• RE: Issue 182: Fault Code restriction: "At Most One Fault Proposa l" Henrik Frystyk Nielsen
• RE: Issue 182: Fault Code restriction: "At Most One Fault Proposa l" noah_mendelsohn@us.ibm.com
• RE: Soap Message Canonicalization (SM-C14N) Henrik Frystyk Nielsen
• RE: Issue 182: Fault Code restriction: "At Most One Fault Proposal" Henrik Frystyk Nielsen
• RE: Issue 182: Fault Code restriction: "At Most One Fault Proposal" Henrik Frystyk Nielsen
• Draft resolution text for Issue 181 Martin Gudgin
• using xsi:type with the SOAP encoding rules Tim Ewald
• RE: Issue with soap-rpc:result Tim Ewald
• SOAP & WSDL tutorial Handoko
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. Paul Prescod
• RE: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. Andrew Layman
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. Paul Prescod
• RE: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. Andrew Layman

Friday, 22 February 2002

• RE: Soap Message Canonicalization (SM-C14N) noah_mendelsohn@us.ibm.com
• ANN: Microsoft contribution to SOAP 1.2 test collection Kirill Gavrylyuk
• CFP: Middleware for Web Services Vinoski, Stephen
• Re: Issue 133: multple methods per URI Mark Nottingham
• RE: XMLP/XMLE Use cases and processing models Eugene Kuznetsov
• Issue 51: Support different message patterns John Ibbotson
• Issue 154: Role invariance - proposed resolution Marc Hadley
• Draft resolution for issue 59 Jacek Kopecky
• RE: Issue with soap-rpc:result Jacek Kopecky
• Issue 67: convey error information Williams, Stuart
• RE: Issue 182: Fault Code restriction: "At Most One Fault Proposa l" Williams, Stuart
• RE: Issue 133: multple methods per URI Williams, Stuart
• RE: Issue 182: Fault Code restriction: "At Most One Fault Proposa l" Williams, Stuart
• RE: Issue 182: Fault Code restriction: "At Most One Fault Proposa l" Williams, Stuart
• RE: Issue 182: Fault Code restriction: "At Most One Fault Proposa l" Williams, Stuart

Thursday, 21 February 2002

• RE: Issue 182: Fault Code restriction: "At Most One Fault Proposal" Henrik Frystyk Nielsen
• Issue 133: multple methods per URI Mark Nottingham
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. Mark Nottingham
• Re: Issue 182: Fault Code restriction: "At Most One Fault Proposal" Christopher Ferris
• RE: Issue 182: Fault Code restriction: "At Most One Fault Proposal" Henrik Frystyk Nielsen
• RE: Soap Message Canonicalization (SM-C14N) Henrik Frystyk Nielsen
• RE: Issue 182: Fault Code restriction: "At Most One Fault Proposal" noah_mendelsohn@us.ibm.com
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. noah_mendelsohn@us.ibm.com
• RE: Issue 182: Fault Code restriction: "At Most One Fault Proposa l" Williams, Stuart
• ETF: Proposed Resolution for Issue 184 Asir S Vedamuthu
• RE: Soap Message Canonicalization (SM-C14N) noah_mendelsohn@us.ibm.com
• RE: Issue 182: Fault Code restriction: "At Most One Fault Proposal" Henrik Frystyk Nielsen
• RE: Soap Message Canonicalization (SM-C14N) Henrik Frystyk Nielsen
• Re: XMLP/XMLE Use cases and processing models Christopher Ferris
• help !!! Ibhar Software
• Re: Issue 182: Fault Code restriction: "At Most One Fault Proposal" Jean-Jacques Moreau
• Re: Issue 182: Fault Code restriction: "At Most One Fault Proposal" Christopher Ferris
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. S. Alexander Jacobson
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTT P binding preamble. Jean-Jacques Moreau
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. Paul Prescod
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTT P binding preamble. Paul Prescod
• Re: Soap Message Canonicalization (SM-C14N) Fred Carter
• Issue 182: Fault Code restriction: "At Most One Fault Proposal" Williams, Stuart

Wednesday, 20 February 2002

• Re: SOAP Encoding multistructs Jacek Kopecky
• RE: Soap Message Canonicalization (SM-C14N) noah_mendelsohn@us.ibm.com
• RE: Soap Message Canonicalization (SM-C14N) Henrik Frystyk Nielsen
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTT P bi nding preamble. Mark Nottingham
• RE: Issue 133: SOAP and Web Architecture: Draft sentences for HTT P bi nding preamble. Williams, Stuart
• RE: Soap Message Canonicalization (SM-C14N) noah_mendelsohn@us.ibm.com
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTT P bi nding preamble. Mark Nottingham
• RE: Issue 133: SOAP and Web Architecture: Draft sentences for HTT P binding preamble. Williams, Stuart
• RE: Soap Message Canonicalization (SM-C14N) Henrik Frystyk Nielsen
• Re: Soap Message Canonicalization (SM-C14N) Mark Nottingham
• minutes of 13 feb 2002 Yves Lafon
• RE: Soap Message Canonicalization (SM-C14N) noah_mendelsohn@us.ibm.com
• Re: Soap Message Canonicalization (SM-C14N) Rich Salz
• RE: Soap Message Canonicalization (SM-C14N) Henrik Frystyk Nielsen
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTT P bi nding preamble. Mark Nottingham
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTT P bi nding preamble. Paul Prescod
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. Jean-Jacques Moreau
• Re: SOAP Encoding multistructs Asir S Vedamuthu
• Re: ETF and editors: Issue 17 and 48: Proposal for describing when to use SOAP encoding noah_mendelsohn@us.ibm.com
• RE: Issue with soap-rpc:result Tim Ewald
• RE: Issue with soap-rpc:result Tim Ewald
• RE: Issue 133: SOAP and Web Architecture: Draft sentences for HTT P bi nding preamble. Williams, Stuart
• SOAP Encoding multistructs Jacek Kopecky
• ETF: Telecon Minutes, Tuesday Feb 19th 2002 Asir S Vedamuthu
• RE: XMLP/XMLE Use cases and processing models noah_mendelsohn@us.ibm.com
• ETF's proposal for issue 78: RPC structs and Encoding root attribute Jacek Kopecky
• RE: Issue 133: SOAP and Web Architecture: Draft sentences for HTT P bi nding preamble. Williams, Stuart
• RE: XMLP/XMLE Use cases and processing models David Orchard
• RE: XMLP/XMLE Use cases and processing models David Orchard
• Re: Soap Message Canonicalization (SM-C14N) Rich Salz

Tuesday, 19 February 2002

• Proposal for resolving issue 180 Henrik Frystyk Nielsen
• Re: Soap Message Canonicalization (SM-C14N) noah_mendelsohn@us.ibm.com
• RE: XMLP/XMLE Use cases and processing models noah_mendelsohn@us.ibm.com
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. Mark Nottingham
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. Mark Nottingham
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. Paul Prescod
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. Martin Gudgin
• Re: XMLP/XMLE Use cases and processing models Joseph Reagle
• Re: Soap Message Canonicalization (SM-C14N) Rich Salz
• Re: ETF and editors: Issue 17 and 48: Proposal for describing when to use SOAP encoding Marc Hadley
• Re: Proposal for issue 78: RPC structs and Encoding root attribute Marc Hadley
• Re: ETF and editors: Issue 17 and 48: Proposal for describing when to use SOAP encoding Jacek Kopecky
• ETF and editors: Issue 17 and 48: Proposal for describing when to use SOAP encoding Henrik Frystyk Nielsen
• Re: Proposal for issue 78: RPC structs and Encoding root attribute Jacek Kopecky
• Re: Proposal for issue 78: RPC structs and Encoding root attribute Asir S Vedamuthu
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. Paul Prescod
• Re: Proposal for issue 78: RPC structs and Encoding root attribute Martin Gudgin
• Re: Proposal for issue 78: RPC structs and Encoding root attribute Jacek Kopecky
• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. Martin Gudgin
• Re: Proposal for issue 78: RPC structs and Encoding root attribute Marc Hadley
• Re: Soap Message Canonicalization (SM-C14N) Marc Hadley

Monday, 18 February 2002

• Re: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. Paul Prescod

Tuesday, 19 February 2002

• Issue #44 : proposed closing text Glen Daniels
• RE: XMLP/XMLE Use cases and processing models David Orchard
• Re: Soap Message Canonicalization (SM-C14N) noah_mendelsohn@us.ibm.com
• Re: SOAP Encoding: Default values noah_mendelsohn@us.ibm.com
• RE: XMLP/XMLE Use cases and processing models noah_mendelsohn@us.ibm.com

Monday, 18 February 2002

• RE: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. Henrik Frystyk Nielsen
• RE: SOAP Encoding: Default values Henrik Frystyk Nielsen
• Proposal for issue 78: RPC structs and Encoding root attribute Jacek Kopecky
• Re: Soap Message Canonicalization (SM-C14N) Christopher Ferris
• Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble. Williams, Stuart
• Re: Soap Message Canonicalization (SM-C14N) Rich Salz
• Re: RPC/Encoding dependency Jacek Kopecky
• Re: Soap Message Canonicalization (SM-C14N) Rich Salz
• Re: RPC/Encoding dependency Jacek Kopecky
• Re: SOAP Encoding: Default values Marc Hadley
• CFP: O'Reilly Open Source Convention XML (II). dirkx@covalent.net

Sunday, 17 February 2002

• RE: Soap Message Canonicalization (SM-C14N) Andrew Layman
• RE: SOAP Encoding and Schema Andrew Layman
• RE: Issue with soap-rpc:result Andrew Layman
• RE: Soap Message Canonicalization (SM-C14N) Andrew Layman
• RE: SOAP Encoding: Default values Andrew Layman
• Re: Soap Message Canonicalization (SM-C14N) Mark Nottingham

Saturday, 16 February 2002

• Re: Soap Message Canonicalization (SM-C14N) Rich Salz
• Re: Soap Message Canonicalization (SM-C14N) Rich Salz
• Re: Soap Message Canonicalization (SM-C14N) Mark Nottingham
• Re: Soap Message Canonicalization (SM-C14N) Mark Nottingham
• RE: XMLP/XMLE Use cases and processing models David Orchard
• RE: New Issue: Fault Code Restrictions Henrik Frystyk Nielsen
• RE: XMLP/XMLE Use cases and processing models Noah Mendelsohn

Friday, 15 February 2002

• RE: Issue with soap-rpc:result Noah Mendelsohn
• Re: Soap Message Canonicalization (SM-C14N) Noah Mendelsohn

Saturday, 16 February 2002

• Proposed resolution for issue 103 Henrik Frystyk Nielsen
• Proposed Resolution for Issues 50 and 57 Mountain, Highland M

Friday, 15 February 2002

• Re: Soap Message Canonicalization (SM-C14N) Rich Salz
• Re: Soap Message Canonicalization (SM-C14N) Christopher Ferris
• Issue 33 : Proposed resolution Glen Daniels
• SOAP Encoding: Default values Martin Gudgin

Thursday, 14 February 2002

• SOAP Encoding and Schema Martin Gudgin

Tuesday, 12 February 2002

• Re: RPC/Encoding dependency Martin Gudgin

Friday, 15 February 2002

• Re: Soap Message Canonicalization (SM-C14N) Rich Salz
• RE: Soap Message Canonicalization (SM-C14N) Henrik Frystyk Nielsen
• Re: Soap Message Canonicalization (SM-C14N) Rich Salz
• Soap Message Canonicalization (SM-C14N) Rich Salz
• oops! Re: Resolving the ednote in part 1 section 5.1 Christopher Ferris
• Re: Resolving the ednote in part 1 section 5.1 Christopher Ferris
• RE: Issue with soap-rpc:result Jacek Kopecky
• RE: Issue with soap-rpc:result Jacek Kopecky
• RE: Issue with soap-rpc:result Jacek Kopecky
• RE: Issue with soap-rpc:result Jacek Kopecky
• RE: Issue with soap-rpc:result Jacek Kopecky

Thursday, 14 February 2002

• RE: Resolving the ednote in part 1 section 5.1 Henrik Frystyk Nielsen
• Re: FYI: BCP 56, RFC 3205 on HTTP Layering S. Alexander Jacobson
• RE: Issue with soap-rpc:result Tim Ewald
• RE: Issue with soap-rpc:result Tim Ewald
• RE: Issue with soap-rpc:result noah_mendelsohn@us.ibm.com
• RE: Issue with soap-rpc:result noah_mendelsohn@us.ibm.com
• Re: Resolving the ednote in part 1 section 5.1 noah_mendelsohn@us.ibm.com
• RE: Issue with soap-rpc:result Jacek Kopecky
• Re: FYI: BCP 56, RFC 3205 on HTTP Layering Mark Nottingham
• FYI: BCP 56, RFC 3205 on HTTP Layering Larry Masinter

Wednesday, 13 February 2002

• RE: XMLP/XMLE Use cases and processing models David Orchard
• RE: XMLP/XMLE Use cases and processing models David Orchard
• RE: Issue with soap-rpc:result Tim Ewald
• RE: Issue with soap-rpc:result Tim Ewald
• Resolving the ednote in part 1 section 5.1 Henrik Frystyk Nielsen
• Re: TBTF: Proposed resolution issue 179 noah_mendelsohn@us.ibm.com
• Re: Possibly defaulted (was RE: Minutes for Thurs 7th Feb 2002 Telcon) Simon Fell
• minutes Yves Lafon
• Re: Possibly defaulted (was RE: Minutes for Thurs 7th Feb 2002 Telcon) Jacek Kopecky
• Re: TBTF: Proposed resolution issue 179 Marc Hadley
• RE: Issue with soap-rpc:result Jacek Kopecky

Tuesday, 12 February 2002

• Re: TBTF: Proposed resolution issue 179 Christopher Ferris
• RE: TBTF: Proposed resolution issue 179 Henrik Frystyk Nielsen
• Re: TBTF: Proposed resolution issue 179 noah_mendelsohn@us.ibm.com
• Proposed issue: Separately named specifications Paul Prescod
• RE: New issue: Default values of SOAP header block attributes Henrik Frystyk Nielsen
• Re: Issue with soap-rpc:result Rich Salz
• Issues 16 and 113: Proposed resolution Henrik Frystyk Nielsen
• Re: Issue with soap-rpc:result Jacek Kopecky
• ETF: Telcon Minutes Tues 12th Feb 2002 Marc Hadley
• RE: Issue with soap-rpc:result noah_mendelsohn@us.ibm.com
• Re: XMLP/XMLE Use cases and processing models Takeshi Imamura
• [Issue] XML Legacy Types in SOAP Encoding Schema Asir S Vedamuthu
• Re: Possibly defaulted (was RE: Minutes for Thurs 7th Feb 2002 Telcon) Simon Fell
• [Issue] Status of SOAP 1.2 Encoding Schema Asir S Vedamuthu
• ETF: Proposed Resolution for Issue #163 Asir S Vedamuthu
• ETF: Proposed Resolution for Issue #167 Asir S Vedamuthu
• Re: Proposal for resolution of issue 176 Jean-Jacques Moreau
• New Issue: Fault Code Restrictions Marc Hadley
• Re: Updated Proposal for Rewrite of Part 1 Section 2 Marc Hadley
• Re: Proposal for resolution of issue 176 Marc Hadley
• Re: Proposal for resolution of issue 176 Jean-Jacques Moreau
• Re: Updated Proposal for Rewrite of Part 1 Section 2 Jacek Kopecky
• Re: New issue: Default values of SOAP header block attributes Jean-Jacques Moreau
• Re: TBTF: Proposed resolution issue 179 Marc Hadley
• Re: Possibly defaulted (was RE: Minutes for Thurs 7th Feb 2002 Telcon) Jacek Kopecky
• Re: RPC/Encoding dependency Jacek Kopecky
• Re: RPC Mapping Jacek Kopecky
• RE: Issue with soap-rpc:result Jacek Kopecky
• RE: Issue with soap-rpc:result Jacek Kopecky
• RE: Proposal for resolution of issue 176 Henrik Frystyk Nielsen
• Re: Proposal for resolution of issue 176 Rich Salz
• Re: Proposal for resolution of issue 176 Rich Salz
• Re: Proposal for resolution of issue 176 Christopher Ferris
• RE: Proposal for resolution of issue 176 Henrik Frystyk Nielsen
• Issue 55: Proposed resolution Henrik Frystyk Nielsen
• Re: Proposal for resolution of issue 176 Christopher Ferris

Monday, 11 February 2002

• Re: Proposal for resolution of issue 176 noah_mendelsohn@us.ibm.com
• RE: Proposal for resolution of issue 176 Henrik Frystyk Nielsen
• Re: Proposal for resolution of issue 176 Christopher Ferris
• Re: Proposal for resolution of issue 176 noah_mendelsohn@us.ibm.com
• Re: Proposal for resolution of issue 176 Christopher Ferris
• Re: Proposal for resolution of issue 176 Rich Salz
• Re: Proposal for resolution of issue 176 Christopher Ferris
• Re: TBTF: Proposed resolution issue 179 noah_mendelsohn@us.ibm.com
• Re: Proposal for resolution of issue 176 noah_mendelsohn@us.ibm.com
• Re: Issue with soap-rpc:result Rich Salz
• RE: Email binding Mountain, Highland M
• RE: SOAP & REST Mike Dierken
• Re: Updated Proposal for Rewrite of Part 1 Section 2 Marc Hadley
• RE: Issue 133, and permitting no body Mike Dierken
• TBTF: Proposed resolution issue 179 Marc Hadley
• Re: New issue: Default values of SOAP header block attributes noah_mendelsohn@us.ibm.com
• Re: Possibly defaulted (was RE: Minutes for Thurs 7th Feb 2002 Telcon) Marc Hadley
• Updated Proposal for Rewrite of Part 1 Section 2 Marc Hadley
• Proposal for resolution of issue 176 Henrik Frystyk Nielsen
• Re: TBTF: revised proposed resolution for i178 noah_mendelsohn@us.ibm.com

Sunday, 10 February 2002

• New issue: Default values of SOAP header block attributes Henrik Frystyk Nielsen

Saturday, 9 February 2002

• Re: Reflective systems Rich Salz
• Re: RPC Mapping Martin Gudgin
• Îáó÷åíèå âàëþòíûì ñïåêóëÿöèÿì CSC@w3.org
• Re: XMLP/XMLE Use cases and processing models noah_mendelsohn@us.ibm.com
• Re: RPC Mapping noah_mendelsohn@us.ibm.com
• Re: Issue with encodingStyle noah_mendelsohn@us.ibm.com
• Re: [soapbuilders] Updated interop round 2 client results Simon Fell
• RE: Issue with soap-rpc:result Tim Ewald

Friday, 8 February 2002

• RE: Issue with soap-rpc:result noah_mendelsohn@us.ibm.com
• RE: Issue with soap-rpc:result Tim Ewald
• Possibly defaulted (was RE: Minutes for Thurs 7th Feb 2002 Telcon) Andrew Layman
• RE: Issue with soap-rpc:result Andrew Layman
• TBTF: revised proposed resolution for i178 Christopher Ferris
• Re: RPC Mapping Martin Gudgin
• RE: RPC Mapping Henrik Frystyk Nielsen
• Re: RPC Mapping Martin Gudgin
• RE: RPC Mapping Henrik Frystyk Nielsen
• RPC/Encoding dependency Martin Gudgin
• RE: Issue with soap-rpc:result Jacek Kopecky
• RPC Mapping Martin Gudgin
• RE: Issue with soap-rpc:result Jacek Kopecky
• Re: Email binding Jean-Jacques Moreau
• Re: Email binding Jean-Jacques Moreau
• ETF: NOTATION in soap-encoding schema Martin Gudgin
• ETF: Minutes for Thurs 7th Feb 2002 Telcon Marc Hadley

Thursday, 7 February 2002

• Sorry for the duplicate posts Tim Ewald
• RE: Issue with soap-rpc:result Andrew Layman
• RE: Issue with encodingStyle Andrew Layman
• Re: XMLP/XMLE Use cases and processing models Joseph Reagle
• RE: Issue with soap-rpc:result Tim Ewald
• RE: Issue with soap-rpc:result Tim Ewald
• RE: Issue with encodingStyle Tim Ewald
• Issue with encodingStyle Tim Ewald
• Issue with soap-rpc:result Tim Ewald
• Issue with soap-rpc:result Tim Ewald
• RE: Issue with soap-rpc:result Tim Ewald
• RE: SOAP & REST Williams, Stuart
• Re: SOAP & REST Mark Baker
• Re: SOAP & REST Yves Lafon
• RE: Issue with soap-rpc:result Tim Ewald
• Re: SOAP & REST Mark Baker
• Email binding Yves Lafon
• Re: SOAP & REST Noah Mendelsohn
• RE: Issue with soap-rpc:result Noah Mendelsohn
• RE: Issue with encodingStyle Jacek Kopecky
• RE: Issue with soap-rpc:result Jacek Kopecky
• RE: Issue with soap-rpc:result Jacek Kopecky
• RE: Issue 133, and permitting no body Williams, Stuart
• RE: SOAP & REST Williams, Stuart
• Re: SOAP & REST Mark Baker
• Re: Issue 133, and permitting no body Mark Baker
• Re: SOAP & REST Mark Nottingham
• RE: Issue with soap-rpc:result Don Box
• Re: SOAP & REST noah_mendelsohn@us.ibm.com
• RE: Issue with soap-rpc:result noah_mendelsohn@us.ibm.com
• RE: Issue 133, and permitting no body noah_mendelsohn@us.ibm.com
• RE: Issue with encodingStyle Andrew Layman
• RE: Issue with soap-rpc:result Don Box
• RE: Issue with soap-rpc:result Don Box
• RE: Issue with soap-rpc:result Don Box
• RE: Issue with encodingStyle noah_mendelsohn@us.ibm.com
• RE: Issue with encodingStyle Bob Cunnings

Wednesday, 6 February 2002

• RE: Issue with encodingStyle noah_mendelsohn@us.ibm.com
• Re: Issue with soap-rpc:result noah_mendelsohn@us.ibm.com
• Re: Proposed rewrite of Part 1, section 2 (long) Christopher Ferris
• RE: Issue 177: missing elements same as nils? Henrik Frystyk Nielsen
• RE: Proposed rewrite of Part 1, section 2 (long) noah_mendelsohn@us.ibm.com
• Re: Issue with soap-rpc:result Simon Fell
• Re: SOAP & REST Mark Baker
• RE: Issue 133, and permitting no body John J. Barton
• Re: Reflective systems John J. Barton
• RE: Issue with soap-rpc:result David E. Cleary
• Re: Issue with soap-rpc:result Simon Fell
• FYI - possibly typographical errors bill palmer
• RE: Issue with soap-rpc:result Tim Ewald
• RE: Issue with encodingStyle Matt Long
• Re: XMLP/XMLE Use cases and processing models Joseph Reagle
• Re: Issue with encodingStyle Bob Cunnings
• Re: Issue with soap-rpc:result Jacek Kopecky
• Issue with encodingStyle Tim Ewald
• Issue with soap-rpc:result Tim Ewald
• Re: Issue 133: SOAP and The Web Architecture noah_mendelsohn@us.ibm.com
• RE: Issue 133, and permitting no body Williams, Stuart
• Antwort: Issue 177: missing elements same as nils? mario.jeckle@daimlerchrysler.com
• Re: Issue 133, and permitting no body Yves Lafon
• Re: Issue 133, and permitting no body noah_mendelsohn@us.ibm.com
• Re: Issue 177: missing elements same as nils? Jacek Kopecky
• Re: SOAP & REST Yves Lafon
• Re: XMLP/XMLE Use cases and processing models Jean-Jacques Moreau
• Re: SOAP Encoding - Arrays Jacek Kopecky
• Re: NOTATION attribute invalid in soap-encoding Jean-Jacques Moreau
• Issue 177: missing elements same as nils? Henrik Frystyk Nielsen
• XMLP/XMLE Use cases and processing models David Orchard
• Re: Issue 133, and permitting no body Mark Baker
• Re: Reflective systems Mark Baker
• SOAP & REST Mark Baker
• Re: Issue 133, and permitting no body Mark Nottingham
• Re: Issue 133, and permitting no body John J. Barton
• Re: Reflective systems Rich Salz

Tuesday, 5 February 2002

• Re: Reflective systems noah_mendelsohn@us.ibm.com
• Re: Issue 133, and permitting no body noah_mendelsohn@us.ibm.com
• Re: Reflective systems S. Alexander Jacobson
• Re: Reflective systems Marwan Sabbouh
• Re: Reflective systems John J. Barton
• Re: NOTATION attribute invalid in soap-encoding Martin Gudgin
• Re: TBTF: security considerations proposed text Mark Baker
• Re: SOAP Encoding - Arrays Simon Fell
• Re: TBTF: security considerations proposed text Christopher Ferris
• Re: NOTATION attribute invalid in soap-encoding Jean-Jacques Moreau
• Re: NOTATION attribute invalid in soap-encoding Martin Gudgin
• RE: NOTATION attribute invalid in soap-encoding Max Johnson
• Re: Issue 133, and permitting no body Mark Baker
• Re: NOTATION attribute invalid in soap-encoding Jean-Jacques Moreau
• Re: TBTF: security considerations proposed text Jean-Jacques Moreau
• RE: Issue 133, and permitting no body Williams, Stuart
• minutes of 23/01/2002 teleconference Yves Lafon
• Re: Reflective systems Marwan Sabbouh
• array dimension zero? Jacek Kopecky
• Re: SOAP Encoding - Arrays Jacek Kopecky
• Re: Reflective systems Kurt Cagle
• TBTF: proposal for issue #57 Christopher Ferris
• TBTF: proposed resolution for i178 Christopher Ferris
• Re: SOAP Encoding - Arrays Simon Fell
• RE: NOTATION attribute invalid in soap-encoding Paul Cotton
• Re: Issue 133, and permitting no body Mark Nottingham
• Re: Issue 133, and permitting no body Mark Nottingham

Monday, 4 February 2002

• Reflective systems Mark Baker
• Re: Issue 133, and permitting no body Mark Baker
• Re: Issue 133, and permitting no body Rich Salz
• Re: Issue 133, and permitting no body Mark Baker
• RE: Issue 133, and permitting no body Champion, Mike
• Re: Issue 133, and permitting no body Mark Baker
• TBTF: security considerations proposed text Christopher Ferris
• RE: Issue 133, and permitting no body Williams, Stuart
• Re: Issue 133, and permitting no body Mark Baker
• RE: Issue 133, and permitting no body Williams, Stuart
• Re: Issue 133, and permitting no body Mark Nottingham
• XML name encoding examples Henrik Frystyk Nielsen
• Re: Issue 133, and permitting no body Mark Nottingham
• RE: DIME and SOAP in DIME specs submitted as IETF Internet Drafts Henrik Frystyk Nielsen
• Re: TBTF: SOAP MEP vs TMEP Christopher Ferris
• Re: DIME and SOAP in DIME specs submitted as IETF Internet Drafts Jean-Jacques Moreau
• RE: Issue 133, and permitting no body Williams, Stuart
• Re: TBTF: SOAP MEP vs TMEP Marc Hadley
• Re: Who Faulted (was RE: Proposed rewrite of Part 1, section 2 (l ong) ) Marc Hadley

Sunday, 3 February 2002

• Re: Issue 133, and permitting no body Mark Baker

Saturday, 2 February 2002

• Re: Issue 133, and permitting no body Mark Nottingham
• Re: Issue 133, and permitting no body Mark Baker
• Re: Issue 133, and permitting no body Mark Baker
• Re: Issue 133, and permitting no body Noah Mendelsohn
• DIME and SOAP in DIME specs submitted as IETF Internet Drafts Henrik Frystyk Nielsen
• Re: Issue 133, and permitting no body Mark Baker
• Issue 102: Clarify Rules for Delivering Fault Messages Williams, Stuart
• RE: TBTF: SOAP MEP vs TMEP Williams, Stuart

Friday, 1 February 2002

• RE: TBTF: SOAP MEP vs TMEP noah_mendelsohn@us.ibm.com
• RE: One-way messaging in SOAP 1.2 noah_mendelsohn@us.ibm.com
• Re: Issue 133: SOAP and The Web Architecture Hugo Haas
• Re: Issue 133, and permitting no body Yves Lafon
• Re: Issue 133, and permitting no body noah_mendelsohn@us.ibm.com
• Re: Issue 133, and permitting no body Mark Nottingham
• Re: Issue 133, and permitting no body Mark Baker
• Re: Issue 133, and permitting no body Mark Baker
• Re: Issue 133, and permitting no body Yves Lafon
• Re: Issue 133, and permitting no body Mark Nottingham
• Re: Issue 133, and permitting no body Mark Baker
• Re: Rules for intermediaries handling of PIs, whitespace, etc. Mark Nottingham
• RE: Who Faulted (was RE: Proposed rewrite of Part 1, section 2 (l ong) ) Williams, Stuart
• RE: One-way messaging in SOAP 1.2 Williams, Stuart
• Re: Issue 133, and permitting no body noah_mendelsohn@us.ibm.com
• Re: Who Faulted (was RE: Proposed rewrite of Part 1, section 2 (l ong) ) noah_mendelsohn@us.ibm.com
• RE: Who Faulted (was RE: Proposed rewrite of Part 1, section 2 (l ong) ) Williams, Stuart
• Re: Issue 133, and permitting no body Mark Baker
• Re: Issue 133, and permitting no body Mark Baker
• Re: Who Faulted (was RE: Proposed rewrite of Part 1, section 2 (l ong) ) Christopher Ferris
• Re: Issue 133, and permitting no body Yves Lafon
• Re: Who Faulted (was RE: Proposed rewrite of Part 1, section 2 (l ong) ) Jean-Jacques Moreau
• Re: SOAP Encoding - Arrays Jacek Kopecky
• Re: Who Faulted (was RE: Proposed rewrite of Part 1, section 2 (l ong) ) Jean-Jacques Moreau
• Re: Who Faulted (was RE: Proposed rewrite of Part 1, section 2 (l ong) ) Jean-Jacques Moreau
• RE: Issue 133, and permitting no body Henrik Frystyk Nielsen
• RE: Who Faulted (was RE: Proposed rewrite of Part 1, section 2 (l ong) ) Henrik Frystyk Nielsen

Last message date: Thursday, 28 February 2002 21:58:15 UTC