This page records the original set of OBO Foundry principles as codified in 2006. For the current latest collection, see this page.

Version as of 24 April 2006

1. The ontology must be open and available to be used by all without any constraint other than (a) its origin must be acknowledged and (b) it is not to be altered and subsequently redistributed under the original name or with the same identifiers.

   The OBO ontologies are for sharing and are resources for the entire community. For this reason, they must be available to all without any constraint or license on their use or redistribution. However, it is proper that their original source is always credited and that after any external alterations, they must never be redistributed under the same name or with the same identifiers.

2. The ontology is in, or can be expressed in, a common shared syntax. This may be either the OBO syntax, extensions of this syntax, or OWL.

   The reason for this is that the same tools can then be usefully applied. This facilitates shared software implementations. This criterion is not met in all of the ontologies currently listed, but we are working with the ontology developers to have them available in a common OBO syntax.

3. The ontologies possesses a unique identifier space within the OBO Foundry.

   The source of a term (i.e. class) from any ontology can be immediately identified by the prefix of the identifier of each term. It is, therefore, important that this prefix be unique. For more details see the ID policy.

4. The ontology provider has procedures for identifying distinct successive versions.

5. The ontology has a clearly specified and clearly delineated content.

   The ontology must be orthogonal to other ontologies already lodged within OBO.

   The major reason for this principle is to allow two different ontologies, for example anatomy and process, to be combined through additional relationships. These relationships could then be used to constrain when terms could be jointly applied to describe complementary (but distinguishable) perspectives on the same biological or medical entity.

   As a corollary to this, we would strive for community acceptance of a single ontology for one domain, rather than encouraging rivalry between ontologies.

6. The ontologies include textual definitions for all terms.

   Many biological and medical terms may be ambiguous, so terms should be defined so that their precise meaning within the context of a particular ontology is clear to a human reader.

7. The ontology uses relations which are unambiguously defined following the pattern of definitions laid down in the OBO Relation Ontology.

8. The ontology is well documented.

9. The ontology has a plurality of independent users.

10. The ontology will be developed collaboratively with other OBO Foundry members.