RE: confusion on where to discuss trading partners

[Scott Hinkelman/Austin/IBM <srh@us.ibm.com>]

Int the use case, the reason for search could be to discover who supports a
specific business process. If so, the

the download could consist of the info for a specific support business
process, which would be

the SupportedBusinessProcess in the following picture.......

(See attached file: TPinvariants.gif)

Scott Hinkelman
Senior Software Engineer, IBM Austin
Emerging Technologies, SWG
512-823-8097 (TL 793-8097) (Cell: 512-940-0519)
srh@us.ibm.com, Fax: 512-838-1074



David Burdett <david.burdett@commerceone.com> on 08/31/2000 04:06:00 PM

To:   Martin W Sachs/Watson/IBM@IBMUS, ebxml-transport@lists.ebxml.org
cc:
Subject:  RE: confusion on where to discuss trading partners



A few more comments inline

<SNIP/>



PROBLEM AREAS AND SUGGESTED SOLUTIONS ...
-----------------------------------------
PROBLEM 1
There is a use case where, the information one party holds about another is
sent in an ebXML message (see the 2nd use case in the attachment to my
email: Dated: Tue 08/22/2000 2:36 PM; Subject: Trading Partner/Party
Discovery/Agreement Use Cases). This means that there is a conflice between
1a) and 2a).
SUGGESTED SOLUTION
1. TRP amends the ebXML Message Header so that there are place(s) in the
document structure to either:
  a) reference a previously agreed the Trading Partner Agreement,

MWS:  In my mind, this is the existing TPAInfo and its subelements
  b) hold an actual Trading Partner Profile

MWS:  Wouldn't this just be payload for an ebXML message?

DB: No, as some of the information, particularly the ebXML Messaging
Service
stuff would need to be visible to the ebXML Messaging Service Layer. So I
would put it in an additional optional "principal header" under the top
level of the ebXML Header Document.

<SNIP/>

Compuserve GIF