There is indeed "versioning" in the CPP - that for the CPP schema itself (i.e., the version of the OASIS CPP specification), and for other related OASIS specifications. But I'm not sure whether there's also a capability to "version" the "instance" of the CPP, though. In any event, it's a real requirement for us to have some mechanism to tell whether the CPP electronic partner profile has changed at all.
I don't envy you reading all that OASIS stuff! I might warn you, though: when you read up on the ebXML CPP, it looks big, ugly and complex - and most of that stuff is irrelevant to traditional EDI. Actually we might end up using only two or three things from the existing CPP schema (e.g., Delivery Channel, Certificate Management, Party Definition), and be off on our own devising a (general-purpose) legacy EDI extension. I would suggest putting aside the OASIS ebXML CPP specification. I think it will only confuse us for now. We really need to build our own requirements based on *our* needs - including everything we'd want to see in a partner profile if we were starting from scratch. It can be organized any way (UML diagram, spreadsheet, Access Database) that floats your boat. Then we can take that list and give it to the OASIS CPP/A group and let them help us to retrofit the existing CPP to allow for "legacy" EDI extensions. We might have to "educate" the OASIS CPP/A group on "legacy" EDI and Healthcare Transactions so they see just how this old message-centric stuff works! 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 ----- Original Message ----- From: "Dave Minch" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, 05 June, 2002 10:45 PM Subject: RE: registry and repository- version control The CPP spec does allow for versioning. I've used the trading partner profile from our Sybase "paperfree" application as a model for TP information, and have added several elements beyond that. Rachel is correct in that most EDI translators appear to have a more or less sophisticated trading partner profile management function. Dave Minch T&CS Project Manager John Muir / Mt. Diablo Health System Walnut Creek, CA (925) 941-2240
