Hi Diego, I understand your point but I am not sure that slot naming is really working out as any of us envisaged. In the vast majority of cases where we specify an archetype pattern in the slot description we also leave the constraint open-ended because experience has shown us that too tightly coupling the parent and child leads to over-complication of dependencies and insufficient flexibility to cope with new use cases. In this respect the slot filling constraint acts as useful 'design guidance' i.e this is the sort of archetype we expect to be slotted in here but others (including V2 versions are allowed).
I agree with you in those instances where we do tightly constrain a slot to be filled with only a certain pattern but in those cases we would also probably want to make a judgement about the fitness of subsequent versions on a case-by-case basis i.e I would probably not want the version allowed to be open-ended since I need to make sure that the breaking change introduced in V1-V2 does not also mess up whatever imposed the need for a tight constraint in the first place. So, in theory, you are correct but in practice, I suspect the current approach is working quite well, though I am sure there will be examples of errors and inconsistencies. The semantic referencing will work quite well for slot filling and was part of the reason for adhering closely to semver.org numbering but I am not so sure it works at individual archetype level for slot constraint definitions. Ian On 25 September 2014 15:19, Diego Bosc? <yampeku at gmail.com> wrote: > > > > I thought we would convert to this system some years ago, but people > seem to > > be happy with the current system for now. It won't work forever > though.... > > > > We agree on this. We just must be aware of the potential problems of > using current archetypes. > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > -- Dr Ian McNicoll office / fax +44(0)141 560 4657 mobile +44 (0)775 209 7859 skype ianmcnicoll ian at freshehr.com Clinical modelling consultant freshEHR Director openEHR Foundation Honorary Senior Research Associate, CHIME, UCL BCS Primary Health Care www.phcsg.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20140930/04b4a6fd/attachment.html>
