xml-dist-app@w3.org from December 2000 by subject

15 & 29 Nov teleconference minutes

[DR 008, 040] - Summary and proposal

[DR 22, 25, 28, 122]

[DR 309] Vague?

[DR 609] I18N experts' view

[DR008] - passing arbitrary content

[DR040] - Binary data

[DR119] Binary data

[DR120] Compact Encoding and Compression Issues

[DR304], [R502], [DR058], [DR025], [DR028], [DR067] and "mess age patterns"

[DR304], [R502], [DR058], [DR025], [DR028], [DR067] and "message patterns"

[DR609] feedback

[DS10] Message header and payload encryption

[DS11] Communication via multiple intermediaries

[DS12] Communication via heterogeneous transports

[DS14] Quality of service provision

[DS15] Communication via an intermediary

[DS16] Asynchronous messaging

[DS1] Fire-and-forget to single receiver

[DS2] Fire-and-forget to multiple receivers

[DS3] Request-response

[DS4] Remote Procedure Call (RPC)

[DS5] Request with transport level response

[DS6] Request with encrypted payload

[DS7] Third party intermediary

[DS8] Conversational message exchange

[DS9] Message data signature and encryption

[Fwd: text/xml for SOAP (and XP) considered harmful]

[R300] References have changed

[R608] and digital signatures

[xml-dist-app] <none>

An error in the example in section 5.4.1?

Another real world use case from the DCOM list; requirement for async processing in XP

application/something+xml (was text/xml for SOAP (and XP) conside red harmful)

CFP XML and Distributed Applications

Comments on XML Protocol Reqs

Dec 6 teleconference minutes

DR 121: Additional transport services

DR 122: Mapping issues

DR 123: HTTP-NG, out-of-order delivery

DR 22: raw TCP usage

DR 25: Multicast (again)

DR 28: Multicast

DR 28: Multicast and R502

DR 28: Multicast and R502 (fwd)

DR027: Audit trails

DR031: Routing

DR033: UI interactions

DR046 -- Application Semantics and Security

DR051 and DR006: Identification of message

DR058: Interaction patterns

DR065

DR069 -- RPC and Application Semantics

DR109: Resources/object references

DR124: Application Semantics

DR125: Defining app layer semantics

DR305 -- ongoing discussion

DR309 -- ongoing discussion

DS1

DS2

DS5

DS8

ebXML and XML Protocol

ebXML press release

example usage scenarios and use cases

f2f regrets

Feedback from ebXML's TRP Vice Chair RE: SOAP and ebXML

Happy New Year

Intermediaries and remote URI references (was: RE: [DR008] - pass ing arbitrary content)

MIME marking for SOAP and XP (was text/xml for SOAP (and XP) con sidered harmful)

MSIE/Mac in P2P mode

New draft of the requirements document available

New Scenario

Proposed revised wording for XP receiver

Proposed revised wording for XP sender

Proposed revised wording of 6.3 preamble

Rational behind rewording of sender and receiver

Redmond meeting directions

Response to "On the use of HTTP as a Substrate for Other Prot oco ls"

Response to "On the use of HTTP as a Substrate for Other Protoco ls"

Section 4.3: edited requirements (rev. 2)

SOAP and ebXML

SOAP Messages with Attachments, W3C Submission

SOAP spec.: HTTP binding

Strawman: Abstract Model for XP

Sun position on SOAP and ebXML

text/xml for SOAP (and XP) considered harmful

Typical use case to consider - FW: [SOAP] SQL Image File in SOAP message

use case [communication libaries and application data]

use case [multiple, asynchronous response patterns]

use case [SAX-style XP handlers]

use case [thin clients and binary/application data]

use case for XP -- revalue smart card

validating an xml file

What is the difference in using XML, Java applets and Html interms of Security and performance

Which 4 orgs can set de jure standards (was RE: SOAP and ebXML)

XML Protocol Requirements published as a W3C Working Draft

Last message date: Sunday, 31 December 2000 07:18:00 UTC