XML Messaging
David Burdett <david.burdett@commerceone.com> Sat, 22 January 2000 00:41 UTC
Return-Path: <ietf-trade-errors@lists.eListX.com>
Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-31 #39671) id <0FOP00101OKMTE@eListX.com>; Fri, 21 Jan 2000 19:41:10 -0500 (EST)
Received: from FILTER-DAEMON by eListX.com (PMDF V5.2-31 #39671) id <0FOP00101OKLTD@eListX.com> (original mail from david.burdett@commerceone.com); Fri, 21 Jan 2000 19:41:09 -0500 (EST)
Received: from FILTER-DAEMON by eListX.com (PMDF V5.2-31 #39671) id <0FOP00103OKKTB@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822; ietf-trade@lists.eListX.com); Fri, 21 Jan 2000 19:41:08 -0500 (EST)
Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-31 #39671) id <0FOP00101OKITA@eListX.com> for ietf-trade@filter.eListX.com (ORCPT rfc822; ietf-trade@lists.eListX.com); Fri, 21 Jan 2000 19:41:06 -0500 (EST)
Received: from zeus.commerceone.com (mail.commerceone.com [204.71.220.19]) by eListX.com (PMDF V5.2-31 #39671) with ESMTP id <0FOP00NI4OKH3G@eListX.com> for ietf-trade@lists.eListX.com; Fri, 21 Jan 2000 19:41:06 -0500 (EST)
Received: by ZEUS with Internet Mail Service (5.5.2448.0) id <CJW6PX0H>; Fri, 21 Jan 2000 16:43:50 -0800
Content-return: allowed
Date: Fri, 21 Jan 2000 16:38:08 -0800
From: David Burdett <david.burdett@commerceone.com>
Subject: XML Messaging
To: "IETF Trade (E-mail)" <ietf-trade@lists.eListX.com>
Cc: "Donald E. Eastlake (E-mail)" <dee3@torque.pothole.com>
Message-id: <123B7EB05559D311B0D900A0C9EA3D76DB6984@NEPTUNE>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-type: MULTIPART/MIXED; BOUNDARY="Boundary_(ID_fbC2fYKDwhnRQJmuQYSxcw)"
X-MS-TNEF-Correlator: <123B7EB05559D311B0D900A0C9EA3D76DB6984@NEPTUNE>
I just want to let everyone know that I've submitted the first draft of a "requirements" paper for XML Messaging to the Internet drafts editor. I guess this is likely to be published sometime early next week. The objective of XML Messaging as stated in the paper to provide a "generic approach to the reliable, resilient, secure, tamper resistant, authenticated exchange of XML or other electronic documents over insecure, unreliable transport mechanisms". In thinking about XML Messaging I can see significant benefit in splitting the specification up into several different parts. So far I have identified the following in addition to a "requirements" specification: * Common XML Message Elements * Document Exchange and Transactions * Reliable Messaging * Secure Messaging * Document Choreography Definitions * Common Document Exchanges * Transport Protocol Supplements I think that the more we people we can get working on these the better. Finally this is a **first** draft and realize that there is a **lot** of discussion and thought required to make an XML Messaging standard real. I look forward to working with you all. Regards David Advanced Technology, CommerceOne 1600 Riviera Ave, Suite 200, Walnut Creek, CA 94596, USA Tel: +1 (925) 941 4422 or +1 (650) 623 2888; mailto:david.burdett@commerceone.com; Web: http://www.commerceone.com
- XML Messaging David Burdett