Re: Technical Architecture TR&P section - REISSUE

[mwsachs@us.ibm.com]

Re-sending because of delivery failure

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

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
*************************************************************************************
---------------------- Forwarded by Martin W Sachs/Watson/IBM on 08/25/2000
01:07 PM ---------------------------

Martin W Sachs
08/24/2000 12:40 AM

To:   dick@8760.com
cc:   Ebxml <ebxml-transport@lists.ebxml.org>
From: Martin W Sachs/Watson/IBM@IBMUS
Subject:  Re: Technical Architecture TR&P section - REISSUE  (Document
      link: Martin W. Sachs)

Dick,

TA Section 3 looks good.  I am not speechless, however:

Section 3.1, Messaging Service Description

Line 5:  Please say that the abstract interface is between the message
service and the application, with some mention of BP here.  In the abstract
specifications sense, that interface is really between the messaging
service spec and the BP spec.

Line 33: Figure on page 3:  Should add a box at the top showing either
application or BP or both

Section 3.3  Messaging  Layer Functions

Line 70: Please add a new bullet after the first bullet:  Routing of
messages to the destination based on TPAId, ConversationId, and Action.

Line  90:  At-most-once delivery should be a sub-bullet under Reliable
Delivery.  It is one of at least two possibilities.

Line 93:  Please put in a few words on the meaning of "fire and forget".
IP could be viewed as a "fire and forget" since it is unacknowledged and
totally unreliable.  I believe that your intent is a mode which is so
reliable that it has no need for ACKs.

Line 124 (figure on page 2):  Please add message routing and application
support services to this figure.

Line 175, ebXML Message Header Structure:  Is this much detail needed in
the technical architecture document?  It is repeating details that are in
the Messaging Service document.

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
*************************************************************************************



Dick Brooks <dick@8760.com> on 08/17/2000 03:49:25 PM

Please respond to dick@8760.com

To:   Ebxml <ebxml-transport@lists.ebxml.org>
cc:
Subject:  Technical Architecture TR&P section - REISSUE



Folks,

I received a request to add line numbers to the TR&P portion of the TA
draft, so here is an updated version.

I'm providing this information to the TR&P group for two reasons:

1. To ensure that TR&P & TA are in agreement with regard to the scope and
purpose of TR&P's part of the architecture puzzle

2. Give you an opportunity to comment on the TR&P portion of TA before it
goes out for review by the entire ebXML community.

Dick Brooks
Group 8760
110 12th Street North
Birmingham, AL 35203
dick@8760.com
205-250-8053
Fax: 205-250-8057
http://www.8760.com/

InsideAgent - Empowering e-commerce solutions