Orchestra version 1.0 introduced Concepts. The big idea is that a semantic concept can have different representations in different protocols, even between different versions of FIX. Mapping a concept to different encodings can be used to inform message translators and the like. The gap in Orchestra is that there is no common registry or model of concepts. This could be improved by using the terminology of ISO/IEC 11179, and concepts could be registered in a metadata catalog that conforms to that standard. (The standard is currently in review.)
See ISO/IEC 11179-3:2013 Metadata registries (MDR) - Part 3: Registry metamodel and basic attributes
11.1.2.2.2 Description of Conceptual_Domain
Conceptual_Domain is a class each instance of which models a conceptual domain (3.2.21), a set of value
meanings (3.2.141) which may either be enumerated or expressed via a description.
For example, one possible conceptual domain could be countries of the world. It might be associated with two
value domains (3.2.140): three letter country codes, and full country names. The conceptual domain might
be used in several data element concepts (3.2.29), e.g., “person’s country of residence”, “person’s country of
birth”, “person’s country of citizenship”.
A conceptual domain can facilitate the mapping of equivalent values of two or more value domains that share
the conceptual domain.
Orchestra version 1.0 introduced Concepts. The big idea is that a semantic concept can have different representations in different protocols, even between different versions of FIX. Mapping a concept to different encodings can be used to inform message translators and the like. The gap in Orchestra is that there is no common registry or model of concepts. This could be improved by using the terminology of ISO/IEC 11179, and concepts could be registered in a metadata catalog that conforms to that standard. (The standard is currently in review.)
See ISO/IEC 11179-3:2013 Metadata registries (MDR) - Part 3: Registry metamodel and basic attributes