[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: ebXML PoC: allocation of partners to tasks/roles
All, Based on the matrix so far (other participants may still join -- I also heard from Netfish, e.g.), I've tried to do a fair allocation of participants to tasks/roles. I believe it's an NP-complete problem :), given all the combinations of roles, reliability, registry, etc., but I've attempted to come up with a good solution anyway. The intent of this allocation is for the partners to agree on scenarios for the PoC. Once we settle on payloads/processes, likely to include GCI, we can attach those to the exchanges as listed below. We'll still also need to assign transport protocols (HTTP, SMTP) to the this allocation. I've used single characters to denote the partners (except fo SU=Sun and ST=Sterling): A = Ajuba, C=Cisco,E=Extol,F=Fujitsu/Savvion,I=IPNet,T=TIE,V=Viquity,W=webMethods, X=XMLG "buyer" hub "seller" reliable messaging registry provider ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- --- E I I C F V SU ST E W F yes SU I V SU X C W A SU V C T T E W V F A T W C V A T I A T none W yes E V F yes X S none F ST This is of course still very flexible. -Philippe _______________________________ Philippe De Smedt Architect Viquity Corporation (www.viquity.com) 1161 N. Fair Oaks Avenue Sunnyvale, CA 94089-2102 (408) 548-9722 (408) 747-5586 (fax) pdesmedt@viquity.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC