[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: ebXML PoC -- feedback to working groups
Philippe, I assume the custom CPA proposal/acceptance protocol was just to fill a hole in the POC flow for Tokyo. IMHO, a general purpose Event Notification mechanism that is based on a general puprose publish/subscribe mechanism is a better alternative. Note that I made a proposal for such a service which articulates the CPA proposal/acceptance scenario as an example. The proposal can be found at: http://lists.ebxml.org/archives/ebxml-regrep/200010/msg00033.html See section 1.3 for CPA proposal/acceptance protocol related example. -- Regards, Farrukh Kenji Nagahashi wrote: > <snip> > > [TP,TRP] Bootstrapping problem in CPA proposal have to be resolved. POC > assumed the CPA proposal/acceptance is a well-known service and exchanged > message between implicitly agreed interfaces. In reality, Its transport > information have to be either predescribed by ebXML specification or found > in the to-be-partner's CPP obtained from registry. Later case requires the > means (and its spec) with which CPA accepter can find which CPP to use, ex. > attatching CPP (or its URL) with the proposed CPA. -- Regards, Farrukh
begin:vcard n:Najmi;Farrukh tel;fax:781-442-1610 tel;work:781-442-0703 x-mozilla-html:TRUE url:www.sun.com org:Sun Microsystems;Java Software adr:;;1 Network Drive, MS BUR02-302;Burlington;MA;01803-0902;USA version:2.1 email;internet:najmi@east.sun.com fn:Farrukh S. Najmi end:vcard
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC