Thursday, 31 October 2002
Wednesday, 30 October 2002
- Issue 392: revised proposal
- Resolution of Issue 359
- RE: Yet another proposal for issue 355
- Yet another proposal for issue 355
- Proposed resolution text for Issue 359
Tuesday, 29 October 2002
- Re: Issue 294 Proposed resolution - mark II
- Updated proposal for Issue 355 ( and 262 )
- Issue 392: draft proposals
- Updates to feature list based on disposition of Last Call issues
Monday, 28 October 2002
Tuesday, 29 October 2002
- FW: Proposal for Issue 385 (AF conformance clause)
- Additions to Usage Scenarios
- RE: Proposal for Issue 385 (AF conformance clause)
- Re: Proposal for issue 394: Some unprocessed headers should stay
- Re: Proposal for issue 394: Some unprocessed headers should stay
- RE: Proposal for issue 390
- RE: Proposal for issue 390
- Issue 388 Proposed Resolution
- Re: Issue 392: any one remembers?
- Issue 294 Proposed resolution - mark II
Monday, 28 October 2002
Sunday, 27 October 2002
- RE: Use of XML Messaging in Multicasting?
- Re: Proposal for issue 390
- Proposal for issue 390
- RE: Use of XML Messaging in Multicasting?
- Use of XML Messaging in Multicasting?
Friday, 25 October 2002
- Alternate SOAP 1.2 email binding
- proposal for issue 391 (how IDREF URIs are dereferenced)
- Proposal for issue 394: Some unprocessed headers should stay
Thursday, 24 October 2002
- RE: proposal for issue 393 (concrete packaging spec)
- Re: proposal for issue 393 (concrete packaging spec)
- proposal for issue 393 (concrete packaging spec)
Wednesday, 23 October 2002
Tuesday, 22 October 2002
- Re: Question regarding uniqueness of soap Fault in body
- RE: Proposal for SOAP 1.2 LC-Issue 371: Multiple Choice Assertions
- RE: Proposal for issue 277 - part 2
- RE: Proposal for SOAP 1.2 LC-Issue 371: Multiple Choice Assertions
- Re: Proposal for SOAP 1.2 LC-Issue 371: Multiple Choice Assertions
Monday, 21 October 2002
- Proposal for SOAP 1.2 LC-Issue 371: Multiple Choice Assertions
- RE: Proposal for new last call issue: Some unprocessed headersshould stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headersshould stay
- Re: Proposal for new last call issue: Some unprocessed headers should stay
Friday, 18 October 2002
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for issue 277 - part 2
- RE: Proposal for issue 277 - part 2
- Proposed Resolution: Issue 294 - "message exchange context out of nowhere?"
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for issue 277 - part 2
- Re: Proposal for issue 277 - part 2
- RE: Proposal for new last call issue: Some unprocessed headersshould stay
- RE: Proposal for issue 277 - part 2
- IMPLEMENTERS NOTE: Re: updated implementation summary
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for issue 277 - part 2
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- Re: updated implementation summary
- updated implementation summary
- Re: Proposal for issue 277 - part 2
- RE: Proposal for new last call issue: Some unprocessed headersshould stay
- Re: Issues 368 and 369 Proposal
- Re: Issue 389 proposal
- Re: Proposal for new last call issue: Some unprocessed headersshould stay
- Re: Issue 389 proposal
- [AF] Proposal for Issue 387
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- [AF] Proposal for issue 386 resolution
- Re: Proposal for issue 277 - part 2
- Re: Issues 368 and 369 Proposal
Thursday, 17 October 2002
- RE: Proposal for new last call issue: Some unprocessed headersshould stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headersshould stay
- Issue 389 proposal
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- Text for issue 300/359
- FYI: WS-I Basic Profile Working Group Draft published
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- Text for issue 300/359
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for issue 277 - part 2
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for issue 277 - part 1
Wednesday, 16 October 2002
Thursday, 17 October 2002
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for various Infosetisms
Wednesday, 16 October 2002
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for various Infosetisms
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed header s should stay
- Re: SOAP intermediaries (Some unprocessed headers should stay)
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for issue 277 - part 2
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for issue 277 - part 1
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- RE: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Question regarding uniqueness of soap Fault in body
- SOAP intermediaries (Some unprocessed headers should stay)
Tuesday, 15 October 2002
- Question regarding uniqueness of soap Fault in body
- Re: Proposal for new last call issue: Some unprocessed headers should stay
- Re: Proposal for new last call issue: Some unprocessed headers should stay
Monday, 14 October 2002
- Proposal for new last call issue: Some unprocessed headers should stay
- Re: Issues 368 and 369 Proposal
- Re: Issues 368 and 369 Proposal
- Proposal for Issue 363 - RPC return accessor
- Proposal for issue 277 - part 2
- Proposal for issue 277 - part 1
- Issue 367 Proposal
- Issues 368 and 369 Proposal
Friday, 11 October 2002
Wednesday, 9 October 2002
- RE: Issue 364 proposal
- RE: Issue 364 proposal
- Issue 364 proposal
- Possibly editorial problem in Data Model and Encoding
Tuesday, 8 October 2002
Monday, 7 October 2002
- Re: Proposal for issue 327
- Re: Proposal for issue 327
- Re: Proposal for issue 327
- RE: Proposal for issue 327
- Re: Proposed resolution on using schemas to default itemType and nodeClass (subissue of 231)
- Re: Proposal for issue 327
- Re: Are gateways SOAP intermediaries?
- Re: Are gateways SOAP intermediaries?
- RE: Are gateways SOAP intermediaries?
Friday, 4 October 2002
Thursday, 3 October 2002
Tuesday, 1 October 2002
- Re: Proposal for various Infosetisms
- Re: Proposal for various Infosetisms
- Re: Proposal for various Infosetisms
- Re: Proposal for various Infosetisms
- Re: Proposal for various Infosetisms
- RE: Proposal for various Infosetisms
- Re: Proposal for various Infosetisms
- RE: Proposal for various Infosetisms
- Re: Proposal for various Infosetisms
- RE: Proposal for various Infosetisms
- RE: Proposal for various Infosetisms
- RE: Proposal for various Infosetisms
- RE: Proposal for various Infosetisms