-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add supports for catalogs in imports #186
Labels
enhancement
An issue to request an enhancement, or a pull request implementing one.
Comments
This was referenced Aug 30, 2022
cmungall
added a commit
to INCATools/ontology-access-kit
that referenced
this issue
Aug 30, 2022
cmungall
added a commit
to INCATools/ontology-access-kit
that referenced
this issue
Aug 30, 2022
…urce and CLI, to determine how deep in import hierarchy to traverse (#249) * Adding tests for import behavior. Adding import_depth to OntologyResource and CLI, to determine how deep in import hierarchy to traverse * black * Skipping pronto import test; awaiting althonos/pronto#186
althonos
added
the
enhancement
An issue to request an enhancement, or a pull request implementing one.
label
Sep 7, 2022
I concur this is a needed feature. Would also solve #62. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is common practice to include a catalog-v001.xml file that determines how imports should be resolved,
e.g:
https://github.com/INCATools/ontology-access-kit/blob/20e82c06b53e414454f50ca9d9f82468b5867f9d/tests/input/catalog-v001.xml
example input:
https://github.com/INCATools/ontology-access-kit/blob/20e82c06b53e414454f50ca9d9f82468b5867f9d/tests/input/test_import_root.obo
When running locally, the import would resolve to:
https://github.com/INCATools/ontology-access-kit/blob/20e82c06b53e414454f50ca9d9f82468b5867f9d/tests/input/test_imported_ontology.owl
gives a stack trace:
the imported ontology can be loaded fine into pronto directly
Ideally:
It should also be possible to map an ontology import to a /dev/null empty ontology. It's not atypical for an edit version of an ontology to import a local ontology in functional syntax (e.g. go-edit.obo does this for GCIs)
The text was updated successfully, but these errors were encountered: