[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [ebxml-iic] Simple trading partner configuration for ebMS
We are finding that the cpp is tooo complex to implement just for the msh. This seems like it would be a start, especially if it is a near or proper subset of the whole cpp. rik -----Original Message----- From: Dale Moberg [mailto:dmoberg@cyclonecommerce.com] Sent: Friday, August 23, 2002 8:39 PM To: Matthew MacKenzie; ebxml-iic@lists.oasis-open.org Cc: Cppalist (E-mail) Subject: RE: [ebxml-iic] Simple trading partner configuration for ebMS Hi Matt, I skimmed the schema you provided. I guess it is one of the "70/30" optimization gambits. Anders from OpenEbXML has proposed a similar lightweight schema within the JSR 157 group. As such, I think it might be worthwhile sending to the ebxml CPPA TC for consideration. It is especially interesting in that it might promote adoption of profile/protocol-binding technologies, because of its minimalisticYetEssential view of configuring the b2b side of the MSH. So the advantage I see is that it is geared for the ebXML MSH (it may ignore some of the PKI support the security risk document recommended--I would think about adding that in, at least optionally). A political problem is that it more or less dispenses with the BPSS hooks (and so becomes choreography/flow/orchestration/process independent). That may be feasible via the modularity doctrine, however. Would you be willing to cross post the example and schema to ebXML-CPPA? Maybe a few words in support of a CPA-lite could accompany the post? Thanks, Dale Moberg -----Original Message----- From: Matthew MacKenzie [mailto:matt@xmlglobal.com] Sent: Friday, August 23, 2002 4:07 PM To: ebxml-iic@lists.oasis-open.org Subject: [ebxml-iic] Simple trading partner configuration for ebMS Team, As we discussed during the F2F today, I've put together a simple CPA replacement that has the bare minimum configuration information for 2 parties. These could be what we use for specifying MSH configuration for conformance and interoperability. It also could form a CPA replacement, which is designed over time to meet vendor needs as per discussions we had today (Myself, Hatem@IPNet, Jeff@Cyclone). If you're interested in this development for use beyond testing, please help me out by supplying feedback -- is there anything missing that a good MSH needs out of a TPA? Regards, Matt ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
Attachment:
Rik Drummond (rvd2@drummondgroup.com).vcf
Description: text/vcard
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC