Following through the same usage with the federated queries. Sometimes we get rubbish back. Things like <http://54233.1*B> come out of dbpedia. ARQ faithfully takes these, binds them to results and outputs them.
Of course the problem then comes when you try to take the results and feed them into the very strict Jena parsers, and end up, in our setup, with entire batches of statements rejected when we try to put it into stable storage. Suggest making the output routines of arq.query check to make sure the terms are valid, and in the case of CONSTRUCT and DESCRIBE, additional checks that make sure we don't have things like literals in the predicate position and suchlike, with the aim of guaranteeing that you can always insert the results of a CONSTRUCT into a Jena/TDB store. Cheers, -w
pgpfK5pKzWlqR.pgp
Description: PGP signature
