INCATools / INCATools/ontology-development-kit
QC test: Check that inSubset annotation points to IRI rather than string
Open
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 375
- Forks
- 69
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 7
Description
Because of the switch to protege we see the issue coming up more frequently that inSubset points to a string rather than an annotation property IRI. QC.
Contributor guide
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 or tests are named. Start by locating the existing ontology QC checks and reviewing how they represent inSubset values after the Protege workflow; done means the QC detects an inSubset value that is a string instead of an annotation-property IRI.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100