[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: minutes 14-Dec-2000 TR&P con-call
Unfortunately, I was not on the call for the first issue. I can understand a wish to avoid point-to-multipoint distribution of an ebXML payload as a complicating issue. However, what I was proposing in that comment was not such a distribution model. I was focussing on allowing the originator to use multiple domains to identify the recipient. This may be particularly important in multi-hop cases, where the originator does not know how to identify the end recipient to all intermediate MSHs. Rather than add yet another requirement to the CPA, why not allow the originator to identify the recipient in whatever ways they have available. Each MSH could use its "favourite" domain from the provided list to correctly forward the payload (either to the application context or another MSH). Can this issue be reopened? thanx, doug -----Original Message----- From: christopher ferris [mailto:chris.ferris@east.sun.com] Sent: December 14, 2000 09:11 To: ebxml-transport@lists.ebxml.org Subject: minutes 14-Dec-2000 TR&P con-call Attendees Dick Brooks David Burdett Andrew Eisenberg Doug Bunting Chris Ferris Ralph Berwanger Prasad Yendluri Robert Adams Jerry ... AIAG (sorry, my system crashed with the original minutes...) Dale Moberg Maryann Hondo Rik Drummond Ian Jones (for less than a minute;-) Minutes Issue 10 - Multiple PartyId Detail - 7.9.1 - Recommend changing phrase PartyID element to 'one or more PartyID elements'. discussion. unanimous opposition. There will be likely ramifications with CPA which cannot be addressed. There are other ways of achieving the same effect (such as mail aliases). Vote: not to accept </ SNIP>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC