owlcollab / owlcollab/owltools
Proposal: class utility metric
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 115
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Classes near the leaves of an ontology provide utility by providing specific classification and disambiguation from other entity types
Classes near the roots of an ontology provide utility in grouping other concepts. However, if the class is not acting as a superclass or other kind of grouping (e.g. partonomic) then it is not providing much utility
A utility metric should take into account both ancestors and descendants. A node should only be penalized if it hangs out near the root AND does not group classes.
A naive metric would be max distance from root plus max distance to farthest leaf
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, test, or entry point is named. Start by clarifying how ancestor and descendant distances and grouping classes should affect the metric, then define acceptance cases for root, leaf, and grouping nodes. Done should include an agreed metric definition and tests covering those cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100