Re: ebXML TR&P Interoperabiltiy event

[Nicholas Kassem <Nick.Kassem@eng.sun.com>]

At 08:28 AM 6/20/2000 -0400, mwsachs@us.ibm.com wrote:
>Any need to share code or hardware in the real world will defeat the whole
>purpose of ebXML.  One of the most important requirements on what we in IBM
>Research are doing with tpaML and its runtime is that there must be no
>requirement for a pair of partners to use the same application code,
>run-time middleware, or hardware.

Agreed.


>If anyone is really worried about IP in the business process area, build
>the demo based on the business process layer of a public-domain protocol
>such as OBI.  It wouldn't be OBI because it would have ebXML messaging
>instead of the current OBI messaging but it should avoid any IP hassles at
>the business process layer.

We picked the OTA work in an earlier prototype to demonstrate some higher 
level notions (transport neutrality, role of ebXML TR&P, ebXML 
value-proposition etc. etc.) I think we are now passed that point but I 
think there are still some engineering level details that need to be worked 
out. Hence my earlier post / invitation.

Nick


=======================================================================
= This is ebxml-transport, the general mailing list for the ebXML     =
= Transport project team. The owner of this list is                   =
= owner-ebxml-transport@oasis-open.org                                =
=                                                                     =
= To unsubscribe, send mail to majordomo@lists.oasis-open.org with    =
= the following in the body of the message:                           =
=      unsubscribe ebxml-transport                                    =
= If you are subscribed using a different email address, put the      =
= address you subscribed with at the end of the line; e.g.            =
=      unsubscribe ebxml-transport myname@company.com                 =
=======================================================================