[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: ebXML TR&P Interoperabiltiy event
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. 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. 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 ************************************************************************************* Christopher Ferris <chris.ferris@east.sun.com>@lists.oasis-open.org on 06/20/2000 06:41:01 AM Sent by: owner-ebxml-transport@lists.oasis-open.org To: Nicholas Kassem <Nick.Kassem@eng.sun.com> cc: ebXML Transport <ebXML-Transport@lists.oasis-open.org> Subject: Re: ebXML TR&P Interoperabiltiy event Nick, Yes, I think that this would be a good idea. However, it would seem to me that it would be necessary to share an example business process to prove interoperability, no? e.g. the same set of message types. Either that, or some form of generic message handler which logged the messages and returned (or triggered) some reasonable follow on message would be needed to demonstrate the ability to map a specific type of message from a specific partner to a specific handler, etc. The business process folk will want to see that as evidence that all is rosy. Cheers, Chris Nicholas Kassem wrote: > > Dear Transporters, > > I am thinking through what it would take to establish a regular > interoperability event demonstrating TR&P functionality. Given that we have > an upcoming meeting in August, it would be good if we had an engineering > level event where we could work through implementation issues, problems > etc. This is not going to be a marketing event though we may choose (if the > participants elect to do so) publicize our findings. My thinking is that, > in this way, we will not discourage immature implementations from coming > forward. > > The goal will be to shake-out bugs in early implementations and improve the > specifications. > > My expectation is that there will be no need to share code, or hardware to > accomplish this. So participants who have concerns about IP should expect > to be able to share a mail-server, a private network and that's about it. > Hosting of Web servers, development tools etc. etc. will be a private > matter and implementation specific. > > If you feel that wire-level interoperability is an important dimension of > the ebXML TR&P work - please contact me directly. Thanks in advance. > > Regards, > Nick > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Nicholas Kassem > Java Software, Sun Microsystems Inc., > nickk@eng.sun.com > 408-863-3535 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > ======================================================================= > = 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 = > ======================================================================= -- _/_/_/_/ _/ _/ _/ _/ Christopher Ferris - Enterprise Architect _/ _/ _/ _/_/ _/ Phone: 781-442-3063 or x23063 _/_/_/_/ _/ _/ _/ _/ _/ Email: chris.ferris@East.Sun.COM _/ _/ _/ _/ _/_/ Sun Microsystems, Mailstop: UBUR03-313 _/_/_/_/ _/_/_/ _/ _/ 1 Network Drive Burlington, MA 01803-0903 ======================================================================= = 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 = =======================================================================
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC