On Thu, 2008-05-08 at 04:56 -0300, Tim Cook wrote: > IF so then I believe that the development issues are really one of > management and tools. Since it is completely logical that a > specialization of an archetype will reside in the same folder of the > development tree (as is the case with the ones I've seen). The tools > could scan the directory for specializations of the current archetype. > Warn the developer that specializations exist. Prior to committing any > changes ask the developer to approve an email to the author(s) of the > specialization(s) with the revision_history enclosed. If we were to add > a datetime stamp attribute to the specialization section along with the > parent archetype id then if the first email was lost, the tools could > check the parent and see if it had been modified since the last time the > specialization was edited.
There is always one of those; "oh, why didn't I say ..." things you think of right after clicking the Send button. :-) The ADL files are under SVN control. Are the knowledge workers using those features? Editing locally and submitting commits? These changes are already recorded and can easily be sent via email to subscribers. The openEHR Java list does this quite nicely. --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/20080508/3c6bc86c/attachment.asc>
