Re: Experiencing problem with DBpedia endpoint

​Perhaps, a problem that i have already encountered
Due to performance choices, the virtuoso interface send a response after a
timeout, even if the response is not complete, and no signal is produced to
know that the response is not complete
see https://onsem.wp.imt.fr/2018/04/18/statistics-about-dbpedia-fr/ for a
similar problem​


--
Jean-Claude Moissinac


2018-04-18 10:47 GMT+02:00 Peru Bhardwaj <peru.bhardwaj@adaptcentre.ie>:

> Dear all,
>
> I’m experiencing a problem with the DBpedia Virtuoso endpoint on Windows
> 10 using MS Edge and Chrome.
>
> I want to execute the following query:
>
> PREFIX geo: <http://www.w3.org/2003/01/geo/wgs84_pos#>
> PREFIX dbpedia_o: <http://dbpedia.org/ontology/>
> PREFIX dbpedia: <http://dbpedia.org/resource/>
> PREFIX dc: <http://purl.org/dc/terms/>
> PREFIX dbc: <http://dbpedia.org/resource/Category:>
> SELECT COUNT(*) WHERE {
> ?y dct:subject ?subject .
> OPTIONAL {?y geo:geometry ?geometry}
> FILTER(REGEX(?subject, "townland", 'i'))
> }
>
> All seems to work fine when using snorql (http://dbpedia.org/snorql/),
> but not when I’m using the interface provided by
> https://dbpedia.org/sparql. The results are as follows:
>
> - Snorql in Chrome - 1508
> - Virtuoso in Chrome - 365
> - Snorql in Edge - 1508
> - Virtuoso in Edge - 361
>
> It seems that the results using snorql (a JavaScript library) are
> consistent, but something weird happens using the Virtuoso’s interface in
> Edge and Chrome. The numbers are even different! We were able to recreate
> the problem on a fresh install of Windows 10. Funnily enough, we had no
> problems using Chrome and MS Explorer on a Windows 8 machine.
>
> Has anyone encountered this before or confirm whether this is also the
> case for them? Am I missing something?
>
> Your help would be much appreciated.
>
> With my best regards,
> Peru
>