xml-dist-app@w3.org from May 2001 by author

Andrew Layman

• RE: FW: a question about mustunderstand. (Monday, 21 May)
• RE: XMLP/SOAP spec - processing instructions (Monday, 21 May)

Andy Neilson

• RE: SOAPAction Proposal (Thursday, 10 May)

Asir S Vedamuthu

• Re: Positions on issue 19 (Tuesday, 29 May)
• Re: Positions on issue 19 (Tuesday, 29 May)

Bob Cunnings

• RE: An analysis of mustUnderstand and related issues (Friday, 25 May)
• Re: Finding Faults in headers (Tuesday, 22 May)
• Re: Finding Faults in headers (Tuesday, 22 May)
• Re: XMLP/SOAP spec - processing instructions (Monday, 21 May)
• Re: An analysis of mustUnderstand and related issues (Saturday, 12 May)
• SOAPAction Proposal (Thursday, 3 May)

Chinh Le

• [Question] XML market data (Wednesday, 30 May)

christopher ferris

• Re: XMLP WG Issue 12 (Thursday, 31 May)
• Re: Clarifications list for SOAP specification (Wednesday, 30 May)
• Re: Issue 16: methods with void return type and no out params (Monday, 28 May)

Collier, Timothy R

• RE: HTTP Asynchronous Client Notifications (draft paper) (Friday, 18 May)
• RE: HTTP Asynchronous Client Notifications (draft paper) (Friday, 18 May)

Corda, Ugo

• RE: SOAPAction Proposal (Friday, 4 May)

Daniel Barclay

• Re: [i95, i22] - Proposal for clarifying use of SOAPAction (Monday, 7 May)
• Re: [i95, i22] - Proposal for clarifying use of SOAPAction (Thursday, 3 May)
• Re: SOAPAction Proposal (Thursday, 3 May)
• Re: Internationalization issue. (Thursday, 3 May)
• Re: mustUnderstand on client side (Thursday, 3 May)
• Re: [i95, i22] - Proposal for clarifying use of SOAPAction (Wednesday, 2 May)
• Re: [i95, i22] - Proposal for clarifying use of SOAPAction (Tuesday, 1 May)
• Re: [soapbuilders] question re: namespace hierarchies (Tuesday, 1 May)

Daniela Florescu

• RE: SOAPAction Proposal (Friday, 4 May)

Dave Winer

• Re: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)
• Re: SOAPAction Proposal (Thursday, 3 May)

David Clay

• module template draft 2 (Wednesday, 9 May)

David E. Cleary

• RE: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)

David Fallside

• test (Tuesday, 8 May)
• XMLP ed. drafts available for comment (Sunday, 6 May)

dehora

• RE: SOAPAction Proposal (Wednesday, 9 May)

Dick Brooks

• Gartner Group note on ebXML specs... (Friday, 25 May)
• FW: UN/CEFACT and OASIS Introduce ebXML-DEV Mail List (Tuesday, 22 May)
• FW: Statement from the CSG on the forward direction for UN/CEFACT's E-Business standards (Monday, 21 May)
• FYI - FW: ebXML APPROVED (Monday, 14 May)
• UN/CEFACT and OASIS Meeting Showcases ebXML for Healthcare and B2B (Sunday, 13 May)
• FYI - FW: ebXML Approved (Sunday, 13 May)
• RE: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)
• RE: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Tuesday, 8 May)
• RE: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)
• RE: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Monday, 7 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Monday, 7 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Monday, 7 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Thursday, 3 May)
• RE: SOAPAction Proposal (Thursday, 3 May)
• RE: Must understand mustUnderstand proposal (Thursday, 3 May)
• RE: SOAPAction Proposal (Thursday, 3 May)
• RE: mustUnderstand on client side (Wednesday, 2 May)
• RE: mustUnderstand on client side (Wednesday, 2 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Wednesday, 2 May)
• RE: mustUnderstand on client side (Tuesday, 1 May)

