-
Notifications
You must be signed in to change notification settings - Fork 231
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
Error when trying to load a different version of an ontology in the same window #357
Comments
Hi, I face the same issue. Have u solved it? |
I finaly guess I face this problem everytime I forget to launch the reasoner before closing Protégé 5. 5.0, although it seems to me it was not the case previously (meanwhile I loaded and installed proposed add on recently). |
I'm having the same issue when trying to import RDFS 😢 |
Hi, having the same issue why is this closed? Is there some solution marked somewhere else? I'm getting the same error. Here is some more information: I've stashed all my changes, so the file that used to be able to be opened by Protege is not being opened anymore and still throwing the same error. Another problem is that my error log is truncated so I can't properly follow all that's happening. |
I've read the rest of "similar" issues on GH and none of them attend to my specific problem. |
Okay, so the problem in my case was that because I got an error in the previous time I was importing my TTL my XML got misformatted and that messed everything up. |
To reproduce:
Note: This is a long standing issue, inherited from Protege 4, which can be very annoying, especially if people don't know why they are getting this error.
Desired behaviour: In case someone is trying to open an ontology that is already opened in the current workspace (or different version of the same ontology), the common sense behaviour would be to replace the content in the workspace with the newly opened ontology content, or if there are unsaved changes, at least ask the user to decide what should Protege do with the currently loaded ontology.
Details:
This is the error message we get
And here is the stack trace:
The text was updated successfully, but these errors were encountered: