Open egonw opened 3 years ago
I'm curious about your future plans on this. In particular, I notice that you group units into "unit types". This is analogous to what QUDT calls quantitykinds, but there are currently 847 different quantitykinds (with some sharing the same dimensionality). I'd be happy to discuss approaches you might consider that would not require you to manually define your unit types and thus expand your coverage.
Fair warning: I am not a programmer, just a modeler, so I'm quite ignorant of any Java implications!
but there are currently 847 different quantitykinds (with some sharing the same dimensionality).
In the past I hardcoded a number of them often used in pharmaceutical sciences. It's actually not that hard to autogenerate these classes from the ontology, something I did in the past in metabolomics ("MetWare") too, indeed.
but there are currently 847 different quantitykinds (with some sharing the same dimensionality).
In the past I hardcoded a number of them often used in pharmaceutical sciences. It's actually not that hard to autogenerate these classes from the ontology, something I did in the past in metabolomics ("MetWare") too, indeed.
This sounds pretty interesting.
Like: