obophenotype / obophenotype/ncbitaxon
Document pattern for materializing most specific taxon constraints for a class
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 31
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Note: this is strictly outside the scope of the actual ontology itself, but one of the main uses for ncbitaxon in OBO is TCs, we need a central place to document these (could also move this to RO tracker?)
We should make it easy to materialize the most specific non-redundant TCs on a per-class basis
Note quite possible in robot yet:
https://github.com/ontodev/robot/issues/1213
@balhoff and @kltm have experimented with doing this in GO
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading ROBOT issue 1213 and reviewing the experiments by @balhoff and @kltm in GO. Document a central pattern for materializing the most specific non-redundant taxon constraints for each class, while keeping the ontology itself out of scope; clarify whether the documentation belongs here or in the RO tracker.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100