We did get mention in the minutes from the OASIS ebXML CPPA Technical Committee meeting (June 3, 4, 5, 2002), at http://lists.oasis-open.org/archives/ebxml-cppa/200206/doc00001.doc.
Note that their "New requirements" include support for "legacy" telecommunication protocols, which will surely please some of our participants: HealthCare - William Kammerer .. Support for legacy connectivity (modem-based (XMODEM, Kermit), Bisync). Need ability to specify phone numbers, scripts, modem settings, etc. .. Moberg - we need to investigate how we can extend DeliveryChannel to do this. .. Looking for ebReg/Rep POC. Want to search based on any commonly used corporate identifiers (DUNS, NPID, .). The blurb about "ebReg/Rep POC" simply refers to a "Proof of Concept" for the Healthcare Registry that we hope to do with NIST; see http://www.mail-archive.com/routing%40wedi.org/msg00655.html. Dick Brooks and I joined the OASIS CPP/A group on a teleconference call last Tuesday to apprise them of our status. I think we're on the same wavelength, in that we agree much of our EDI partner profile stuff will be in an XML document of our own schema design, XLINK'ed from the main CPP. Our stuff will eventually turn into the OASIS ebXML "legacy" EDI CPP extension schema. I may have forgotten to confirm with Dale Moberg, Chair of the OASIS CPP/A Technical Committee, but I believe that WEDI/SNIP is the first group in the world attempting to make ebXML work with "legacy" EDI. William J. Kammerer Novannet, LLC. Columbus, US-OH 43221-3859 +1 (614) 487-0320
