Skip to main content
PLOS ONE logoLink to PLOS ONE
. 2024 Jan 18;19(1):e0285093. doi: 10.1371/journal.pone.0285093

Coordinating virus research: The Virus Infectious Disease Ontology

John Beverley 1,2,*, Shane Babcock 2,3, Gustavo Carvalho 4, Lindsay G Cowell 5, Sebastian Duesing 6, Yongqun He 7, Regina Hurley 2,8, Eric Merrell 1,2, Richard H Scheuermann 9,10,11, Barry Smith 1,2
Editor: Barry L Bentley12
PMCID: PMC10796065  PMID: 38236918

Abstract

The COVID-19 pandemic prompted immense work on the investigation of the SARS-CoV-2 virus. Rapid, accurate, and consistent interpretation of generated data is thereby of fundamental concern. Ontologies–structured, controlled, vocabularies–are designed to support consistency of interpretation, and thereby to prevent the development of data silos. This paper describes how ontologies are serving this purpose in the COVID-19 research domain, by following principles of the Open Biological and Biomedical Ontology (OBO) Foundry and by reusing existing ontologies such as the Infectious Disease Ontology (IDO) Core, which provides terminological content common to investigations of all infectious diseases. We report here on the development of an IDO extension, the Virus Infectious Disease Ontology (VIDO), a reference ontology covering viral infectious diseases. We motivate term and definition choices, showcase reuse of terms from existing OBO ontologies, illustrate how ontological decisions were motivated by relevant life science research, and connect VIDO to the Coronavirus Infectious Disease Ontology (CIDO). We next use terms from these ontologies to annotate selections from life science research on SARS-CoV-2, highlighting how ontologies employing a common upper-level vocabulary may be seamlessly interwoven. Finally, we outline future work, including bacteria and fungus infectious disease reference ontologies currently under development, then cite uses of VIDO and CIDO in host-pathogen data analytics, electronic health record annotation, and ontology conflict-resolution projects.

Introduction

The value of cross-discipline meta-data analysis has been evident in the COVID-19 pandemic. Early in the pandemic, for example, prostate oncologists [1, 2] attempted to leverage existing research on enzymes crucial in host cell penetration by SARS-CoV-2 to explain differences in disease severity across sex [3, 4]; immunologists combined insights from research on SARS-CoV-1 and MERS-CoV with chemical compound profiles to identify treatment options for SARS-CoV-2 [57]; pediatric researchers, observing that children have fewer nasal epithelia susceptible to SARS-CoV-2 infection than adults, suggested this difference may explain symptom disparities between the two groups [8, 9]. The sheer volume of data collected by life-science researchers, the speed at which it is generated, range of its sources, quality, accuracy, and urgency of need for assessment of usefulness, has resulted in complex, multidimensional datasets, often annotated using discipline- or institution-specific terminologies and coding systems that lead to data silos [1012].

Data silos emerge in life science research when data concerning an area of research is stored in a manner that makes it accessible to one group, but inaccessible to others. The use of proprietary information systems, differing storage methods, and distinct coding standards across life science that is characteristic of such silos undermines interoperability, meta-data analysis, pattern identification, and discovery across disciplines [13, 14]. Ontologies–interoperable, logically well-defined, controlled vocabularies representing common entities and relations across disciplines using consensus terminologies–constitute a well-known solution to these problems through mitigation of the formation of data silos. The need for rapid analysis of evolving datasets representing coronavirus research motivated the development of the Virus Infectious Disease Ontology (VIDO; https://bioportal.bioontology.org/ontologies/VIDO), comprised of textual definitions for terms and relations and logical axioms supporting automated consistency checking, querying over datasets, and interoperability with other ontologies. VIDO is an extension of the widely-used Infectious Disease Ontology Core (IDO Core; https://bioportal.bioontology.org/ontologies/IDO) [15, 16], which comprises terminological content common to all investigations of infectious disease. VIDO extends IDO with terms specific to the domain of infectious diseases caused by viruses and provides a foundation for ontologies representing specific viral infectious diseases, such as COVID-19.

VIDO is available under the Creative Commons Attribution 4.0 license (https://creativecommons.org/licenses/by/4.0/) and its current and past versions can be found at the National Center for Biomedical Ontology (NCBO) Bioportal [17], the Ontobee repository (http://www.ontobee.org/), and the Ontology Lookup Service (https://www.ebi.ac.uk/ols/index). VIDO was developed in collaboration with relevant domain experts, including immunologists and virologists, and by drawing on the expertise of the IDO developers to ensure alignment with principles outlined by the Open Biological and Biomedical Ontology (OBO) Foundry [18], thereby supporting interoperability with existing Foundry ontologies [19]. VIDO development is a transparent process, with all discussions available on GitHub (https://github.com/infectious-disease-ontology-extensions). All aspects of development, including addition of new terms, are driven by the needs of researchers investigating viruses and nearby domains. The ontology is thus not viewed as exhaustive of the domain of virus research but remains sensitive to evolving knowledge.

Methods

OWL, Protégé, Mace4, and Prover9

VIDO is formally represented in the OWL2 Web Ontology Language (https://www.w3.org/TR/owl2-overview/). OWL2 is an expansion of the Resource Description Framework (RDF; https://www.w3.org/TR/rdf-primer/) and of RDF Schema, which represent data as sets of subject- predicate-object directed graphs, and which can be queried using the SPARQL Protocol and RDF Query Language (https://www.w3.org/TR/sparql11-query/). OWL2 supplements these languages by allowing for description of classes, members of classes, relations among individuals, and annotation properties. Formally, the OWL2 vocabulary can be mapped to a decidable fragment of first-order logic, meaning there is an algorithm which can determine the truth-value for any statement expressed in the language in a finite number of steps [20]. Restricting expressions to a decidable language allows automated consistency and satisfiability checking [21]. VIDO was developed using the Protégé-OWL editor (https://protege.stanford.edu/) and tested against OWL reasoners such as HermiT [22] and Pellet [23]. Additionally, logical axioms underwriting these ontologies were translated into the Common Logic Interchange Format, and subsequently evaluated using the Mace4 model checker and Prover9 proof generator within the Macleod toolkit (https://github.com/thahmann/macleod).

Alignment with OBO Foundry ontologies

Ontologies are widely used in bioinformatics, supporting data standardization, integration, sharing, reproducibility, and automated reasoning. The Gene Ontology (GO; https://bioportal.bioontology.org/ontologies/GO), for example, maintains species-neutral annotations of gene products and functions, and since its inception in 1998 it has inspired an explosion of biomedical ontologies covering all domains of the life sciences [19, 24, 25]. These early developments led to worries, however, that data silos–the very problem ontologies were designed to address–might reemerge [10] as researchers developed ontologies using concepts local to their discipline. By 2007, the Open Biomedical and Biological Ontologies (OBO) Foundry [18] was created to provide guidance for ontology developers and promote alignment and interoperability. OBO Foundry design principles require that ontologies: use a well-specified syntax that is unambiguous, with a common space of identifiers; that they be openly available in the public domain, have a specified scope, be developed in a modular fashion in a collaboration with ontologists covering nearby domains, and import a common set of relations from the Relations Ontology (RO; https://obofoundry.org/ontology/ro.html). The OBO library (http://obofoundry.org/) presently consists of over 250 ontologies, including some externally developed ontologies such as the NCI Thesaurus (https://ncithesaurus.nci.nih.gov/ncitbrowser/) and the NCBI Taxonomy (https://www.ncbi.nlm.nih.gov/taxonomy). It also contains some constructed ab initio to satisfy OBO principles. At its core is Basic Formal Ontology (BFO; https://bioportal.bioontology.org/ontologies/BFO), a top-level ontology covering general classes such as material entity, quality, process, function and role [10, 2629] which provides the architecture “on which OBO Foundry ontologies are built.” BFO is, moreover, an ISO/IEC approved standard 21838–2 (https://www.iso.org/standard/74572.html).

Where BFO is domain-neutral, other OBO Foundry ontologies represent types of entities in more specific domains, using terms such as disease, cell division, surgical procedure, and so forth. Ideally, domain ontologies are constructed using a methodology for formulating definitions through a process of downward population from BFO. The resulting alignment with BFO, and the conformance to OBO Foundry principles, foster integration across ontologies. VIDO was designed with alignment and conformance in mind. Development of each ontology follows metadata conventions adopted by many OBO Foundry ontologies [30]. These conventions require that every term introduced into the ontology has a unique IRI, textual definitions, definition source, designation of term editor(s), and preferred term label. In the interest of coordinating development with existing OBO ontologies, VIDO developers imported terms where possible from existing OBO library ontologies and constructed logical definitions using imported terms. Development was guided by best practices for definition construction [10, 31]. New primitive terms were introduced when needed after consultation with domain experts, review of relevant literature, and careful examination of the OBO library to avoid redundancy.

Hub and spokes approach

VIDO follows the “hub and spokes” methodology [32, 33] for ontology development. That is, VIDO is a spoke ontology, extending from the Infectious Disease Ontology Core (IDO Core; https://bioportal.bioontology.org/ontologies/IDO) as its hub. IDO Core is an OBO ontology consisting of terms, relations, natural language definitions and associated logical axioms representing phenomena common across research in infectious diseases [15]. IDO Core has long provided a base from which more specific infectious disease ontologies extend, and it has been recently updated to keep pace with scientific and top-level architecture changes [16]. Extensions of IDO Core covering specific infectious diseases are created, first, by importing needed terms from IDO Core and other OBO Foundry ontologies, and second, by constructing the domain-specific terms where needed to adequately characterize entities in the relevant domain. Fig 1 illustrates example extensions, such as the Brucellosis Infectious Disease Ontology (IDOBRU; https://bioportal.bioontology.org/ontologies/IDOBRU) the Influenza Infectious Disease Ontology (IDOFLU; https://bioportal.bioontology.org/ontologies/FLU), and more recently the Coronavirus Infectious Disease Ontology (CIDO; https://bioportal.bioontology.org/ontologies/CIDO). Each aims to be semantically interoperable with OBO library ontologies [11, 3436]. VIDO was designed to occupy the ontological space between such virus-specific ontologies and IDO Core. As a result, more specific virus-related ontologies such as CIDO [37] and IDOFLU are being curated to extend directly from VIDO, rather than directly from IDO Core.

Fig 1. Relationships among BFO, GO, OGMS, IDO Core, and OBI.

Fig 1

Results

The Virus Infectious Disease Ontology

VIDO takes IDO Core as its starting point, but also imports terms relevant to the domain of viruses from several other OBO Foundry ontologies, such as GO, the Ontology for General Medical Science (OGMS; https://bioportal.bioontology.org/ontologies/OGMS) and the Ontology for Biomedical Investigation (OBI; https://bioportal.bioontology.org/ontologies/OBI) [14]. The color- coded Fig 1 illustrates several importing relationships which provide the basis for VIDO definitions which we examine in what follows.

Acellular structure

Like IDO Core, VIDO imports from OGMS. Examples of such imported terms are:

disorder = def Material entity that is a clinically abnormal part of an extended organism.

A part of a material entity is “clinically abnormal” if it is not expected in the life plan for entities of the relevant type and is causally linked to elevated risk–that is, risk exceeding some threshold–of illness, death, or disfunction [38]. Extended organism is imported from OGMS and organism from OBI, where they are defined as follows:

extended organism = def An object aggregate consisting of an organism and all material entities located within the organism, overlapping the organism, or occupying sites formed in part by the organism.

organism = def A material entity that is an individual living system, such as animal, plant, bacteria, or virus, that is capable of replicating or reproducing, growth and maintenance in the right environment. An organism may be unicellular or made up, like humans, of many billions of cells divided into specialized tissues and organs.

Here we run into the first of several ontological puzzles that emerged while developing VIDO. On the one hand, this definition aligns with common usage of the term “organism” among researchers for whom its instances are cellular entities [39, 40]. On the other hand, the textual definition includes viruses among its instances, which are in every case acellular. Debates over organism (https://github.com/OBOFoundry/COB/issues/6) among ontology developers have resulted in deprecation of the OBI term in favor of a nearby term from the Common Anatomy Reference Ontology (https://bioportal.bioontology.org/ontologies/CARO) with the label: organism or virus or viroid. At first glance, this appears to avoid the preceding worries, but further inspection reveals that this class is annotated as being an “exact synonym” of organism, and so suffers from the same issues raised above. Even if we put aside this latter issue, however, there are still two further concerns. First, introducing disjunctive classes is ad hoc [10]. Second, this disjunctive class leads naturally to debates over whether viruses are alive, since it classifies viruses alongside paradigmatic living entities. Decades of discussion have not resolved this question [4146], and it is not obvious that we need an answer for the purposes of ontological modelling. It is unclear where consensus will land; in the interest of future-proofing our ontologies we should provide virus content in a way that neutral in regard to this issue to the maximal extent that this is possible. Rather than introduce an ad hoc disjunctive class, IDO Core, VIDO, and CIDO developers collaborated to add the following classes to IDO Core [47]:

self-replicating organic structure = def Object consisting of an organic structure that is able to initiate replication of its structure in a host.

acellular self-replicating organic structure = def Self-replicating organic structure comprised of acellular organic parts.

Which is imported to VIDO as the parent class of the term virus. The term virus is imported from the NCBITaxon [48] (https://bioportal.bioontology.org/ontologies/NCBITAXON), alongside terms relevant to virology, such as prion and satellite.

Virus

The NCBITaxon provides an extensive list of life science terms, but it has its limitations. As discussed in [16], NCBITaxon categorizes virus terms using the International Committee on Taxonomy of Viruses (ICTV). While an impressive taxonomy, the ICTV exhibits gaps in virus classification [49, 50]. Additionally, NCBITaxon combined with standard ontology engineering tools such as Ontofox (http://ontofox.hegroup.org/) [51] often leads to ontology developers importing superfluous portions of ICTV structured hierarchies, resulting in overwhelming taxonomies that are challenging for users to navigate. Fig 2 illustrates such a taxonomy found in IDOBRU, but importing an entire ICTV hierarchy is not uncommon (see for example the Schistosomiasis Ontology (IDOSCHISTO) [16]). Lastly, the NCBITaxon does not provide textual definitions for most terms within its scope. As stated, we seek to respect OBO Foundry metadata conventions [30] and ontology engineering best practices [10, 31]; consequently, virus and other terminological content in VIDO must have textual definitions supplied.

Fig 2. NCBITaxon imported to IDOBRU, located on Bioportal.

Fig 2

Standard definitions of “virus” provide a starting point for a textual definition, but caution is once again needed. Viruses are often described as obligate pathogens [52, 53], since virus replication requires host machinery for production and assembly of viral components. However, defining a class virus solely in terms of what viruses typically do runs the risk of overlooking what viruses are, materially speaking. Compare: Homo sapiens are obligate aerobes, but this is no definition of the class. Insofar as we are defining the virus class, it is better to attend to genetic and structural components common to all viruses, and best to define the material entity in a way that captures obligate pathogenicity. VIDO accordingly defines:

virus = def Acellular self-replicating organic structure with RNA or DNA genetic material which uses host metabolic resources for RNA or DNA replication.

VIDO developers have contacted NCBITaxon developers proposing that the definitions we provide below be added to respective NCBITaxon terms. Other requests have been submitted, for example, to update the label of the NCBITaxon term from “Viruses” to “virus” in order to avoid ambiguous reference between classes and their instances [10].

Rather than import in accordance with the ICTV taxonomy, subclasses of virus are imported from NCBITaxon in alignment with the Baltimore Classification [54], which groups viruses into seven exhaustive classes based on genetic structure. For example, one subclass of virus is:

positive-sense single-stranded RNA virus = def Virus with genetic material encoded in single-stranded RNA that can be translated directly into proteins.

Which is a class representing one of the seven Baltimore Classification categories. These Baltimore Classification classes provide parent classes from which terms for more specific viruses can extend. Fig 3 illustrates how the Baltimore Classification appears in the Protégé visualization of the class positive-sense single-stranded RNA virus alongside viral replication pathways underwritten by genetic differences in viruses.

Fig 3. VIDO representation of the Baltimore Classification in Protégé Editor.

Fig 3

By incorporating the Baltimore Classification, we provide developers of virus-specific domain ontologies an ontological representation of viruses that is simpler and easier to navigate than the ICTV, which currently underwrites the NCBITaxon.

VIDO subclasses of virus include those common in virology research, such as bacteriophage–viruses that infect bacteria–virophage–viruses that infect viruses–oncovirus–viruses that cause cancer–and mycovirus–viruses that infect fungi. As well as:

virion = def Virus that is in its assembled state consisting of genomic material (DNA or RNA) surrounded by coating molecules.

Some researchers use “virion” and “virus” synonymously [55]. Some define “virion” so that instances only exist outside host cells [56], or they distinguish virions outside host cells from those inside host cells, calling the former “mature virions.” Some claim “virion” is best understood as analogous to a sperm cell [57, 58]. Ontologically speaking, one might model the relationship between a virus and its virion in a variety of ways: virion is to a virus as human infant is to human, or as human student is to human, or as human gamete is to human. Treating virions as akin to gametes is uncommon among researchers. Between the remaining options, we adopt the first, treating virion as a type of virus, since adopting the alternative would suggest a virion is simply a virus that is in a specific context, a result that overlooks the importance of genomic assembly to identifying virions.

Incidentally, some viruses do not replicate faithfully, perhaps resulting in genetically distinct mutants or–in extreme cases–an inactive aggregate of virion components. Virus mutations may undermine host immune system recognition of viral threats, as evidenced by the difficulty in developing vaccines for certain influenza strains. If there are too many mutations, however, then a virus may lose its ability to replicate, an observation used in development of treatments for polio and hepatitis C which exacerbate respective virus mutations [59, 60]. VIDO thus provides the term:

disordered virus = def Acellular self-replicating organic structure having some clinically abnormal arrangement of viral components (e.g. viral capsid, viral DNA/RNA).

Viruses falling in this class may be associated with diseases much different from those associated with viruses that do not exhibit disorder. Terms for viral components are imported to VIDO: from GO, viral nucleocapsid, viral capsid, capsomere, viral envelope; from the Chemical Entities of Biological Interest (ChEBI) ontology (https://bioportal.bioontology.org/ontologies/CHEBI) [61, 62], nucleic acid and ribonucleic acid; from the Protein Ontology (https://bioportal.bioontology.org/ontologies/PR), protein and viral protein.

Infectious structure

The term “pathogen” is indexed to species or to stages in the developmental cycle of a species. A given virus may engage in mutual symbiosis with one species, while exhibiting pathogenic behavior towards others [63, 64]. Mature plants are often susceptible to different pathogens than developing plants [6568]. We capture virus pathogenicity in VIDO in steps. From IDO Core [16], we import dispositions borne by pathogens and infectious agents, as follows:

pathogenic disposition = def Disposition borne by a material entity to establish localization in, or produce toxins that can be transmitted to, an organism or acellular structure, either of which may form disorder in the entity or immunocompetent members of the entity’s species.

infectious disposition = def Pathogenic disposition borne by a pathogen to be transmitted to a host and then become part of an infection in that host or in immunocompetent members of the same species as the host.

The class infectious agent in IDO Core is a subclass of organism, and so cannot include instances of virus. To address this issue, the term infectious structure was developed to parallel the IDO Core term infectious agent and to provide a logically defined subclass of acellular self-replicating organic structure. The term infectious disposition bridges infectious acellular structures and infectious organisms since instances of each bear an infectious disposition. Moreover, the logical definitions of infectious structure and infectious agent are such that, though the former is a defined subclass of acellular self-replicating organic structure and the latter a subclass of organism, they are both inferred subclasses of pathogen.

As discussed in [16], establishment of localization used in pathogenic disposition is characterized using the IDO Core term establishment of localization in host representing tethering or adhesion to a host, while “formation of disorder” abbreviates appearance of disorder, which is a process that results in formation of a disorder. The definition of pathogenic disposition is meant to reflect a temporal ordering between establishment of localization and appearance of disorder. This is reflected explicitly in the logical axioms associated with the class. Similarly, in the definition of infectious disposition there is an intended temporal ordering between transmission to a host–represented by pathogen transmission process imported from the Pathogen Transmission Ontology (https://bioportal.bioontology.org/ontologies/PTRANS)–and becoming part of an infection–represented by the IDO Core process of establishing an infection. A pathogen bearing an infectious disposition that generates disorder in a host will have been transmitted to the host prior to establishing localization in the host and will have established an infection prior to the appearance of disorder.

The complexity of the definitions of pathogenic disposition and infectious disposition reflect the variety of pathogen examples documented in contemporary literature. Consider S. aureus, an opportunistic pathogen [56] in humans. We count S. aureus as a pathogen, even when it does not realize disorder in a host, since it is nevertheless disposed to localize in a human host and generate disorder if given the opportunity. This is a BFO disposition of S. aureus as it is an “internally-grounded” property of the entity [32]. That is, it is part of the material basis of S. aureus to generate disorder in human hosts if given the chance. This is analogous to the way salt has a disposition to dissolve, based on its lattice structure, independently of whether it ever realizes this disposition. Opportunistic pathogens are not pathogens because of an opportunity; they are pathogens because they are disposed to localize and cause disorder in a host.

Consider now, C. botulinum, a pathogen which produces a toxin and which may produce a spore ingested by humans. This bacterium is a pathogen for adult humans since the toxins often result in disorder when ingested. Furthermore, C. botulinum may cause infection in human infants if, say honey colonized by C. botulinum is ingested. The sugar content of honey inhibits C. botulinum growth, but in the low-oxygen, low-acid intestines of human infants, spores can localize, grow, and produce toxins resulting in disorder. Thus, C. botulinum counts as a human infant pathogen. Nevertheless, because C. botulinum is not itself disposed to invade or be transmitted to human infants, we do not say the bacterium is infectious [69]. Being part of an infection is not itself sufficient for something to be counted as infectious. Pathogens bearing an infectious disposition must be disposed to both transmit and become part of an infection. Many opportunistic pathogens, for example, are not infectious.

Consider lastly, the respective definitions of infectious disposition and pathogenic disposition address instances where mutations in hosts may block realization of disorder or infection. In such cases, an infectious pathogen may nevertheless be transmissible and cause disorder or infection in others. For example, HIV-1 is a pathogen that may localize in a host with CCR-5 mutations [70] that block the virus from attaching to host cells, and so block pathogenesis to AIDS. Similarly, P. falciparum may be transmitted to a host with a sickle-cell trait that blocks manifestation of the disease malaria [71, 72]. However, P. falciparum and HIV-1 count as pathogens even if they do not result in the formation of disorders for hosts with a sickle-cell trait or CCR-5 mutation, respectively. IDO Core reflects this characterization. Each pathogen may be transmitted to immunocompetent members of the same species as the host, and so count as bearing instances of infectious disposition and pathogenic disposition. Note, the fact that P. falciparum and HIV-1 do not result in the formation of disorders in hosts with sickle-cell traits or CCR-5 mutations should not suggest that there are no clinical abnormalities associated with these traits or mutations. Individuals with, say, CCR-5 mutations do exhibit clinical abnormalities, and so do exhibit disorders. But these disorders are due to the CCR-5 mutation rather than the HIV-1 infection.

Whenever an infectious disposition is realized, this is always in some site in a host, via some transmission to that host, and some generation of infection and disorder in that host. Infectious structures–such as viruses–bear this disposition. For example, each SARS-CoV-2 virus is disposed to be transmitted to hosts, localize, cause infection, and result in disorder.

Pathogen host

Until recently, microbiologists, immunologists, virologists, and others studying pathogenesis have engaged in either host-centered or pathogen-centered pathogenesis research [7377]. Each approach has led to impressive research results. But emphasizing one aspect of host-pathogen interactions at the expense of the other may leave valuable questions unanswered [78]. Emphasis, for example, solely on pathogenic factors of SARS-CoV-2 will provide only a partial explanation of various pathogenesis pathways observed in clinical settings. IDO Core and VIDO prioritize neither host nor pathogen in representation of pathogens and associated diseases, adopting the Damage Response Framework (DRF) for guidance in development of relevant terms [7982]. According to the DRF, pathogenesis results from interactions between both host and pathogen interacting primarily through host damage, which is a function of the intensity and degree of host response and pathogen factors. Host and pathogen interactions thus influence manifestations of signs, symptoms, and disease. IDO Core now defines hosts and pathogens in terms of roles and allows that acellular structures may also be pathogen hosts, such as when a virus hosts a virophage:

host role = def Role borne by either an organism whose extended organism contains a distinct material entity, or an acellular structure containing a distinct material entity, realized in use of that structure or organism as a site of reproduction or replication.

pathogen host role = def Host role borne by an organism or acellular structure having a pathogen as part.

Following BFO, roles are “externally grounded” realizable entities that may be gained or lost based on circumstance without necessarily involving material change to their bearer, such as the role a student acquired once enrolled in a university.

The Symptom Ontology (https://bioportal.bioontology.org/ontologies/SYMP) provides a extensive terminological content for representing symptoms owing to viral infection, such as fever, taste alteration, and so on [83]. Given the importance of asymptomatic carriers in viral infection spread, moreover, attention is also given in IDO Core to:

symptomatic carrier role = def Pathogen host role borne by an organism whose extended organism contains a pathogen bearing an infectious disposition towards the host, and the host has manifested symptoms of the infectious disease caused by the pathogen.

asymptomatic carrier role = def Pathogen host role borne by an organism whose extended organism contains a pathogen bearing an infectious disposition towards the host, and the host has no symptoms of the infectious disease caused by the pathogen.

subclinical infection = def Infection that is part of an asymptomatic carrier.

The definition of the term subclinical infection reflects standard use of the terms “subclinical” and “asymptomatic” while allowing for asymptomatic clinically abnormal infections. VIDO extends subclinical infection to subclinical virus infection, namely, those subclinical infections caused by a virus. These remarks bring us full circle to the term disorder introduced above, since clinical abnormality is associated with disorder. When that disorder stems from infection it counts as an:

infectious disorder = def Disorder that is part of an extended organism which has an infectious pathogen part, that exists as a result of a process of formation of disorder initiated by the infectious pathogen.

And when the adverted pathogen is a virus, it falls in the VIDO class:

virus disorder = def Infectious disorder that exists as a result of a process of formation of disorder initiated by a virus.

Viral disease

Medical researchers draw a distinction between symptoms and signs, a distinction which OBO Foundry ontologies respect (from OGMS [38]):

symptom = def Process experienced by the patient which can only be experienced by the patient, that is hypothesized to be clinically relevant.

qualitative sign = def Abnormal observable quality of a part of a patient that is hypothesized to be clinically relevant.

processual sign = def Abnormal processual entity occurring in a patient that is hypothesized to be clinically relevant.

An asymptomatic carrier infected with SARS-CoV-2 likely exhibits signs indicating that the infection is clinically abnormal, such as ground-glass opacities. Such asymptomatic carriers exhibit an instance of the VIDO class virus disorder which is the material basis of a viral disease:

infectious disease = def Disease whose physical basis is an infectious disorder.

viral disease = def Infectious disease inhering in a virus disorder that is a disorder due to the presence of the virus.

Worth noting is that these definitions are consistent with the CDC’s case criteria definitions adopted between April 5, 2020 and February 28, 2023, which indicate that the presence of the SARS-CoV-2 genome or relevant antigens in an individual is sufficient to count as a case of COVID-19, asymptomatic or not [8486]. A viral disease may be realized in a disease course:

infectious disease course = def Disease course that is the realization of an infectious disease.

viral disease course = def Infectious disease course whose physical basis is a virus disorder that is clinically abnormal in virtue of the presence of the relevant virus.

Here infectious disease and infectious disease course are imported from IDO Core, and are subclasses, respectively, of disease and disease course, which are imported from OGMS.

Viral epidemiology

Changes in viral disease and infection incidence are among the targets of epidemiological investigation. VIDO imports from IDO Core:

infectious disease incidence = def Quality that inheres in an organism population and is the number of realizations of an infectious disease for which the infectious disease course begins during a specified period.

infectious disease incidence rate = def Quality that inheres in an organism population and is the infectious disease incidence proportion per unit time.

infectious disease incidence proportion = def Quality that inheres in an organism population and is the proportion of members of the population not experiencing an infectious disease course at the beginning of a specified period and in whom the infectious disease begins during the specified period.

organism population = def Aggregate of organisms of the same species.

Additionally, VIDO imports from IDO Core other important epidemiological terms, such as infection prevalence, infectivity, and infectious disease mortality rate. Each are specifically dependent entities inhering in some material entity, though not always in some organism population. For example, infectivity is a quality inhering in instances of pathogen. Additionally, VIDO imports from IDO Core:

infection incidence = def Quality that inheres in an organism population and is the number of organisms in the population that become infected with a pathogen during a specified period.

on which infectious disease incidences depend, as infectious disease realizations require infection.

A quality process profile is a type of process which tracks changes of specific qualities in material entities over time [26]. For example, a patient’s temperature will likely fluctuate over time, as will many other qualities of the patient. The specific fluctuations of temperature in the patient over time is a process profile, which reflects common abstractions used in clinical diagnosis and testing and manifesting in charts prepared from time-series data. Changes in qualities of clinical interest may follow several patterns, each of which can be defined as a subclass of process profile. A patient’s temperature may exhibit a linear increase followed by a linear decrease. Similarly, there are process profile instances of cyclical patterns, for instance the seasonal patterns of influenza [87]. Such patterns can be tracked in VIDO by classes such as:

viral disease incidence profile = def Infectious disease incidence profile comprised of a series of determinate viral disease incidence qualities caused by a specific virus in a population over time.

viral disease incidence proportion profile = def Infectious disease incidence proportion profile comprised of a series of viral disease incidence proportion qualities caused by a specific virus per unit time.

viral disease incidence rate profile = def Infectious disease incidence rate profile comprised of a series of viral disease rate qualities caused by a specific virus per unit time.

Extending VIDO to CIDO

VIDO serves as a bridge between IDO Core and the IDO extension ontologies representing specific viral diseases. Of particular importance during the pandemic has been the Coronavirus Infectious Disease Ontology (CIDO; https://bioportal.bioontology.org/ontologies/CIDO), developed by the He Group at the University of Michigan. CIDO provides terminological content that facilitates representations of coronavirus genome, protein structures, epidemiological surveillance, vaccine development, and treatment options. The ontology has been used to annotate data pertaining to 136 known anti-coronavirus drugs [6], as well as in the identification of approximately 110 candidate drugs [7] for potential drug repurposing projects with respect to COVID-19 [88]. More recently, CIDO has been employed as a general framework for understanding host-pathogen interactions [78]. IDO Core, VIDO, and CIDO development teams work together closely in the interest of ensuring ontology alignment.

CIDO will extend from VIDO by adopting, among other terms:

coronavirus disease = def Viral disease inhering in a coronavirus disorder.

coronavirus disease course = def Viral disease course that is the realization of some coronavirus disease and has as a participant a coronavirus.

This extension example illustrates a downward population recipe useful for aligning CIDO terms to VIDO, by starting with a given virus term from the latter, and restricting subclasses based on features of coronaviruses and associated diseases. Moreover, common coronavirus features can be reused from OBO ontologies to complement the CIDO characterization of the virus, such as the viral envelop glycoprotein spikes [89, 90]. Some such terms are specializations of terms from the Protein Ontology (https://bioportal.bioontology.org/ontologies/PRO), e.g. spike glycoprotein (SARS- CoV-2). CIDO covers existing and novel coronaviruses in general, and so provides resources for detailed comparison of coronavirus biological profiles. Fig 4 illustrates various links between VIDO and CIDO, and the IDO Core and GO ontologies.

Fig 4. Relationships among GO, IDO Core, VIDO, and CIDO.

Fig 4

SARS-CoV-2 pathogenesis

Characterizing pathogenesis to COVID-19 is aided by terms such as:

COVID-19 = def Coronavirus disease inhering in a SARS-CoV-2 disorder.

COVID-19 disease course = def Coronavirus disease course that is the realization of some COVID-19 disease and has participant SARS-CoV-2.

Ontologically precise representation of COVID-19 pathogenesis is crucial for understanding the range of symptoms and signs which appear across demographics [9194]. Ontological representation of COVID-19 pathogenesis is aided by reusing OBO Foundry ontology terms, resulting in the following definition:

SARS-CoV-2 pathogenesis = def Coronavirus pathogenesis process realization of an infectious

disposition inhering in SARS-CoV-2 or a SARS-CoV-2 population, having at least the proper process parts:

  1. pathogen transmission,

  2. establishment of localization in host,

  3. process of establishing an infection, and

  4. appearance of a virus disorder.

Instances of SARS-CoV-2 pathogenesis are asserted as part of some COVID-19 disease course. The term coronavirus pathogenesis will ultimately be imported to CIDO, as a subclass of the VIDO term viral pathogenesis, itself a subclass of:

pathogenesis = def Process that generates the ability of a pathogen to induce disorder in an organism.

which is imported from GO. As defined, pathogenesis is a success term [25], in that it encompasses formation of disorder in an entity. Of course, this is not meant to imply that SARS-CoV-2 infections necessarily lead to successful pathogenesis. SARS-CoV-2 infections, for example, may not lead to host disorder, in which case there would be no pathogenesis. Just as important as it is to represent SARS-CoV-2 pathogenesis to COVID-19, adequate representation of the target domain requires representation of pathogenesis to acute respiratory distress syndrome (ARDS), one of the leading causes of death in those infected by SARS-CoV-2 [95, 96]:

acute respiratory distress syndrome = def Progressive and life-threatening pulmonary distress in the absence of an underlying pulmonary condition, usually following major trauma or surgery.

which may be imported from the Experimental Factor Ontology (https://bioportal.bioontology.org/ontologies/EFO). Similar remarks apply to other diseases associated with SARS-CoV-2 pathogenesis.

SARS-CoV-2 pathogenesis involves transmission of SARS-CoV-2 virions. From PTRANS (https://bioportal.bioontology.org/ontologies/PTRANS) is imported:

pathogen transmission process = def Process during which a pathogen is transmitted directly or indirectly to a new host.

From which SARS-CoV-2 specific terms can be constructed. Additionally, IDO Core provides important role terms relevant to pathogen transmission, such as:

pathogen transporter role = def Role borne by a material entity in or on which a pathogen is located, from which the pathogen may be transmitted to a new host.

An important subclass fomite role–roughly, a pathogen transporter role borne by a non-living entity–may feature in SARS-CoV-2 transmission via instances of fomite role bearing:

respiratory droplet = def Respiratory secretion composed of a bounded portion of liquid which maintains its shape due to surface tension.

respiratory droplet SARS-CoV-2 fomite = def Respiratory droplet fomite with SARS-CoV-2 part.

Knowledge of transmission steps supports strategies designed to break the transmission chain.

Worth noting is that the OBO library ontology APOLLO-SV (https://bioportal.bioontology.org/ontologies/APOLLO-SV) also contains terms, such as contact tracing and quarantine control strategy, which may be leveraged to represent virus-specific transmission control strategies.

SARS-CoV-2 replication

SARS-CoV-2 pathogenesis involves replication in a host. The term virus replication is defined in VIDO as a subclass of the IDO Core term replication, specifically:

virus replication = def Replication process in which a virus containing some portion of genetic material inherited from a parent virus is replicated.

And instances of viral disease course and virus pathogenesis have virus replication as parts. SARS-CoV-2 replication occurs within an:

incubation process = def Process beginning with the establishment of an infection in a host and ending with the onset of symptoms by the host, during which pathogens are multiplying in the host.

Which occupies an incubation interval and may precede a communicability interval. The corresponding process during which SARS-CoV-2 hosts bear a contagiousness disposition has proper part some latency process which itself has an eclipse process as part::

communicability interval = def One-dimensional temporal region during which a pathogen host bears a contagiousness disposition.

latency process = def Process beginning with the establishing of an infection in a host and ending when the host becomes contagious, during which pathogens are multiplying in the host.

eclipse process = def Process beginning with the establishment of a virus in a host and ending with the first appearance of a virion following viral release, during which an infecting virus is uncoating to begin genome replication.

The last are specific to viruses, and so specific to VIDO. Viral dormancy is a virus-specific term from VIDO occurring over a:

viral dormancy interval = def One-dimensional temporal region on which a virus is no longer replicating but remains within a host cell and which may be reactivated to begin replication again.

Viral dormancy is characteristic of familiar viruses such as varicella zoster and herpes simplex.

VIDO includes as a temporal subdivision of a virus developmental process:

virus generative stage = def Infectious structure generative stage that is a temporal subdivision of a virus developmental process.

Subclasses of which include the stages through which viruses may proceed during replication:

virus attachment stage = def Virus generative stage during which a virion protein binds to molecules on the host surface or host cell surface projection.

virus penetration stage = def Virus generative stage during which a virion or viral nucleic acid breaches the barriers of a host.

SARS-CoV-2 attachment stage = def Virus attachment stage during which SARS-CoV-2 bonds with a host cell.

SARS-CoV-2 penetration stage = def Virus penetration stage during which SARS-CoV-2 penetrates a host cell.

SARS-CoV-2 susceptibility

Only cells with certain features are susceptible to SARS-CoV-2 infection [16]. For example, successful infection in humans typically involves SARS-CoV-2 attachment to alveolar epithelial cells through angiotensin-converting enzyme 2 (ACE2) receptors [9799]. Cells lacking ACE2 receptors seem protected from attachment by SARS-CoV-2. Those with receptors can be represented in CIDO using:

SARS-CoV-2 adhesion susceptible cell = def Virus adhesion susceptible cell with a functional receptor part bearing an adhesion disposition realized in a SARS-CoV-2 attachment stage.

adhesion disposition = def Disposition borne by a macromolecule that is the disposition to participate in an adhesion process.

Where adhesion disposition is imported from IDO Core and virus adhesion susceptible cell defined in VIDO. The ACE2 functional receptor is defined in the Protein Ontology (https://bioportal.bioontology.org/ontologies/PRO):

angiotensin-converting enzyme 2 = def A protein that is a translation product of the human ACE2 gene or a 1:1 ortholog thereof.

Attachment is frequently followed by cell penetration, where cell cleavage is aided by transmembrane protease serine 2 (TMPRSS2) prior to SARS-CoV-2 cell membrane fusion [100, 101]. These observations motivate introducing terminological content for defining SARS-CoV-2 penetration susceptible cell such as:

SARS-CoV-2 penetration disposition = def Virus penetration disposition borne by a functional receptor complex that is the disposition to participate in a SARS-CoV-2 penetration process.

Ontological representation of the SARS-CoV-2 replication cycle provides targets for disruption or regulation of that cycle, which is important to rational drug design [102106]:

negative regulation of SARS-CoV-2 attachment = def Negative regulation of coronavirus replication process that stops, prevents, or reduces the frequency of some SARS-CoV- 2 attachment stage.

negative regulation of SARS-CoV-2 penetration = def Negative regulation of coronavirus replication that stops, prevents, or reduces the frequency of some SARS-CoV-2 penetration stage.

Following our strategy of linking VIDO and CIDO, parent classes of negative regulation of coronavirus classes have a proper home in CIDO, while their parent classes–negative regulation of viruses more generally–have a proper home in VIDO.

Annotations

Coverage in VIDO and CIDO can be illustrated by annotation of coronavirus research articles.

Consider the following overview of SARS-CoV-2 pathogenesis (compare bold with Fig 5): Following replication, cell lysis of SARS-CoV-2 coronavirus virions causes host cells to release molecules which function to warn nearby cells. When recognized by epithelial cells, endothelial, and alveolar macrophages, proteins such as IL-6, IP-10, and MCPI, are released which attract T cells, macrophages, and monocytes to the site of infection, promoting inflammation. In disordered immune systems, immune cells accumulate in the lungs, then propagate to and damage other organs. In normal immune systems, inflammation attracts T cells which neutralize the virus at the site of infection. Antibodies circulate, preventing SARS-CoV-2 infection, and alveolar macrophages recognize SARS-CoV-2 and eliminate virions via phagocytosis [92, 107, 108].

Fig 5. Relationships among BFO, GO, OGMS, IDO Core, the Cell Ontology (CL), VIDO, the Common Core Ontology (CCO), OBI, IAO, the Uber-Anatomy Ontology (UBERON), CIDO, ChEBI, PRO (Protein Ontology), and PTRANS.

Fig 5

In a more ontologically oriented language, we speak of the relevant part of a host’s immune response as being disposed to manifest a response that eliminates SARS-CoV-2 infection, while SARS-CoV-2 has a disposition to block manifestation of this immune system response. Consider next a color-coded selection from the Lancet [109] concerning SARS-CoV-2:

“The viral loads in throat swabs and sputum samples peaked at around 5–6 days after symptom onset, ranging from around 10^4 to 10^7 copies per mL during this time.”

SARS-CoV-2 infected hosts contain the highest concentration of SARS-CoV-2 virions–the viral load–during the incubation interval [110]. Viral load is a common measurement of the proportion of virions to fluid, and for SARS-CoV-2 is frequently measured from host sputum. VIDO provides the resources for annotating virus quantification:

viral load = def Quality inhering in a portion of fluid that is the proportion of virions to volume of that portion of fluid

Our color-coding of the above passage from the Lancet models term reuse across existing ontologies. For example, developers can use VIDO and CIDO terms alongside terms from the Common Core Ontology (https://github/com/CommonCoreOntology/CommonCoreOntologies) such as is measured by, measurement information content entity, has integer value, uses measurement unit, and milliliter measurement unit. Other virus quantification metric terms, such as multiplicity of viral infection ‐ the ratio of virions to susceptible cells in a target area–can be found in VIDO as well.

Discussion

Motivated to standardize virus ontology extensions of IDO Core, we have developed VIDO and provided a recipe for connecting VIDO to more virus-specific extensions of IDO Core, illustrated by connecting VIDO to CIDO. Summarizing our results, we have introduced acellular structure as a parent class to virus, motivated using the Baltimore classification to model viruses rather than the International Committee on Taxonomy of Viruses classification, revised IDO Core’s pathogen and host classes to accommodate acellular structures, and extended IDO Core’s infectious disease, infectious disease course, and infectious disease epidemiology classes to cover viruses. We then introduced bridge classes in VIDO to better align IDO Core and CIDO, illustrating throughout how CIDO terminological content can be extended and enriched to represent SARS-CoV-2 pathogenesis, associated transmission processes, virus transporters, replication stages and associated temporal extents, as well as pathogenesis regulation. Our attention was then turned to annotations of texts concerning SARS-CoV-2 and COVID-19, by which we highlighted how ontologies using common vocabularies may be seamlessly interwoven to provide broad annotation coverage for the domain.

VIDO and CIDO are not the only ontologies developed to support curation of COVID-19 data [111114]. However, most alternatives are stand-alone initiatives, and so subject to the silo problems typically found in ontologies developed outside the scope of the OBO Foundry and with no attention to its principles. That said, VIDO and CIDO developers have participated in harmonization efforts aimed at semantic integration across COVID-19 ontologies [115]. Notably, harmonization efforts have resulted in the deprecation of the COVID-19 Infectious Disease Ontology (IDO-COVID-19)–introduced in a preprint version of the current paper [116]–with parties agreeing its scope was subsumed by CIDO. Additionally, VIDO and CIDO have been used to highlight ontology conflict resolution strategies [117]. It is not uncommon for ontology researchers working independently in nearby domains to construct overlapping ontology content.

The harmonization efforts of the VIDO and CIDO development teams signal to the wider ontology community our willingness to reuse terms where possible and obsolete terms or cede terms to other ontologies when needed.

VIDO and CIDO enable extensive representation of virus-related research. The very scope of VIDO provides challenges, however, as does the specificity of CIDO. For these reasons, attempts have been made to foster community-driven development of both. The development team for each ontology spanned disciplines in the life sciences, and to ensure the computational viability of the formal representation of each ontology, included specialists in logic. Often, terms were developed then presented to domain specialists for vetting, after which they were refined through discussion.

As in the case of all scientific ontologies, refinement will continue as research advances, and further collaborators are welcome. Interested parties may contact the corresponding author to be invited to on-going VIDO development meetings and may contact co-author He for invitation to development meetings concerning CIDO. Additionally, collaborators are encouraged to raise issues on respective GitHub issue trackers for VIDO (https://github.com/infectious-disease-ontology-extensions/VIDO) and CIDO (https://github.com/CIDO-ontology/cido).

The existence of IDO Core extensions covering infectious disease-causing entities other than viruses suggests a need for the creation of reference ontology extensions of IDO covering bacteria, fungi, and parasites. To that end, development of the Bacteria Infectious Disease Ontology is underway (https://github.com/infectious-disease-ontology-extensions/Bacteria-Infectious-Disease-O ntology) as is the development of the Fungal Infectious Disease Ontology (https://github.com/SydCo99/MIDO). The methodology illustrated in the development of VIDO provides a recipe for such reference ontology creation. Additionally, the methodology illustrated in the development of CIDO provides a recipe for the creation of novel virus-specific ontologies, namely, by extending them from existing virus ontologies. Adoption of these methodologies by developers during ontology construction will significantly reduce the labor involved in ontology creation. Related, linking research on infectious diseases to developments on non-infectious diseases is no less important than our focus here. In this respect, VIDO and CIDO benefit from alignment with IDO Core, which itself aligns with the Ontology of General Medical Science (OGMS), whose scope extends beyond infectious disease. What this means in practice is that, for example, kidney disease [118] and cancer [119] researchers accurately using the OGMS vocabulary to represent data, invariably use ontology terms and methodologies common to IDO Core, VIDO, and CIDO, thereby lowering barriers to data integration and interoperability.

VIDO and CIDO are being used to annotate host-coronavirus protein-protein interactions, in the interest of developing more effective treatment strategies for those infected by SARS-CoV-2 or variants [37]. While various treatments have been authorized for emergency use [120], there is significant room for improvement. Rather than focus on a single drug to treat infected patients, VIDO and CIDO developers have pursued investigating drug cocktail strategies to improve treatment outcomes. Foundational to these investigations has been proper characterization of viral proteins playing different roles in host-coronavirus interactions which impact pathogenesis [78].

From another direction, VIDO and CIDO have been used in automated electronic health-record annotation [121], in particular those involving COVID-19 data, which highlights the importance of providing researchers with terminological content relevant to nearby domains. Recent developments at the intersection of ontology engineering and machine learning research have, moreover, motivated the need for formally well-defined ontologies in machine learning pipelines using minimal data [122]. By exploiting formal axioms in, for example, the Gene Ontology, impressive zero-shot predictions for protein functions can be generated [123]. We believe the formal axiomatization of VIDO makes it a particularly promising ontology for inclusion in zero-shot research and intend to explore how VIDO may supplement machine learning efforts in future work.

Conclusion

Ontologies provide important tools for overcoming contemporary big data challenges. It is incumbent on working ontologists representing life science research to seek harmonization with nearby ontologies, else we run the risk of reinstating the same big data challenges ontologies have previously been so successful at addressing. VIDO represents a substantial effort to characterize viruses in general, in a collaborative, computationally tractable manner. CIDO too represents a significant effort to characterize coronaviruses in a specific, no less collaborative, no less computationally tractable manner. Connecting VIDO to CIDO improves semantic interoperability among IDO Core-conformant infectious disease ontologies and, moreover, improves interoperability with other BFO-conformant ontologies, ranging from the OBO Foundry to numerous other ontology projects employing BFO as a top-level architecture. Consequently, our work provides researchers resources for gathering and coordinating life science data while avoiding issues that so frequently undermine automating integration and analyses of the data flood in which we so often find ourselves [124126].

Acknowledgments

Many thanks to Asiyah Yu Lin for assistance in VIDO development and harmonization; to Darren Natale and Sydney Cohen for helpful critical feedback on earlier drafts; to Amanda Hicks and Neil Otte for comments on the VIDO rdf files; to participants at the 2022 International Conference on Biomedical Ontologies, with particular thanks to Alexander Diehl and Chris Stoeckert for their helpful feedback before, during, and after the conference. Figures were designed by or in consultation with Rain Yuan.

Data Availability

The Virus Infectious Disease Ontology artifact can be found in the following Github repository: https://github.com/infectious-disease-ontology-extensions/ido-virus. The Coronavirus Infectious Disease Ontology artifact can be found in the following Github repository: https://github.com/CIDO-ontology/cido.

Funding Statement

Sources of funding for this article for John Beverley and Shane Babcock stem from the NIH / NLM T5 Biomedical Informatics and Data Science Research Training Programs. Barry Smith’s source of funding stemmed from the NIH under NCATS 1UL1TR001412 (Buffalo Clinical and Translational Research Center). No other co-authors were funded to pursue work on this project. Moreover, the funders had no role in the study design, data collection and analysis, decision to publish, or preparation of the manuscript.

References

  • 1.Mollica V, Rizzo A, Massari F. (2020). The Pivotal Role of TMPRSS2 in Coronavirus Disease 2019 and Prostate Cancer. Future Oncology. doi: 10.2217/fon-2020-0571 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 2.Stopsack K, et al. (2020). TMPRSS2 and COVID-19: Serendipity or Opportunity for Intervention? Cancer Discovery. doi: 10.1158/2159-8290.CD-20-0451 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 3.Sharma G, et al. (2020). Sex Differences in Mortality from COVID-19 Pandemic. JACC Case Reports. 2(9). doi: 10.1016/j.jaccas.2020.04.027 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 4.Jin J, et al. (2020). Gender Differences in Patients with COVID-19: Focus on Severity and Mortality. Frontiers in Public Health. doi: 10.3389/fpubh.2020.00152 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 5.Ong E, Wong MU, Huffman A, He Y (2020) COVID-19 Coronavirus Vaccine Design Using Reverse Vaccinology and Machine Learning. Front. Immunol. 11(1581). doi: 10.3389/fimmu.2020.01581 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 6.Liu Y, et al. (2021) Ontological modeling and analysis of experimentally or clinically verified drugs against coronavirus infection. Scientific Data. 8(16). doi: 10.1038/s41597-021-00799-w [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 7.Sayers S, et al. Victors: a web-based knowledge base of virulence factors in human and animal pathogens. Nucleic Acid Res. 2019; 47:D693–D700. doi: 10.1093/nar/gky999 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 8.Dong Y, et al. (2020). Epidemiological Characteristics of 2143 Pediatric Patients with 2019 Coronavirus Disease in China. Pediatrics. doi: 10.1542/peds.2020-0702 [DOI] [PubMed] [Google Scholar]
  • 9.Bunyavanich S. (2020). Nasal Gene Expression of Angiotensin-Converting Enzyme 2 in Children and Adults. JAMA. 323(23):2427–9. doi: 10.1001/jama.2020.8707 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 10.Arp R, Smith B, Spear A. (2015) Building Ontologies with Basic Formal Ontology. Cambridge, MA: MIT Press. [Google Scholar]
  • 11.He Y, et al. (2020). CIDO, a community-based ontology for coronavirus disease knowledge and data integration, sharing, and analysis. Scientific data. (7):181. doi: 10.1038/s41597-020-0523-6 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 12.Griffiths EJ, et al. (2022). Future-proofing and maximizing the utility of metadata: The PHA4GE SARS-CoV-2 contextual data specification package. Gigascience. doi: 10.1093/gigascience/giac003 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 13.Taylor CF, et al. (2008) Promoting coherent minimum reporting guidelines for biological and biomedical investigations: the MIBBI project. Nat Biotechnol. 26(8):889–96. doi: 10.1038/nbt.1411 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 14.Bandrowski A, et al. (2016) The Ontology for Biomedical Investigations. PLoS ONE 11 (4): e0154556. doi: 10.1371/journal.pone.0154556 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 15.Cowell LG, Smith B. (2010) Infectious Diseases Ontology. In: Sintchenko V, editor. Infectious Disease Informatics. New York, NY: Springer. p. 373–95. [Google Scholar]
  • 16.Babcock S, Beverley J, Cowell LG, Smith B. (2021) The Infectious Disease Ontology in the age of COVID-19. J Biomed Semantics. 12(1). doi: 10.1186/s13326-021-00245-1 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 17.Musen M, et al. (2008) BioPortal: Ontologies and Data Resources with the Click of a Mouse. AMIA Annu Symp Proc. 1223–4. [PubMed] [Google Scholar]
  • 18.The Open Biomedical Ontologies Foundry. http://obofoundry.org/ Accessed 11 Mar 2023.
  • 19.Smith B, et al. (2007) The OBO Foundry: coordinated evolution of ontologies to support biomedical data integration. Nat Biotechnol. 25:1251–1255. doi: 10.1038/nbt1346 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 20.Baader F, Horrocks I, Lutz C, Sattler U. (2017). An Introduction to Description Logic. Cambridge: University Press. doi: 10.1017/9781139025355 [DOI] [Google Scholar]
  • 21.Homer H, Selman AL. (2011) Computability and Complexity Theory: Texts in Computer Science. 2nd Edition. Springer. [Google Scholar]
  • 22.Shearer R, Motik B, Horrocks I. (2008) HermiT: A Highly-Efficient OWL Reasoner. OWLED. [Google Scholar]
  • 23.Evren Sirin BP, Bernardo Grau C, Kalyanpur Aditya, Yarden Katz. (2007) Pellet: A practical OWL-DL reasoner Web Semantics: Science, Services and Agents on the World Wide Web. 5(2):51–3. [Google Scholar]
  • 24.The Gene Ontology Consortium. (2019) The Gene Ontology Resource: 20 years and still GOing. Nucleic Acids Res. 47:D330–D338. doi: 10.1093/nar/gky1055 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 25.Ashburner M. et al. (2000) Gene ontology: tool for the unification of biology. The Gene Ontology Consortium. Nature genetics. 25, 25–29. Epub 2000/05/10. doi: 10.1038/75556 . [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 26.Smith B. (2012) Classifying Processes: An Essay in Applied Ontology. Ratio. (4):463–488. doi: 10.1111/j.1467-9329.2012.00557.x [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 27.Smith B. (2012) On Classifying Material Entities in Basic Formal Ontology. Interdisciplinary Ontology: Proceedings of the Third Interdisciplinary Ontology Meeting. Tokyo: Keio University Press. 1–13.
  • 28.Spear A, Ceusters W, Smith B. (2016) Functions in Basic Formal Ontology. Applied Ontology. (11):103–128. [Google Scholar]
  • 29.Otte NJ, Beverley J, Ruttenberg A. (2022) BFO: Basic Formal Ontology. Applied Ontology. 17–43. [Google Scholar]
  • 30.Schober D, et al. (2009) Survey-based naming conventions for use in OBO Foundry ontology development. BMC Bioinformatics. 10:125. epub 2009/04/29. 1471-2105-1 doi: 10.1186/1471-2105-10-125 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 31.Seppala S, Ruttenberg A, Schreiber Y, Smith B. (2016). Definitions in Ontologies. Cahiers de Lexicologie. 109(2):175–207. [Google Scholar]
  • 32.Goldfain A, Smith B, Cowell LG. (2010) Dispositions and the infectious disease ontology. In: Galton A, Mizoguchi R, editors. Formal Ontology in Information Systems: Proceedings of the 6th International Conference (FOIS 2010). Amsterdam: IOS Press.
  • 33.Janssen T. et al. (2010) Introduction: Ontologies, Semantic Technologies, and Intelligence. Ontologies and Semantic Technologies for Intelligence. [Google Scholar]
  • 34.Lin Y, Xiang Z, He Y. (2011) Brucellosis ontology (IDOBRU) as an extension of the infectious disease ontology. J Biomed Semant. doi: 10.1186/2041-1480-2-9 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 35.Lin Y, Xiang Z, He Y. (2015) Ontology-based representation and analysis of host-Brucella interactions. J Biomed Semant. doi: 10.1186/s13326-015-0036-y [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 36.Luciano J, Schriml L, Squires B, Scheuermann R. (2008) The Influenza Infectious Disease Ontology (I-IDO). The 11th Annual Bio-Ontologies Meeting, ISMB. [Google Scholar]
  • 37.He Y, et al. (2022) A comprehensive update on CIDO: the community-based coronavirus infectious disease ontology. J Biomed Semantics. 13(1):25. doi: 10.1186/s13326-022-00279-z [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 38.Scheuermann R, Ceusters W, Smith B. (2009). Towards an Ontological Treatment of Disease and Diagnosis. AMIA Joint Summit on Translational Science. 116–20. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3041577/ [PMC free article] [PubMed] [Google Scholar]
  • 39.Foulger RE, et al. (2015). Representing Virus-Host Interactions and other Multi-Organism Processes in the Gene Ontology. BMC Microbiology. 15. 146. doi: 10.1186/s12866-015-0481-x [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 40.Hulo C, et al. (2017). The Ins and Outs of Eukaryotic Viruses: Knowledge Base and Ontology of a Viral Infection. PLoS One. 12:2. doi: 10.1371/journal.pone.0171746 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 41.Raoult D. (2014). How the Virophage Compels the Need to Readdress the Classification of Microbes. Virology. doi: 10.1016/j.virol.2014.11.014 [DOI] [PubMed] [Google Scholar]
  • 42.Roault D. Forterre P. (2008). Redefining Viruses: Lessons from Mimivirus. Nature Reviews Microbiology. 6, 315–9. doi: 10.1038/nrmicro1858 [DOI] [PubMed] [Google Scholar]
  • 43.Koonin EV, Starokadomskyy P. (2016) Are Viruses Alive? The Replicator Paradigm Sheds Decisive Light on an Old but Misguided Question. Studies in History and Philosophy of Science. 59. 125–34. doi: 10.1016/j.shpsc.2016.02.016 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 44.Claverie JM. (2008) Encyclopedia of Virology 3rd Edition.
  • 45.Krupovic M, et al. (2016). A Classification System for Virophages and Satellite Viruses. Archives of Virology. 161, 233–47. doi: 10.1007/s00705-015-2622-9 [DOI] [PubMed] [Google Scholar]
  • 46.Rodrigo AL, et al. (2019). Giant Viruses and Their Virophage Parasites. Reference Module in Life Sciences. doi: 10.1016/B978-0-12-809633-8.20924-2 [DOI] [Google Scholar]
  • 47.He Y. (2022). Ontological Classification of Self-replicating Organic Structures. Preprint. 1–8. doi: 10.31219/osf.io/n2zkh [DOI]
  • 48.Federhen S. (2012) The NCBI Taxonomy Database. Nucleic Acids Res. 40:D136–D143. doi: 10.1093/nar/gkr1178 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 49.Mahmoudabadi G, Philops R. (2018). A Comprehensive and Quantitative Exploration of Thousands of Viral Genomes. eLife. doi: 10.7554/eLife.31955 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 50.Kuhn J. (2020). Virus Taxonomy. Reference Modules in Life Sciences. doi: 10.1016/B978-0-12-809633-8.21231-4 [DOI] [Google Scholar]
  • 51.Xiang Z, Courtot M, Brinkman RR, Ruttenberg A, He Y. (2010) OntoFox: webbased support for ontology reuse. BMC research notes 3:175, 1–12, doi: 17560500-3-175 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 52.Dimmock NJ, et. al. (2007). Introduction to Modern Virology. 6th edition. Blackwell Publishing.
  • 53.Cann A. (2016). Principles of Molecular Virology. Academic Press. [Google Scholar]
  • 54.Baltimore D. (1971). Expression of Animal Virus Genomes. Bacteriological Reviews. 35, 235–41. doi: 10.1128/br.35.3.235-241.1971 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 55.Maier H, Bickerton E. Britton P. (2015). Coronavirus: An Overview of their Replication and Pathogenesis. Coronaviruses. 1282: 1–23. doi: 10.1007/978-1-4939-2438-7_1 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 56.Bauman R. (2017). Microbiology with Disease Taxonomy. Pearson Publishing. [Google Scholar]
  • 57.Claverie J. (2006). Viruses take Center Stage in Cellular Evolution. Genome Biology. 7(6). 110. doi: 10.1186/gb-2006-7-6-110 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 58.Forterre P. (2010). Defining Life: The Virus Viewpoint. Origins of Life Evolution Biosphere. 40(2). 151–60. doi: 10.1007/s11084-010-9194-1 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 59.Crotty S. (2001). RNA Virus Error Catastrophe: Direct Molecular Test by Using Ribavarin. Proceedings of the National Academy of Sciences. 98(12). 6895–6900 doi: 10.1073/pnas.111085598 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 60.Pfeiffer J. (2003). A Single Mutation in Poliovirus RNA-Dependent RNA Polymerase Confers Resistance to Mutagenic Nucleotide Analogs via Increased Fidelity. Proceedings of the National Academy of Sciences. 100(12). 7289–7294 doi: 10.1073/pnas.1232294100 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 61.Degtyarenko K, et al. ChEBI: a database and ontology for chemical entities of biological interest. Nucleic Acids Res. 2008; 36:D344–D350. doi: 10.1093/nar/gkm791 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 62.Hastings J. et al. ChEBI in 2016: Improved services and an expanding collection of metabolites. Nucleic acids research 44, D1214–1219, doi: 10.1093/nar/gkv1031 (2016). [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 63.Barr JJ, et al. (2013). Bacteriophage Adhering to Mucus Provide a Non-Host Derived Immunity. PNAS. 110(26) 10771–6. doi: 10.1073/pnas.1305923110 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 64.Meyer JR. (2013). Sticky Bacteriophage Protect Animal Cells. PNAS. 110(23) 10475–6. doi: 10.1073/pnas.1307782110 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 65.Karasov TL, Chae E, Herman JJ, Bergelson J. (2017) Mechanisms to mitigate the trade-off between growth and defense. Plant Cell 29, 666–680. doi: 10.1105/tpc.16.00931 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 66.Yassour M, et al. (2016) Natural history of the infant gut microbiome and impact of antibiotic treatment on bacterial strain diversity and stability. Sci. Transl. Med. 8, 343ra381 doi: 10.1126/scitranslmed.aad0917 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 67.Simon AK, Hollander GA, McMichael A. (2015) Evolution of the immune system in humans from infancy to old age. Proc. R. Soc. Lond. B 282, 20143085 doi: 10.1098/rspb.2014.3085 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 68.Critchlow JT, Norris A, Tate AT. (2019) The legacy of larval infection on immunological dynamics over metamorphosis. Philos Trans R Soc Lond B Biol Sci. 374(1783):20190066. doi: 10.1098/rstb.2019.0066 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 69.Ananthanarayan R., Paniker J. (2005). Textbook of Microbiology. 7th Edition. [Google Scholar]
  • 70.Samson M. (1996). Resistance to HIV-1 Infection in Caucasian Individuals bearing Mutant Alleles of the CCR-5 Chemokine Receptor Gene. Nature. 382(6593): 722–5. doi: 10.1038/382722a0 [DOI] [PubMed] [Google Scholar]
  • 71.Tiffert T, et al. (2005). The hydration state of human red blood cells and their susceptibility invasion by Plasmodium falciparum. Blood, 105(12) 4853–4860. [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 72.Goldfain A, Smith B, Cowell LG. (2011) Towards an ontological representation of resistance: the case of MRSA. J Biomed Inform. 44:35–41. doi: 10.1016/j.jbi.2010.02.008 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 73.Osterhaus AD, Fouchier RA, Kuiken T. (2004) The aetiology of SARS: Koch’s postulates fulfilled. Philosophical transactions of the Royal Society of London. Series B, Biological sciences 359, 1081–1082, doi: 10.1098/rstb.2004.1489 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 74.Falkow S. (1988) Molecular Koch’s postulates applied to microbial pathogenicity. Rev Infect Dis 10 Suppl 2, S274–276, doi: 10.1093/cid/10.supplement_2.s274 [DOI] [PubMed] [Google Scholar]
  • 75.Rivers TM. (1937) Viruses and Koch’s Postulates. Journal of bacteriology 33, 1–12. doi: 10.1128/jb.33.1.1-12.1937 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 76.Finlay BB, Falkow S. (1997) Common themes in microbial pathogenicity revisited. Microbiol. Mol. Biol. Rev. 61, 136–169. doi: 10.1128/mmbr.61.2.136-169.1997 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 77.Hacker J, Blum–Oehler G, Mühldorfer I, Tschäpe H. (1997) Pathogenicity islands of virulent bacteria: structure, function and impact on microbial evolution. Mol. Microbiol. 23, 1089–1097. doi: 10.1046/j.1365-2958.1997.3101672.x [DOI] [PubMed] [Google Scholar]
  • 78.Yu H, et al. (2022) A New Framework for Host-Pathogen Interaction Research. Frontiers in Immunology. doi: 10.3389/fimmu.2022.1066733 [DOI] [PMC free article] [PubMed]
  • 79.Pirofski L, Casadevall A. (2020). Pathogenesis of COVID-19 from the Perspective of the Damage-Response Framework. MBio. 11(4). 1–12. doi: 10.1128/mBio.01175-20 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 80.Methot P, Alizon S. (2014). What is a Pathogen? Towards a Process View of Host-Parasite Interactions. Virulence. 5(8). 775–85. doi: 10.4161/21505594.2014.960726 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 81.Casadevall A, Pirofski L. (2003). The Damage-Response Framework of Microbial Pathogenesis. Nature Reviews Microbiology. 1, 17–24. doi: 10.1038/nrmicro732 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 82.Morrison T, Garsin D. (2020). Pathogenesis of COVID-19 from the Perspective of the Damage-Response Framework. Host-Microbe Biology. doi: 10.1128/mBio.01175-20 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 83.Talukder A, Razu SR, Alif SM, Rahman MA, (2022) Association Between Symptoms and Severity of Disease in Hospitalised Novel Coronavirus (COVID-19) Patients: A Systematic Review and Meta-Analysis. J Multidiscip Healthc. 2022;15:1101–1110. doi: 10.2147/JMDH.S357867 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 84.Centers for Disease Control and Prevention. (2020). Coronavirus Disease 2019 (COVID-19) 2020 Interim Case Definition, Approved April 2, 2020. https://ndc.services.cdc.gov/case-definitions/coronavirus-disease-2019-2020/ Accessed Mar 11 2023.
  • 85.Council of State of Territorial Epidemiologists. (2023). Standardization Surveillance Case Definition and National Notification for 2019 Coronavirus Disease (COVID-19). https://ndc.services.cdc.gov/conditions/coronavirus-disease-2019-covid-19/ Accessed Mar 11 2023.
  • 86.Centers for Disease Control and Prevention. (2023). Coronavirus Disease 2019 (COVID-19) 2023 Case Definition, Approved February 28, 2023. https://ndc.services.cdc.gov/case-definitions/coronavirus-disease-2019-covid-19/ Accessed Mar 11 2023.
  • 87.Tamerius J, Nelson MI, Zhou SZ, Viboud C, Miller MA, Alonso WJ. Global influenza seasonality: reconciling patterns across temperate and tropical regions. Environ Health Perspect. 2011;119(4):439–445. doi: 10.1289/ehp.1002383 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 88.Zhou Y. (2020). Network-based Drug Repurposing for Novel Coronavirus 2019-nCoV/SARS-CoV-2. Cell Discovery. 6(14). doi: 10.1038/s41421-020-0153-3 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 89.Li F. (2016) Structure, Function, and Evolution of Coronavirus Spike Proteins. Annu Rev Virol. 3(1):237–261. doi: 10.1146/annurev-virology-110615-042301 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 90.Schoeman D, Fielding BC. (2019) Coronavirus envelope protein: current knowledge. Virol J 16, 69. doi: 10.1186/s12985-019-1182-0 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 91.Kikkert M. (2020) Innate Immune Evasion by Human Respiratory RNA Viruses. J Innate Immun 12, 4–20, doi: 10.1159/000503030 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 92.Tay MZ, Poh CM, Renia L, MacAry PA, Ng LFP. (2020) The trinity of COVID-19: immunity, inflammation and intervention. Nat Rev Immunol. 20, 363–374. doi: 10.1038/s41577-020-0311-8 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 93.Yu H, et al. (2020). Ontology-based Systematic Classification and Analysis of Coronaviruses, Hosts, and Host-Coronavirus Interactions towards Deep Understanding of COVID-19. arXiv preprint. a rXiv:2006.00639. [Google Scholar]
  • 94.Laracy J, et al. (2022). Comparison of coronavirus disease 2019 (COVID-19) symptoms at diagnosis among healthcare personnel before and after the emergence of the omicron variant. Infection Control & Hospital Epidemiology, 1–3. doi: 10.1017/ice.2022.105 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 95.Guo YR, et al. (2020). The origin, transmission and clinical therapies on coronavirus disease 2019 (COVID-19) outbreak–an update on the status. Military Medical Research. 7(1):11. doi: 10.1186/s40779-020-00240-0 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 96.Solaimanzadeh I (2020). Acetazolamide, Nifedipine and Phosphodiesterase Inhibitors: Rationale for Their Utilization as Adjunctive Countermeasures in the Treatment of Coronavirus Disease 2019 (COVID-19). Cureus. 12 (3): e7343. doi: 10.7759/cureus.7343 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 97.Kuba K, et al. (2005) A crucial role of angiotensin converting enzyme 2 (ACE2) in SARS coronavirus-induced lung injury. Nature medicine 11, 875–879, doi: 10.1038/nm1267 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 98.Letko M, Marzi A, Munster V. (2020) Functional assessment of cell entry and receptor usage for SARS-CoV-2 and other lineage B betacoronaviruses. Nature microbiology, doi: 10.1038/s41564-020-0688-y [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 99.Chen Y, Liu Q, Guo D. (2020) Emerging coronaviruses: Genome structure, replication, and pathogenesis. J Med Virol 92, 418–423, doi: 10.1002/jmv.25681 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 100.Hoffmann M. et al. (2020) SARS-CoV-2 Cell Entry Depends on ACE2 and TMPRSS2 and Is Blocked by a Clinically Proven Protease Inhibitor. Cell 181, 271–280 e278, doi: 10.1016/j.cell.2020.02.052 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 101.Shapira T, et al. (2022) A TMPRSS2 inhibitor acts as a pan-SARS-CoV-2 prophylactic and therapeutic. Nature 605, 340–348. doi: 10.1038/s41586-022-04661-w [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 102.Grau-Pujol B, Camprubí D, Marti-Soler H, Fernández-Pardos M, Guinovart C, Muñoz J. (2020) Pre-exposure prophylaxis with hydroxychloroquine for high-risk healthcare workers during the COVID-19 pandemic: A structured summary of a study protocol for a multicentre, double-blind randomized controlled trial. Trials. 21(1):688. doi: 10.1186/s13063-020-04621-7 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 103.Moderna Announces Phase 3 COVE Study of mRNA Vaccine against COVID-19 (mRNA-1273) Begins. Press Release (2020); https://investors.modernatx.com/news-releases/news-release-details/moderna-announces-phase-3-cove-study-mrna-vaccine-against-covid.
  • 104.A Study to Evaluate Efficacy, Safety, and Immunogenicity of mRNA-1273 Vaccine in Adults Aged 18 Years and Older to Prevent COVID-19, ClinicalTrials.gov Identifier: NCT04470427, https://clinicaltrials.gov/ct2/show/NCT04470427.
  • 105.Pfizer and Biotech Choose Lead mRNA Vaccine Candidate against COVID-19 and Commence Pivotal Phase 2/3 Global Study. Press Release. (2020). https://www.pfizer.com/news/press-release/press-release-detail/pfizer-and-biontech-choose-lead-mrna-vaccine-candidate-0
  • 106.Folegatti P, Ewer K. (2020). Safety and Immunogenecity of the ChAdOx1 nCoV-19 Vaccine against SARS-CoV-2: A Preliminary Report of a Phase 1/2, Single-blind, Randomized Controlled Trial. The Lancet. doi: 10.1016/S0140-6736(20)31604-4 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 107.Chousterman BG, Swirski FK, Weber GF. (2017) Cytokine storm and sepsis disease pathogenesis. Semin Immunopathol 39, 517–528, doi: 10.1007/s00281-017-0639-8 [DOI] [PubMed] [Google Scholar]
  • 108.Ye Q, Wang B, Mao J. (2020) The pathogenesis and treatment of the `Cytokine Storm’ in COVID-19. J Infect, doi: 10.1016/j.jinf.2020.03.037 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 109.Pan Y. et al. (2020). Viral Load of SARS-CoV-2 in Clinical Samples. The Lancet. 20(4):411–2. doi: 10.1016/S1473-3099(20)30113-4 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 110.Gandhi M, Yokoe DS, Havlir DV. (2020) Asymptomatic Transmission, the Achilles’ Heel of Current Strategies to Control Covid-19. The New England journal of medicine. doi: 10.1056/NEJMe2009758 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 111.WHO COVID-19 Rapid Version CRF. https://bioportal.bioontology.org/ontologies/COVIDCRFRAPID Accessed Mar 11 2023.
  • 112.COVID-19 Surveillance Ontology. https://bioportal.bioontology.org/ontologies/COVID19 Accessed Mar 11 2023.
  • 113.Linked COVID-19 Data Ontology. https://github.com/Research-Squirrel-Engineers/COVID-19. Accessed Mar 11 2023.
  • 114.COVID-19 Research Knowledge Graph. https://github.com/nasa-jpl-cord-19/covid19-knowledge-graph. Accessed Mar 11 2023.
  • 115.Lin AY, et al. (2021) A Community Effort for COVID-19 Ontology Harmonization. The 12th International Conference on Biomedical Ontologies. 122–127. [PMC free article] [PubMed] [Google Scholar]
  • 116.B everley J, Smith B, Babcock S, Cowell LG. (2020). Coordinating Coronavirus Research: The COVID-19 Infectious Disease Ontology. Preprint. doi: 10.17605/OSF.IO/7EJ4H [DOI] [Google Scholar]
  • 117.Keet C.M., Grütter R. Toward a systematic conflict resolution framework for ontologies. J Biomed Semant 12, 15 (2021). 10.1186/s13326-021-00246-0 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 118.Ong E, Wang LL, Schaub J, et al. Modelling kidney disease using ontology: insights from the Kidney Precision Medicine Project. Nat Rev Nephrol. 2020;16(11):686–696. doi: 10.1038/s41581-020-00335-w [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 119.Silva MC, Eugénio P, Faria D, Pesquita C. Ontologies and Knowledge Graphs in Oncology Research. Cancers (Basel). 2022;14(8):1906. Published 2022 Apr 10. doi: 10.3390/cancers14081906 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 120.Beigel JH, Tomashek KM, Dodd LE, Mehta AK, Zingman BS, Kalil AC, et al. Remdesivir for the treatment of Covid-19 ‐ preliminary report. N Engl J Med. 2020. [DOI] [PubMed] [Google Scholar]
  • 121.Keloth VK, Zhou S, Lindemann L, et al. Mining of EHR for interface terminology concepts for annotating EHRs of COVID patients. BMC Med Inform Decis Mak. 2023;23(Suppl 1):40. Published 2023 Feb 24. doi: 10.1186/s12911-023-02136-0 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 122.Smaili FZ, Gao X, Hoehndorf R. Formal axioms in biomedical ontologies improve analysis and interpretation of associated data. Bioinformatics. 2020. Apr 1;36(7):2229–2236. doi: 10.1093/bioinformatics/btz920. ; PMCID: PMC7141863. [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 123.Kulmanov M, Hoehndorf R. DeepGOZero: improving protein function prediction from sequence and zero- shot learning based on ontology axioms. Bioinformatics. 2022. Jun 24;38(Suppl 1):i238–i245. doi: 10.1093/bioinformatics/btac256. ; PMCID: PMC9235501. [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 124.Apolinario-Arzube Ó. et al. (2020) CollaborativeHealth: Smart Technologies to Surveil Outbreaks of Infectious Diseases Through Direct and Indirect Citizen Participation. In: Silhavy R. (eds) Applied Informatics and Cybernetics in Intelligent Systems. Advances in Intelligent Systems and Computing. 1226. doi: 10.1007/978-3-030-51974-2_1 [DOI]
  • 125.Bernasconi A, Canakoglu A, Masseroli M, Pinoli P, Ceri S. (2021) A review on viral data sources and search systems for perspective mitigation of COVID-19. Brief Bioinform. 22(2):664–675. doi: 10.1093/bib/bbaa359 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 126.Azzi S, Michalowski W, Iglewski M. Developing a pneumonia diagnosis ontology from multiple knowledge sources. Health Informatics Journal. 2022;28(2). doi: 10.1177/14604582221083850 [DOI] [PubMed] [Google Scholar]

Decision Letter 0

Barry L Bentley

3 Feb 2023

PONE-D-22-32364

Coordinating Virus Research: The Virus Infectious Disease Ontology

PLOS ONE

Dear Dr. Beverley,

Thank you for submitting your manuscript to PLOS ONE. After careful consideration, we feel that it has merit but does not fully meet PLOS ONE’s publication criteria as it currently stands. Therefore, we invite you to submit a revised version of the manuscript that addresses the points raised during the review process.

Please submit your revised manuscript by Mar 17 2023 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org. When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file.

Please include the following items when submitting your revised manuscript:

  • A rebuttal letter that responds to each point raised by the academic editor and reviewer(s). You should upload this letter as a separate file labeled 'Response to Reviewers'.

  • A marked-up copy of your manuscript that highlights changes made to the original version. You should upload this as a separate file labeled 'Revised Manuscript with Track Changes'.

  • An unmarked version of your revised paper without tracked changes. You should upload this as a separate file labeled 'Manuscript'.

If you would like to make changes to your financial disclosure, please include your updated statement in your cover letter. Guidelines for resubmitting your figure files are available below the reviewer comments at the end of this letter.

If applicable, we recommend that you deposit your laboratory protocols in protocols.io to enhance the reproducibility of your results. Protocols.io assigns your protocol its own identifier (DOI) so that it can be cited independently in the future. For instructions see: https://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols. Additionally, PLOS ONE offers an option for publishing peer-reviewed Lab Protocol articles, which describe protocols hosted on protocols.io. Read more information on sharing protocols at https://plos.org/protocols?utm_medium=editorial-email&utm_source=authorletters&utm_campaign=protocols.

We look forward to receiving your revised manuscript.

Kind regards,

Barry L. Bentley, Ph.D.

Academic Editor

PLOS ONE

Journal Requirements:

When submitting your revision, we need you to address these additional requirements.

1. Please ensure that your manuscript meets PLOS ONE's style requirements, including those for file naming. The PLOS ONE style templates can be found at

https://journals.plos.org/plosone/s/file?id=wjVg/PLOSOne_formatting_sample_main_body.pdf and

https://journals.plos.org/plosone/s/file?id=ba62/PLOSOne_formatting_sample_title_authors_affiliations.pdf

2. We noticed you have some minor occurrence of overlapping text with the following previous publication(s), which needs to be addressed:

- https://pubmed.ncbi.nlm.nih.gov/34275487/?

In your revision ensure you cite all your sources (including your own works), and quote or rephrase any duplicated text outside the methods section. Further consideration is dependent on these concerns being addressed.

3. Thank you for stating the following financial disclosure:

“NO”

At this time, please address the following queries:

a)        Please clarify the sources of funding (financial or material support) for your study. List the grants or organizations that supported your study, including funding received from your institution.

b)        State what role the funders took in the study. If the funders had no role in your study, please state: “The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript.”

c)        If any authors received a salary from any of your funders, please state which authors and which funders.

d)        If you did not receive any funding for this study, please state: “The authors received no specific funding for this work.”

Please include your amended statements within your cover letter; we will change the online submission form on your behalf.

4. Thank you for stating the following in your Competing Interests section: 

“NO”

Please complete your Competing Interests on the online submission form to state any Competing Interests. If you have no competing interests, please state "The authors have declared that no competing interests exist.", as detailed online in our guide for authors at http://journals.plos.org/plosone/s/submit-now

 This information should be included in your cover letter; we will change the online submission form on your behalf.

5. In your Data Availability statement, you have not specified where the minimal data set underlying the results described in your manuscript can be found. PLOS defines a study's minimal data set as the underlying data used to reach the conclusions drawn in the manuscript and any additional data required to replicate the reported study findings in their entirety. All PLOS journals require that the minimal data set be made fully available. For more information about our data policy, please see http://journals.plos.org/plosone/s/data-availability.

Upon re-submitting your revised manuscript, please upload your study’s minimal underlying data set as either Supporting Information files or to a stable, public repository and include the relevant URLs, DOIs, or accession numbers within your revised cover letter. For a list of acceptable repositories, please see http://journals.plos.org/plosone/s/data-availability#loc-recommended-repositories. Any potentially identifying patient information must be fully anonymized.

Important: If there are ethical or legal restrictions to sharing your data publicly, please explain these restrictions in detail. Please see our guidelines for more information on what we consider unacceptable restrictions to publicly sharing data: http://journals.plos.org/plosone/s/data-availability#loc-unacceptable-data-access-restrictions. Note that it is not acceptable for the authors to be the sole named individuals responsible for ensuring data access.

We will update your Data Availability statement to reflect the information you provide in your cover letter.

6. Please review your reference list to ensure that it is complete and correct. If you have cited papers that have been retracted, please include the rationale for doing so in the manuscript text, or remove these references and replace them with relevant current references. Any changes to the reference list should be mentioned in the rebuttal letter that accompanies your revised manuscript. If you need to cite a retracted article, indicate the article’s retracted status in the References list and also include a citation and full reference for the retraction notice.

[Note: HTML markup is below. Please do not edit.]

Reviewers' comments:

Reviewer's Responses to Questions

Comments to the Author

1. Is the manuscript technically sound, and do the data support the conclusions?

The manuscript must describe a technically sound piece of scientific research with data that supports the conclusions. Experiments must have been conducted rigorously, with appropriate controls, replication, and sample sizes. The conclusions must be drawn appropriately based on the data presented.

Reviewer #1: Yes

Reviewer #2: Yes

********** 

2. Has the statistical analysis been performed appropriately and rigorously?

Reviewer #1: N/A

Reviewer #2: Yes

********** 

3. Have the authors made all data underlying the findings in their manuscript fully available?

The PLOS Data policy requires authors to make all data underlying the findings described in their manuscript fully available without restriction, with rare exception (please refer to the Data Availability Statement in the manuscript PDF file). The data should be provided as part of the manuscript or its supporting information, or deposited to a public repository. For example, in addition to summary statistics, the data points behind means, medians and variance measures should be available. If there are restrictions on publicly sharing data—e.g. participant privacy or use of data from a third party—those must be specified.

Reviewer #1: Yes

Reviewer #2: Yes

********** 

4. Is the manuscript presented in an intelligible fashion and written in standard English?

PLOS ONE does not copyedit accepted manuscripts, so the language in submitted articles must be clear, correct, and unambiguous. Any typographical or grammatical errors should be corrected at revision, so please note any specific errors here.

Reviewer #1: Yes

Reviewer #2: Yes

********** 

5. Review Comments to the Author

Please use the space provided to explain your answers to the questions above. You may also include additional comments for the author, including concerns about dual publication, research ethics, or publication ethics. (Please upload your review as an attachment if it exceeds 20,000 characters)

Reviewer #1: This manuscript describes VIDO as an extension of IDO. It is well written and easy to understand. There are a few minor issues to be addressed.

on page 2, the first instance of "data silos" is italicized. It is not clear why it is, but it would be nice to explain what is meant by the phrase. In certain circles, it is well understood, but the audience of plos one is broad enough that it would be nice to have a short explanation.

On pages 14 and 15, the definitions for host role and pathogen role seem to be reversed. The host is not meant to be acellular?

On page 18, coronaviris disease and disease course terms and mentioned, yet no coronavirus terms could be found in VIDO. Has this work not been completed yet? If so, please state this or say when it will be released.

On page 22, the sentence that starts with "With participants found from familiar..." near the top of the page is an incomplete sentence.

On page 22 at the bottom of the page, the link to a human ACE2protein is mentioned. I would have expected a link to a higher node species independent protein. Is VIDO human specific? Many other species can be infected with coronaviruses. Is that data outside the scope of VIDO? If so, please mention this.

On page 25, the fact that collaborators are welcomed could use an explanation - are there weekly calls that others can join or should it be via github requests or just by email or all of the above?

On page 25, the Fungal and Bacterial Infectious Disease Ontologies are welcomed news, however, how and if IDO and its children relate to non-infectious diseases would be very interesting to projects that must represent all types of diseases, including those that are not infectious.

If you have any data on usage or projects that are currently collaborating, that information would be nice to have.

Extra information that would be very interesting to address, but may be out of scope of this article, so are not required for publication:

Any discussion regarding the interoperability of IDO and VIDO with other ontologies and any plans to migrate IDO terms to other ontologies having the same or similar terms, for example 'host' and 'viral latency' are in GO would be nice to have. 'Infectious disease' is in many other ontologies, 'syndrome' is on OGMS, 'latency' is in PATO. 'Adhesion disposition' and 'incubation process' are not virus specific terms, so should live outside of VIDO, for example.

Reviewer #2: Some specific examples of data silos rather than just mentioning might be helpful in the article to entertain the readers. In the same vein, just mentioning of the machine learning algorithm with the reference[6] to predict efficient Covid vaccine demands more specific examples of machine learning projects where the ontologies might play a crucial role (as claimed in the article). Having said that, perhaps, there is a need to tightly couple or link the article’s developmental ontologies to any machine learning projects in characterizing viruses in a collaborative, computationally tractable manner, more importantly, for the researchers across the disciplines.

A more clarification is needed on how incorporating the Baltimore classification provides developers in VIDO more specific virus classes within a succinct, navigable, and ontological structure as claimed in the article.

In the discussion section that follows the results, perhaps a paragraph of a high-level summary of the results section could be fruitful which can then be subsequently linked with the points discussed on the VIDO and CIDO.

Finally, perhaps, a conclusions section might be useful to deliver a powerful statement in connecting the VIDO to the CIDO.

********** 

6. PLOS authors have the option to publish the peer review history of their article (what does this mean?). If published, this will include your full peer review and any attached files.

If you choose “no”, your identity will remain anonymous but your review may still be made public.

Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy.

Reviewer #1: No

Reviewer #2: No

**********

[NOTE: If reviewer comments were submitted as an attachment file, they will be attached to this email and accessible via the submission site. Please log into your account, locate the manuscript record, and check for the action link "View Attachments". If this link does not appear, there are no attachment files.]

While revising your submission, please upload your figure files to the Preflight Analysis and Conversion Engine (PACE) digital diagnostic tool, https://pacev2.apexcovantage.com/. PACE helps ensure that figures meet PLOS requirements. To use PACE, you must first register as a user. Registration is free. Then, login and navigate to the UPLOAD tab, where you will find detailed instructions on how to use the tool. If you encounter any issues or have any questions when using PACE, please email PLOS at figures@plos.org. Please note that Supporting Information files do not need this step.

PLoS One. 2024 Jan 18;19(1):e0285093. doi: 10.1371/journal.pone.0285093.r002

Author response to Decision Letter 0


17 Mar 2023

Response to Reviewers

We very much appreciate the reviewers’ comments throughout; we feel our submission has been improved by working through the helpful feedback offered.

Reviewer #1

This manuscript describes VIDO as an extension of IDO. It is well written and easy to understand. There are a few minor issues to be addressed.

on page 2, the first instance of "data silos" is italicized. It is not clear why it is, but it would be nice to explain what is meant by the phrase. In certain circles, it is well understood, but the audience of plos one is broad enough that it would be nice to have a short explanation.

We appreciate the reviewer’s feedback and have added a brief description of data silos as well as motivating examples. We have removed the italics since they appear to have been distracting.

On pages 14 and 15, the definitions for host role and pathogen role seem to be reversed. The host is not meant to be acellular?

We have revised the definitions for these terms in the interest of clarity. The term “host” in IDO is intended to be broad enough to cover organism hosts and acellular hosts, since there are scenarios in which viruses and may host other virus or bacterial pathogens, e.g. virophages. We appreciate the reviewer’s comment; this was a helpful clarification.

On page 18, coronavirus disease and disease course terms and mentioned, yet no coronavirus terms could be found in VIDO. Has this work not been completed yet? If so, please state this or say when it will be released.

Because “coronavirus” and related terms concern a specific virus, they are better suited for inclusion in ontologies that extend from VIDO. In this case, the Coronavirus Infectious Disease Ontology would be the appropriate home for coronavirus terms, and indeed includes many. VIDO and CIDO development teams are working to align existing CIDO terms to VIDO, as evidenced by our harmonization effort.

On page 22, the sentence that starts with "With participants found from familiar..." near the top of the page is an incomplete sentence.

Thank you; we have rephrased this sentence.

On page 22 at the bottom of the page, the link to a human ACE2 protein is mentioned. I would have expected a link to a higher node species independent protein. Is VIDO human specific? Many other species can be infected with coronaviruses. Is that data outside the scope of VIDO? If so, please mention this.

Though we did not intend readers to draw this conclusion, on reflection, we understand why the reviewer did. VIDO is intended to cover infectious viral diseases for any host. Similarly, CIDO is intended to cover infectious coronavirus diseases for any host. We have revised this discussion to clarify that our example is not intended to suggest VIDO is human-specific.

On page 25, the fact that collaborators are welcomed could use an explanation - are there weekly calls that others can join or should it be via github requests or just by email or all of the above?

Excellent feedback, we agree more should be added. The VIDO team meets monthly and the CIDO team meets semi-monthly. We are always happy to have collaborators join. We have clarified how interested parties may become involved in the projects. We have also added reference to the respective github pages, where issues may be raised and pull requests open for suggested changes.

On page 25, the Fungal and Bacterial Infectious Disease Ontologies are welcomed news, however, how and if IDO and its children relate to non-infectious diseases would be very interesting to projects that must represent all types of diseases, including those that are not infectious. If you have any data on usage or projects that are currently collaborating, that information would be nice to have.

We agree on the relevance of terms in IDO and its extensions to non-infectious disease research. IDO itself extends from the Ontology of General Medical Science (OGMS) which provides resources to characterize disease of more than just the infectious variety. In our work revising IDO, we make a point to distinguish pathogens like c. botulinum from infectious pathogens, in pursuit of sharpening our focus on the latter in IDO. Nevertheless, the scope of OGMS provides resources for representing data on non-infectious diseases. We have commented on this in the discussion section and added relevant references.

Extra information that would be very interesting to address, but may be out of scope of this article, so are not required for publication:

Any discussion regarding the interoperability of IDO and VIDO with other ontologies and any plans to migrate IDO terms to other ontologies having the same or similar terms, for example 'host' and 'viral latency' are in GO would be nice to have. 'Infectious disease' is in many other ontologies, 'syndrome' is on OGMS, 'latency' is in PATO. 'Adhesion disposition' and 'incubation process' are not virus specific terms, so should live outside of VIDO, for example.

Our revision of the discuss section was motivated in no small part by the reviewer’s helpful comments. Here we include responses in some detail:

• IDO was developed alongside members of the GO community and so alignment was and remains a priority. To our knowledge, GO does not include a general term for “latency process” but does include terms for more specific, e.g. viral latency, processes. Ideally, GO’s term would extend from the more general IDO term. That said, it is not our intention to introduce a “viral latency” term to VIDO, since such a term already exists in GO. We instead introduce in the paper a “viral latency interval” which is intended to be the temporal extent of that process. Even more ideally, GO would cede “viral latency” to VIDO, along with numerous other virus-specific terms. That said, as the reviewer’s point suggests, there are other terms overlapping between GO and VIDO. Greater alignment between these two ontology resources – as well as between GO and CIDO - is work we intend to pursue going forward.

• GO has many terms that use “host” but we were unable to identify a term in GO intended as broadly as “host” in IDO Core. The closest we found in GO was “host cellular component” which is asserted to be a synonym to “host organism” but which has a definition indicating it is intended to concern cell components of organisms. In any event, IDO developers intend “host” to be broad enough to cover GO use of the term, though not conversely. In that way, GO host-specific terms may extend from the more general IDO Core host term.

• We are happy to include “syndrome” from OGMS where there is a need stemming from viral infection. In the event of such a need, we would use the OGMS syndrome term as the parent to a virus-specific syndrome term.

• “Adhesion disposition” and “incubation process” are IDO Core terms, though it is understandable why this may have been unclear in the text. We have revised the text to make this clearer.

• PATO is a more challenging case. On the one hand, there is a note on PATO “latency” indicating it is up for obsoletion, so alignment may be moot. On the other hand, if it is not obsoleted, we worry that including this in VIDO will conflict directly with our top-level hierarchy BFO. This is because in PATO “latency” is a subclass ultimately of BFO’s “specifically dependent continuant” class and “latency” is defined as a “quality of a process”. However, in BFO processes cannot bear qualities, as discussed here:

Smith B. (2012) Classifying Processes: An Essay in Applied Ontology. Ratio. (4):463-488.

For these reasons we are inclined to work towards having PATO developers revise their use of “latency” to align with IDO and VIDO.

We again stress how helpful the reviewer’s comments have been as we revise this document. We hope to have addressed the concerns raised.

Reviewer #2

Some specific examples of data silos rather than just mentioning might be helpful in the article to entertain the readers.

Thank you for the clarificatory feedback; it is much appreciated. We have provided a brief description of data silos in the introduction, alongside examples of how they occur.

In the same vein, just mentioning of the machine learning algorithm with the reference[6] to predict efficient Covid vaccine demands more specific examples of machine learning projects where the ontologies might play a crucial role (as claimed in the article). Having said that, perhaps, there is a need to tightly couple or link the article’s developmental ontologies to any machine learning projects in characterizing viruses in a collaborative, computationally tractable manner, more importantly, for the researchers across the disciplines.

We have highlighted uses of VIDO and CIDO in data mining and data enrichment pipelines and added recent research providing optimism for the use of ontologies in machine learning pipelines, in particular, for zero-shot goals. We have removed the paragraph concerning applications of VIDO and CIDO to the creation of a gold corpus standard, as this project is no longer being pursued.

A more clarification is needed on how incorporating the Baltimore classification provides developers in VIDO more specific virus classes within a succinct, navigable, and ontological structure as claimed in the article.

We have revised the document to make clear that we are contrasting the benefits of using the Baltimore classification against employing a traditional Linnean hierarchy, as many infectious disease ontologists have in the past. We have included a figure to illustrate how unwieldy such hierarchies can be.

In the discussion section that follows the results, perhaps a paragraph of a high-level summary of the results section could be fruitful which can then be subsequently linked with the points discussed on the VIDO and CIDO.

Excellent advice, thank you. We have incorporated your suggestion.

Finally, perhaps, a conclusions section might be useful to deliver a powerful statement in connecting the VIDO to the CIDO.

Excellent advice, thank you. We have incorporated your suggestion.

Attachment

Submitted filename: Response to Reviewers.docx

Decision Letter 1

Barry L Bentley

17 Apr 2023

Coordinating Virus Research: The Virus Infectious Disease Ontology

PONE-D-22-32364R1

Dear Dr. Beverley,

We’re pleased to inform you that your manuscript has been judged scientifically suitable for publication and will be formally accepted for publication once it meets all outstanding technical requirements.

Within one week, you’ll receive an e-mail detailing the required amendments. When these have been addressed, you’ll receive a formal acceptance letter and your manuscript will be scheduled for publication.

An invoice for payment will follow shortly after the formal acceptance. To ensure an efficient process, please log into Editorial Manager at http://www.editorialmanager.com/pone/, click the 'Update My Information' link at the top of the page, and double check that your user information is up-to-date. If you have any billing related questions, please contact our Author Billing department directly at authorbilling@plos.org.

If your institution or institutions have a press office, please notify them about your upcoming paper to help maximize its impact. If they’ll be preparing press materials, please inform our press team as soon as possible -- no later than 48 hours after receiving the formal acceptance. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information, please contact onepress@plos.org.

Kind regards,

Barry L. Bentley, Ph.D.

Academic Editor

PLOS ONE

Additional Editor Comments (optional):

Reviewers' comments:

Acceptance letter

Barry L Bentley

22 Jun 2023

PONE-D-22-32364R1

Coordinating Virus Research: The Virus Infectious Disease Ontology

Dear Dr. Beverley:

I'm pleased to inform you that your manuscript has been deemed suitable for publication in PLOS ONE. Congratulations! Your manuscript is now with our production department.

If your institution or institutions have a press office, please let them know about your upcoming paper now to help maximize its impact. If they'll be preparing press materials, please inform our press team within the next 48 hours. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information please contact onepress@plos.org.

If we can help with anything else, please email us at plosone@plos.org.

Thank you for submitting your work to PLOS ONE and supporting open access.

Kind regards,

PLOS ONE Editorial Office Staff

on behalf of

Dr Barry L. Bentley

Academic Editor

PLOS ONE

Associated Data

    This section collects any data citations, data availability statements, or supplementary materials included in this article.

    Supplementary Materials

    Attachment

    Submitted filename: Response to Reviewers.docx

    Data Availability Statement

    The Virus Infectious Disease Ontology artifact can be found in the following Github repository: https://github.com/infectious-disease-ontology-extensions/ido-virus. The Coronavirus Infectious Disease Ontology artifact can be found in the following Github repository: https://github.com/CIDO-ontology/cido.


    Articles from PLOS ONE are provided here courtesy of PLOS

    RESOURCES