RE: ebXML Transport, Routing and Packaging Requirements

["Rik Drummond" <drummond@onramp.net>]

i think the addresses should also include the email address and our
packaging, at least until we figure we can't do it, should also allow for
non xml contents, to help with migration from older implemenations.  best
regards, rik

-----Original Message-----
From: owner-ebxml-transport@lists.oasis-open.org
[mailto:owner-ebxml-transport@lists.oasis-open.org]On Behalf Of David
Burdett
Sent: Tuesday, November 30, 1999 6:19 PM
To: ebXML Transport (E-mail)
Subject: ebXML Transport, Routing and Packaging Requirements


Looking through the initial evaluation that Henry Lowe produced, I realised
that it might be helpful if we had more "flesh" around what these
requirements actually mean. So I've drafted up a document that takes the
original list we produced at the workshop and attempted to put some clearer
definitions of what each of the "one-liners" actually mean. If we can agree
these defintions we should be able to make a much more accurate and fairer
comparison.

Anyway I'm sure that the definitions I've come up with are probably
incomplete and certainly they can be improved by your collective expert
reveiw, so please let me have any comments/suggestions you have.

Regards

David
 <<ebXML Transport Requirements.pdf>>

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