New CR to handle non-inclusive two-sided ranges

Implementers (archive)
1

In the NHS work, Sam has discovered the need to support non-inclusive
two-sided ranges in ADL, e.g. 0 > x <= 1000

This means some relatively easy additions to the dADL parse rules (you
need to include the dADL primitive type patterns in the cADL production
rule set as well).
I have created a CR for this - see
http://coruscant.chime.ucl.ac.uk:8200/openEHR_Collector/projects/specifications/CR/242.
I will put up the changed ADL document in a day or so, as well as a test
archetype. I have a vague feeling that someone else brought this up as
well, but I can't find the post. If someone remembers, I will credit
them as a co-raiser.

- thomas beale

2

I have a vague feeling that someone else brought this up as
well, but I can't find the post. If someone remembers, I will credit
them as a co-raiser.

Hi, Tom.

Chris Date raised this issue in "Temporal Data and the Relational Model" in
2003, the range being a time interval. Maybe you remember it from there?

Is he a member?

- Paul