Re: Marty, what do you see the variables being that ms will use...

[Martin W Sachs/Watson/IBM <mwsachs@us.ibm.com>]

Gordon,

You are asking an excellent question.  It appears that the layers below the
messaging service are not in ebXML's charter at the moment. On the hand,
what's below the messaging service is a set of existing standards.  On the
other hand, there is a serious interoperability issue if the
transport-layer things are not specified somewhere.

One answer (maybe actually the right one) is that if the ebXML TPA includes
all of the tags (or their equivalent) that tpaML has in the transport and
business protocol sections, and all of the text (or equivalent) that is
around them in tpaML, then interoperability is assured.  It will be
essential that ebXML accept the transport-level tags even though it isn't
doing anything else at the transport level.


Regards,
Marty


*************************************************************************************

Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287;  IBM tie line 863-7287
Notes address:  Martin W Sachs/Watson/IBM
Internet address:  mwsachs @ us.ibm.com
*************************************************************************************



"Gordon van Huizen" <gvanhuiz@progress.com> on 08/31/2000 10:42:37 AM

Please respond to gvh@progress.com

To:   Martin W Sachs/Watson/IBM@IBMUS
cc:
Subject:  Re: Marty, what do you see the variables being that ms will
      use...



Marty,


Martin W Sachs/Watson/IBM wrote:

> In my mind, what we mean when we have used the term "application
services"
> is a set of functions that is logically part of the application layer but
> for which there are great benefits in performing these services in the
> run-time middleware.  To recap, the IBM Research prototype run-time (BPF)
> includes these services among others:
>
>    Sequencing Rules
>    Business document generation and parsing
>    Security
>    Correlation of conversations
>    Logging
>    Recovery

The above is a wonderfully crisp statement that adds a lot of clarity
for implementors. Will something like this be captured in some ebXML
spec?

-gvh-