QUDT Release 2.1.27

PLEASE NOTE!
SHACL users will immediately notice something new with this release. Specifically, we are beginning the process of deprecating the commonly used relation qudt:unit in favor of qudt:hasUnit. This is consistent with the other similar relations qudt:hasQuantityKind and qudt:hasDimensionVector. You can continue using qudt:unit in your data files for a while (probably for a year), but you will get a sh:Info validation message when you invoke SHACL validation checking.

OWL users will not get any SHACL validation message of course, but please be aware that the relation qudt:unit will eventually go away in favor of qudt:hasUnit.

---

Other updates include:

• Catching some typos and generally keeping things orderly and consistent (thanks @ektrah)
• Deprecated qudt:allowedUnitOfSystem to qudt:applicableSystem. Again, this is for consistency, analogous to qudt:applicableUnit that is used to point a QuantityKind instance back to "applicable" units. Here's the description of qudt:applicableSystem:
  "This property relates a unit of measure with a unit system that does not define the unit, but allows its use within the system. An allowed unit must be convertible to some dimensionally eqiuvalent unit that is defined by the system."
• Changed the way we deprecate properties. Instead of declaring them instances of qudt:deprecatedProperty, we instead add the triple
  <old-property> qudt:deprecated true (consistent with how we deprecate instances).
• Fixed a number of erroneous vaem:namespace declarations (even in some deprecated graphs).
• Some new units, quantity kinds and dimension vectors (thanks @mgberg, @elisagirola and @JAC28)
• Added the constant Pi, by request

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 size and capabilities of QUDT!