Change log

This log documents significant changes for each release. This project follows Semantic Versioning.

[3.1.0] - 2023-06-07

Fixed

• {degF} is now correctly validated as valid.
• The toBaseUnits serice, in the XML format, will now sometimes include warning messages in a new "Messages" tag, for cases like {degF}, which are probably meant to be [degF]. Likewise, for the JSON format, there is a new "Messages" field. For the plain text format, these messages are appended on additional lines following the normal output.

[3.0.0] - 2023-05-04

Changed

• Replaced the implementation of the toBaseUnits API with one based on the ucum-lhc JavaScript library. This corrects some issues, and also adds support for annotations. In the process, there have been the following changes in the output for this API:
  1. "Special" units (in the sense of the UCUM specification) no longer include the result quantity, to avoid confusion and accidental misuse of those values as scale factors.
  2. The plain text format has changed so that the base unit string is a valid UCUM unit, and also to use "~" instead of "=" for "special" units (for the same reason as in (1).

[2.3.18] - 2023-03-30

Fixed

• Updated the ucum-lhc library to 4.1.8; spaces are no longer valid in annotations for the isValidUCUM web service API. For now, the other two web service APIs (ucumtransform & toBaseUnits) are not validating characters in annotations. (Actually, toBaseUnits has never accepted annotations.)

[2.3.15] - 2023-03-06

Fixed

• There was a problem introduced with the previous version with the isValidUCUM API when validating the % unit, which is valid but which was producing an error.

[2.3.14] - 2023-01-18

Changed

• Replaced the implementation of the isValidUCUM API with one based on the ucum-lhc JavaScript library. This was done to correct an issue with nested parantheses, which will still pose a problem for the other APIs. Assuming this version is successful, work will be done to revise the other APIs to also use ucum-lhc.

[2.3.12] - 2022-12-13

Changed

• Updated website header and footer and logo.

[2.3.11] - 2022-11-10

Fixed

• APIs toBaseUnits & ucumtransform for cases 'mL2' and '(m3).(g2)' (exponents on non-base units, and parentheses around terms). Parentheses are still not handled very well. In particular, isValidUCUM with '((m).g)', which used to return an error, now returns 'false', though it is actually valid.

[2.3.3] - 2020-11-18

Fixed

• Due to an issue with our implementation, we have introduced (hopefully temporarily) a limit of three digits on exponents.

[2.3.1] - 2020-10-05

Fixed

• The plain text version of the toBaseUnits API reported in an incorrect quantity in some cases. (The JSON and XML output were correct already.)
• The returned Content-Type header on toBaseUnits API now contains a "qs" parameter. This was added to stabilize the default content-type as XML.

[2.3.0] - 2020-08-19

Added

• Mass, mole, and equivalent units can now be converted, with some limitations. See https://ucum.nlm.nih.gov/ucum-service.html#mass-mol-eq

[2.1.2] - 2018-08-27

Fixed

• Target units are now permitted to begin with a number.

[2.1.0] - 2018-05-17

Added

• Support for URL-encoded "/" charcters in unit expressions, i.e. sending "%2F" instead of "/" for division between units. Previously, only "/" for division was allowed, which meant one could not simply URL-encode the whole unit expression.

[2.0.4] - 2018-03-30

Changed

• Disclaimer on conversion API
• URL for the Clinical Table Search Service

[2.0.3] - 2018-02-12

Added

• Disclaimer to conversion API

[2.0.2] - 2018-02-09

Fixed

• Corrected XSS vulnerabilities

[2.0.1] - 2018-02-08

Added

• A link to a PDF of commonly used UCUM expressions from real-world data.

[2.0.0] - 2018-01-29

Changed

• The outer tag name for XML responses has changed to UCUMWebServiceResponse.

[1.0.0] - 2018-01-05

Initial version

• Web service is essentially the same as the version at xml4pharmaserver.com.