Friday, 1 June 2001
Thursday, 31 May 2001
- RE: An analysis of mustUnderstand and related issues
- Re: XMLP WG Issue 12
- Re: XMLP WG Issue 12
- XMLP WG Issue 12
- RE: An analysis of mustUnderstand and related issues
- Proposed Clarification for Issues 4 and 23
Wednesday, 30 May 2001
- ANNOUNCE: Apache SOAP v2.2 Released
- Re: Clarifications list for SOAP specification
- RE: An analysis of mustUnderstand and related issues
- Re: Clarifications list for SOAP specification
- [Question] XML market data
- Re: Positions on issue 19
- Clarifications list for SOAP specification
Tuesday, 29 May 2001
- RE: Positions on issue 19
- Re: Positions on issue 19
- RE: Positions on issue 19
- Re: Positions on issue 19
- Spec Issue
- Re: Positions on issue 19
- Re: Positions on issue 19
- Re: Positions on issue 19
- Re: Positions on issue 19
- Re: Issue 16: methods with void return type and no out params
Monday, 28 May 2001
- Re: Issue 16: methods with void return type and no out params
- Re: Issue 16: methods with void return type and no out params
- Re: Issue 16: methods with void return type and no out params
- Re: Positions on issue 19
- Re: On the ordering of header entries
- Re: On the ordering of header entries
- Re: Positions on issue 19
- Re: Issue 16: methods with void return type and no out params
- Positions on issue 19
Sunday, 27 May 2001
Saturday, 26 May 2001
- Re: An analysis of mustUnderstand and related issues
- Re: An analysis of mustUnderstand and related issues
- Re: An analysis of mustUnderstand and related issues
- FW: a question about mustunderstand.
Friday, 25 May 2001
- RE: Three new Web Services specs: SOAP-RP, DIME, and XLANG
- RE: Issue 16: methods with void return type and no out params
- RE: An analysis of mustUnderstand and related issues
- Gartner Group note on ebXML specs...
- Re: Issue 16: methods with void return type and no out params
- Re: Issue 16: methods with void return type and no out params
- RE: An analysis of mustUnderstand and related issues
- Issue 16: methods with void return type and no out params
- Re: [soapbuilders] Re: An analysis of mustUnderstand and related issues
- Re: An analysis of mustUnderstand and related issues
- RE: An analysis of mustUnderstand and related issues
Thursday, 24 May 2001
- RE: literal XML encoding?
- Re: literal XML encoding?
- Three new Web Services specs: SOAP-RP, DIME, and XLANG
- Re: literal XML encoding?
- RE: literal XML encoding?
- Re: literal XML encoding?
- RE: On the ordering of header entries
- Re: literal XML encoding?
Wednesday, 23 May 2001
- RE: An analysis of mustUnderstand and related issues
- literal XML encoding?
- Minutes of the 16 May teleconference
- Re: On the ordering of header entries
- RE: An analysis of mustUnderstand and related issues
Tuesday, 22 May 2001
- Re: Finding Faults in headers
- Re: An analysis of mustUnderstand and related issues
- Re: Finding Faults in headers
- Re: Finding Faults in headers
- Re: Finding Faults in headers
- RE: Finding Faults in headers
- Re: XMLP/SOAP spec - processing instructions
- RE: FW: a question about mustunderstand.
- Re: Finding Faults in headers
- Re: XMLP/SOAP spec - processing instructions
- FW: UN/CEFACT and OASIS Introduce ebXML-DEV Mail List
- Finding Faults in headers
- Re: FW: a question about mustunderstand.
- Re: FW: a question about mustunderstand.
- Re: Processing model
Thursday, 17 May 2001
Monday, 21 May 2001
- Re: Processing model
- FW: Statement from the CSG on the forward direction for UN/CEFACT's E-Business standards
- RE: FW: a question about mustunderstand.
- Re: FW: a question about mustunderstand.
- RE: XMLP/SOAP spec - processing instructions
- Re: XMLP/SOAP spec - processing instructions
- XMLP/SOAP spec - processing instructions
- Encoding non-XML-friendly names
- Re: On the ordering of header entries
- Re: On the ordering of header entries
- Re: On the ordering of header entries
- On the ordering of header entries
- RE: Intent for siblings after the Body?
Sunday, 20 May 2001
Saturday, 19 May 2001
- Re: Intent for siblings after the Body?
- Re: Intent for siblings after the Body?
- Intent for siblings after the Body?
- Processing model
- Re: FW: a question about mustunderstand.
- RE: Some issues with request/response binding to sync/async trans port .
Friday, 18 May 2001
- FW: a question about mustunderstand.
- RE: Some issues with request/response binding to sync/async trans port .
- RE: Some issues with request/response binding to sync/async transport .
- Some issues with request/response binding to sync/async transport .
- RE: HTTP Asynchronous Client Notifications (draft paper)
- RE: HTTP Asynchronous Client Notifications (draft paper)
- RE: HTTP Asynchronous Client Notifications (draft paper)
- RE: HTTP Asynchronous Client Notifications (draft paper)
- RE: HTTP Asynchronous Client Notifications (draft paper)
- RE: HTTP Asynchronous Client Notifications (draft paper)
- RE: HTTP Asynchronous Client Notifications (draft paper)
- How about an XML datatype?
Thursday, 17 May 2001
Wednesday, 16 May 2001
Thursday, 17 May 2001
Wednesday, 16 May 2001
Thursday, 17 May 2001
Wednesday, 16 May 2001
- RE: An analysis of mustUnderstand and related issues
- RE: An analysis of mustUnderstand and related issues
- 9 may 2001 teleconference minutes
- RE: Proposal and issues surrounding MustUnderstand faults
- Re: An analysis of mustUnderstand and related issues
- RE: An analysis of mustUnderstand and related issues
- RE: An analysis of mustUnderstand and related issues
- Re: An analysis of mustUnderstand and related issues
- Re: An analysis of mustUnderstand and related issues
- Regrets for June meeting
- 2 May 2001 teleconferences minutes
- Re: An analysis of mustUnderstand and related issues
- [Done Repost] Re: Must understand mustUnderstand proposal
- Re: [Repost] Re: Must understand mustUnderstand proposal
- [Repost] Re: Must understand mustUnderstand proposal
- [Repost] Re: Must understand mustUnderstand proposal
- [Repost] Re: Must understand mustUnderstand proposal
- [Repost] Re: Must understand mustUnderstand proposal
- [Repost] Re: Must understand mustUnderstand proposal
Tuesday, 15 May 2001
- Re: An analysis of mustUnderstand and related issues
- Re: An analysis of mustUnderstand and related issues
- Re: Reqs/AM - Comments/Questions
- Re: An analysis of mustUnderstand and related issues
- Re: An analysis of mustUnderstand and related issues
- Re: An analysis of mustUnderstand and related issues
- WSFL (Web Services Flow Language) spec released!
Monday, 14 May 2001
- RE: An analysis of mustUnderstand and related issues
- Re: An analysis of mustUnderstand and related issues
- FYI - FW: ebXML APPROVED
- Re: Proposal and issues surrounding MustUnderstand faults
- Re: An analysis of mustUnderstand and related issues
- Re: An analysis of mustUnderstand and related issues
Sunday, 13 May 2001
Saturday, 12 May 2001
- Re: An analysis of mustUnderstand and related issues
- Re: An analysis of mustUnderstand and related issues
- Re: Proposal and issues surrounding MustUnderstand faults
- An analysis of mustUnderstand and related issues
Friday, 11 May 2001
- RE: Proposal and issues surrounding MustUnderstand faults
- Proposal and issues surrounding MustUnderstand faults
- Re: Proposal: Module for checking mustUnderstand headers have been processed
- Re: Proposal: Module for checking mustUnderstand headers have been processed
- Re: module template draft 2
- Re: Proposal: Module for checking mustUnderstand headers have been processed
- Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal)
- Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal)
- Re: xml transfer over TCP
- [Binary data] Application/Multiplexed content-type draft
- Re: Reqs/AM - Comments/Questions
- Web Browser's location bar display problem
Thursday, 10 May 2001
- Regrets.
- Re: Proposal: Module for checking mustUnderstand headers have been processed
- Re: Rennes->Dinard?
- Re: Proposal: Module for checking mustUnderstand headers have been processed
- Re: BEEP vs. HTTP as transport for XMLP/SOAP (was xml transfer over TCP)
- Re: Rennes->Dinard?
- BEEP vs. HTTP as transport for XMLP/SOAP (was xml transfer over TCP)
- Re: SOAPAction Proposal
- Overspecification
- RE: xml transfer over TCP
- Re: xml transfer over TCP
- Re: xml transfer over TCP
- RE: SOAPAction Proposal
- Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal)
- Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal)
- Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal)
Wednesday, 9 May 2001
Thursday, 10 May 2001
- Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal)
- Re: SOAPAction Proposal
- RE: Some basic (naive?) questions about mustunderstand.
- Some basic (naive?) questions about mustunderstand.
- Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal)
Wednesday, 9 May 2001
- RE: SOAPAction Proposal
- RE: SOAPAction Proposal
- Re: module template draft 2
- module template draft 2
- Re: Proposal: Module for checking mustUnderstand headers have been processed
- xml transfer over TCP
- Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal)
- Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal)
- Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal)
- Re: Must understand mustUnderstand proposal
- RE: Untargetted blocks (was Re: Must understand mustUnderstand pr oposal)
- Re: Untargetted blocks (was Re: Must understand mustUnderstand proposal)
- Re: HTTP Asynchronous Client Notifications (draft paper)
- Untargetted blocks (was Re: Must understand mustUnderstand proposal)
- Re: xml transfer over TCP
- Re: Must understand mustUnderstand proposal
- Re: Must understand mustUnderstand proposal
Tuesday, 8 May 2001
Wednesday, 9 May 2001
Tuesday, 8 May 2001
- RE: HTTP Asynchronous Client Notifications (draft paper)
- RE: SOAP/XML Protocol and filtering, etc.
- RE: About the IETF list... (was: SOAP/XML Protocol and filtering, etc.)
- RE: About the IETF list... (was: SOAP/XML Protocol and filtering, etc.)
- RE: About the IETF list... (was: SOAP/XML Protocol and filtering, etc.)
- RE: About the IETF list... (was: SOAP/XML Protocol and filtering, etc.)
- RE: SOAP/XML Protocol and filtering, etc.
- RE: SOAP/XML Protocol and filtering, etc.
- RE: About the IETF list... (was: SOAP/XML Protocol and filtering, etc.)
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- Re: SOAP/XML Protocol and filtering, etc.
- test
- RE: SOAP/XML Protocol and filtering, etc.
- Re: SOAP/XML Protocol and filtering, etc.
- RE: SOAP/XML Protocol and filtering, etc.
- Re: SOAP/XML Protocol and filtering, etc.
- Re: SOAP/XML Protocol and filtering, etc.
- Re: SOAP/XML Protocol and filtering, etc.
- Re: SOAP/XML Protocol and filtering, etc.
- RE: SOAP/XML Protocol and filtering, etc.
- About the IETF list... (was: SOAP/XML Protocol and filtering, etc.)
- Re: SOAP/XML Protocol and filtering, etc.
- RE: SOAP/XML Protocol and filtering, etc.
- Re: SOAP/XML Protocol and filtering, etc.
- RE: SOAP/XML Protocol and filtering, etc.
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- Re: SOAP/XML Protocol and filtering, etc.
- RE: SOAPAction Proposal
- RE: SOAP/XML Protocol and filtering, etc.
- RE: SOAPAction Proposal
Monday, 7 May 2001
Tuesday, 8 May 2001
- Re: SOAP/XML Protocol and filtering, etc.
- Re: SOAP/XML Protocol and filtering, etc.
- RE: SOAPAction Proposal
- RE: SOAPAction Proposal
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- Re: Reqs/AM - Comments/Questions
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: SOAPAction Proposal
- RE: SOAPAction Proposal
- RE: SOAP/XML Protocol and filtering, etc.
- RE: SOAP/XML Protocol and filtering, etc.
- Re: SOAP/XML Protocol and filtering, etc.
Monday, 7 May 2001
- Regrets for 5/9
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- Fwd: Re: SOAP/XML Protocol and filtering, etc.
- RE: SOAP/XML Protocol and filtering, etc.
- RE: SOAPAction thoughts from elsewhere
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: SOAPAction thoughts from elsewhere
- Proposal: Module for checking mustUnderstand headers have been processed
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: SOAPAction thoughts from elsewhere
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- Re: HTTPSOAP - was SOAPAction Proposal
- RE: SOAPAction thoughts from elsewhere
- Re: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- Re: SOAPAction thoughts from elsewhere
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- SOAPAction thoughts from elsewhere
- Re: [i95, i22] - Proposal for clarifying use of SOAPAction
- Re: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: SOAPAction Proposal
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- xml transfer over TCP
- RE: SOAPAction Proposal
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: HTTP GET requests (was Re: SOAPAction Proposal)
- RE: SOAPAction Proposal
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: SOAPAction Proposal
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- HTTP GET requests (was Re: SOAPAction Proposal)
- Re: [i95, i22] - Proposal for clarifying use of SOAPAction
- Re: [i95, i22] - Proposal for clarifying use of SOAPAction
Sunday, 6 May 2001
- Re: [i95, i22] - Proposal for clarifying use of SOAPAction
- Re: SOAPAction Proposal
- Re: SOAPAction Proposal
- Re: SOAPAction Proposal
- Re: Must understand mustUnderstand proposal
- Re: Must understand mustUnderstand proposal
- Re: Must understand mustUnderstand proposal
- XMLP ed. drafts available for comment
Saturday, 5 May 2001
Friday, 4 May 2001
Saturday, 5 May 2001
Friday, 4 May 2001
- RE: SOAPAction Proposal
- RE: SOAPAction Proposal
- Re: SOAPAction Proposal
- Re: SOAPAction Proposal
- Re: SOAPAction Proposal
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- Re: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- Re: Must understand mustUnderstand proposal
- Re: Must understand mustUnderstand proposal
- RE: Must understand mustUnderstand proposal
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
Thursday, 3 May 2001
- Re: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- Re: Must understand mustUnderstand proposal
- Re: Must understand mustUnderstand proposal
- Re: SOAPAction Proposal
- Re: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: SOAPAction Proposal
- RE: SOAPAction Proposal
- RE: mustUnderstand on client side
- Re: Must understand mustUnderstand proposal
- Re: SOAPAction Proposal
- Re: SOAPAction Proposal
- Re: Must understand mustUnderstand proposal
- Re: Must understand mustUnderstand proposal
- Re: Must understand mustUnderstand proposal
- Re: Must understand mustUnderstand proposal
- RE: RE: SOAPAction Proposal
- RE: SOAPAction Proposal
- Re: Internationalization issue.
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- SOAPAction Proposal
- Re: RE: SOAPAction Proposal
- Re: mustUnderstand on client side
- RE: SOAPAction Proposal
- Re: SOAPAction Proposal
- RE: Must understand mustUnderstand proposal
- RE: SOAPAction Proposal
- Re: SOAPAction Proposal
- Re: Must understand mustUnderstand proposal
- RE: Must understand mustUnderstand proposal
- Re: Must understand mustUnderstand proposal
- Re: Must understand mustUnderstand proposal
- SOAPAction Proposal
- Re: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- Must understand mustUnderstand proposal
Wednesday, 2 May 2001
- RE: Internationalization issue.
- Re: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: mustUnderstand on the client side
- RE: mustUnderstand on client side
- RE: mustUnderstand on client side
- RE: mustUnderstand on client side
- RE: mustUnderstand on client side
- RE: mustUnderstand on client side
- RE: mustUnderstand on client side
- RE: mustUnderstand on client side
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- RE: mustUnderstand on client side
- [xml-dist-app] <none>
- RE: mustUnderstand on client side
- RE: mustUnderstand on client side
- RE: mustUnderstand on client side
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
Tuesday, 1 May 2001
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- Re: [i95, i22] - Proposal for clarifying use of SOAPAction
- Re: [soapbuilders] question re: namespace hierarchies
- RE: mustUnderstand on client side
- RE: [i95, i22] - Proposal for clarifying use of SOAPAction
- Re: [i95, i22] - Proposal for clarifying use of SOAPAction