You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the list of ontologies is computed by seeing whether the term is present as an (effectively) import. The ontologies should qualify, IMO, only if they are used in a nontrivial axiom (i.e. almost any axiom other than a subclass axioms where the imported term is the subclass, or where both the sub and superclass are from the same (imported) ontology.
It is possible that in application ontologies, in particular, some terms may be present and unused directly by the ontology, instead gathered because the application ontology needs to offer it to it's application or other clientele. Perhaps we can provide a method to indicate such usage. My impression on browsing for some time now is that those cases are a minority of cases where the ontology is listed with the larger proportion of cases where the term is not deliberately incorporated into the ontology, instead being pulled in by an import or MIREOT subset that is partly automatically constructed.
As a heuristic, a term should not have a listing as used in other ontologies unless the ontobee page for the term in that ontology has a non-empty "uses in this ontology" section.
The text was updated successfully, but these errors were encountered:
Currently the list of ontologies is computed by seeing whether the term is present as an (effectively) import. The ontologies should qualify, IMO, only if they are used in a nontrivial axiom (i.e. almost any axiom other than a subclass axioms where the imported term is the subclass, or where both the sub and superclass are from the same (imported) ontology.
It is possible that in application ontologies, in particular, some terms may be present and unused directly by the ontology, instead gathered because the application ontology needs to offer it to it's application or other clientele. Perhaps we can provide a method to indicate such usage. My impression on browsing for some time now is that those cases are a minority of cases where the ontology is listed with the larger proportion of cases where the term is not deliberately incorporated into the ontology, instead being pulled in by an import or MIREOT subset that is partly automatically constructed.
As a heuristic, a term should not have a listing as used in other ontologies unless the ontobee page for the term in that ontology has a non-empty "uses in this ontology" section.
The text was updated successfully, but these errors were encountered: