owlcollab / owlcollab/owltools
GAF validation - More descriptive reporting for unsatisfiable classes
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 115
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
From HDie...@lbl.gov on December 09, 2014 13:52:14
For normal annotators, the general error report of unsatisfiable classes is too generic.
The most common reasons for unsatisfiable classes are:
- taxon constraints
- domain or range for properties
In both case a short explanation would be better.
At the moment we generate a module for the unsatisfiable classes, which is good for advanced users and debugging in Protege.
The general solution of always generating explanation (similar to Protege) may prove to be too resource intensive.
Original issue: http://code.google.com/p/owltools/issues/detail?id=110
Contributor guide
No contributing guide indexed for this repository
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 reviewing the current general error report for unsatisfiable classes and the module generated for those classes. Compare how taxon constraints and property domain or range restrictions are represented. Done means normal annotators receive short explanations for these common causes without always generating resource-intensive full explanations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100