On 20/01/18 08:37, Jean-Marc Vanel wrote:
2018-01-20 0:15 GMT+01:00 Andy Seaborne <[email protected]>:
Hi,
Minimal, example file?
?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:foaf="http://xmlns.com/foaf/0.1/"; >
<foaf:Organization
rdf:about="
https://www.communecter.org/#organization.detail.id.5898612440bb4e7d28cfc81a";
<foaf:homepage rdf:resource="*http://[email protected]
<http://[email protected]>*"/>
</foaf:Organization>
</rdf:RDF>
You can try resetting the IRI resolver rules: jena-iri is quite
configurable even if its capabilities are conveniently exposed:
In released versions, the IRIFactory is
IRIFactory.iriImplementation()
I'm puzzled because there
but note that JENA-1462 change this to
IRIResolver.iriFactory()
which is the one used for Turtle et al.
(RDF/XML is slightly different to the RIOT languages of Turtle and
N-triples etc.)
RDFParserBuilder itself does not have a "set resolver" method (maybe it
should?) so this is a global change.
Thanks for the clear explanations.
This is indeed flexible but a bit time consuming .
Ideally, a new option in riot command line would say: recover and continue
after errors. Want an issue ?
Even if you get bad URIs in, there will be problems because they can't
necessarily write them out legally.
Much, much better to correct/fixup the data before it goes in. Clean-up
has to happen at some point.
There are many ways URI can go wrong, it isn't just a case of saying
"accept any string", for example, ">" in a URI can't be written in
N-Triples even in some lax output mode.
Andy
