the current ADL and AOM specifications do not include lists as a way to constrain dates, times, date/times or durations, although the ADL document implies that it is included without showing any examples. To my knowledge, this has never been required, and it does not seem terribly useful. It would not be that hard to add - it would require small changes to the ADL spec, the AOM spec, the parser grammars, and additions to the test archetypes…but I am inclined simply to correct the text in the ADL specification to remove this possibility for now…any objections?
Actually the Java component has implemented support for list of values in c_date, c_time and c_datetime. I tend to think it will be useful and more consistent to allow that way of constraining primitive values following the same pattern used for c_string, c_integer etc. The support for that in parser is easy to fix (there is already some date/time list values in the test adl for basic types).
Actually the Java component has implemented support for list of values
in c_date, c_time and c_datetime. I tend to think it will be useful
and more consistent to allow that way of constraining primitive values
following the same pattern used for c_string, c_integer etc. The
support for that in parser is easy to fix (there is already some
date/time list values in the test adl for basic types).
Actually the Java component has implemented support for list of values
in c_date, c_time and c_datetime. I tend to think it will be useful
and more consistent to allow that way of constraining primitive values
following the same pattern used for c_string, c_integer etc. The
support for that in parser is easy to fix (there is already some
date/time list values in the test adl for basic types).
but can anyone think of a use case in health? I have never seen one...