Re: ebXML TR&P Interoperabiltiy event

[Christopher Ferris <chris.ferris@east.sun.com>]

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