Is DV_STATE and it's profile constraint C_DV_STATE used anywhere in the specs?

[borut.jures]

@thomas.beale

If you want to implement the inclusion logic (not saying you should!), it’s here…

I didn’t know about the " model_name" rule. I should include that in the validator.

Thank you for sharing your code. I have something similar to build a list of available models:

@borut.jures

I’ve implemented automated loading of the included schemas and can now use much simpler list of included specifications:

Conflicting specifications in Archie's BuiltinReferenceModels class

I believe I figured it out. RM releases 1.0.3, 1.0.4 and 1.1.0 work well together. They only clash with the original RM release 1.0.2. I’ve implemented automated loading of the included schemas and can now use much simpler list of included specifications: static const _specifications = [ // 'original/Release-1.0.2/openehr_ehr_102.bmm', //'RM/Release-1.0.3/openehr_rm_103.bmm', //'RM/Release-1.0.4/openehr_rm_104.bmm', 'RM/Release-1.1.0/openehr_rm_110.bmm', 'PROC/Release-1.…