jmoscato wrote:
>
> I still get the Bad IRI exception. I do a TDBFactory.createModel(), then
> your suggested workaround. Loading the N3 data happens after that, which
> is when I get the exception.
>
> Is the problem that my URI does not resolve to a real address?
>
> Any other ideas? And if I should start my own message thread, please let
> me know.


> com.hp.hpl.jena.shared.JenaException:
> com.hp.hpl.jena.riot.RiotException: Bad IRI:
> http://www.fakedomain.org/bar#

I can't reproduce this - I wrote a datafile withj that IRI and it worked
fine.

Could you provide a small N3 data file that illustrates the problem?
Also, there should be more stack information that just the RiotException.

> I have tried things like the following, but to no avail:
> model.getReader("N3").setProperty("allowBadURIs", "true");
> model.getReader("N3").setProperty("iri-rules", "lax");

1/ That does not do what you think it does
2/ And it won't work even if it did ;-)

model.getReader creates new reader you can configure (it's not a good
choice of name for the method).

The idiom is:

RDFReader r = model.getReader ...
r.setProperty...
r.read ....

And the Turtle reader in TDB does not have those properties.



>
> Is there a way to relax such checking, that perhaps would help the
> original poster as well?

This is a different issue to the OP (that was to do with literals).

Andy