Reuse/consider alignment with iTEM / SDMX code about nomenclature HOT 1 OPEN

In terms of community process, points I made on today's IIASA/ECE call:

• For a given concept, e.g. FUEL, it is possible to create more than one code list.
• Different users or modelers can (should!) directly describe the codes that appear in the internal structure of their model/analytical workflow.
• As above, one code list can be established as the recommended one for a given community, and used to prepare templates used in that community.
• As long as data specifies which data structure, and thus code list, is being used, it can be validated against that code list.
• Transformations can be established between any pair of code lists, with appropriate operations:
  • Rename/map, when two different lists include codes with different meaning but same IDs.
  • (Dis)aggregation, when codes do not map directly to one another.
• The action of transforming data from one “template” to another decomposes to simple steps:
  • Separate quantities.
  • For each quantity:
    • For each dimension:
      • If the source and target data structure use the same code list, do nothing.
      • If the code lists differ, apply a transformation from the source code list to the target code list.

from nomenclature.