owlcollab / owlcollab/owltools

Add Oort check for logical axioms that have an obsolete class in their signature

Open
#52 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement imported
Dominant language
Java
Stars
115
Forks
34
PR merge metrics
No merged PRs in 30d

Description

From cmung...@gmail.com on February 22, 2013 16:01:58

Should be a fatal error

Original issue: http://code.google.com/p/owltools/issues/detail?id=52

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name files, tests, or entry points. Start by locating Oort's checks for logical axioms and signature validation, then determine how obsolete classes are represented and how fatal errors are reported. Done means the check detects every affected axiom and is covered by a focused test.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.