RE: [ebxml-msg] Messaging Spec v1.092

From
System
Date
2002-01-07T11:42:00+00:00
ID
Thread
RE: [ebxml-msg] Messaging Spec v1.092
MHonArc v2.5.2 -->

ebxml-msg message

[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [Elist Home]

Subject: RE: [ebxml-msg] Messaging Spec v1.092

From: "Burdett, David" <>

To: 'Martin W Sachs' <>,David Fischer <>

Date: Mon, 07 Jan 2002 08:39:38 -0800

Title: RE: [ebxml-msg] Messaging Spec v1.092

Marty

You said ...

>>>MWS:  See my first comment above.  You cannot avoid the runtime database unless you think that you can legislate a single software and middleware configuration that everyone is required to use on pain of ...<<<

I agree you cannot legislate, but you should be able to define default parameters for sending a message reliably, for example, which does not require prior negotiation.

What we need to do, is make a decision early-on in the development of the next spec on whether we are going to develop:
1. A Negotiation Protocol, which leads to the agreement of a CPA, which then results in the exchange of messages according to the ebMS spec (which is what I think you are suggesting Marty), or

2. A lighter weight spec which allows messages to be sent without prior negotiation but which can reference a negotiated agreement if it exists (which is what I am suggesting).

Currently I think there are some who think the first approach is overkill and won't be used by SMEs or the Web Services community, and some who think the second approach won't work. Either a way decision on the way forward has to be made.

David