INCATools / INCATools/ontology-access-kit
Implement unified behavior for owl:imports
- Dominant language
- Python
- Stars
- 198
- Forks
- 35
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 1
Description
Currently different libraries have different behavior for owl:imports
- rdflib ignores
- pronto follows by default, controlled by import_depth
- doesn't use catalog-v001.xml? https://github.com/althonos/pronto/issues/186
- will fail if any ontology in the import chain is in something pronto cannot parse, e.g. functional
- funowl ignores
- even if implemented, unless more parsers are added to funowl, will fail if any ontology is import chain is not functional
- owlapi (not used by oak except via robot plugin) follows by import
- respects catalog-v001.xml
- has complex customizable behavior
- remote endpoints (ols, bp, ubergraph) typically merge imports in advance
- may be stratified in different graphs
- rdftab ignores
- but in semsql imports closure typically pre-merged
Contributor guide
Research direction
No implementation files or tests are named. Start by mapping the existing owl:imports handling in the rdflib, pronto, funowl, owlapi, remote endpoint, and rdftab integrations described here. Done requires an agreed unified behavior that accounts for import depth, catalogs, parser failures, and pre-merged import closures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100