Doug Davis

• RE: An analysis of mustUnderstand and related issues (Thursday, 31 May)
• Spec Issue (Tuesday, 29 May)
• Re: FW: a question about mustunderstand. (Tuesday, 22 May)
• Re: On the ordering of header entries (Monday, 21 May)
• Re: On the ordering of header entries (Monday, 21 May)
• Processing model (Saturday, 19 May)
• Re: FW: a question about mustunderstand. (Saturday, 19 May)
• RE: An analysis of mustUnderstand and related issues (Thursday, 17 May)
• RE: An analysis of mustUnderstand and related issues (Wednesday, 16 May)
• Re: An analysis of mustUnderstand and related issues (Tuesday, 15 May)
• Re: An analysis of mustUnderstand and related issues (Tuesday, 15 May)
• Re: Proposal: Module for checking mustUnderstand headers have been processed (Friday, 11 May)
• Re: Proposal: Module for checking mustUnderstand headers have been processed (Thursday, 10 May)
• Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal) (Thursday, 10 May)
• Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal) (Wednesday, 9 May)
• RE: About the IETF list... (was: SOAP/XML Protocol and filtering, etc.) (Tuesday, 8 May)
• RE: SOAPAction Proposal (Tuesday, 8 May)
• Re: Reqs/AM - Comments/Questions (Tuesday, 8 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Tuesday, 8 May)
• RE: SOAPAction Proposal (Tuesday, 8 May)
• Regrets for 5/9 (Monday, 7 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Friday, 4 May)
• Re: Must understand mustUnderstand proposal (Friday, 4 May)
• Re: Must understand mustUnderstand proposal (Friday, 4 May)
• Re: RE: SOAPAction Proposal (Thursday, 3 May)
• Re: SOAPAction Proposal (Thursday, 3 May)
• Re: Must understand mustUnderstand proposal (Thursday, 3 May)
• RE: mustUnderstand on client side (Wednesday, 2 May)

Dr Colin Adam

• RE: Some issues with request/response binding to sync/async transport . (Friday, 18 May)

duglin

• Re: An analysis of mustUnderstand and related issues (Saturday, 26 May)
• Re: An analysis of mustUnderstand and related issues (Saturday, 26 May)
• FW: a question about mustunderstand. (Saturday, 26 May)

Eamon O'Tuathail

• BEEP vs. HTTP as transport for XMLP/SOAP (was xml transfer over TCP) (Thursday, 10 May)
• RE: HTTP Asynchronous Client Notifications (draft paper) (Tuesday, 8 May)
• RE: HTTP GET requests (was Re: SOAPAction Proposal) (Monday, 7 May)

Eric Jenkins

• XMLP WG Issue 12 (Thursday, 31 May)

Eugene Kuznetsov

• RE: HTTP Asynchronous Client Notifications (draft paper) (Friday, 18 May)
• RE: SOAPAction Proposal (Wednesday, 9 May)

Francis Norton

• Re: literal XML encoding? (Thursday, 24 May)
• Re: literal XML encoding? (Thursday, 24 May)
• literal XML encoding? (Wednesday, 23 May)

Frank DeRose

• RE: Issue 16: methods with void return type and no out params (Friday, 25 May)
• Issue 16: methods with void return type and no out params (Friday, 25 May)
• RE: HTTP Asynchronous Client Notifications (draft paper) (Saturday, 5 May)
• RE: mustUnderstand on the client side (Wednesday, 2 May)

Glen Daniels

• Proposal and issues surrounding MustUnderstand faults (Friday, 11 May)

Henrik Frystyk Nielsen

• RE: An analysis of mustUnderstand and related issues (Thursday, 31 May)
• RE: Positions on issue 19 (Tuesday, 29 May)
• RE: Positions on issue 19 (Tuesday, 29 May)
• Positions on issue 19 (Monday, 28 May)
• RE: Issue 16: methods with void return type and no out params (Sunday, 27 May)
• Three new Web Services specs: SOAP-RP, DIME, and XLANG (Thursday, 24 May)
• RE: An analysis of mustUnderstand and related issues (Wednesday, 23 May)
• RE: Finding Faults in headers (Tuesday, 22 May)
• RE: FW: a question about mustunderstand. (Tuesday, 22 May)
• On the ordering of header entries (Monday, 21 May)
• RE: Intent for siblings after the Body? (Monday, 21 May)
• RE: An analysis of mustUnderstand and related issues (Wednesday, 16 May)
• RE: An analysis of mustUnderstand and related issues (Wednesday, 16 May)
• RE: Proposal and issues surrounding MustUnderstand faults (Wednesday, 16 May)
• RE: An analysis of mustUnderstand and related issues (Wednesday, 16 May)
• RE: An analysis of mustUnderstand and related issues (Monday, 14 May)
• RE: Untargetted blocks (was Re: Must understand mustUnderstand proposal) (Wednesday, 9 May)
• RE: About the IETF list... (was: SOAP/XML Protocol and filtering, etc.) (Tuesday, 8 May)
• RE: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)
• RE: About the IETF list... (was: SOAP/XML Protocol and filtering, etc.) (Tuesday, 8 May)
• RE: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)
• RE: SOAPAction Proposal (Tuesday, 8 May)
• RE: SOAPAction Proposal (Tuesday, 8 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Tuesday, 8 May)
• RE: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Monday, 7 May)
• RE: SOAP/XML Protocol and filtering, etc. (Monday, 7 May)
• RE: SOAPAction thoughts from elsewhere (Monday, 7 May)
• RE: SOAPAction thoughts from elsewhere (Monday, 7 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Monday, 7 May)
• RE: SOAPAction Proposal (Monday, 7 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Monday, 7 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Monday, 7 May)
• RE: HTTP GET requests (was Re: SOAPAction Proposal) (Monday, 7 May)
• RE: SOAPAction Proposal (Monday, 7 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Monday, 7 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Friday, 4 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Friday, 4 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Friday, 4 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Thursday, 3 May)
• RE: SOAPAction Proposal (Thursday, 3 May)
• RE: RE: SOAPAction Proposal (Thursday, 3 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Thursday, 3 May)
• RE: SOAPAction Proposal (Thursday, 3 May)
• RE: Internationalization issue. (Wednesday, 2 May)
• RE: mustUnderstand on client side (Wednesday, 2 May)
• RE: mustUnderstand on client side (Wednesday, 2 May)
• RE: mustUnderstand on client side (Wednesday, 2 May)
• RE: mustUnderstand on client side (Wednesday, 2 May)
• RE: mustUnderstand on client side (Wednesday, 2 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Wednesday, 2 May)

Hugo Haas

• Re: XMLP WG Issue 12 (Thursday, 31 May)
• Re: Issue 16: methods with void return type and no out params (Friday, 25 May)
• Minutes of the 16 May teleconference (Wednesday, 23 May)
• Re: Processing model (Monday, 21 May)
• Re: Header order [was: An analysis of mustUnderstand and related issues] (Thursday, 17 May)
• Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal) (Thursday, 10 May)
• Untargetted blocks (was Re: Must understand mustUnderstand proposal) (Wednesday, 9 May)
• HTTP GET requests (was Re: SOAPAction Proposal) (Monday, 7 May)
• Re: Must understand mustUnderstand proposal (Thursday, 3 May)
• Re: [i95, i22] - Proposal for clarifying use of SOAPAction (Thursday, 3 May)

J.P. Martin-Flatin

• Re: HTTP Asynchronous Client Notifications (draft paper) (Wednesday, 9 May)

Jake Savin

• Re: [i95, i22] - Proposal for clarifying use of SOAPAction (Monday, 7 May)

Jean-Jacques Moreau

• Header order [was: An analysis of mustUnderstand and related issues] (Thursday, 17 May)
• Re: An analysis of mustUnderstand and related issues (Wednesday, 16 May)
• [Done Repost] Re: Must understand mustUnderstand proposal (Wednesday, 16 May)
• Re: [Repost] Re: Must understand mustUnderstand proposal (Wednesday, 16 May)
• [Repost] Re: Must understand mustUnderstand proposal (Wednesday, 16 May)
• [Repost] Re: Must understand mustUnderstand proposal (Wednesday, 16 May)
• [Repost] Re: Must understand mustUnderstand proposal (Wednesday, 16 May)
• [Repost] Re: Must understand mustUnderstand proposal (Wednesday, 16 May)
• [Repost] Re: Must understand mustUnderstand proposal (Wednesday, 16 May)
• Re: An analysis of mustUnderstand and related issues (Monday, 14 May)
• Re: module template draft 2 (Friday, 11 May)
• Re: Proposal: Module for checking mustUnderstand headers have been processed (Friday, 11 May)
• Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal) (Friday, 11 May)
• Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal) (Friday, 11 May)
• Re: xml transfer over TCP (Friday, 11 May)
• [Binary data] Application/Multiplexed content-type draft (Friday, 11 May)
• Re: Reqs/AM - Comments/Questions (Friday, 11 May)
• Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal) (Wednesday, 9 May)
• Re: xml transfer over TCP (Wednesday, 9 May)
• Re: Must understand mustUnderstand proposal (Wednesday, 9 May)
• Re: Must understand mustUnderstand proposal (Wednesday, 9 May)
• Re: Must understand mustUnderstand proposal (Thursday, 3 May)
• Re: Must understand mustUnderstand proposal (Thursday, 3 May)
• Re: Must understand mustUnderstand proposal (Thursday, 3 May)
• Re: Must understand mustUnderstand proposal (Thursday, 3 May)

Jeffrey Kay

• RE: About the IETF list... (was: SOAP/XML Protocol and filtering, etc.) (Tuesday, 8 May)
• RE: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)
• RE: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Tuesday, 8 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Tuesday, 8 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Monday, 7 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Monday, 7 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Monday, 7 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Monday, 7 May)

John J. Barton

• Re: literal XML encoding? (Thursday, 24 May)
• Re: xml transfer over TCP (Thursday, 10 May)
• Re: HTTPSOAP - was SOAPAction Proposal (Monday, 7 May)

Kasi, Jay

• RE: An analysis of mustUnderstand and related issues (Friday, 25 May)
• RE: Some issues with request/response binding to sync/async trans port . (Saturday, 19 May)
• FW: a question about mustunderstand. (Friday, 18 May)
• RE: Some issues with request/response binding to sync/async trans port . (Friday, 18 May)
• Some issues with request/response binding to sync/async transport . (Friday, 18 May)
• RE: HTTP Asynchronous Client Notifications (draft paper) (Friday, 18 May)
• RE: An analysis of mustUnderstand and related issues (Wednesday, 16 May)
• RE: Proposal and issues surrounding MustUnderstand faults (Friday, 11 May)
• Regrets. (Thursday, 10 May)
• RE: Some basic (naive?) questions about mustunderstand. (Thursday, 10 May)
• Some basic (naive?) questions about mustunderstand. (Thursday, 10 May)

Keith Ballinger

• RE: literal XML encoding? (Thursday, 24 May)
• RE: literal XML encoding? (Thursday, 24 May)

Keith Moore

• Re: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)
• Re: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)
• Re: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)
• Re: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)
• Re: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)
• Re: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)
• Re: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)
• Re: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)

Krishna Sankar

• RE: SOAPAction Proposal (Monday, 7 May)

Kurt Cagle

• HTTPSOAP - was SOAPAction Proposal (Saturday, 5 May)

Larry Masinter

