W3C home > Mailing lists > Public > xml-dist-app@w3.org > March 2002

RE: Email binding issue

From: Mountain, Highland M <highland.m.mountain@intel.com>
Date: Tue, 5 Mar 2002 10:10:47 -0800
Message-ID: <ED492E16A0B8D311AC490090276D20841709BF36@FMSMSX31>
To: "'Mark Baker'" <distobj@acm.org>, xml-dist-app@w3.org
Mark,

In an earlier draft of this document, there were SMTP (and POP3) commands
included to illustrate mail client and server interaction.  A small sub team
met and decided that it is not the responsibility of SOAP to define email
infrastructure communication and therefore, these commands should not be in
the binding document.  The email infrastructure (i.e. which email clients,
servers and associated commands along the message path) is of no interest to
SOAP, just the content of the mail message.

Thoughts?

Highland


-----Original Message-----
From: Mark Baker [mailto:distobj@acm.org]
Sent: Tuesday, March 05, 2002 10:27 AM
To: xml-dist-app@w3.org
Subject: Email binding issue


Sorry, the for the delay, but I've just had my first look at the email
binding.

This binding is to RFC 2822 a message format used with RFC 2821, the
SMTP protocol.  The use of RFC 2822 in 4.1.1.1 and 4.1.2.3 is fine
for specifying SMTP header, but is insufficient for an email binding.

Is it just not yet complete?  Have I misunderstood the intent?  Because
it seems to me that in order to validate the SOAP protocol binding
framework, we should really try to bind SOAP to an actual protocol. 8-)

MB
-- 
Mark Baker, Chief Science Officer, Planetfred, Inc.
Ottawa, Ontario, CANADA.      mbaker@planetfred.com
http://www.markbaker.ca   http://www.planetfred.com
Received on Tuesday, 5 March 2002 13:11:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:09 GMT