Sunday, 31 December 2000
Friday, 29 December 2000
Wednesday, 27 December 2000
- Re: MSIE/Mac in P2P mode
- Re: MSIE/Mac in P2P mode
- MIME marking for SOAP and XP (was text/xml for SOAP (and XP) con sidered harmful)
- application/something+xml (was text/xml for SOAP (and XP) conside red harmful)
- MSIE/Mac in P2P mode
Tuesday, 26 December 2000
Monday, 25 December 2000
Saturday, 23 December 2000
Friday, 22 December 2000
- RE: Proposed revised wording of 6.3 preamble
- Re: Proposed revised wording of 6.3 preamble
- Re: [DS5] Request with transport level response
- Re: Proposed revised wording of 6.3 preamble
- Re: Strawman: Abstract Model for XP
- [xml-dist-app] <none>
- DS8
- DS5
- DS2
- DS1
- Re: Strawman: Abstract Model for XP
- Rational behind rewording of sender and receiver
- Proposed revised wording for XP receiver
- Proposed revised wording for XP sender
- Proposed revised wording of 6.3 preamble
Thursday, 21 December 2000
- Re: [DS4] Remote Procedure Call (RPC)
- Re: [DS4] Remote Procedure Call (RPC)
- Sun position on SOAP and ebXML
- RE: [DS1] Fire-and-forget to single receiver
- RE: [DS1] Fire-and-forget to single receiver
- Re: [DS2] Fire-and-forget to multiple receivers
- Re: [DS1] Fire-and-forget to single receiver
- Re: Strawman: Abstract Model for XP
- [DS15] Communication via an intermediary
- [DS10] Message header and payload encryption
- [DS14] Quality of service provision
- [DS16] Asynchronous messaging
- [DS9] Message data signature and encryption
- [DS12] Communication via heterogeneous transports
- [DS11] Communication via multiple intermediaries
- Re: [DS1] Fire-and-forget to single receiver
- [DS8] Conversational message exchange
- [DS7] Third party intermediary
- [DS6] Request with encrypted payload
- [DS5] Request with transport level response
- [DS1] Fire-and-forget to single receiver
- [DS4] Remote Procedure Call (RPC)
- [DS3] Request-response
- [DS2] Fire-and-forget to multiple receivers
Wednesday, 20 December 2000
- example usage scenarios and use cases
- RE: Comments on XML Protocol Reqs
- Re: SOAP spec.: HTTP binding
- RE: use case [SAX-style XP handlers]
- Comments on XML Protocol Reqs
- Re: text/xml for SOAP (and XP) considered harmful
Tuesday, 19 December 2000
- XML Protocol Requirements published as a W3C Working Draft
- RE: text/xml for SOAP (and XP) considered harmful
- use case [multiple, asynchronous response patterns]
- use case [communication libaries and application data]
- use case [thin clients and binary/application data]
- Re: text/xml for SOAP (and XP) considered harmful
- use case [SAX-style XP handlers]
- RE: text/xml for SOAP (and XP) considered harmful
- RE: text/xml for SOAP (and XP) considered harmful
- RE: text/xml for SOAP (and XP) considered harmful
- Re: text/xml for SOAP (and XP) considered harmful
- Re: text/xml for SOAP (and XP) considered harmful
- RE: text/xml for SOAP (and XP) considered harmful
- RE: SOAP spec.: HTTP binding
Monday, 18 December 2000
- RE: SOAP spec.: HTTP binding
- RE: SOAP spec.: HTTP binding
- RE: SOAP spec.: HTTP binding
- SOAP spec.: HTTP binding
- Re: text/xml for SOAP (and XP) considered harmful
- Dec 6 teleconference minutes
- RE: text/xml for SOAP (and XP) considered harmful
Saturday, 16 December 2000
- RE: [Fwd: text/xml for SOAP (and XP) considered harmful]
- RE: [Fwd: text/xml for SOAP (and XP) considered harmful]
- RE: [Fwd: text/xml for SOAP (and XP) considered harmful]
- [xml-dist-app] <none>
Friday, 15 December 2000
Thursday, 14 December 2000
Wednesday, 13 December 2000
- RE: text/xml for SOAP (and XP) considered harmful
- RE: DR027: Audit trails
- RE: text/xml for SOAP (and XP) considered harmful
- RE: DR027: Audit trails
- validating an xml file
- RE: Response to "On the use of HTTP as a Substrate for Other Prot oco ls"
- RE: text/xml for SOAP (and XP) considered harmful
- RE: text/xml for SOAP (and XP) considered harmful
- Re: text/xml for SOAP (and XP) considered harmful
- RE: [DR008] - passing arbitrary content
- RE: DR046 -- Application Semantics and Security
- RE: DR125: Defining app layer semantics
- RE: DR051 and DR006: Identification of message
- RE: [R608] and digital signatures
- RE: DR027: Audit trails
- RE: DR065
- RE: DR033: UI interactions
- RE: text/xml for SOAP (and XP) considered harmful
Tuesday, 12 December 2000
- An error in the example in section 5.4.1?
- RE: text/xml for SOAP (and XP) considered harmful
- RE: text/xml for SOAP (and XP) considered harmful
- Re: Response to "On the use of HTTP as a Substrate for Other Protoco ls"
- RE: text/xml for SOAP (and XP) considered harmful
- Re: text/xml for SOAP (and XP) considered harmful
- RE: text/xml for SOAP (and XP) considered harmful
- RE: text/xml for SOAP (and XP) considered harmful
- ebXML press release
- Re: text/xml for SOAP (and XP) considered harmful
- RE: text/xml for SOAP (and XP) considered harmful
- Re: text/xml for SOAP (and XP) considered harmful
- RE: text/xml for SOAP (and XP) considered harmful
- text/xml for SOAP (and XP) considered harmful
Monday, 11 December 2000
- SOAP Messages with Attachments, W3C Submission
- Re: Which 4 orgs can set de jure standards (was RE: SOAP and ebXML)
- Re: Which 4 orgs can set de jure standards (was RE: SOAP and ebXML)
- Re: Which 4 orgs can set de jure standards (was RE: SOAP and ebXML)
- Re: Which 4 orgs can set de jure standards (was RE: SOAP and ebXML)
- Re: Which 4 orgs can set de jure standards (was RE: SOAP and ebXML)
- Re: Which 4 orgs can set de jure standards (was RE: SOAP and ebXML)
- Which 4 orgs can set de jure standards (was RE: SOAP and ebXML)
Sunday, 10 December 2000
Monday, 11 December 2000
- Re: Intermediaries and remote URI references (was: RE: [DR008] - pass ing arbitrary content)
- RE: Intermediaries and remote URI references (was: RE: [DR008] - pass ing arbitrary content)
- RE: Intermediaries and remote URI references (was: RE: [DR008] - pass ing arbitrary content)
- RE: Intermediaries and remote URI references (was: RE: [DR008] - pass ing arbitrary content)
Saturday, 9 December 2000
Sunday, 10 December 2000
- Re: Intermediaries and remote URI references (was: RE: [DR008] - pass ing arbitrary content)
- RE: Intermediaries and remote URI references (was: RE: [DR008] - pass ing arbitrary content)
- Re: Intermediaries and remote URI references (was: RE: [DR008] - pass ing arbitrary content)
Saturday, 9 December 2000
- Intermediaries and remote URI references (was: RE: [DR008] - pass ing arbitrary content)
- RE: [DR008] - passing arbitrary content
- f2f regrets
- Another real world use case from the DCOM list; requirement for async processing in XP
- RE: SOAP and ebXML
- Feedback from ebXML's TRP Vice Chair RE: SOAP and ebXML
- RE: SOAP and ebXML
- RE: SOAP and ebXML
Friday, 8 December 2000
- RE: [DR008] - passing arbitrary content
- RE: SOAP and ebXML
- RE: [DR008] - passing arbitrary content
- RE: [DR008] - passing arbitrary content
- [R300] References have changed
- RE: [DR008] - passing arbitrary content
- Re: SOAP and ebXML
- Re: SOAP and ebXML
- RE: SOAP and ebXML
- RE: SOAP and ebXML
- RE: SOAP and ebXML
- Typical use case to consider - FW: [SOAP] SQL Image File in SOAP message
- RE: SOAP and ebXML
- Re: SOAP and ebXML
- RE: SOAP and ebXML
- RE: SOAP and ebXML
- Redmond meeting directions
- RE: SOAP and ebXML
- RE: SOAP and ebXML
Thursday, 7 December 2000
- RE: [DR008] - passing arbitrary content
- Re: SOAP and ebXML
- RE: SOAP and ebXML
- RE: SOAP and ebXML
- New draft of the requirements document available
- RE: SOAP and ebXML
- use case for XP -- revalue smart card
- [DR 008, 040] - Summary and proposal
- RE: [DR008] - passing arbitrary content
- RE: SOAP and ebXML
- [DR609] feedback
- RE: SOAP and ebXML
- RE: [DR008] - passing arbitrary content
- RE: ebXML and XML Protocol
- ebXML and XML Protocol
- RE: [DR304], [R502], [DR058], [DR025], [DR028], [DR067] and "mess age patterns"
- RE: SOAP and ebXML
- SOAP and ebXML
Wednesday, 6 December 2000
- [DR304], [R502], [DR058], [DR025], [DR028], [DR067] and "message patterns"
- [R608] and digital signatures
- 15 & 29 Nov teleconference minutes
- RE: DR046 -- Application Semantics and Security
- RE: DR065
- Section 4.3: edited requirements (rev. 2)
- Re: DR065
- Re: DR058: Interaction patterns
- Re: DR109: Resources/object references
- Re: DR051 and DR006: Identification of message
- Re: DR 122: Mapping issues
- Re: DR 122: Mapping issues
- RE: [DR008] - passing arbitrary content
- RE: [DR008] - passing arbitrary content
- DR065
- DR124: Application Semantics
- DR109: Resources/object references
- DR058: Interaction patterns
- DR033: UI interactions
- DR125: Defining app layer semantics
- DR027: Audit trails
- DR051 and DR006: Identification of message
- DR031: Routing
- DR069 -- RPC and Application Semantics
- DR046 -- Application Semantics and Security
- RE: [DR008] - passing arbitrary content
- RE: [DR008] - passing arbitrary content
- RE: [DR008] - passing arbitrary content
- Response to "On the use of HTTP as a Substrate for Other Protoco ls"
- RE: [DR008] - passing arbitrary content
- RE: [DR008] - passing arbitrary content
- RE: [DR008] - passing arbitrary content
- What is the difference in using XML, Java applets and Html interms of Security and performance
- RE: DR 28: Multicast and R502 (fwd)
- Re: [DR040] - Binary data
- Re: DR 28: Multicast and R502
- Re: DR 122: Mapping issues
- Re: [DR040] - Binary data
- RE: [DR008] - passing arbitrary content
- RE: [DR008] - passing arbitrary content
- RE: [DR008] - passing arbitrary content
- RE: [DR 609] I18N experts' view
Tuesday, 5 December 2000
- RE: [DR008] - passing arbitrary content
- RE: [DR008] - passing arbitrary content
- RE: [DR008] - passing arbitrary content
- RE: [DR008] - passing arbitrary content
- RE: [DR008] - passing arbitrary content
- RE: [DR008] - passing arbitrary content
- RE: DR 28: Multicast and R502
- RE: [DR040] - Binary data
- RE: [DR008] - passing arbitrary content
- RE: [DR040] - Binary data
- RE: DR 121: Additional transport services
- Re: [DR 609] I18N experts' view
- RE: [DR040] - Binary data
- RE: [DR008] - passing arbitrary content
- Re: DR 122: Mapping issues
- Re: DR 122: Mapping issues
- RE: [DR008] - passing arbitrary content
- Re: [DR008] - passing arbitrary content
- RE: [DR008] - passing arbitrary content
- RE: [DR040] - Binary data
- Re: [DR008] - passing arbitrary content
- Re: [DR120] Compact Encoding and Compression Issues
- Re: [DR040] - Binary data
- Re: [DR008] - passing arbitrary content
- Re: DR 121: Additional transport services
- Re: DR 22: raw TCP usage
- RE: [DR 609] I18N experts' view
- RE: [DR040] - Binary data
- RE: DR 121: Additional transport services
- RE: DR 123: HTTP-NG, out-of-order delivery
- RE: DR 22: raw TCP usage
- [DR 22, 25, 28, 122]
Monday, 4 December 2000
- [DR120] Compact Encoding and Compression Issues
- [DR040] - Binary data
- [DR008] - passing arbitrary content
- Re: DR 122: Mapping issues
- [DR119] Binary data
- Re: DR 122: Mapping issues
- Re: [DR 609] I18N experts' view
- Re: DR 122: Mapping issues