Re: Archetype publication question - implications for implementers

2015-10-23 Thread Thomas Beale
As a reminder, the current draft spec on versioning and lifecycle is here, and as usual, comments are welcome

Re: OpenEHR maintenance

2015-10-23 Thread Bert Verhees
On 23-10-15 15:06, Øystein Nytrø wrote: Would anyone care to comment on how OpenEHR should keep tools, models and implementations fresh, sparkling, consistent and usable? HI Øystein, OpenEHR is a specification, although there is some sourcecode, regard that as an extra service, developed by s

OpenEHR maintenance

2015-10-23 Thread Øystein Nytrø
I am reviewing the rise and development of domain specific OO models. There are many... Just a question of maintenance of OpenEHR: Versioning is fine. Forking is already happening (cfr. ISO-standardized units or not). Every fork is a bad thing - it requires double work, fosters arguments, div

RE: Archetype publication question - implications for implementers

2015-10-23 Thread Diego Boscá
Not sure that having two archetypes really complicates the systems. I'm pretty sure that systems are already using more than two archetypes. If they are versions of the same archetype is not different than supporting different archetypes. If your system has dependencies on how a given archetype is