On Tue, 2009-02-03 at 16:18 +0000, Ian McNicoll wrote: > Hi Thomas, I was suggesting the RM version be recorded when the > archetype is officially published or revisioned and re-published. This > is the only time when an archetype author can be expected to take some > account of the underlying RM when designing or revising the model. It > is not a perfect solution but it gives some estimation of the RM > version that the author was working against when designing the > archetype. The archetype tools could automatically record the RM > version whenever an archetype lifecyle transitions to published or has > its version/revision updated.
Exactly. Each time the archetype is touched the tools can look to see if the current RM is in the list. The tool should probably know how to invalidate previously valid versions as well. --Tim -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090203/504e333c/attachment.asc>
