Now we have multiple unit systems in the Fuseki database. QUDT has definitions of units, unit classes, and conversion factors. Modelica has definitions of the units that can be found in the Modelica tool. The next step is to create mappings between the unit systems.
Although some units can be mapped automatically by searching for the same name or symbol, for some units it is not possible. We must support a user defining manually the mappings between the unit systems.
The CSV will have two columns. The first row will have a prefix which should be applied to all of the other elements in the table. Each row defines that two units are equivalent.
From this CSV, we should have a Python script that generates OWL XML that contains the equivalence statements.
Now we have multiple unit systems in the Fuseki database. QUDT has definitions of units, unit classes, and conversion factors. Modelica has definitions of the units that can be found in the Modelica tool. The next step is to create mappings between the unit systems.
Although some units can be mapped automatically by searching for the same name or symbol, for some units it is not possible. We must support a user defining manually the mappings between the unit systems.
From our discussion, we expect that the user will create a spreadsheet for their mappings. They will save this spreadsheet as a CSV file. An example CSV file is in the repository: https://github.com/adamnagel/qudt-for-domain-tools/blob/issue-11/modelica/mapping-to-qudt.csv
The CSV will have two columns. The first row will have a prefix which should be applied to all of the other elements in the table. Each row defines that two units are equivalent.
From this CSV, we should have a Python script that generates OWL XML that contains the equivalence statements.