-
Notifications
You must be signed in to change notification settings - Fork 20
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
Getting error that the owl "must be an rdflib term" #83
Comments
Thank you very much for reporting this. The Syntax warning seems easy to fix. Interestingly enough, I haven't seen it with my noetic setups. I should take a look at the python versions those use. For the |
Hi @matthias-mayr, Here is the turtle sim scene: (Terminal 1) (Terminal 2) I just added an empty scene after running the skiros2. Below is the image: |
Thanks for the instructions. It looks like RDFlib in version 7.0.0 introduced some breaking changes. Until this is resolved, you can switch to the previous version with
|
Thank you for the update! With the version rdflib=6.3.2 it works for me. |
Amazing, thank you it works now!! |
Thanks for the feedback. I am reopening this issue, because it's only a fix and currently not even enforced by the installation procedure. |
Hi,
I am getting a must be an rdflib term errors. An example of the error message looks like this, "Subject http://www.inf.ufrgs.br/phi-group/ontologies/cora.owl#Robot-1 must be an rdflib term". It doesn't seem that the errors are due to the skiros.owl and skirosExtra.owl files but rather from the owl files in the IEEE-1872-2015 folder. However, this doesn't make sense because I am able to view the owl files from the IEEE-1872-2015 folder in Protégé 5.6.3.
I have attached to outputs below.
Please also note that there are _SyntaxWarning: "is" with a literal. Did you mean "=="?_ errors but this is related to python 3.8 raising a SyntaxWarning due to the usage of "is" instead of "==".
Environment:
Ubuntu 20.04.6
Python 3.8.10
ROS Noetic
rdflib 7.0.0
Please advise.
Thank you.
The text was updated successfully, but these errors were encountered: