perspective details TBD

-> need to be tested further (potential ambiguities), ultimately using the rules from TX may be the better way forward to avoid maintaining another grammar, or at least perhaps reusing that by importing and refining

Removed unused rules + updated for some meta-model changes + added XXX comments for pending updates.

+ support for EnumDataType
+ support for inherited members
+ system specification for generated configuration functions to resolve identically named ports across system components
+ support for extended component types

+ LiteralValueUse compatibility (int / bool)
+ inherited member handling
+ better value and template handling

* exports do not include compiled classes otherwise..