...
Some changes will be required at some point:
The typology_id relates to… what? And how is it used?
Regardless, the typology_id should reflect the ID of the specific typology processor that will be invoked for this instance of the network map. To be more specific, the typology_id should be renamed to the typology_processor_id. There may, at some future point, be multiple typology processors active in an Actio implementation for different scoring or monitoring schemes. Typology processors with arbitrarily different themes may then have a different ID, after which iterations or versions of a specific typology processor “theme” (hence, ID), will have separate version progression.
typology_name is fine, and refers to the name of the typology as a descriptor for the typology configuration used to compose the rules into a typology score.
typology_version by itself is largely insufficient, since a typology processor may have a version, and a typology config may also have a (possibly separate) version. The current typology_version describes the version of the typology configuration that is being used, and should be renamed to the typology_configuration_version. Yes, we have been referring to the typology configuration as the typology expression, but this is probably overly specific (and not technically accurate), so we should relabel expression to configuration to be more consistent with the configuration artefacts in the rest of the evaluation pipeline.
In addition to the typology_configuration_version, we will also need a new typology_processor_version to account for versioning of the typology processor itself.
Another proposed new field will be the typology description to add some legibility to the Network Map for users and configurers.