Peter, Elkin, Peter L., M.D. wrote: > > Also, I would recommend taking a > look at the ebXML registry which is > a federated Open Source registry which > is currently available. Also, Sun is > implementing OWL support within the > registry (which may be handy for users > interested in direct reasoning from > Archetypes).
Sorry for not responding to this sooner. In all honesty, I didn't 'get' your point at first. Heck, I may still not be getting it ;-) But having given it some thought and *trying* to understand it, I do have some thoughts and questions. Before I get started, though, let me ask for clarification on a couple of things. As I read the ebXML.org site, they do not have a registry currently available. What they have available is a *specification* for a registry. The way I read the site, they expect others to actually implement registries. If I've missed something, could you point me to it? Were you citing the ebXML registry as a mechanism we should look at using? If so, in what way? Again as I read the site, what the ebXML registry registers is companies and information about them that allows other companies to identify them for the purpose of doing business with them electronically. Sellers publish their "Collaboration Protocol Profile or CPP as defined by [ebCPP] to the Registry. The CPP describes the seller, the role it plays, the services it offers and the technical details on how those services may be accessed. ... The buyer browses the Registry ... to discover a suitable seller. For example the buyer may look for all parties that are in the Automotive Industry, play a seller role, support the RosettaNet PIP3A4 [Purchase Order business protocol] process and sell Car Stereos. The buyer discovers the seller's CPP and decides to engage in a partnership with the seller." (p. 16, "OASIS/ebXML Registry Services Specification v2.5) The definition and registry of the *protocols* (think Archetypes) used by the companies registered within an ebXML registry is a seperate issue, handled by organizations like RosettaNet. It seems to me that the next issue we'll face (perhaps very soon) WRT Archetypes is more like the one tackled by RosettaNet than the one tackled by ebXML. The ebXML-type provider registry looks like an issue that won't come up until after the first one is resolved. I'd apprecite hearing your thoughts. Best regards, Bill - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
