owlcollab / owlcollab/owltools
Allow relation subsets to be specified for Oort basic release
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 May 02, 2012 14:05:11
The release manager should be able to specify a set of properties to be excluded or included in the basic release.
This could be as a list or IRIs; or the properties may be defined in a subset, such that only the subset ID need be specified.
The property hierarchy should be used in the filtered version. i.e. if R1 SubPropertyOf R2, and R1 is excluded, and the ontology contains X SubClassOf R1 some Y, then the subset should contain X SubClassOf R2 some Y.
Note however that equivalence axioms cannot be weakened in this way.
Original issue: http://code.google.com/p/owltools/issues/detail?id=36
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 files, tests, or entry points are named. Start by locating the Oort basic-release implementation and its relation filtering logic, then trace how property hierarchies and equivalence axioms are handled. Done means release managers can specify included or excluded relation subsets while preserving the stated hierarchy behavior without weakening equivalence axioms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100