Von: openEHR-technical <openehr-technical-boun...@lists.openehr.org> Im Auftrag
von Thomas Beale
Gesendet: Dienstag, 18. Dezember 2018 18:39
An: openehr-technical@lists.openehr.org
Betreff: Re: AW: Syntax for including archetypes in SLOTs, regardless of version
The example below
openEHR-EHR-OBSERVATION\.body_mass_index(-[a-zA-Z0-9_]+)*\.v[0-2] means that
not only v0, v1, v2 are valid, but also v10, v15, v27 to name a few.
the regex character class [0-2] matches only a single digit having the
character values in the series 0-2, i.e. 0, 1, or 2.
[SG] Sure – but if it is were the case that only a partial match is required,
anything could be added to the left or the right (as long as it makes a valid
archetype id).
Now that you mention it, I do seem to remember we specified a very long time
ago that those regexes did have to be full validating ones.
[SG] That’s exactly what I mean, yes, thank you. (And that then ensures that
the above does not match v10 or v15…)
So that means using something more like
openEHR-EHR-OBSERVATION\.body_mass_index(-[a-zA-Z0-9_]+)*\.v(0|[1-9][0-9]*)(\.(0|[1-9][0-9]*)){0.2}
as the checker regex in CKM, and patterns like
openEHR-EHR-OBSERVATION\.body_mass_index(-[a-zA-Z0-9_]+)*\.v.*, where the
trailing '.*' matches anything, and the validator regex ensures it is only
semver dotted version patterns.
- thomas
_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
