Skip to content

Update fp-000-summary.md library->foundry #2858

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nataled merged 1 commit into from
Mar 10, 2026
Merged

Update fp-000-summary.md library->foundry #2858

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion principles/fp-000-summary.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ P10) <b>Commitment To Collaboration</b> - OBO Foundry ontology development, in c

P11) <b>Locus of Authority</b> - There should be a person who is responsible for communications between the community and the ontology developers, for communicating with the Foundry on all Foundry-related matters, for mediating discussions involving maintenance in the light of scientific advance, and for ensuring that all user feedback is addressed.

P12) <b>Naming Conventions</b> - The names (primary labels) for elements (classes, properties, etc.) in an ontology must be intelligible to scientists and amenable to natural language processing. Each primary label SHOULD be unique among OBO Library ontologies, and MUST be unique within its own ontology.
P12) <b>Naming Conventions</b> - The names (primary labels) for elements (classes, properties, etc.) in an ontology must be intelligible to scientists and amenable to natural language processing. Each primary label SHOULD be unique among OBO Foundry ontologies, and MUST be unique within its own ontology.

P13) <b>Notification of Changes</b> - Ontologies SHOULD announce major changes to relevant stakeholders and collaborators ahead of release.

Expand Down