Thomas Beale wrote: >> >> > This is an important point. > > I have to admit that I thought we had an rm_version attribute on the > ARCHETYPE class (see > http://svn.openehr.org/specification/TRUNK/publishing/architecture/am/aom.pdf), > > but I see that we don't. If we did, it would mean that the archetype > could be checked for compatibility with the reference model. > > However, clearly if we wanted an > openEHR-EHR-OBSERVATION.cardiology_exam archetype for Release-1.0 and > for Release-2.0, we would have a problem. Starting from Release 1.0 we > have rules about what can change, and one of them is that changes to > the reference model that are not error corrections can only occur in a > new major release (i.e. Release-2.0, rather than say Release 1.0.1 or > 1.1). I should have said: changes to the reference model that are not error corrections or are not agreed by the whole community can only occur in a new major release. I.e., error corrections can be made; so can changes that everyone agrees to - usually these will be small enhancements that are so obviously sensible that everyone wants them.
- thomas
