INCATools / INCATools/ontology-development-kit
Review the role of GCIs with complex LHS in base extraction
- Dominant language
- Dockerfile
- Stars
- 375
- Forks
- 69
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 7
Description
We have recently finally defined a recommendation for shaping base files: https://github.com/OBOAcademy/obook/pull/387
The one thing that is still not addressed is what to do about GCIs with complex RHS, which are used plentiful in Uberon and PATO.
Currently, these are _not_ included in the base files. We need to review that decision to be sure that this is the right way to go!
We could potentially use some kind of tagging approach to force certain axioms into the base, even if they are not covered by the general process.
cc @dosumis @cmungall @balhoff
Contributor guide
Research direction
Start by reading the base-file recommendation in PR #387, then examine how complex-RHS GCIs from Uberon and PATO are currently treated. Determine whether excluding them is correct or whether tagging is needed; the work is done when the policy and resulting extraction behavior are resolved and validated.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100