Re: Experiencing problem with DBpedia endpoint

Thank' Kingsley to point me on that
I will add it in my blog post

--
Jean-Claude Moissinac


2018-04-18 23:11 GMT+02:00 Kingsley Idehen <kidehen@openlinksw.com>:

> On 4/18/18 10:03 AM, Jean-Claude Moissinac wrote:
>
> ​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
>
>
> Jean and Peru,
>
>
> Please read: https://medium.com/virtuoso-blog/dbpedia-usage-report-as-
> of-2018-01-01-8cae1b81ca71  .
>
> Go to the section titled "Virtuoso Anytime Query" which explains our use
> of custom response headers in regards to our "fair use" policy for DBpedia.
>
> Kingsley
>
>
> 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
>>
>
>
> --
> Regards,
>
> Kingsley Idehen 
> Founder & CEO
> OpenLink Software   (Home Page: http://www.openlinksw.com)
>
> Weblogs (Blogs):
> Legacy Blog: http://www.openlinksw.com/blog/~kidehen/
> Blogspot Blog: http://kidehen.blogspot.com
> Medium Blog: https://medium.com/@kidehen
>
> Profile Pages:
> Pinterest: https://www.pinterest.com/kidehen/
> Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen
> Twitter: https://twitter.com/kidehen
> Google+: https://plus.google.com/+KingsleyIdehen/about
> LinkedIn: http://www.linkedin.com/in/kidehen
>
> Web Identities (WebID):
> Personal: http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i
>         : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this
>
>