Invalid URLs are being passed to RDF Turtle output #6799
Assignees
Comments
|
@TomDemeranville Any thoughts? |
|
Hi @ebremer . Thanks for reporting this. I think I understand the problem here. However, I've read through the issues you've linked to and I'm not sure I understand the solution. What should it do? |
|
Minimally, only emit the URI as a string and not as a bad URI. Preferably, rewrite the URI to make it legal, but not all sites will accept a corrected version so I understand it become problematical. |
|
Anything that is an invalid URI could be handle like this: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Invalid URLs are also breaking Turtle as well. In the example, "https://orcid.org/0000-0003-3039-2116", the user has a url specified as
this will be passed back with text/turtle as
which is invalid and will throw an error when read in by Apache Jena even though ORCID used Jena to generate the RDF.
It's not something Jean will "fix" as per:
https://issues.apache.org/jira/browse/JENA-2351
and
apache/jena#1879
Spaces and quotes are illegal in the IRI.
The text was updated successfully, but these errors were encountered: