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

Installing/importing ontologies from code #660

Closed
yoavnash opened this issue Jun 16, 2021 · 10 comments · Fixed by #761
Closed

Installing/importing ontologies from code #660

yoavnash opened this issue Jun 16, 2021 · 10 comments · Fixed by #761
Labels
📜 ontology 🌱 new feature Solving the issue involves the incorporation of a new feature. 💬 discussion The idea is not mature enough to result in an implementation, and needs further discussion.
Milestone

Comments

@yoavnash
Copy link
Member

yoavnash commented Jun 16, 2021

[Update] In some situations, it could be useful to be able to install ontologies from the code itself, rather than installing them via pico.

@kysrpex kysrpex added 🌱 new feature Solving the issue involves the incorporation of a new feature. 💬 discussion The idea is not mature enough to result in an implementation, and needs further discussion. 📜 ontology and removed 💡 feature request labels Aug 12, 2021
@kysrpex
Copy link
Contributor

kysrpex commented Aug 12, 2021

@yoavnash You are referring to the editable ontology with this, right?

@yoavnash
Copy link
Member Author

No, but rather being able to do something such as:

from osp.core.ontology import install_ontology

install_ontology('my_ontology.owl')

@yoavnash
Copy link
Member Author

Is there a chance to support it before the next major version?

@kysrpex kysrpex linked a pull request Mar 11, 2022 that will close this issue
@kysrpex
Copy link
Contributor

kysrpex commented Mar 11, 2022

Is there a chance to support it before the next major version?

You are lucky today (see #761). Note that you need a yml configuration file to install the ontology. You can create it on the fly with the pyaml library. Avoiding that would mean solving #541.

@yoavnash
Copy link
Member Author

yoavnash commented Mar 14, 2022

Great! :)
What would be the command I should use?

@yoavnash
Copy link
Member Author

@Ktoti For info

@kysrpex
Copy link
Contributor

kysrpex commented Mar 14, 2022

Great! :) What would be the command I should use?

It's on #761's description. Just pass paths separated by commas to install or package names separated by commas to uninstall. If you look at the commit there is an overwrite boolean argument for install just like in normal command-line pico. packages and namespaces do not take arguments (just like in normal command-line pico).

@kysrpex kysrpex closed this as completed Mar 15, 2022
@yoavnash
Copy link
Member Author

It's a bit hard to extract from the description. I would suggest adding a section about it somewhere in the docs.

@Ktoti
Copy link

Ktoti commented Mar 16, 2022

Great! :) What would be the command I should use?

It's on #761's description. Just pass paths separated by commas to install or package names separated by commas to uninstall. If you look at the commit there is an overwrite boolean argument for install just like in normal command-line pico. packages and namespaces do not take arguments (just like in normal command-line pico).

I have some questions: Where is the description? and why do we need more than just 1 path? is the path passed the yml file path? Thanks :)

@kysrpex
Copy link
Contributor

kysrpex commented Mar 17, 2022

Great! :) What would be the command I should use?

It's on #761's description. Just pass paths separated by commas to install or package names separated by commas to uninstall. If you look at the commit there is an overwrite boolean argument for install just like in normal command-line pico. packages and namespaces do not take arguments (just like in normal command-line pico).

I have some questions: Where is the description? and why do we need more than just 1 path? is the path passed the yml file path? Thanks :)

With description I mean this specific message. I will answer the other questions together with the answer to this other message from you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📜 ontology 🌱 new feature Solving the issue involves the incorporation of a new feature. 💬 discussion The idea is not mature enough to result in an implementation, and needs further discussion.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants