Ontology Development Kit: a toolkit for building, maintaining, and standardising biomedical ontologies

Similar to managing software packages, managing the ontology life cycle involves multiple complex workflows such as preparing releases, continuous quality control checking, and dependency management. To manage these processes, a diverse set of tools is required, from command line utilities to powerf...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Veröffentlicht in:arXiv.org 2022-07
Hauptverfasser: Matentzoglu, Nicolas, Goutte-Gattat, Damien, Shawn Zheng Kai Tan, Balhoff, James P, Carbon, Seth, Caron, Anita R, Duncan, William D, Flack, Joe E, Haendel, Melissa, Harris, Nomi L, Hogan, William R, Charles Tapley Hoyt, Jackson, Rebecca C, Kim, HyeongSik, Kir, Huseyin, Larralde, Martin, McMurry, Julie A, Overton, James A, Peters, Bjoern, Pilgrim, Clare, Stefancsik, Ray, Sofia MC Robb, Toro, Sabrina, Vasilevsky, Nicole A, Walls, Ramona, Mungall, Christopher J, Osumi-Sutherland, David
Format: Artikel
Sprache:eng
Schlagworte:
Online-Zugang:Volltext
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
Beschreibung
Zusammenfassung:Similar to managing software packages, managing the ontology life cycle involves multiple complex workflows such as preparing releases, continuous quality control checking, and dependency management. To manage these processes, a diverse set of tools is required, from command line utilities to powerful ontology engineering environments such as ROBOT. Particularly in the biomedical domain, which has developed a set of highly diverse yet inter-dependent ontologies, standardising release practices and metadata, and establishing shared quality standards, are crucial to enable interoperability. The Ontology Development Kit (ODK) provides a set of standardised, customisable, and automatically executable workflows, and packages all required tooling in a single Docker image. In this paper, we provide an overview of how the ODK works, show how it is used in practice, and describe how we envision it driving standardisation efforts in our community.
ISSN:2331-8422
DOI:10.48550/arxiv.2207.02056