Re: poor version management in archetype editor

[Williamtfgoossen@cs.com]

In a message dated 28-11-2008 10:23:59 W. Europe Standard Time, richard.kavanagh@nhs.net writes: 
> A combination of a good version management tool and an internal configuration management policy works well for us, I would be happy to discuss this with others.
>   
>  We use subversion as our version management tool and find it indispensible for us.. I would be interested to hear what other archetype/template authors use for their configuration management.
>   
>  regards
>  Richard Kavanagh
> Head of Interoperability Specifications
> Data Standards and Products
> NHS Connecting for Health
> Tel : +44 (0)113 397 4398
> Mob : +44 (0)7770 644449
> Richard.Kavanagh@nhs.net
> www.connectingforhealth.nhs.uk
>
> NHS Connecting for Health supports the NHS in providing better, safer care by delivering computer systems and services which improve the way patient information is stored and accessed.


I understand that subversion is used as more or less external software from the archetype editor tool. 

That is fine, but still leaves the need to be able to save an archetype as:  

body temperature draft v01.adl

and after making changes and update and redistribution, 

body temperature draft v02.adl

and when all parties agree it is finished

body temperature draft v1.adl

However, as I understand, such a simple version policy is not possible with the archetype editor, because it makes from scratch on only v1 of all variants. 
I agree with mr Hilbert that this is a feature of a simple program, e.g. notepad does it already. 

If this is what mr. Kavanagh calls configuration management, that is fine with me, as long as the archetype editor allows us to do this. 


Sincerely yours,

dr. William TF Goossen
director 
Results 4 Care b.v.
De Stinse 15
3823 VM Amersfoort
the Netherlands
email: Results4Care@cs.com
phone + 31654614458
fax +3133 2570169
www.results4care.nl
Dutch Chamber of Commerce number: 32133713