> 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
Well, the scheme here (using subversion) could be to - check in a first version of "body temperature" - create a branch "draft" - checkout, modify, checkin - when satisfied tag as "v0.1", "v0.2", ... - when satisfied with the draft branch merge it back into the main branch Or similar approaches. Basically it is more of a policy question. Versioning as such probably should not be the genuine job of the Archetype Editor in itself. However, if that editor *understood* versioning and could access/integrate an external tool that would make proper use of versioning a lot easier, particularly for users not yet familiar with that sort of thing. Karsten Hilbert -- Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
