...
- This requires a change to the RM, to insert some new abstract classes between DATA_VALUE and the existing types, such as: DV_ATOM and DV_CONTAINER, with DV_LIST inheriting from the latter. This is needed so that DV_LIST.items can be specified to be List<DV_ATOM> (leaving out the 2 intermediate classes would allow DV_LIST>DV_LIST<T>>, which we do not want).
- MAJOR: A lot of archetypes that currently assume ELEMENT.value is an atomic DATA_VALUE type would need to be changed to constrain it to DV_ATOM. This might affect a large number of archetypes.
- query engines would have to be modified to handle DV_LIST<T> similarly to solution 3 above.
- Because XML schema cannot properly support generic types, the schemas would require kludge classes like DvListDvText etc, for each possible type DV_X that might have a DV_LIST<DV_X> counterpart. More or less as for solution 3.
...