The Problem
Currently in ADL value set constraints are defined in two ways. External value sets are defined as a reference in the archetype terminology section, identified using an ac-code. In the terminology section a binding can be added, which is a URI to an external ref-set or value set, e.g. sitting in some CTS2 terminology service in which a copy of SNOMED CT is to be found.
...
The question here is: where should the value set really be defined? As described here, it's inline in the archetype constraint definition, right in the middle of all the quantity, structural and other constraints. But since a value set is a terminological entity, should it really be defined in the archetype terminology section, and just referred to from the constraint definition part?
Implemented Solution
An earlier proposal is shown in the following section. What I have actually implemented is shown here, and is more like Daniel Karlsson's suggestion on the technical list. In it, all inline constraints are treated as either:
...