ADL syntax for named nodes on profile datatypes

Description

A requirement recently arose to model a Choice construct which has multiple identical datatypes and which therefore require named nodes. It appears that current ADL 1.4 does not define a syntax to represent node-naming when the datatype is part of a custom profile -see (C_DV_QUANTITY) below:

ELEMENT[at0023] occurrences matches {0..1} matches { – Ambient oxygen
value matches {
(C_DV_QUANTITY) <
property = <[openehr::126]>
list = <
["1"] = <
units = <"l/m">
magnitude =
<|0.0..50.0|>
>
>
>
DV_PROPORTION[at0050] matches {
numerator matches {|0.0..1.0|}
is_integral matches {False}
type matches {1}
}
DV_PROPORTION[at0051] matches {
numerator matches {|0.0..100.0|}
is_integral matches {False}
type matches {2}
}
}

Environment

None

Activity

Show:
D
May 11, 2009, 5:39 PM

I'm having the same problem and I was wondering if the nodeId could not be used to resolve this problem.

Thomas Beale
May 9, 2015, 1:31 PM

This is fixed in ADL / AOM 2, with the tuple syntax. I believe this can be added to ADL 1.4 or ADL 1.5 (to be) as a backward compatible addition, so that tools read in C_DV_QUANTITY (which would still be valid) and output the tuple form of the same node.

Reporter

Ian McNicoll

Labels

None

Components

Affects versions

Priority

Minor
Configure