• RE: About the IETF list... (was: SOAP/XML Protocol and filtering, etc.) (Tuesday, 8 May)

Linda Norton

• [xml-dist-app] <none> (Wednesday, 2 May)

Lloyd Wood

• RE: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)

Lucas Gonze

• RE: xml transfer over TCP (Thursday, 10 May)
• xml transfer over TCP (Wednesday, 9 May)
• xml transfer over TCP (Monday, 7 May)

Marc Hadley

• Proposed Clarification for Issues 4 and 23 (Thursday, 31 May)
• Re: Issue 16: methods with void return type and no out params (Tuesday, 29 May)
• Re: Processing model (Tuesday, 22 May)

Marc J. Hadley

• Re: literal XML encoding? (Thursday, 24 May)
• Re: Reqs/AM - Comments/Questions (Tuesday, 15 May)
• Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal) (Thursday, 10 May)
• Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal) (Thursday, 10 May)
• Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal) (Wednesday, 9 May)
• Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal) (Wednesday, 9 May)
• Re: [i95, i22] - Proposal for clarifying use of SOAPAction (Friday, 4 May)
• Re: Must understand mustUnderstand proposal (Thursday, 3 May)

mario.jeckle@daimlerchrysler.com

• Re: XMLP/SOAP spec - processing instructions (Tuesday, 22 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Friday, 4 May)

Mark A. Jones

• Re: Issue 16: methods with void return type and no out params (Friday, 25 May)

Mark Baker

• Re: SOAPAction Proposal (Thursday, 10 May)

Mark Jones

• Re: An analysis of mustUnderstand and related issues (Wednesday, 16 May)
• Re: An analysis of mustUnderstand and related issues (Tuesday, 15 May)
• Re: An analysis of mustUnderstand and related issues (Monday, 14 May)
• Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal) (Thursday, 10 May)
• Re: Must understand mustUnderstand proposal (Wednesday, 9 May)
• Re: Must understand mustUnderstand proposal (Thursday, 3 May)

Mark Nottingham

• Re: XMLP WG Issue 12 (Friday, 1 June)
• Re: Issue 16: methods with void return type and no out params (Monday, 28 May)
• Re: Positions on issue 19 (Monday, 28 May)
• Re: Issue 16: methods with void return type and no out params (Monday, 28 May)
• Re: On the ordering of header entries (Wednesday, 23 May)
• Re: An analysis of mustUnderstand and related issues (Saturday, 12 May)
• Re: Proposal and issues surrounding MustUnderstand faults (Saturday, 12 May)
• Re: BEEP vs. HTTP as transport for XMLP/SOAP (was xml transfer over TCP) (Thursday, 10 May)
• Re: SOAPAction Proposal (Thursday, 10 May)
• RE: About the IETF list... (was: SOAP/XML Protocol and filtering, etc.) (Tuesday, 8 May)
• About the IETF list... (was: SOAP/XML Protocol and filtering, etc.) (Tuesday, 8 May)
• Fwd: Re: SOAP/XML Protocol and filtering, etc. (Monday, 7 May)
• RE: SOAPAction thoughts from elsewhere (Monday, 7 May)
• SOAPAction thoughts from elsewhere (Monday, 7 May)
• Re: HTTPSOAP - was SOAPAction Proposal (Saturday, 5 May)
• Re: SOAPAction Proposal (Friday, 4 May)
• Re: SOAPAction Proposal (Friday, 4 May)
• Re: Must understand mustUnderstand proposal (Thursday, 3 May)
• Re: SOAPAction Proposal (Thursday, 3 May)
• Re: [i95, i22] - Proposal for clarifying use of SOAPAction (Thursday, 3 May)

Martin Gudgin

