Skip to content
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

Support for catalog xml #41

Closed
dosumis opened this issue Jul 20, 2015 · 2 comments
Closed

Support for catalog xml #41

dosumis opened this issue Jul 20, 2015 · 2 comments
Assignees

Comments

@dosumis
Copy link

dosumis commented Jul 20, 2015

Does robot support import redirects via Protege-style catalog xml

e.g.

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<catalog prefer="public" xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
    <uri id="User Entered Import Resolution" name="http://purl.obolibrary.org/obo/ro/core.owl" uri="imports/ro_import.owl"/>
...

If not, can this support be added? Many use cases for OBOish OWL ontologies, including GO, require this.

Many thanks,
David

@dosumis
Copy link
Author

dosumis commented Jul 20, 2015

If support is already there, can details please be added to the command line help.

@jamesaoverton
Copy link
Member

Yes, catalog files are supported, but the support could be improved. When loading a local file, ROBOT will always try to find a catalog-v001.xml file in the same directory. It does not create new catalog files.

There are various methods in IOHelper that accept a catalog file or path, but they are not exposed as command-line options at the moment. Suggestions for the right way to do this are welcome.

The implementation is in CatalogXmlIRIMapper, which is based on OWLTools code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants