Thanks. It will be my reading material on the train ride home. Oh, and the example of groups was just what came to mind. I know it's not very medical, but it seemed (to me, at least) to clarify what it was that I had in mind. In general, I find OpenEHR documentation frustrating, and I rather suspect it is due to a "culture gap" (on my part) more than anything else. === Gregory Woodhouse "Mathematics is the science of patterns." --Lynn Arthur Steen, 1988
----- Original Message ---- From: Thomas Beale <[email protected]> To: For openEHR technical discussions <openehr-technical at openehr.org> Sent: Tuesday, October 17, 2006 2:16:52 PM Subject: Re: Updated Architectural overview Greg, if you would like some mathematics to look at, I suggest Michael Kifer's F-logic paper - ftp://ftp.cs.sunysb.edu/pub/TechReports/kifer/flogic.pdf An archetype is a synthesis of an F-logic query (formally: a constraint on a complex structure) and terminology. The main difference practically speaking is that: a) the reference models is expressed as classes, and is directly in the software b) archetypes are expressed as constraints and are not in the software. - thomas beale _______________________________________________ openEHR-technical mailing list openEHR-technical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