• Re: Positions on issue 19 (Wednesday, 30 May)
• Re: Positions on issue 19 (Tuesday, 29 May)
• Re: Positions on issue 19 (Tuesday, 29 May)
• Re: Positions on issue 19 (Tuesday, 29 May)
• Re: Positions on issue 19 (Monday, 28 May)
• Re: Intent for siblings after the Body? (Sunday, 20 May)
• Re: Proposal: Module for checking mustUnderstand headers have been processed (Thursday, 10 May)
• Re: module template draft 2 (Wednesday, 9 May)
• Proposal: Module for checking mustUnderstand headers have been processed (Monday, 7 May)
• Re: SOAPAction thoughts from elsewhere (Monday, 7 May)
• Re: [i95, i22] - Proposal for clarifying use of SOAPAction (Monday, 7 May)
• Re: [i95, i22] - Proposal for clarifying use of SOAPAction (Monday, 7 May)
• Re: [i95, i22] - Proposal for clarifying use of SOAPAction (Sunday, 6 May)
• Re: SOAPAction Proposal (Sunday, 6 May)
• Re: SOAPAction Proposal (Sunday, 6 May)
• Re: SOAPAction Proposal (Sunday, 6 May)
• Re: Must understand mustUnderstand proposal (Sunday, 6 May)
• Re: Must understand mustUnderstand proposal (Sunday, 6 May)
• Re: Must understand mustUnderstand proposal (Sunday, 6 May)
• SOAPAction Proposal (Thursday, 3 May)
• Must understand mustUnderstand proposal (Thursday, 3 May)
• Re: [i95, i22] - Proposal for clarifying use of SOAPAction (Tuesday, 1 May)

marwan sabbouh

• Re: Rennes->Dinard? (Thursday, 10 May)

Michael Champion

• Re: XMLP WG Issue 12 (Friday, 1 June)

Mike Dierken

• RE: HTTP Asynchronous Client Notifications (draft paper) (Friday, 18 May)

mrossi@csc.com

• Re: XMLP/SOAP spec - processing instructions (Tuesday, 22 May)

Narahari, Sateesh

• RE: HTTP Asynchronous Client Notifications (draft paper) (Friday, 18 May)

Nilesh Sawant

• Guidelines for SOAP..? (Thursday, 17 May)

Noah_Mendelsohn@lotus.com

• Re: Clarifications list for SOAP specification (Wednesday, 30 May)
• RE: An analysis of mustUnderstand and related issues (Wednesday, 30 May)
• Clarifications list for SOAP specification (Wednesday, 30 May)
• Re: Positions on issue 19 (Tuesday, 29 May)
• RE: An analysis of mustUnderstand and related issues (Friday, 25 May)
• RE: An analysis of mustUnderstand and related issues (Wednesday, 23 May)
• Re: An analysis of mustUnderstand and related issues (Tuesday, 22 May)
• Re: FW: a question about mustunderstand. (Monday, 21 May)
• RE: HTTP Asynchronous Client Notifications (draft paper) (Friday, 18 May)
• RE: An analysis of mustUnderstand and related issues (Wednesday, 16 May)
• Re: An analysis of mustUnderstand and related issues (Wednesday, 16 May)
• Re: An analysis of mustUnderstand and related issues (Tuesday, 15 May)
• Re: An analysis of mustUnderstand and related issues (Tuesday, 15 May)
• Re: An analysis of mustUnderstand and related issues (Monday, 14 May)
• An analysis of mustUnderstand and related issues (Saturday, 12 May)
• Re: Proposal: Module for checking mustUnderstand headers have been processed (Friday, 11 May)
• Re: Rennes->Dinard? (Thursday, 10 May)
• Re: Proposal: Module for checking mustUnderstand headers have been processed (Wednesday, 9 May)
• RE: SOAPAction Proposal (Tuesday, 8 May)
• RE: SOAPAction thoughts from elsewhere (Monday, 7 May)
• Re: SOAPAction Proposal (Friday, 4 May)
• Re: SOAPAction Proposal (Friday, 4 May)
• Re: Must understand mustUnderstand proposal (Thursday, 3 May)
• RE: mustUnderstand on client side (Wednesday, 2 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Tuesday, 1 May)

