uo: update license to CC BY 4.0 and add usages - #2933
Merged
Merged
Conversation
The UO repository's LICENSE.md is CC BY 4.0, but this registry entry still said CC BY 3.0 (and README.md/uo-odk.yaml said CC BY 2.0). The maintainers have settled on CC BY 4.0 and the ontology header now declares dcterms:license https://creativecommons.org/licenses/by/4.0/, so the registry needs to match or the Open check fails on a license mismatch. Also adds a usages block for FP09. The three listed users all demonstrably reference UO terms: OBI, the HUPO-PSI mass spectrometry CV, and STATO.
Run 'python -m obofoundry.standardize_metadata' so the usages block matches the canonical key ordering enforced by TestStandardizedYaml.
deepakunni3
reviewed
Aug 11, 2026
cthoyt
added
ontology metadata
deepakunni3
self-requested a review
September 29, 2026 15:54
deepakunni3
requested changes
Sep 29, 2026
deepakunni3
left a comment
deepakunni3
left a comment
Member
There was a problem hiding this comment.
@leechuck Could you please take a look at the above review comment and suggestion for expressing usage. Would be great to get your input to finalize
Co-authored-by: Deepak <deepakunni3@users.noreply.github.com>
Contributor
Author
|
Sorry for the delay! Yes, the suggestions look better than what I had initially. I applied them to the PR. |
The unquoted colon in the dashboard example description broke YAML parsing in extract-metadata.py (make test). Quoting matches the output of obofoundry.standardize_metadata. Claude-Session: https://claude.ai/code/session_01C8W1pJ4TkQ3eeaoEdQeUL8
deepakunni3
self-requested a review
October 2, 2026 10:00
deepakunni3
approved these changes
Oct 2, 2026
Member
|
Thank you for the quick response @leechuck ! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two changes to the UO (Units of Measurement Ontology) registry entry. I maintain UO.
License: CC BY 3.0 → CC BY 4.0
UO's licensing was inconsistent across its own repository:
LICENSE.mdwas CC BY 4.0,README.mdand the ODK config said CC BY 2.0, and this registry entry said CC BY 3.0. We have settled on CC BY 4.0, matchingLICENSE.md, and made every in-repo statement agree.The ontology header now declares
dcterms:license https://creativecommons.org/licenses/by/4.0/(it previously declared no license at all, which is why the Open check was erroring). Sincefp_001compares the ontology license against the registry license and errors on a mismatch, this entry has to move to 4.0 as well.Companion PR on the ontology side: bio-ontology-research-group/unit-ontology#98
Adding
usagesfor FP09Plurality of Users has been erroring with "Missing usages". The three users listed all demonstrably reference UO terms — verified by counting
UO:references in each ontology's current release:ms)obi)stato)All three also appear in the OBO Foundry's own "Which ontologies use it?" list on the UO dashboard.
Validation
util/validate-metadata.pypasses on the modified entry with zero errors and zero warnings, and produces a metadata grid byte-identical to the one from the unmodified entry.Running the OBO Dashboard code locally against UO's next release with this registry entry takes FP01 Open and FP09 Plurality of Users from ERROR to PASS.