My take on this is that such archetypes need to be fairly inclusive and stable, using templates to constrain.
There is no guarantee that versions will remain compatible. As revisions are only extensions, this should work. Versioning (breaking change for existing data , needs to be limited to when there is real benefit as software will need to change. Cheers Sam Sent from my Windows Phone ________________________________ From: jacky.lauchunkin at gmail.com<mailto:[email protected]> Sent: ?22/?09/?2014 10:47 AM To: openehr-technical<mailto:openehr-technical at lists.openehr.org> Subject: Problem with version and specialisation Dear All, I met a problem when using specialisation and version. For example, I have two archetypes, openEHR-DEMOGRAPHIC-PERSON.patient.v1 and openEHR-DEMOGRAPHIC-PERSON.patient-specialise.v1. Archetype openEHR-DEMOGRAPHIC-PERSON.patient-specialise.v1 is specialised from openEHR-DEMOGRAPHIC-PERSON.patient.v1. Let's say the archetype openEHR-DEMOGRAPHIC-PERSON.patient-specialise.v1 have modified for several times and its current version is v3. And now openEHR-DEMOGRAPHIC-PERSON.patient.v1 has upgraded to version 2, openEHR-DEMOGRAPHIC-PERSON.patient.v2. Can I simply upgrade openEHR-DEMOGRAPHIC-PERSON.patient-specialise.v3 to version 4 so that I can change its specilisation to openEHR-DEMOGRAPHIC-PERSON.patient.v2? ________________________________ Best wishes! Jacky.Lau 2014-09-19 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20140922/b17a8193/attachment.html>
