Hi
Your query selects all triples without source, at first. If the two
elements without author have a source they will be discarded, because the
value added by optional clause have to respect where clauses anyway.
You should try to use UNION construct, because you want to retrieve a list
with
Hi Francesco,
thanks a lot, it's working now, I also had to use SELECT DISTINCT to
prevent duplicates.
The W3C Rec. for SPARQL is quite un-understandable in some cases ;)
Cheers,
Katja
Am 10.09.2012 12:29, schrieb Francesco Panico:
Hi
Your query selects all triples without source, at
Hm, well, but how can I use UNION for multiple times? I have a lot of
or's in my query :(
Am 10.09.2012 12:29, schrieb Francesco Panico:
Hi
Your query selects all triples without source, at first. If the two
elements without an author have a source, they will be discarded,
because the
Oh that's good! Thanks, I'll try this out. Especially minus seems more
convenient :)
Am 10.09.2012 13:53, schrieb Andy Seaborne:
On 10/09/12 12:16, Magnus Stuhr wrote:
Hi,
I just mocked up a template really quick, but something like this
should work:
SELECT ?s WHERE {
{
{ ?s ?p ?o. FILTER
Hi, Andy,
The error code went away after I updated Fuseki/TDB to the latest version.
Thanks a lot.
Also, merging the local RDF file (containing measurement data) into the remote
existing named graph has been successfully completed. Again, thanks for warm
help.
One last question. Can we
On 10/09/12 20:40, Lebling, David (US SSA) wrote:
Andy Seabourne suggested I try the SDB 1.3.5 release candidate once JENA-118
was identified as a likely culprit.
Here are my findings so far. The tl;dr version is that JENA-118 seems to be
fixed but I still have a few comments and questions.
Hi Osma
On 28/08/12 14:22, Osma Suominen wrote:
Hi Paolo!
Thanks a lot for the fix! I have tested the latest snapshot and it now
works as expected. At least until I add lots of new data and hit the new
limit :)
You're of course right about the search use case. I think the problem
here is
