Hi, I need to create an OPT that contains the ACTION.procedure archetype, but
when exporting the OPT I get this error:
Failed to export operational template. openEHR-EHR-ACTION.procedure.v1.adlERROR
- line 1: parse error [last token = V_IDENTIFIER]line 1: In 'archetype' clause;
expecting archety
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, sin
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
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: @ianm
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
.
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
That will be the one then.
Thx
Ian
On Wed, 22 Jul 2015 at 14:29, Diego Boscá 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" escribió:
>
>> Thanks Diego
>>
>> What is the difference between the 2 ?
>>
>> Ian
>> On Wed, 22
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" escribió:
> Thanks Diego
>
> What is the difference between the 2 ?
>
> Ian
> On Wed, 22 Jul 2015 at 13:55, Diego Boscá wrote:
>
>> Put v[0-9] or v[0-9](\.[0-9])* to allow multiple subver
Thanks Diego
What is the difference between the 2 ?
Ian
On Wed, 22 Jul 2015 at 13:55, Diego Boscá wrote:
> Put v[0-9] or v[0-9](\.[0-9])* to allow multiple subversions
> El 22/7/2015 14:22, "Ian McNicoll" escribió:
>
>> Hi Dave,
>>
>> I recognise the problem which is a result of the transition
Put v[0-9] or v[0-9](\.[0-9])* to allow multiple subversions
El 22/7/2015 14:22, "Ian McNicoll" 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 the new vers
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 arche
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
13 matches
Mail list logo
