v3.0.0
Please note!
As mentioned in Release 2.1.47, we are coming out with version 3.0.0 with this Release. This could be a breaking change for your applications, since some of you may be using the versioned graph URIs that include "2.1". Moving forward, those will include "3.0.x", but of course the un-versioned graphs will always resolve to the latest version. So, for example, if you use the owl:imports mechanism, your application could import http://qudt.org/2.1/vocab/unit if you want to stay with 2.1, http://qudt.org/3.0.0/vocab/unit if you want to explicitly migrate to the new Release, or http://qudt.org/vocab/unit if you want to always get the latest Release.
In Release 3.0.0, we have removed all the deprecated entities that have accumulated to date. In the 2.1 releases, they all contained the triple:
<entity> qudt:deprecated true
If you have been using SHACL, you should have already been receiving notifications during validation if you were using properties or instances that were marked as deprecated, so you had an opportunity to migrate to the replacement concepts. With this new Release, those entities no longer exist.
Changes
3.0.0 - 2025-02-13
Changed
- Replaced
2.1
with$$QUDT_VERSION$$
in all graph URI references. This will result in URIs containing
full semantic versions, such as 3.0.0, moving forward. Note that this is a breaking change, hence
the transition to QUDT version 3. Versionless graph URIs are still dereferenceable on the web.
Deprecated
- Removed all previously deprecated entities, to begin a new cycle of deprecation when needed.
Fixed
- Corrected unit symbols containing some kind of conversion artifact, e.g. ''
- Fix dimension vector of unit:MicroMOL-PER-M2-SEC2
- Added the newly referred-to dimension vector to the dv vocabulary
- Corrected 456 unit symbols of derived unist by generating them based on their factors. Note: correcting
derived unit symbols without correcting their factor units (e.g.km/hr
->km/h
withouthr
->h
)
will not solve the problem in the long term. We are not yet automatically detecting and correcting
incorrect derived unit symbols but it might happen in the future. If we started doing that, the factors
would take precedence. - Corrected the language tag
@en-us
to@en-US
- Corrected a small number of conversion multipliers
And as always, a big thank-you to all of you for bringing many of these issues to our attention, and even better, for providing submissions to extend the coverage and capabilities of QUDT!