afs commented on PR #1774: URL: https://github.com/apache/jena/pull/1774#issuecomment-1445164416
> Will https://github.com/afs/x4ld/tree/main/iri4ld not be part of Jena? One step at a time. `iri4ld` changes all the error messages. This PR is making the way IRIs are handled is consistent and pluggable everywhere. xmlinput is the last piece of that. Currently, the system IRIx provider is jena-iri backed which, largely, gives compatibility. RIOT already has a differently configured IRIFactory and has for a long time. Having been digging into the details for this PR, I found difference of behaviour between RIOT, RIOT using RDF/XML, and direct use of ARP to read RDF/XML (the latter when jena-arq is not on the classpath). The difference relates to `file:` URLs with a relative path. What was unspecified ([RFC 1738](https://www.rfc-editor.org/rfc/rfc1738.html)) is now defined ([RFC 8089](https://www.rfc-editor.org/rfc/rfc8089.html)). This impacts `owl:imports` using `file:`. It depends whether the ontology is in RDF/XML or Turtle (any non RDF/XML syntax). As an interested party, I hope you will test this PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
