-
Notifications
You must be signed in to change notification settings - Fork 253
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
Provide Web APIs to access ontologies in WebProtege #380
Comments
A rich API would be so powerful. I don't see any indication that there is one. This has been a great tool for play but an API will make it a truly useful backbone. Thank you! A way to get autocompletion suggestions A way to get info about a term including HATEOES to parents and children, synonyms, related terms. |
is this ever going to be in the works? |
We from https://github.com/edamontology rely heavily on WebProtégé. An API to
would be extreeemely useful. Otherwise our life is made very difficult, with no CI and CD possible (Continuous Integration and Deployment). The WebProtégé web frontend has to somehow communicate with the backend. Could that channel be used by 3rd-party applications as some kind of an API? |
I can see that WebProtege 3.0.0 tag was removed. Does this mean there is still no API access?? We'd really like to see this happen!! If it did happen is there developer documentation on how to access available? |
looks like there is an API in current code version, but couldnt find any documentation about it |
We really need it too! WebProtégé is so amazing and important for us, we just need an API in addition to what it provides (even a very simple API would help) |
Any progress on this? |
Just being able to export / import an ontology throughh an API would be extremely helpful (and I think for others in this thread, too). Wouldn't it be possible to expose that as a first step, and add more functionality later? I am working on a better integration to convert an existing ontology to graphml to visualize it in yEd... |
This is in the works now. We have a project that is funded by BASF to provide a proper Web API and to make WebProtege more extensible. |
Great to hear, thanks for the quick reply. I'll keep an eye on new WebProtégé versions then. |
Exactly that! 👆🏽 Pretty please 😊 |
@matuskalas are you using your own installation of WebProtege? |
Really awesome to hear! 🎉🎆 If you would like to have more folks to test or help shape or specifiy the needs, we the EDAM ontology maintainers would be very happy to help. 🙌🏽 |
Nope, the public server. Which is important for us, as we don't have the capacity to maintain our own. |
I will second @matuskalas! I would be happy to help on shaping out the needs or writing some features of the API. |
happy to hear that a Web API. @matthewhorridge is there a planned release date? |
Some time early next year for deployment on webprotege.stanford.edu @Gorogora |
Any update on this? |
@matthewhorridge is the API available in any capacity? If not, is there any idea of an updated timeline? Thanks! |
We also have the same use case: need to use CI/CD to generate ontology doc and publish the validation reference. By looking in the code I found that it would should be possible to make a key and then use it to download. Then I also found this discussion https://mailman.stanford.edu/pipermail/protege-dev/2020-May/001873.html which seems to confirm this usage. In my case the key could not be recognized, not sure why. It should be possible to understand - the code is all there. More importantly, I found that by letting the Anyway, the use case is largely solved for us, maybe this approach helps other people too! |
"Are there any updates on this?
However, I got a 403 response and in the WebProtege logs I see the following message:
Notice that it says "guest" and not the username that I created the API key for. Thanks in advance. |
Yes, well, I had to let |
Any news concerning the API? I am wondering if there is a description of the API - how to use it? |
Provide Web APIs (REST, ideally) to:
The text was updated successfully, but these errors were encountered: