Revise name for the main class about nomenclature HOT 2 CLOSED

Calling the class X for the moment, I think this maps exactly to what SDMX Information Model calls a DSD, or data structure definition ("DataStructureDefinition" as a class name).

Other thoughts (without repeating anything said in the linked issue):

• As far as I can tell, one X can refer to multiple Codelists, but only one Codelist per concept/dimension. For instance, there cannot be two Codelists for "AREA" or "REGION" in the same X.

• A DSD is a "maintainable artefact", which means it has a number of attributes. These can all be used to clarify the relation to a research project, e.g.

  • id: "NAVIGATE"
  • name: "NAVIGATE data structure"
  • description: "Main data structure for model intercomparison in WPX of the NAVIGATE H2020 project."
  • maintainer: this is a reference to an Agency, with 1 or more Contacts; those can be used to store info about the project or its secretariat or specific people within it.
  • version, etc.

• The same research project might produce and use multiple Codelists for the same concept, e.g. for different work packages, or different versions of them over time. So it's probably not correct if the class name implies there is a 1:1 relationship between a project and a specific version of a specific codelist for a certain concept.

• The term registry is used in SDMX to refer to a web service which keeps track of other web services or data providers.
  There is an "SDMX Global Registry" browseable here: https://registry.sdmx.org/organisations/dataproviders.html

  For example, a registry might include that IAMC is an Organization/Agency that maintains a web service at a certain URL which can be used to retrieve information on some DSDs (e.g. including the hypothetical NAVIGATE DSD, above) and/or data that is in the structure described by the DSD. (The registry could also include that IIASA is a separate organization that maintains a different service, etc.) The registry might also republish multiple "REGION" Codelists (each from a different other providers/projects/etc.; or different versions from the same provider), so a user can access the one(s) desired.

• I think template should be retained only for the specific meaning of: a file in a specific format (e.g. an Excel file) which a user is expected to fill in with actual data.

  By design, a filled-in template file will be "data that is structured according to the DSD."

from nomenclature.

Revisited this thread and I consider the key point from this issue closed with the renaming to DataStructureDefinition - please re-open or start another issue if relevant items remain unanswered.

from nomenclature.