RE: Trading Partner Logical Identification based on EDIFACT or X12qualifiers

[David RR Webber <Gnosis_@compuserve.com>]

Message text written by INTERNET:dick@8760.com
> 
Marty

I'm not debating the point that a repository interface CAN be useful (in
fact I believe it could be useful in certain cases). My position is that a
programmatic API to a repository SHOULD NOT BE MANDATORY within ebXML.


Dick Brooks<

>>>>>>>>>>>>>>>>>>>>>>

Dick,

We are headed into a religious war here.

Let's see if we can agree on some sensible next steps.

1) TRP to review items in interchange header where repository API reference
     could potentially add value / resolve semantic definitions dynamically
to
      allow TP's to define their own interchange reference tables / values.

2)  TRP to review with TPA authentication mechanisms and tracking
      mechanisms to ensure reliable and secure interchanges
      (I did not say 100% secure!).

3)  TRP to review with BP and RegRep issue of exposing Business 
      Process matrix that shows what BP and associated transactions a
      valid interchange between TP's can contain.

4)  TRP to review with TPA how a profile can e established that will
      allow plug-n-play automatic configuration of TP linkages between
      a new TP and / or TP system.

5)  Look at TRP POC designs that could validate some or all of above.

6) RegRep to provide feedback on both lightweight and 
     tightly coupled mechanisms for Repository interfacing with 
     XML based API.  (As part of the RegRep POC for Tokyo this is
     already implied BTW).

Once all of above is better understood then we can make a real
determination of what it means to "require use of a repository" as
opposed to "mandate use of" as opposed to seeing just what
is involved and the mechanisms, and how these support both
ebXML Requirements, and Technical Architecture, which of 
course is the prime directive here.

Thanks, DW.