I think you sent this to the wrong email...
On 8/14/06, Rodrigo Filgueira <rfilgue at fing.edu.uy> wrote: > > Thomas, thank you for your answer. > My dificulty was centered more in understanding the contribution concept. > If this is a concept used in versioning control systems I do not know. > > Examples would be a good start in order to improve docs. > I'll go that way and put an example, you tell me If my conclusions are > correct. > This example is based in the system we are implementing: > > Let's say I have a web based form where I register information > corresponding to three different COMPOSITIONS. > This data submission would be a CONTRIBUTION, and of course I would have > three versioned compositions. > > Let's say now I edit the information registered before and submit it > again. > This would produce a whole new contribution and (assuming I edited all > three COMPOSITION data) three COMPOSITION versions. > > thanks for your help > > ------------------------------ > > Rodrigo Filgueira > Asistente Docente/Investigador > N?cleo de Ingenier?a Biom?dica, FING - UDELAR > > > > Thomas Beale wrote: > > Rodrigo Filgueira wrote: > > I'm trying to understand where audit details are used and how. > My first thought was that it had to be an attribute of contribution which > is correct, but then I found it is also an attribute of the VERSION class. > > Then I thought, ok this is better, let's audit each version and we are > done. The first version holds the info about the original "submission", the > second for the second version, etc. > > But why do we need it in contribution? of course I'm missing something > because contribution without audit details is nothing. As you may have > probably already discovered out I do not get the need for contributions and > in particular do not understand why EHR has a list of contributions as an > attribute and a list of versioned compositions too. > > because 1 Contribution corresponds to 1 change-set, which might include > new versions in more than one VERSIONED_OBJECT. The audit of each Version > says what each change was about (e.g. a correction, an addition, etc etc) > while the audit for the Contribution corresponds to the group of changes as > a whole, e.g reason might be "encounter 12/07/2004". There will be some > likely repetition of dates and times to be sure - that's what happens in > version control systems. The BitKeeper commercial change managment tool that > we used to use in openEHR works on exactly this principle. > > > I've been reading the common package and these answers are quite elusive > still. > Any help would be greatly appreciated. > > version control is a difficult area for many people to get their heads > around, and maybe the explanations there are not yet good enough. Any > feedback on improving the explanations is welcome. > > - thomas beale > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060814/646468e4/attachment.html>
