Fortunately, we have the capable Dick Brooks looking into the matter of using the ebXML CPP. He also tells me there are compelling reasons to go with ebXML Messaging Services (which as of this date is the only packaging technique supported by a CPP), not the least of which are (1) the cost of client side software is very reasonable (maybe even *free*), and (2) It will include automated trading partner setup features! See http://www.oasis-open.org/committees/ebxml-cppa/ and http://www.oasis-open.org/committees/ebxml-msg/.
The CPP people may not want to hear requests for supporting non-Internet transport protocols or non-ebXML packaging techniques (e.g., EDIINT) - I've kind of lost track of what's happening over there in OASIS, ever since the onset of the "SHALL" - "MAY" battles. If they aren't amenable to expanding the CPP, we just may have to go "off on another tangent and re-create something else" - something more like IBM's tpaML which was the progenitor of ebXML CPP - see http://www.ibm.com/developerworks/library/tpaml.html. I've "volunteered" Tim Collins to look into discovering the tons of permutations "on a multitude of media, protocols, etc...", - including the ugly stuff like modem settings and initialization strings, blah, blah, blah. All that will have to be mechanically represented in some type of XML file (or the 838) - or as an extension of the CPP DeliveryChannel. Speaking of the 838, we also anxiously await the outcome of Dave Minch's investigation into the X12 Trading Partner Profile transaction set, and in a few weeks he will let us know whether it's worth pursuing. William J. Kammerer Novannet, LLC. +1 (614) 487-0320 ----- Original Message ----- From: "Rachel Foerster" <[EMAIL PROTECTED]> To: "'WEDi/SNIP ID & Routing'" <[EMAIL PROTECTED]> Sent: Friday, 15 February, 2002 11:29 AM Subject: RE: UN/CEFACT's Modeling Methodology (UMM) William, <snip> On another topic....if the CPP/CPA specification does not currently support the requirements of this effort, then the logical next step would be for us to take those new requirements to the OASIS Technical Committee, headed up by Marty Sachs of IBM, responsible for the CPP/CPA specification for consideration and addition to the CPP/CPA -- rather than going off on another tangent and re-create something else. This process is not different than the process X12 Committee operates under for requesting modifications to existing standards through a data maintenance request or a new standard via a project proposal. </snip> Rachel Foerster Rachel Foerster & Associates, Ltd. Phone: 847-872-8070
