Re: Trading Partner Logical Identification based on EDIFACT orX12qualifiers

[mwsachs@us.ibm.com]

Gordon,

The repository should contain the TPPs, choreographies, etc,  At least for
long term relationships, this information should be combined into a TPA
between the two parties, which can also be kept in the repository.  The
information would be cached locally when the TPA is installed by the two
parties.  At installation time, the installation software could
authenticate the parties and otherwise validate the TPA information but
there should be no reason to incur the overhead of a query to the
repository on every message.

Note that authentication and nonrepudiation can be applied to the messages
locally, which give some protection against something changing after the
TPA is installed.

We might want to include the repository ID in the TPA so the run-time will
know where to go when it has to go there.

Regards,
Marty

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

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/16/2000 08:48:41 AM

Please respond to gvh@progress.com

To:   dick@8760.com
cc:   David RR Webber <Gnosis_@compuserve.com>, "ebXML Transport (E-mail)"
      <ebXML-Transport@lists.ebxml.org>, David Burdett
      <david.burdett@commerceone.com>
Subject:  Re: Trading Partner Logical Identification based on EDIFACT or
      X12qualifiers



There must be something I'm missing here. Doesn't the repository contain
the TPP for the party plus message choreographies it finds acceptable
(ignoring for a second the factoring of thr two)? If the repository is
optional, where does an ebXML messaging service obtain this vital
ebXML-compliant info? Or does an ebXML message need to understand
several other flavors of this?

If that's the case, and we're not careful to establish over-the-wire
interoperability between ebXML messaging service implementations, remind
me again why we're bothering to do ebXML?

Or are you suggesting that Amazon doesn't need to be ebXML-compliant,
but ebXML providers need to interoperate with whatever they have? That
seems way outside the scope of ebXML, and into the land of vendor
support for multiple eBusiness protocols/frameworks.

-gvh-

Dick Brooks wrote:
>
> David,
>
> We must be practical here, do you really expect Amazon to query a ebXML
> repository for information, I don't think this is practical. The
repository
> MUST be an OPTIONAL part of an ebXML transaction exchange, do we agree? I
> really don't expect Amazon or any other interactive site to change their
> existing systems/databases/repositories to adhere to ebXML's regrep API.
>
> Regarding your question:
> > Have Microsoft said anything about, or have
> > they been
> > asked about, supporting ebXML interchange headers in BizTalk BTW?
> >
> > I'm sure I'll get a chance to ask them at XMLWorld in Boston next
> > month....
>
> I've had numerous conversations with Satish Thatte, Microsoft's BizTalk
> Framework 2 architect about the possible ways BizTalk and ebXML might
work
> together. I expect to have more news on this front after the W3C XML
> Protocols activity begins.
>
> 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
>
> >
> > Thanks, DW.