Thomas, I see that some attributes for some clases are not present in archetypes. For examples language in the Entry class. It is clear to me that the restriction is allready defined by the infariants of that class, but I wonder where do you check or validate that field.
Do you wait until you build the RM object? Another question about this, how do you refer to this attributes in templates? this question arised because there are no archetype paths that lead you to this attributes. Another thing, I believe it is a spec error, the EVENT_CONTEXT class from the COMPOSITION package does not inherit from LOCATABLE. Is that correct? thank you Quoting Thomas Beale <Thomas.Beale at oceaninformatics.biz>: > Rodrigo Filgueira wrote: >> I've been going round in circles about this question all weekend, >> and have two ideas. >> >> 1. It's basic and most important use is to provide reference to >> check the correctness of the arquetypes. >> 2. It is needed for some types of persistence design >> >> Why am I asking myself this? because once assertions are >> implemented, all that may be needed for validating real data may be >> included in archetypes, can't it >> >> am I missing something? > yes....the data. The data are all instances of the reference model, > nothing else. No matter how many openEHR deployments, no matter how > many archetypes or templates - all the data are instances of the one > schema - the reference model. > > - thomas ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
