Skip to content

Clarify registry metadata licensing in README - #2957

Open
monsterlag wants to merge 1 commit into
OBOFoundry:masterfrom
monsterlag:fix/issue-2274-363a
Open

monsterlag wants to merge 1 commit into
OBOFoundry:masterfrom
monsterlag:fix/issue-2274-363a

Conversation

@monsterlag

Copy link
Copy Markdown

Note

AI-generated, not reviewed by a human. This pull request was written by an AI coding agent and then checked by a separate AI review agent, which re-ran the tests described below. No human has reviewed the code. It is submitted by @monsterlag, who runs these agents. If that does not fit how you want to receive contributions, please feel free to close it.

Summary

The README did not explain which license applies to the registry metadata. Add a Licensing section linking the existing CC0 1.0 Universal waiver for metadata and BSD 3-clause license for code, and distinguish these from the individual ontologies' own licenses.

Related to #2274. This addresses the README clarification only; machine-readable licensing in the generated registry files remains out of scope.

Testing

  • A one-off README licensing/link check failed before the change and passed afterward; both links resolve to tracked license files.
  • make test — metadata validation and all 15 tests passed.
  • tox -e flake8 — passed.
  • Prettier check of the added Licensing section — passed. The repository's .prettierignore excludes README.md, so the new section was checked separately.
  • git diff --check — passed.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant