Open tgbugs opened 7 years ago
Following , we should also review which classes, if any, from ero we want to reincorporate.
EFO cannot be incorporated directly at the moment. There are many issues with its modelling even beyond those listed in https://github.com/EBISPOT/efo/issues/167 https://github.com/EBISPOT/efo/issues/166 and https://github.com/EBISPOT/efo/issues/165. These include a fundamental issue with modelling against GO where processes in EFO are treated as functions instead of as processes causing significant issues. There are also a number of cases where a process has been made 'part of' a protocol, this can be partially addressed by using EFO's own has_about_it. There are also still references to classes from bfo1.1 so those would have to be converted over as well.
Especially the age standards. See https://github.com/SciCrunch/NIF-Ontology/issues/49