Dear Graham, Is multiple inheritance in the use case you presented, the only solution? I expect it is not. So why use it. When 'data integrity' is a recurring issue in several archetypes, re- use by inclusion of a 'data integrity' archetype in an other archetypes is a better other solution.
I'm not closely following HL7 Templates. Are the HL7 Templates a separate and diverging piece of work when compared to EN13606-2 or harmonising? Do both the HL7 Templates and CEN Archetypes share identical requiremenets? Gerard -- <private> -- Gerard Freriks, MD Huigsloterdijk 378 2158 LR Buitenkaag The Netherlands T: +31 252544896 M: +31 620347088 E: gfrer at luna.nl Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov 1755 On Oct 16, 2007, at 11:44 PM, Grahame Grieve wrote: > The use case is relatively simple in concept - allowing multiple > inheritance would allow me to "cross-cut" concerns. I could write > an archetype that only dealt a narrow aspect of an information > structure, such as data integrity issues, and then use it across > multiple archetypes, letting them focus on the big picture, not > the minutiae of data integrity, which is mostly overlooked but > ubiquitiously present. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20071017/d5d147e3/attachment.html>
