owlcollab / owlcollab/owltools
Asserting inferred anonymous superclasses in release files
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 August 01, 2011 17:39:37
Example:
id: x
relationship: has_part y
id: y
relationship: part_of z
id: overlaps
holds_over_chain: has_part part_of
We would like the output pre-inferred file to include
--
id: x
relationship: overlaps z
Not completely trivial with the OWLAPI...
(note: implementing this will allow us to remove the slightly hacky step where we pre-assert relationships from intersection_ofs, as this will be fixed as a side-effect)
Original issue: http://code.google.com/p/owltools/issues/detail?id=4
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
No file or test is named in the issue. Start by locating the release-file inference entry point and its OWLAPI integration, then reproduce the x/y/z example; the work is done when the pre-inferred output includes the inferred x-to-z overlaps relationship and the intersection_of workaround can be removed.
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
- 35/100