+1
Cheers,
-koray
From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On
Behalf Of Bakke, Silje Ljosland
Sent: Friday, 7 August 2015 8:07 p.m.
To: For openEHR technical discussions
Subject: RE: Archetype editor, CKM and v0 v1
I'm assuming there's no reaction
Looking at this again, AE currently provides two choices
1. Do not include specialisation, in which case the slot constraint matches
the provided slot archetype name and version exactly.
2. Include specialisation where any specialisation of the provided slot
archetype is allowed (but currently
discussions
Subject: RE: Archetype editor, CKM and v0 v1
On a related note; the openehr.orghttp://openehr.org website still advertises
Archetype Editor v2.2.905 beta from 2013, and Template Designer 2.6.1213.3.
Especially now after the v1 - v0 change, the newest builds should be linked
from
] On
Behalf Of Peter Gummer
Sent: Friday, August 07, 2015 10:55 AM
To: For openEHR technical discussions
Subject: Re: Archetype editor, CKM and v0 v1
Hi Silje,
Yes, that’s true, and we’ve been wanting to do new releases for a long time but
it takes time, which we don’t have. There were some
. Precisely what we'd like to avoid, isn't
it?
Regards,
Silje
From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On
Behalf Of Bakke, Silje Ljosland
Sent: Tuesday, August 04, 2015 10:45 AM
To: For openEHR technical discussions
Subject: RE: Archetype editor, CKM and v0 v1
technical discussions
*Subject:* RE: Archetype editor, CKM and v0 v1
On a related note; the openehr.org website still advertises Archetype
Editor v2.2.905 beta from 2013, and Template Designer 2.6.1213.3.
Especially now after the v1 - v0 change, the newest builds should be
linked from
Sent: Thursday, July 23, 2015 1:07 AM
To: openehr-technical@lists.openehr.org
Subject: Re: Archetype editor, CKM and v0 v1
good point. Maybe a slightly more civilised version would be
\.v[0-9]+(\..*)?
that forces there to be one or more digits, and if there is anything else, it
must start
Technically speaking, if we want to properly match any archetype in a
slot, we need a regex that will match any level of versioning id. Since
matched archetypes will eventually all have 3-part versions (but today
might have only 1-part versions), we need to match thngs like
.v0
.v1
.v0.0.1
Thanks Thomas,
I will go with
\.v[0-9]+.*
which will give us a bit of flexibility and solve Dave's problem (I think!).
unless anyone strongly objects, of course.
Ian
Dr Ian McNicoll
mobile +44 (0)775 209 7859
office +44 (0)1536 414994
skype: ianmcnicoll
email: i...@freshehr.com
twitter:
Hi All
I'm having a bit of an issue with CKM re-versioning archetypes and slots that
reference Clusters.
When I create a new archetype in the archetype editor (Version 2.2.905 Beta),
the archetype is saved as version 1. For example
openEHR-EHR-OBSERVATION. blood_pressure.v1.adl
When I upload
That will be the one then.
Thx
Ian
On Wed, 22 Jul 2015 at 14:29, Diego Boscá yamp...@gmail.com wrote:
Second one allows both the new and the old versioning (e.g. v0.0.5 vs v0)
El 22/7/2015 15:12, Ian McNicoll i...@freshehr.com escribió:
Thanks Diego
What is the difference between the 2 ?
Second one allows both the new and the old versioning (e.g. v0.0.5 vs v0)
El 22/7/2015 15:12, Ian McNicoll i...@freshehr.com escribió:
Thanks Diego
What is the difference between the 2 ?
Ian
On Wed, 22 Jul 2015 at 13:55, Diego Boscá yamp...@gmail.com wrote:
Put v[0-9] or v[0-9](\.[0-9])*
Thanks Diego
What is the difference between the 2 ?
Ian
On Wed, 22 Jul 2015 at 13:55, Diego Boscá yamp...@gmail.com wrote:
Put v[0-9] or v[0-9](\.[0-9])* to allow multiple subversions
El 22/7/2015 14:22, Ian McNicoll i...@freshehr.com escribió:
Hi Dave,
I recognise the problem which is a
Hi Ian,
The + is redundant here, since it’s just saying that there has to be one or
more digits after the ‘v’. But the next thing that it says is that you can have
anything at all after those digits.
So you might as well omit the +:
\.v[0-9].*
This says that there has to be a digit after the
good point. Maybe a slightly more civilised version would be
\.v[0-9]+(\..*)?
that forces there to be one or more digits, and if there is anything
else, it must start with a dot. Somewhat safer perhaps.
- thomas
On 22/07/2015 23:34, Peter Gummer wrote:
Hi Ian,
The + is redundant here,
Good point Sebastian,
I was really thinking towards the future and the same slot constraints
appearing or being redefined in templates where tighter constraints might
be needed.
Is that overkill?
Ian
Dr Ian McNicoll
mobile +44 (0)775 209 7859
office +44 (0)1536 414994
skype: ianmcnicoll
email:
My understanding was that minor version and patch version would not be
part of the normal archetype id, which is what you are looking for here?
Otherwise you'd need to allow -alpha etc here as well?
Sebastian
On 22.07.2015 16:00, Ian McNicoll wrote:
That will be the one then.
Thx
Ian
On
Hi Dave,
I recognise the problem which is a result of the transition to a much
richer and better versioning mechanism.
The Archetype Editor has been updated to handle the new versioning (on the
openEHR Github, not released yet ) but we will need to adapt the slot fill
regex to allow for .v0
Put v[0-9] or v[0-9](\.[0-9])* to allow multiple subversions
El 22/7/2015 14:22, Ian McNicoll i...@freshehr.com escribió:
Hi Dave,
I recognise the problem which is a result of the transition to a much
richer and better versioning mechanism.
The Archetype Editor has been updated to handle
19 matches
Mail list logo
