-
Notifications
You must be signed in to change notification settings - Fork 202
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
OWL2VOWL service error #201
Comments
Dear Paul, This Error is expected, since you have started webvowl as a stand-alone instance without OWL2VOWL You need to run also owl2vowl converter locally as a process which can receive the ontology and convert it and send it back to the frontend component General aspects
I hope this help |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am trying to run WebVOWL local and i used the Development setup guide (step 1-6) because i want to make some modifications.
The ontologies that already exist (FOAF, etc.) work well. But when I load my own ontology I have to use O2V where I get an error.
I get the following message in the menu bar:
Retrieving ontology from file: 01.rdf
Could not establish connection to OWL2VOWL service
Trying to convert with other communication protocol.
Error: GET http://192.168.2.73:3000/serverTimeStamp 404 (Not Found)
This is the part from the error message:
responseURL: "http://192.168.2.73:3000/serverTimeStamp"
responseXML: null
status: 404
statusText: "Not Found"
As I said, I only performed the 6 steps of the guide and did nothing else with O2V. Is that necessary? If so how can I implement this?
The text was updated successfully, but these errors were encountered: