Feature Request: Add type of measure and scale and/or relationships #7
Comments
We still have the scale stored in two places but in our current system that's part of a unit's "id". If the DFC adds that value to its standard then we can use it for lookup and don't need to repeat it. * datafoodconsortium/taxonomies#7
We still have the scale stored in two places but in our current system that's part of a unit's "id". If the DFC adds that value to its standard then we can use it for lookup and don't need to repeat it. * datafoodconsortium/taxonomies#7
We still have the scale stored in two places but in our current system that's part of a unit's "id". If the DFC adds that value to its standard then we can use it for lookup and don't need to repeat it. * datafoodconsortium/taxonomies#7
|
We have identified the QUDT ontology to align with for unit conversion. @Alcoz will match our measures values with We need to select which units to link |
|
I guess that you are referring to https://qudt.org/. Looks comprehensive, and huge. I wonder if any semantic web system has to know most of the semantic web ontologies because it's all connected. 😉 |
Yep, sorry not clear. I was rushing. We won't be using all of it - just referencing the measures we need to with
Definitely... and, it seems to me, no-one has that knowledge & wheels are being reinvented all over the place! 🙄 |
Implementing the interpretation of measurements, I'm mapping all units into a common, scalable data format consisting of:
This could be done in the DFC Connector to not repeat it in every application but we could also store it in the measures.json. It contains the name already. It could either have one of the three types and a scale or each measure could refer to a reference measure of that type with scale. For example, a six-pack could say it's 6 x piece. A millilitre would be 0.001 x litre. We could use SI base units for this.
It would enable every application to compute the total weight or volume of a product without knowing all units. And if the DFC adds a Li (Chinese mile) to the database then all applications would understand it without adding any logic.
The text was updated successfully, but these errors were encountered: