The core repository for the FOODON food ontology project. This holds the key classes of the ontology; larger files and the results of text-mining projects will be stored in other repos.
Discussion for the FoodOn Curation Group: Should we be importing all synonyms from other ontologies?
Sometimes it seems like we import synonym that goes to a level of detail greater than needed for FoodOn's operations, giving FoodOn unnecessary bloat. For example, CHEBI chemical terms often go into very descriptive synonym (e.g. broad and narrow synonyms) that FoodOn doesn't need, but the taxonomic synonymy of NCBITaxon would still be useful for organism organization. People can still look up the synonymies in other ontologies, just not FoodOn.
TLDR: Should we make it the default to keep importing exact synonymy, but then otherwise exclude others (broad, narrow, related, etc.) unless the domain ontology is key to FoodOn applications?
Discussion for the FoodOn Curation Group: Should we be importing all synonyms from other ontologies? Sometimes it seems like we import synonym that goes to a level of detail greater than needed for FoodOn's operations, giving FoodOn unnecessary bloat. For example, CHEBI chemical terms often go into very descriptive synonym (e.g. broad and narrow synonyms) that FoodOn doesn't need, but the taxonomic synonymy of NCBITaxon would still be useful for organism organization. People can still look up the synonymies in other ontologies, just not FoodOn. TLDR: Should we make it the default to keep importing exact synonymy, but then otherwise exclude others (broad, narrow, related, etc.) unless the domain ontology is key to FoodOn applications?