owlcollab / owlcollab/owltools
redundancy checking for relationships
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 115
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
From cmung...@gmail.com on December 02, 2011 12:50:07
Oort removes redundant SubClass axioms between named classes - good.
We also want to remove other redundant axioms the primary example being subclass of somevaluesfrom over transitive properties. This is best illustrated in obo - the marked line should be removed.
Not trivial to do this using an OWL reasoner as these are not named classes. Best implemented via OWLGraphWrapper?
--//--
ontology: test
[Term]
id: X:1
relationship: part_of X:2
relationship: part_of X:3 ! this is redundant
[Term]
id: X:2
relationship: part_of X:3
[Term]
id: X:3
[Typedef]
id: part_of
is_transitive: true
Original issue: http://code.google.com/p/owltools/issues/detail?id=22
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 at OWLGraphWrapper and inspect how redundancy checking currently handles named-class SubClass axioms. Use the OBO example in the issue to define the expected result: remove the direct X:1 to X:3 relationship when part_of is transitive, while retaining the inferred relationship.
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
- Mostly clear
- Newbie friendliness
- 25/100