RE: ebXML TR&P Interoperabiltiy event

[Shumpei NAKAGAKI <nakagaki@mxb.mesh.ne.jp>]

Marc,

I agree with you, because I 'm familier with RNIF and FIF.

Shumpei

At 12:57 00/06/22 -0400, Marc Breissinger wrote:
>I know we picked OTA in an earlier round, but might I suggest we utilize PIP
>3A4 from RosettaNet instead.  The process interaction definition is much
>more complete which will save confusion and the vendors who might implement
>in this event are already intimately familiar with it.  Further, it would
>show how easily ebXML TRP could replace RNIF in the future.
>
>marc
>
>==========================================================================
>Marc Breissinger                                   voice (W): 703-460-2504
>Director, Product Strategy - webMethods, Inc.      voice (C): 703-989-7689
>Email:  marcb@webmethods.com                               We're hiring!!!
>Email2: breissim@earthlink.net              URL: http://www.webmethods.com
>==========================================================================
>
>
> > -----Original Message-----
> > From: owner-ebxml-transport@lists.oasis-open.org
> > [mailto:owner-ebxml-transport@lists.oasis-open.org]On Behalf Of Nicholas
> > Kassem
> > Sent: Tuesday, June 20, 2000 3:41 PM
> > To: mwsachs@us.ibm.com
> > Cc: ebXML Transport
> > Subject: Re: ebXML TR&P Interoperabiltiy event
> >
> >
> > 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                 =
> > =======================================================================
>
>
>=======================================================================
>= 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                 =
>=======================================================================

**************************************
   Shumpei NAKAGAKI(NEC Corporation )
   E-Mail:s-nakagaki@bp.jp.nec.com
         :nakagaki@mxb.mesh.ne.jp
  (Phone:+81 3 3798-6082)
  (Fax:  +81 3 3798-6077)
**************************************

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