Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

To support practical application and mapping

...

Many ontologies in the Disease, Phenotype and Experimental Investigation domains have textual definitions (vocabulary) for class terms which makes them more likely to bring unique value for application. A high proportion of quality textual definitions will facilitate interoperability through mapping the meaning (semantics) of equivalence in different ontologies.

3.13. Naming conventions

Naming conventions used by ontology providers tend to be a heterogeneous and inconsistent. This is because names emerge often in an ad hoc manner rather than through an agreed nomenclature. Of course there are exceptions which are much more mature and consistent, such as the HUGO Gene Nomenclature Committee which provides the authoritative source of human gene names (http://www.genenames.org). Another excellent example is Chemical Entities of Biological Entities (ChEBI) which started as a curated nomenclature for small molecules and has developed into a mature ontology in the OBO Foundry. The OBO principle wiki page, FP_012_naming_conventions (http://wiki.obofoundry.org/wiki/index.php/FP_012_naming_conventions) is under development and mostly mentions the publication entitled "Survey-based naming conventions for use in OBO Foundry ontology development” by Schober et al 2009 (http://www.biomedcentral.com/1471-2105/10/125). This guideline aligns with Malone et al 2016 Rule 5: Textual Definitions Should Be Written for Domain Experts.

...

GuidelineOBO Principle10 Rules of Malone et al 2016

1.Format

http://www.obofoundry.org/principles/fp-002-format.html
2.URIshttp://wikiwww.obofoundry.org/wiki/index.php/FP_003_URIsprinciples/fp-003-uris.htmlRule 3: The Ontology Classes and Relationships Should Persist.
3.Versioninghttp://wikiwww.obofoundry.org/wiki/index.php/FP_004_versioningprinciples/fp-004-versioning.htmlRule 8: Previous Versions Should Be Available
4.Documentationhttp://wikiwww.obofoundry.org/wiki/index.php/FP_008_documentedprinciples/fp-008-documented.html
5.Usershttp://wikiwww.obofoundry.org/wiki/index.php/FP_009_usersprinciples/fp-009-users.htmlRule 6: The Ontology Should Be Developed by the Community but Not Incapacitated by It
6.Authorityhttp://wikiwww.obofoundry.org/wiki/index.php/FP_011_locus_of_authorityprinciples/fp-011-locus-of-authority.htmlRule 6: The Ontology Should Be Developed by the Community but Not Incapacitated by It
7.Maintenancehttp://wikiwww.obofoundry.org/wiki/index.php/FP_016_maintenanceprinciples/fp-016-maintenance.htmlRule 7: The Ontology Should Be under Active Development
8.Licensehttp://wikiwww.obofoundry.org/wiki/index.php/FP_001_openprinciples/fp-001-open.htmlRule 9: Open Data Requires Open Ontologies
9.Content delineation
http://wikiwww.obofoundry.org/wiki/index.php/FP_005_delineated_contentprinciples/fp-005-delineated-content.htmlRule 1: The Ontology Should Be about a Specific Domain of Knowledge
10.Content coveragehttp://www.obofoundry.org/principles/fp-005-delineated-content.htmlRule 2: The Ontology Should Reflect Current Understanding of Biological Systems
11.Content quality
Rule 2: The Ontology Should Reflect Current Understanding of Biological Systems
12.Textual definitionshttp://wikiwww.obofoundry.org/wiki/index.php/FP_006_textual_definitionsprinciples/fp-006-textual-definitions.htmlRule 4: Classes Should Contain Textual Definitions
13.Naming conventionshttp://wikiwww.obofoundry.org/wiki/index.php/FP_012_naming_conventionsprinciples/fp-012-naming-conventions.htmlRule 5: Textual Definitions Should Be Written for Domain Experts
14.Relationshttp://wikiwww.obofoundry.org/wiki/index.php/FP_007_relationsprinciples/fp-007-relations.html
15.Conserved URIshttp://www.obofoundry.org/principles/fp-010-collaboration.html

6. References