Skip to content

Update Policy_for_OBO_namespace_and_associated_PURL_requests.md Library -> Foundry #2869

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 2 commits into from
Mar 24, 2026
Merged

Update Policy_for_OBO_namespace_and_associated_PURL_requests.md Library -> Foundry #2869

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8965a75
Update Policy_for_OBO_namespace_and_associated_PURL_requests.md
nataled Mar 24, 2026
377615c
Merge branch 'master' into nataled-patch-2
nataled Mar 24, 2026
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 docs/Policy_for_OBO_namespace_and_associated_PURL_requests.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ title: OBO Foundry membership requirements and technical details

# Expectations for OBO Membership

1. Participation in the OBO Foundry implies willingness to discuss your project and collaboratively develop it. You are strongly encouraged to build upon the existing suite of ontologies available in the [OBO library](http://obofoundry.org).
1. Participation in the OBO Foundry implies willingness to discuss your project and collaboratively develop it. You are strongly encouraged to build upon the existing suite of ontologies available in the [OBO Foundry](http://obofoundry.org).

2. We recommend projects be orthogonal to each other (i.e. no domain overlap). For those classes that are common across multiple resources (e.g., the class _cell_) we recommend importing terms from an already existing ontology. Application ontologies (those developed for specific data integration tasks) should reuse terms from existing OBO Foundry domain ontologies. At a minimum, we expect attribution of existing work, specifically through the use of PURLs for individual terms and ontologies.

Expand Down
Loading