forked from OBOFoundry/OBOFoundry.github.io
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
581effb
commit f189d31
Showing
1 changed file
with
2 additions
and
2 deletions.
There are no files selected for viewing
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -13,8 +13,8 @@ <h1>The OBO Foundry</h1> | |
|
|
||
| <div class="alert alert-info" role="alert"> | ||
| <p>The OBO Foundry is a collective of ontology developers that are committed to collaboration and adherence to shared principles. The mission of the OBO Foundry is to develop a family of interoperable ontologies that are both logically well-formed and scientifically accurate. To achieve this, OBO Foundry participants voluntarily adhere to and contribute to the development of an evolving set of principles including <a href="/principles/fp-001-open.html">open use</a>, <a href="/principles/fp-010-collaboration.html">collaborative development</a>, <a href="/principles/fp-005-delineated-content.html">non-overlapping and strictly-scoped content</a>, and common <a href="/principles/fp-002-format.html">syntax</a> and <a href="/principles/fp-007-relations.html">relations</a>, based on ontology models that work well, such as the Gene Ontology (GO).</p> | ||
| <p>The OBO Foundry is overseen by an Operations Committee with [Editorial])http://obofoundry.org/docs/EditorialWG.html), <a href="http://obofoundry.org/docs/TechnicalWG.html">Technical</a> and <a href="http://obofoundry.org/docs/OutreachWG.html">Outreach</a> working groups. The processes of the Editorial working group are modelled on the journal refereeing process. A complete treatment of the OBO Foundry is given in <a href="http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2814061/">"The OBO Foundry: coordinated evolution of ontologies to support biomedical data integration"</a>.</p> | ||
| <p>On this site you will find a table of ontologies, available in several formats, with details for each, and documentation on <a href="http://obofoundry.github.io/principles/fp-000-summary.html">OBO Principles</a>.</p> | ||
| <p>The OBO Foundry is overseen by an Operations Committee with <a href="/docs/EditorialWG.html">Editorial</a>, <a href="/docs/TechnicalWG.html">Technical</a> and <a href="/docs/OutreachWG.html">Outreach</a> working groups. The processes of the Editorial working group are modelled on the journal refereeing process. A complete treatment of the OBO Foundry is given in <a href="http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2814061/">"The OBO Foundry: coordinated evolution of ontologies to support biomedical data integration"</a>.</p> | ||
| <p>On this site you will find a table of ontologies, available in several formats, with details for each, and documentation on <a href="/principles/fp-000-summary.html">OBO Principles</a>.</p> | ||
| <p>You can contribute to this site using GitHub <a href="https://github.com/OBOFoundry/OBOFoundry.github.io">OBOFoundry/OBOFoundry.github.io</a> or get in touch with us at <a href="mailto:[email protected]">[email protected]</a>.</p> | ||
| </div> | ||
| </div> | ||
|
|
||