Painter, Philip

• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Friday, 4 May)

Rakesh K Soni

• Web Browser's location bar display problem (Friday, 11 May)

Randy Waldrop

• XMLP/SOAP spec - processing instructions (Monday, 21 May)

Ray Denenberg

• Regrets for June meeting (Wednesday, 16 May)

Rich Salz

• Re: Issue 16: methods with void return type and no out params (Monday, 28 May)
• Re: On the ordering of header entries (Monday, 28 May)
• Re: An analysis of mustUnderstand and related issues (Saturday, 26 May)
• Re: [soapbuilders] Re: An analysis of mustUnderstand and related issues (Friday, 25 May)
• Re: An analysis of mustUnderstand and related issues (Friday, 25 May)
• Re: Finding Faults in headers (Tuesday, 22 May)
• Re: Finding Faults in headers (Tuesday, 22 May)
• Re: Finding Faults in headers (Tuesday, 22 May)
• Finding Faults in headers (Tuesday, 22 May)
• Re: FW: a question about mustunderstand. (Tuesday, 22 May)
• Encoding non-XML-friendly names (Monday, 21 May)
• Re: On the ordering of header entries (Monday, 21 May)
• Re: Intent for siblings after the Body? (Sunday, 20 May)
• Re: Intent for siblings after the Body? (Saturday, 19 May)
• Intent for siblings after the Body? (Saturday, 19 May)
• How about an XML datatype? (Friday, 18 May)
• Re: An analysis of mustUnderstand and related issues (Wednesday, 16 May)
• Re: Proposal and issues surrounding MustUnderstand faults (Monday, 14 May)
• Re: xml transfer over TCP (Thursday, 10 May)
• Re: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)
• Re: [i95, i22] - Proposal for clarifying use of SOAPAction (Monday, 7 May)

Rottier, Pascal

• Overspecification (Thursday, 10 May)
• RE: SOAPAction Proposal (Monday, 7 May)

Sanjiva Weerawarana

• ANNOUNCE: Apache SOAP v2.2 Released (Wednesday, 30 May)
• WSFL (Web Services Flow Language) spec released! (Tuesday, 15 May)

Satish Thatte

• RE: Three new Web Services specs: SOAP-RP, DIME, and XLANG (Friday, 25 May)

Scott Lawrence

• Re: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)
• Re: SOAP/XML Protocol and filtering, etc. (Tuesday, 8 May)

Scott Seely

• Re: SOAPAction Proposal (Thursday, 3 May)

Simon Fell

• Re: Intent for siblings after the Body? (Saturday, 19 May)

Williams, Stuart

• RE: On the ordering of header entries (Thursday, 24 May)
• RE: Untargetted blocks (was Re: Must understand mustUnderstand pr oposal) (Wednesday, 9 May)
• RE: SOAPAction Proposal (Tuesday, 8 May)
• RE: Must understand mustUnderstand proposal (Friday, 4 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Friday, 4 May)
• RE: mustUnderstand on client side (Thursday, 3 May)
• RE: SOAPAction Proposal (Thursday, 3 May)
• RE: Must understand mustUnderstand proposal (Thursday, 3 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Thursday, 3 May)
• RE: mustUnderstand on client side (Wednesday, 2 May)
• RE: mustUnderstand on client side (Wednesday, 2 May)
• RE: [i95, i22] - Proposal for clarifying use of SOAPAction (Tuesday, 1 May)

Yin Leng Husband

• RE: Internationalization issue. (Wednesday, 9 May)

Yves Lafon

• Re: On the ordering of header entries (Monday, 28 May)
• 9 may 2001 teleconference minutes (Wednesday, 16 May)
• 2 May 2001 teleconferences minutes (Wednesday, 16 May)

Last message date: Thursday, 31 May 2001 22:21:53 UTC