NeXus doc building pipeline and appdefs demand that adding properties of concepts have to be spelled out explicitly even though symbolic dim just inherited from the base class

[mkuehbach]

apm_refactoring, 34fc49b, PR #140

Inspect /NXapm/ENTRY/atom_probe/ranging/peak_identification/ION/mass_to_charge_range-field No dimension shown after make local although that concept is not specializing

Effect: *Violates single-source principle (appdefs and base class can generated undesired specializations where unnecessary, resulting appdefs is underconstrained) How to fix:

• Concept-based resolver (e.g. @sanbrock nexus functionalities) needed Problems:
• nexus functionalities would need to actively rewrite appdef spec...

• Better would be:

• Test that in an appdef each concept depending on its type (group, field, attribute) has specific quantities set