On 07/11/2014 12:57, David Moner wrote: > Hello Thomas and thank you very much for pushing this. As we talked > early this year, I think this interim or transitory versions are the > way to go before 2.0 is complete. > Personally, and regarding EN ISO 13606, I also think it is the best > option for the current renewal process to adopt only small changes > that solve limitations or problems of 1.4, and leave the adoption of > 2.0 for the next renewal process, once 2.0 has been fully tested > through implementations and supported by the industry.
Right - I am thinking only that the '1.5' changes would go into the current 13606 renewal. We need to work on this together to massage it into a list that is doable - what you see now on that page is just my first go. > > Regarding the contents of each version, we have to study it in detail, > but probably the philosophy could be: > - 1.5: changes that only affect the parser and maybe need adding some > support classes to the AOM, but that can afterwards be ignored by > systems (e.g. annotations, generated marker, maybe the namespace, ...) > - 1.6: changes that would require that the new edited archetypes have > to be "exported" to 1.4 format to work normally (e.g. change domain > types to tuples, absence of existence and cardinality or the > differential specialization) > - 1.7: changes that would affect how systems use the archetypes (e.g. > unification with templates) I think these are good ways to look at it. I Iike your 1.6 criterion in particular. I think 1.5 will probably need to support the extended ids though, because the problem of 'model-clash' is becoming serious. But - those new ids are in a sense optional, i.e. a system that doesn't care about them due to be self-contained (which may well be true for some 13606 systems, and maybe some of the openEHR ones as well) won't feel any impact. > > Maybe the 1.7 directly corresponds to 2.0... my thinking as well, but I'm not sure yet. - thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20141107/ddfdad0e/attachment.html>
