Sorry Pablo, I see your full reply first time now, I didn't see it
before on my phone, seems my email app was hiding a part of the text..
On 21-06-17 11:20, Pablo Pazos wrote:
Versioning would be when a uses commits a document that is "complete".
IMO incomplete compos should not be final versions, and if one user is
working on an incomplete version, no other user can work on that
(read-write work). If two users need to read-write incomplete compos,
then 2 separate versions are needed and there you have branches.
Linear versioning would not allow to create branches, and new versions
would not be created until the user that has the current version in
read-write mode finishes and commits the completed version. That is
the only way to keep it linear, with locks.
We have the same conclusion, but you were first. Linear version is
needed with locks, only one user at a time changing a persistent
composition (or another kind of dataset, but that is unlikely to happen)
Not sure about removing the current approach from the specs, but
creating a simpler alternative might be of use to enable more and
quicker implementations.
I think it is the only possible conclusion since a distributed version
system cannot be used, because of the inability of users to solve
manually merging problems.
Sorry again for writing what you had already written just before that.
Best regards
Bert
_______________________________________________
openEHR-implementers mailing list
openEHR-implementers@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org
