-
-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
incorporate Allotrope additions #1104
Comments
I know the history of this. Some years ago I was collaborating with Allotrope. They adopted v1.0 of QUDT and chose not to move to v2 because of the QName changes on units. My last knowledge of this is at least 3 years ago. Perhaps they can, or have, moved to v2? |
Then we need to have
@steveraysteveray what do you say? |
Ah, we should discuss. We have indeed considered how to best support people wanting to migrate from QUDT 1.0 to newer versions. skos:exactMatch might be the best way to go here. Allotrope is the only significant body we are aware of that is stuck in 1.0, but there may be others. |
Allotrope is this huge initiative for chemical, lab and other kinds of measurements.
I searched "allotrope" here and came up empty.
https://www.allotrope.org/ontologies has their releases and I looked at
AFO 2024/12 Release Files (zip)
unit.ttl
471kb, 807 unitsquantity.ttl
, 324kbqudt.ttl
, 100kqudt-ext.ttl
, 312kIt would be better to incorporate Allotrope additions to the core QUDT, so they can be reused by others.
eg theirs
unit-ext:BecquerelPerGram
vs oursunit:BQ-PER-KiloGM
The text was updated successfully, but these errors were encountered: