>
> Let's say RM=['1.0.1']
>
> (okay so I apologize for my Python syntax, but it's easy to read).
>
> Second: An archetype is edited (whether it's version changes or not)
> against a tool using RM 1.0.2.
>
> The RM = is now RM=['1.0.1,'1.0.2]
>
>
As I wrote before, if the choice will be that
If different versions of the OpenEHR (or any other model) are
available on an application they should be used as different RM,
because usually the changes in the reference model can make newly
created archetypes (1.0.2 in your example) not to parse with older RM
parsers (1.0.1)
The currently specif
Tim Cook wrote:
>
> There are VERY specific guidelines as to what and what does not
> constitute various archetype version changes. Maybe/maybe not these
> should be reviewed in reference to RM versions?
>
they are under review, that is for sure - we can discuss this a bit more
when the templ
Okay,
Maybe the subject line is a little melodramatic. :-)
But we do have a situation and a good bit of this email (along with your
consultations) will be placed as a Problem Report (PR) on the
openEHR.org website.
My point of view is that we have a multi-level modeling environment and
therefor
4 matches
Mail list logo
