On 03/10/2014 19:54, Bert Verhees wrote: > > > The best solution is to decouple the version from the archetypeId. And > also decouple the file and filename from the archetypeId. > People are responsible for overwriting their documents in Word, or > save a backup, if that is their choice. The same can go for the > archetype-editors.
All - please read my other post where I included some of the AOM spec, showing that the 'identifier' is actually multiple data parts, and the string 'ids' are computed. Something called an 'interface_id' is one of those things; that's just the multi-axial id with only the major version number, e.g. org.openehr::openEHR-EHR-CLUSTER.prescription.v1 This 'id' includes the major version number so that archetypes with breaking changes with respect to each other are treated as different archetypes, operationally. In the design environment, tools know that xxx.v1 and xxx.v2 are related. But that doesn't hold in the runtime environment. Filename is irrelevant, and has been freely choosable for 5-10 years in all archetype modelling tools that I know of. - thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20141003/5b777801/attachment-0001.html>
