OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-transport message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: RE: How simple is the simple in KISS

Not really.

Message headers, in my view simply involves the definition of the content
and structure of the header that must go with a document

Reliable messaging is the active process of waiting for a response to a
message and then, if a response does not arrive within the expected
timescales, fixing the problem. Fixing the problem can include:
1. Simply resending the message, or
2. Doing an inquiry on the destination to see if they got the message - have
a look at the IETF XML Messaging Internet Draft for a fuller explanation of
the ideas here.

So really Message Headers is all about defining the data, and Reliable
Messaging about defining the process.



-----Original Message-----
From: Jenkins Gordon [mailto:gjenkins@singnet.com.sg]
Sent: Monday, March 06, 2000 11:22 PM
To: David Burdett; ebXML Transport (E-mail)
Subject: Re: How simple is the simple in KISS


Are not Items 1 and 2 the same - or close to the same?



Gordon Jenkins
Standard Chartered Bank C&IB
Senior Product Manager: Electronic Commerce
51 Bras Basah

Email : gjenkins@singnet.com.sg

Tel :65-331 5095
----- Original Message -----
From: David Burdett <david.burdett@commerceone.com>
To: ebXML Transport (E-mail) <ebXML-Transport@lists.oasis-open.org>
Sent: Monday, March 06, 2000 1:53 PM
Subject: How simple is the simple in KISS

> There has been a lot of recent discussion about KISS on the list that I
> whole-heartedly support.
> However we must NOT make it so simple that it does not meet minimum
> requirements. So, for what it's worth, here are my **minimum**
> for ebXML Transport. We need to develop specifications for:
> 1. Message Headers. The additional data that must be associated with a
> document so that it can be sent a third party and successfully processed -
> we're working on this
> 2. Reliable Messaging. If for some reason, a message does not get through
> it's destination, then we can identify the problem and recover from it in
> way that does not rely on proprietary reliable messaging protocols.
> 3. Security. We need to know that a message has not changed and is
> authentic, i.e. it has come from the organization or individual it appears
> to have come from
> I know that requirements 2 and 3 are not **always** required, but I think
> that in B2B they will be so frequently required that we will not be get
> widespread adoption of ebXML Transport without them.
> What does everyone else think?
> David
> Advanced Technology, CommerceOne
> 4400 Rosewood Drive 3rd Fl, Bldg 4, Pleasanton, CA 94588, USA
> Tel: +1 (925) 520 4422 or +1 (650) 623 2888;
> mailto:david.burdett@commerceone.com; Web: http://www.commerceone.com

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC