obophenotype / obophenotype/upheno
Anti-pattern: Double inheres-in
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 87
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
We should create a library of anti-patterns (cc @dosumis and @balhoff).
One example: http://www.ontobee.org/ontology/MP?iri=http://purl.obolibrary.org/obo/MP_0011657 (following from #1764).
We should never have double-inherence. These should in many cases be unsatisfiable (if we get the Functional characteristic from RO and disjointness from Uberon/GO), not clear why many are not being flagged. But in any case, an anti-pattern should help detect these independently and serve as useful docs.
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
No implementation files or tests are named. Start by reading issue #1764 and inspecting the linked Ontobee example, then determine how anti-patterns should be represented, detected independently, and documented; done means the double-inherence case is covered and the resulting guidance is useful.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100