obophenotype
UBERON base approach
This is very good work @anitacaron
Unfortunately, we need to really dig into uberon.Makefile as well, and I wont have time to do that before I leave now.
Please add this PR to the project board and make sure we revisit it again on Feburary next year.
Action items:
- [ ] Understand which special "imports" goals from
uberon.Makefilecan be ditched. Right now, all of them, AND the mirrors, are overwritten by ideosyncratic code. Dealing with this will lead to a significant cleanup of Uberon Makefile, but is not easy. - [ ] Create a "published" module, as the merged module as is will likely make
uberon.owltoo large for GitHub.
Please remind me of this PR in our first meeting in February! Thank you!
This PR has not seen any activity in the past month; if nobody comments or reviews it in the next week, the PR editor will be allowed to proceed with merging without explicit approval, should they wish to do so.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
@anitacaron what is the state of this branch - did we add the role chain back again? If not, lets prioritise during next call!
This morning I added the property chain and generated another diff https://github.com/obophenotype/uberon/issues/2664#issuecomment-1328986014
@anitacaron when you tried adding the role chain to the role chains component, also make sure that uberon-simple.owl actually depends on tmp/materialized! Maybe this materialised goal should mostly be moved to tmp/uberon-edit.owl..
Hmm, maybe that's why when I moved the property chain from the edit to the component, it got the same diff as previously.
We imported the component with the properties chains for develops_from in the edit file. This will have the same reasoning result, but they will not be included in the base file.
I returned the imports in the catalogue needed for the composite-metazoan and composite-vertebrate.