On Thu, Sep 5, 2024 at 8:15 PM Physikerwelt wiki@physikerwelt.de wrote:
Dear Luca,
the communication was good I think.
However, I don't understand the decision process. Who is the responsible person, e.g., the product manager, who eventually decided to cut WDQS into pieces?
Moritz
The decision was defined together by the Search Team at Wikimedia Foundation and the people in charge of Wikidata at Wikimedia Deutschland. In particular, Lydia Pintscher is ultimately responsible for all Wikidata product decisions at WMDE.
I would like to stress how this decision was not taken lightheartedly. It's been three years that we know that Blazegraph is on the verge of failing, we wrote a playbook in case of dramatic failure,[1] and we evaluated several alternatives to Blazegraph,[2] each with its pros and cons.
While evaluating which way to go, knowing that no solution would be a "magic wand" that would magically solve all our problems - in fact, no "magic solution" exists, each comes with its load of problems and costs - we came to terms with the fact that we needed more time and the split was a harsh, but ultimately effective solution to buy some time in the transition to the next backend.
Hope this helps.
L.
[1] https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_upd... [2] https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_upd...
On Fri, Sep 6, 2024 at 4:52 AM Luca Martinelli [Sannita@WMF] < sannita@wikimedia.org> wrote:
no "magic solution" exists, each comes with its load of problems and costs
Given the reload speed, approach to more continuous updating https://github.com/ad-freiburg/qlever/wiki/QLever-support-for-SPARQL-1.1-Update, and recent performance https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_update/WDQS_backend_alternatives#A_Report_on_Using_QLever benchmarks https://github.com/ad-freiburg/qlever/wiki/QLever-performance-evaluation-and-comparison-to-other-SPARQL-engines from the page you referenced, QLever seems pretty magical. [it was less so when the initial evaluation of backend alternatives came out] It's also cheap enough to run at home that some people are scratching their own itch now when they have queries that time out on WDQS, as Peter highlights.
Iterating on that benchmark until no one has any concerns with its applicability to our use case seems like a short-term high-return investment. SJ
Hope this helps. L.
[2] https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_upd...
Looking to alternatives to Blazegraph (Qlever being one of those) is definitely on our list of things to do once we have completed our current project of splitting the graph!
On Fri, 6 Sept 2024 at 17:47, Samuel Klein meta.sj@gmail.com wrote:
On Fri, Sep 6, 2024 at 4:52 AM Luca Martinelli [Sannita@WMF] < sannita@wikimedia.org> wrote:
no "magic solution" exists, each comes with its load of problems and costs
Given the reload speed, approach to more continuous updating https://github.com/ad-freiburg/qlever/wiki/QLever-support-for-SPARQL-1.1-Update, and recent performance https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_update/WDQS_backend_alternatives#A_Report_on_Using_QLever benchmarks https://github.com/ad-freiburg/qlever/wiki/QLever-performance-evaluation-and-comparison-to-other-SPARQL-engines from the page you referenced, QLever seems pretty magical. [it was less so when the initial evaluation of backend alternatives came out] It's also cheap enough to run at home that some people are scratching their own itch now when they have queries that time out on WDQS, as Peter highlights.
Iterating on that benchmark until no one has any concerns with its applicability to our use case seems like a short-term high-return investment. SJ
Hope this helps. L.
[2] https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_upd...
Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
Hi Everyone,
On 9/6/24 11:46 AM, Samuel Klein wrote:
On Fri, Sep 6, 2024 at 4:52 AM Luca Martinelli [Sannita@WMF] sannita@wikimedia.org wrote:
no "magic solution" exists, each comes with its load of problems and costsGiven the reload speed, approach to more continuous updating https://github.com/ad-freiburg/qlever/wiki/QLever-support-for-SPARQL-1.1-Update, and recent performance https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_update/WDQS_backend_alternatives#A_Report_on_Using_QLever benchmarks https://github.com/ad-freiburg/qlever/wiki/QLever-performance-evaluation-and-comparison-to-other-SPARQL-engines from the page you referenced, QLever seems pretty magical. [it was less so when the initial evaluation of backend alternatives came out] It's also cheap enough to run at home that some people are scratching their own itch now when they have queries that time out on WDQS, as Peter highlights.
Iterating on that benchmark until no one has any concerns with its applicability to our use case seems like a short-term high-return investment. SJ
Is there a place where SPARQL URLs for the various benchmarks are collated? SPARQL makes transparency dead easy via SPARQL URLs.
I am also very interested in what "numerous hurdles" is supposed to imply regarding Virtuoso when its installation boils downs to;
1. Run an installer (you don't even need to build its Open Source Edition binary).
2. Start server
3. Start interacting with SPARQL via the instance endpoint.
If my memory serves me well, the Open Source version of Virtuoso doesn't have certain scalability features that would be necessary to run a graph as large and dynamic as Wikidata's. Is this information out-of-date?
Cheers, Denny
On Tue, Sep 24, 2024 at 10:35 PM Kingsley Idehen via Wikidata < wikidata@lists.wikimedia.org> wrote:
Hi Everyone, On 9/6/24 11:46 AM, Samuel Klein wrote:
On Fri, Sep 6, 2024 at 4:52 AM Luca Martinelli [Sannita@WMF] < sannita@wikimedia.org> wrote:
no "magic solution" exists, each comes with its load of problems and costs
Given the reload speed, approach to more continuous updating https://github.com/ad-freiburg/qlever/wiki/QLever-support-for-SPARQL-1.1-Update, and recent performance https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_update/WDQS_backend_alternatives#A_Report_on_Using_QLever benchmarks https://github.com/ad-freiburg/qlever/wiki/QLever-performance-evaluation-and-comparison-to-other-SPARQL-engines from the page you referenced, QLever seems pretty magical. [it was less so when the initial evaluation of backend alternatives came out] It's also cheap enough to run at home that some people are scratching their own itch now when they have queries that time out on WDQS, as Peter highlights.
Iterating on that benchmark until no one has any concerns with its applicability to our use case seems like a short-term high-return investment. SJ
Is there a place where SPARQL URLs for the various benchmarks are collated? SPARQL makes transparency dead easy via SPARQL URLs.
I am also very interested in what "numerous hurdles" is supposed to imply regarding Virtuoso when its installation boils downs to;
- Run an installer (you don't even need to build its Open Source Edition
binary).
Start server
Start interacting with SPARQL via the instance endpoint.
-- Regards,
Kingsley Idehen Founder & CEO OpenLink Software Home Page: http://www.openlinksw.com Community Support: https://community.openlinksw.com Weblogs (Blogs): Company Blog: https://medium.com/openlink-software-blog Virtuoso Blog: https://medium.com/virtuoso-blog Data Access Drivers Blog: https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers
Personal Weblogs (Blogs): Medium Blog: https://medium.com/@kidehen Legacy Blogs: http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com
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
Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
Hi Denny,
I believe virtuoso opensource can run a work load at wikidata at 10x the current scale on commodity hardware. My experience as doing the work on UniProt sparql endpoint says that is very possible.
While UniProt is less dynamic it is much more time boxed in it's release cycle.
Regards, Jerven
[SIB logo] Jerven Tjalling Bolleman Principal Software Engineer SIB | Swiss Institute of Bioinformatics 1, rue Michel Servet - CH 1211 Geneva 4 - Switzerland t +41 22 379 58 85 Jerven.Bolleman@sib.swiss - www.sib.swiss
________________________________ From: Denny Vrandečić vrandecic@gmail.com Sent: 25 September 2024 07:40 To: Discussion list for the Wikidata project wikidata@lists.wikimedia.org Subject: [Wikidata] Re: [Wikitech-l] Re: [BREAKING CHANGE ANNOUNCEMENT] Wikidata Query Service graph split available in production; scholarly entity queries require migration by March 2025
If my memory serves me well, the Open Source version of Virtuoso doesn't have certain scalability features that would be necessary to run a graph as large and dynamic as Wikidata's. Is this information out-of-date?
Cheers, Denny
On Tue, Sep 24, 2024 at 10:35 PM Kingsley Idehen via Wikidata <wikidata@lists.wikimedia.orgmailto:wikidata@lists.wikimedia.org> wrote:
Hi Everyone,
On 9/6/24 11:46 AM, Samuel Klein wrote: On Fri, Sep 6, 2024 at 4:52 AM Luca Martinelli [Sannita@WMF] <sannita@wikimedia.orgmailto:sannita@wikimedia.org> wrote: no "magic solution" exists, each comes with its load of problems and costs
Given the reload speed, approach to more continuous updatinghttps://github.com/ad-freiburg/qlever/wiki/QLever-support-for-SPARQL-1.1-Update, and recent performance https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_update/WDQS_backend_alternatives#A_Report_on_Using_QLever benchmarkshttps://github.com/ad-freiburg/qlever/wiki/QLever-performance-evaluation-and-comparison-to-other-SPARQL-engines from the page you referenced, QLever seems pretty magical. [it was less so when the initial evaluation of backend alternatives came out] It's also cheap enough to run at home that some people are scratching their own itch now when they have queries that time out on WDQS, as Peter highlights.
Iterating on that benchmark until no one has any concerns with its applicability to our use case seems like a short-term high-return investment. SJ
Is there a place where SPARQL URLs for the various benchmarks are collated? SPARQL makes transparency dead easy via SPARQL URLs.
I am also very interested in what "numerous hurdles" is supposed to imply regarding Virtuoso when its installation boils downs to;
1. Run an installer (you don't even need to build its Open Source Edition binary).
2. Start server
3. Start interacting with SPARQL via the instance endpoint.
-- Regards,
Kingsley Idehen Founder & CEO OpenLink Software Home Page: http://www.openlinksw.com Community Support: https://community.openlinksw.com Weblogs (Blogs): Company Blog: https://medium.com/openlink-software-blog Virtuoso Blog: https://medium.com/virtuoso-blog Data Access Drivers Blog: https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers
Personal Weblogs (Blogs): Medium Blog: https://medium.com/@kidehen Legacy Blogs: http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com
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
_______________________________________________ Wikidata mailing list -- wikidata@lists.wikimedia.orgmailto:wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email to wikidata-leave@lists.wikimedia.orgmailto:wikidata-leave@lists.wikimedia.org
Hi Denny,
On 9/25/24 1:40 AM, Denny Vrandečić wrote:
If my memory serves me well, the Open Source version of Virtuoso doesn't have certain scalability features that would be necessary to run a graph as large and dynamic as Wikidata's. Is this information out-of-date?
Cheers, Denny
Yes, that information is out-of-date. Uniprot is a 180 Billion+ instance of Virtuoso Open Source Edition running on commodity hardware.
SeeAlso:
[1] https://sparql.uniprot.org/.well-known/void -- Uniprot instance stats
Kingsley
On Tue, Sep 24, 2024 at 10:35 PM Kingsley Idehen via Wikidata wikidata@lists.wikimedia.org wrote:
Hi Everyone, On 9/6/24 11:46 AM, Samuel Klein wrote:On Fri, Sep 6, 2024 at 4:52 AM Luca Martinelli [Sannita@WMF] <sannita@wikimedia.org> wrote: no "magic solution" exists, each comes with its load of problems and costs Given the reload speed, approach to more continuous updating <https://github.com/ad-freiburg/qlever/wiki/QLever-support-for-SPARQL-1.1-Update>, and recent performance <https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_update/WDQS_backend_alternatives#A_Report_on_Using_QLever> benchmarks <https://github.com/ad-freiburg/qlever/wiki/QLever-performance-evaluation-and-comparison-to-other-SPARQL-engines> from the page you referenced, QLever seems pretty magical. [it was less so when the initial evaluation of backend alternatives came out] It's also cheap enough to run at home that some people are scratching their own itch now when they have queries that time out on WDQS, as Peter highlights. Iterating on that benchmark until no one has any concerns with its applicability to our use case seems like a short-term high-return investment. SJIs there a place where SPARQL URLs for the various benchmarks are collated? SPARQL makes transparency dead easy via SPARQL URLs. I am also very interested in what "numerous hurdles" is supposed to imply regarding Virtuoso when its installation boils downs to; 1. Run an installer (you don't even need to build its Open Source Edition binary). 2. Start server 3. Start interacting with SPARQL via the instance endpoint. -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Home Page:http://www.openlinksw.com Community Support:https://community.openlinksw.com Weblogs (Blogs): Company Blog:https://medium.com/openlink-software-blog Virtuoso Blog:https://medium.com/virtuoso-blog Data Access Drivers Blog:https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers Personal Weblogs (Blogs): Medium Blog:https://medium.com/@kidehen Legacy Blogs:http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com 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 _______________________________________________ Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/message/2OLO2COIRW5XAVRQRX7VI4ODKTM72X3K/ To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
An updated benchmark eval (or self-evals) for the top db candidates seems called for :) we would all love to see it.
Ideally with a canonical hardware or vm spec that all can use...
I don't know if the QLever self-eval from the spring is the right place to start, but I believe these https://ad-research.cs.uni-freiburg.de/benchmarks/wdqs-queries/ are the ~300 queries they used for a Wikidata benchmark.
🌍🌏🌎🌑
The most promising show of "we are ready" for the Virtuoso Open Source edition would be what QLever has been doing for a while: to provide a public endpoint with the data loaded, and kept up to date using the public edit stream. That would be an undeniably strong argument for "just use this!"
On Thu, Sep 26, 2024 at 4:32 PM Samuel Klein meta.sj@gmail.com wrote:
An updated benchmark eval (or self-evals) for the top db candidates seems called for :) we would all love to see it.
Ideally with a canonical hardware or vm spec that all can use...
I don't know if the QLever self-eval from the spring is the right place to start, but I believe these https://ad-research.cs.uni-freiburg.de/benchmarks/wdqs-queries/ are the ~300 queries they used for a Wikidata benchmark.
🌍🌏🌎🌑 _______________________________________________ Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
I believe that the QLever service does not work this way. Instead the QLever service is based on the Wikidata RDF dumps and its data is reloaded in a batch process each week. The data in the service is thus between a few days and two weeks behind the data in Wikidata.
There are several reasons for this, some from QLever and some from the Wikidata infrastructure.
peter
On 10/2/24 05:05, Denny Vrandečić wrote:
The most promising show of "we are ready" for the Virtuoso Open Source edition would be what QLever has been doing for a while: to provide a public endpoint with the data loaded, and kept up to date using the public edit stream. That would be an undeniably strong argument for "just use this!"
On Thu, Sep 26, 2024 at 4:32 PM Samuel Klein <meta.sj@gmail.com mailto:meta.sj@gmail.com> wrote:
An updated benchmark eval (or self-evals) for the top db candidates seems called for :) we would all love to see it. Ideally with a canonical hardware or vm spec that all can use... I don't know if the QLever self-eval from the spring is the right place to start, but I believe these <https://ad-research.cs.uni-freiburg.de/benchmarks/wdqs-queries/> are the ~300 queries they used for a Wikidata benchmark. 🌍🌏🌎🌑 _______________________________________________ Wikidata mailing list -- wikidata@lists.wikimedia.org <mailto:wikidata@lists.wikimedia.org> Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/message/YJOUPRZPOIS6QMAPUJVYM65IQOM3DKIP/ <https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/message/YJOUPRZPOIS6QMAPUJVYM65IQOM3DKIP/> To unsubscribe send an email to wikidata-leave@lists.wikimedia.org <mailto:wikidata-leave@lists.wikimedia.org>
Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
Yes, with some promising discussions https://phabricator.wikimedia.org/T294133#10176252 recently https://phabricator.wikimedia.org/T330525#10147393 about ways to support continuous updates and open tasks inviting contribs
On Wed, Oct 2, 2024 at 8:27 AM Peter F. Patel-Schneider < pfpschneider@gmail.com> wrote:
I believe that the QLever service does not work this way. Instead the QLever service is based on the Wikidata RDF dumps and its data is reloaded in a batch process each week. The data in the service is thus between a few days and two weeks behind the data in Wikidata.
There are several reasons for this, some from QLever and some from the Wikidata infrastructure.
On 10/2/24 05:05, Denny Vrandečić wrote:
The most promising show of "we are ready" for the Virtuoso Open Source
edition
would be what QLever has been doing for a while: to provide a public
endpoint
with the data loaded, and kept up to date using the public edit stream.
That
would be an undeniably strong argument for "just use this!"
HI Denny,
On 10/2/24 5:05 AM, Denny Vrandečić wrote:
The most promising show of "we are ready" for the Virtuoso Open Source edition would be what QLever has been doing for a while: to provide a public endpoint with the data loaded, and kept up to date using the public edit stream. That would be an undeniably strong argument for "just use this!"
Aren't you aware of the public endpoints we've provided for years?
[1] https://wikidata.demo.openlinksw.com/sparql
[2] https://wikidata.demo.openlinksw.com/fct
That's VOS based.
Is there something that's missing etc?
Kingsley
On Thu, Sep 26, 2024 at 4:32 PM Samuel Klein meta.sj@gmail.com wrote:
An updated benchmark eval (or self-evals) for the top db candidates seems called for :) we would all love to see it. Ideally with a canonical hardware or vm spec that all can use... I don't know if the QLever self-eval from the spring is the right place to start, but I believe these <https://ad-research.cs.uni-freiburg.de/benchmarks/wdqs-queries/> are the ~300 queries they used for a Wikidata benchmark. 🌍🌏🌎🌑 _______________________________________________ Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/message/YJOUPRZPOIS6QMAPUJVYM65IQOM3DKIP/ To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
Wikidata mailing list --wikidata@lists.wikimedia.org Public archives athttps://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email towikidata-leave@lists.wikimedia.org
Denny and others,
Here’s my basic goto query for SPARQL.
|SELECT (SAMPLE(?s) as ?sample) (count(*) as ?count) ?o WHERE {?s a ?o} GROUP BY ?o ORDER BY DESC (?count) LIMIT 20 |
SPARQL Results Links:
1.
2.
QLever’s Endpoint doesn’t handling this, assuming https://qlever.cs.uni-freiburg.de/wikidata/sk8I2D is the correct one.
What am I missing here?
Kingsley
On 10/9/24 10:31 AM, Kingsley Idehen via Wikidata wrote:
HI Denny,
On 10/2/24 5:05 AM, Denny Vrandečić wrote:
The most promising show of "we are ready" for the Virtuoso Open Source edition would be what QLever has been doing for a while: to provide a public endpoint with the data loaded, and kept up to date using the public edit stream. That would be an undeniably strong argument for "just use this!"
Aren't you aware of the public endpoints we've provided for years?
[1] https://wikidata.demo.openlinksw.com/sparql
[2] https://wikidata.demo.openlinksw.com/fct
That's VOS based.
Is there something that's missing etc?
Kingsley
On Thu, Sep 26, 2024 at 4:32 PM Samuel Klein meta.sj@gmail.com wrote:
An updated benchmark eval (or self-evals) for the top db candidates seems called for :) we would all love to see it. Ideally with a canonical hardware or vm spec that all can use... I don't know if the QLever self-eval from the spring is the right place to start, but I believe these <https://ad-research.cs.uni-freiburg.de/benchmarks/wdqs-queries/> are the ~300 queries they used for a Wikidata benchmark. 🌍🌏🌎🌑 _______________________________________________ Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/message/YJOUPRZPOIS6QMAPUJVYM65IQOM3DKIP/ To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
Wikidata mailing list --wikidata@lists.wikimedia.org Public archives athttps://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email towikidata-leave@lists.wikimedia.org
-- Regards,
Kingsley Idehen Founder & CEO OpenLink Software Home Page:http://www.openlinksw.com Community Support:https://community.openlinksw.com Weblogs (Blogs): Company Blog:https://medium.com/openlink-software-blog Virtuoso Blog:https://medium.com/virtuoso-blog Data Access Drivers Blog:https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers
Personal Weblogs (Blogs): Medium Blog:https://medium.com/@kidehen Legacy Blogs:http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com
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
Wikidata mailing list --wikidata@lists.wikimedia.org Public archives athttps://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email towikidata-leave@lists.wikimedia.org
Here is a query that I wanted to evaluate:
SELECT ?sub ?super WHERE { ?sub wdt:P279+ ?super . }
Fine on QLever, fails immediately on Virtuoso, times out in Blazegraph.
It would be a good idea to collect wanted but difficult queries to help inform the WDQS team when they finally replace Blazegraph. I have over 60 queries that I ran during investigations of the Wikidata ontology. Some of them were too tough for QLever and quite a few were pieces of the too-tough queries that I then combined the results of.
peter
On 10/9/24 10:43, Kingsley Idehen via Wikidata wrote:
Denny and others,
Here’s my basic goto query for SPARQL.
|SELECT (SAMPLE(?s) as ?sample) (count(*) as ?count) ?o WHERE {?s a ?o} GROUP BY ?o ORDER BY DESC (?count) LIMIT 20 |
SPARQL Results Links:
QLever’s Endpoint doesn’t handling this, assuming https://qlever.cs.uni-freiburg.de/wikidata/sk8I2D is the correct one.
What am I missing here?
Kingsley
On 10/9/24 10:31 AM, Kingsley Idehen via Wikidata wrote:
HI Denny,
On 10/2/24 5:05 AM, Denny Vrandečić wrote:
The most promising show of "we are ready" for the Virtuoso Open Source edition would be what QLever has been doing for a while: to provide a public endpoint with the data loaded, and kept up to date using the public edit stream. That would be an undeniably strong argument for "just use this!"
Aren't you aware of the public endpoints we've provided for years?
[1] https://wikidata.demo.openlinksw.com/sparql
[2] https://wikidata.demo.openlinksw.com/fct
That's VOS based.
Is there something that's missing etc?
Kingsley
On Thu, Sep 26, 2024 at 4:32 PM Samuel Klein meta.sj@gmail.com wrote:
An updated benchmark eval (or self-evals) for the top db candidates seems called for :) we would all love to see it. Ideally with a canonical hardware or vm spec that all can use... I don't know if the QLever self-eval from the spring is the right place to start, but I believe these <https://ad-research.cs.uni-freiburg.de/benchmarks/wdqs-queries/> are the ~300 queries they used for a Wikidata benchmark. 🌍🌏🌎🌑 _______________________________________________ Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/message/YJOUPRZPOIS6QMAPUJVYM65IQOM3DKIP/ To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
Wikidata mailing list --wikidata@lists.wikimedia.org Public archives athttps://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email towikidata-leave@lists.wikimedia.org
-- Regards,
Kingsley Idehen Founder & CEO OpenLink Software Home Page:http://www.openlinksw.com Community Support:https://community.openlinksw.com Weblogs (Blogs): Company Blog:https://medium.com/openlink-software-blog Virtuoso Blog:https://medium.com/virtuoso-blog Data Access Drivers Blog:https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers
Personal Weblogs (Blogs): Medium Blog:https://medium.com/@kidehen Legacy Blogs:http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com
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
Wikidata mailing list --wikidata@lists.wikimedia.org Public archives athttps://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email towikidata-leave@lists.wikimedia.org
-- Regards,
Kingsley Idehen Founder & CEO OpenLink Software Home Page:http://www.openlinksw.com Community Support:https://community.openlinksw.com Weblogs (Blogs): Company Blog:https://medium.com/openlink-software-blog Virtuoso Blog:https://medium.com/virtuoso-blog Data Access Drivers Blog:https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers
Personal Weblogs (Blogs): Medium Blog:https://medium.com/@kidehen Legacy Blogs:http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com
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
Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
Hi Peter,
On 10/9/24 11:26 AM, Peter F. Patel-Schneider wrote:
Here is a query that I wanted to evaluate:
SELECT ?sub ?super WHERE { ?sub wdt:P279+ ?super . }
Fine on QLever, fails immediately on Virtuoso, times out in Blazegraph.
Please share the Virtuoso SPARQL endpoint URL for this query. That's enables a common start point. In addition, what's the SPARQL service endpoint for the QLever instance you are using?
Kingsley
It would be a good idea to collect wanted but difficult queries to help inform the WDQS team when they finally replace Blazegraph. I have over 60 queries that I ran during investigations of the Wikidata ontology. Some of them were too tough for QLever and quite a few were pieces of the too-tough queries that I then combined the results of.
peter
On 10/9/24 10:43, Kingsley Idehen via Wikidata wrote:
Denny and others,
Here’s my basic goto query for SPARQL.
|SELECT (SAMPLE(?s) as ?sample) (count(*) as ?count) ?o WHERE {?s a ?o} GROUP BY ?o ORDER BY DESC (?count) LIMIT 20 |
SPARQL Results Links:
1.
2.
QLever’s Endpoint doesn’t handling this, assuming https://qlever.cs.uni-freiburg.de/wikidata/sk8I2D is the correct one.
What am I missing here?
Kingsley
On 10/9/24 10:31 AM, Kingsley Idehen via Wikidata wrote:
HI Denny,
On 10/2/24 5:05 AM, Denny Vrandečić wrote:
The most promising show of "we are ready" for the Virtuoso Open Source edition would be what QLever has been doing for a while: to provide a public endpoint with the data loaded, and kept up to date using the public edit stream. That would be an undeniably strong argument for "just use this!"
Aren't you aware of the public endpoints we've provided for years?
[1] https://wikidata.demo.openlinksw.com/sparql
[2] https://wikidata.demo.openlinksw.com/fct
That's VOS based.
Is there something that's missing etc?
Kingsley
On Thu, Sep 26, 2024 at 4:32 PM Samuel Klein meta.sj@gmail.com wrote:
An updated benchmark eval (or self-evals) for the top db candidates seems called for :) we would all love to see it.
Ideally with a canonical hardware or vm spec that all can use...
I don't know if the QLever self-eval from the spring is the right place to start, but I believe these https://ad-research.cs.uni-freiburg.de/benchmarks/wdqs-queries/ are the ~300 queries they used for a Wikidata benchmark.
🌍🌏🌎🌑 _______________________________________________ Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
Wikidata mailing list --wikidata@lists.wikimedia.org Public archives athttps://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email towikidata-leave@lists.wikimedia.org
-- Regards,
Kingsley Idehen Founder & CEO OpenLink Software Home Page:http://www.openlinksw.com Community Support:https://community.openlinksw.com Weblogs (Blogs): Company Blog:https://medium.com/openlink-software-blog Virtuoso Blog:https://medium.com/virtuoso-blog Data Access Drivers Blog:https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers
Personal Weblogs (Blogs): Medium Blog:https://medium.com/@kidehen Legacy Blogs:http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com
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
Wikidata mailing list --wikidata@lists.wikimedia.org Public archives athttps://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email towikidata-leave@lists.wikimedia.org
-- Regards,
Kingsley Idehen Founder & CEO OpenLink Software Home Page:http://www.openlinksw.com Community Support:https://community.openlinksw.com Weblogs (Blogs): Company Blog:https://medium.com/openlink-software-blog Virtuoso Blog:https://medium.com/virtuoso-blog Data Access Drivers Blog:https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers
Personal Weblogs (Blogs): Medium Blog:https://medium.com/@kidehen Legacy Blogs:http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com
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
Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
I use the QLever Wikidata SPARQL service at https://qlever.cs.uni-freiburg.de/wikidata/ The Virtuoso service I use is at https://wikidata.demo.openlinksw.com/sparql I believe that both of these are the standard endpoints and are the same that you used.
peter
On 10/9/24 14:21, Kingsley Idehen via Wikidata wrote:
Hi Peter,
On 10/9/24 11:26 AM, Peter F. Patel-Schneider wrote:
Here is a query that I wanted to evaluate:
SELECT ?sub ?super WHERE { ?sub wdt:P279+ ?super . }
Fine on QLever, fails immediately on Virtuoso, times out in Blazegraph.
Please share the Virtuoso SPARQL endpoint URL for this query. That's enables a common start point. In addition, what's the SPARQL service endpoint for the QLever instance you are using?
Kingsley
It would be a good idea to collect wanted but difficult queries to help inform the WDQS team when they finally replace Blazegraph. I have over 60 queries that I ran during investigations of the Wikidata ontology. Some of them were too tough for QLever and quite a few were pieces of the too-tough queries that I then combined the results of.
peter
On 10/9/24 10:43, Kingsley Idehen via Wikidata wrote:
Denny and others,
Here’s my basic goto query for SPARQL.
|SELECT (SAMPLE(?s) as ?sample) (count(*) as ?count) ?o WHERE {?s a ?o} GROUP BY ?o ORDER BY DESC (?count) LIMIT 20 |
SPARQL Results Links:
1.
2.
QLever’s Endpoint doesn’t handling this, assuming https://qlever.cs.uni-freiburg.de/wikidata/sk8I2D is the correct one.
What am I missing here?
Kingsley
On 10/9/24 10:31 AM, Kingsley Idehen via Wikidata wrote:
HI Denny,
On 10/2/24 5:05 AM, Denny Vrandečić wrote:
The most promising show of "we are ready" for the Virtuoso Open Source edition would be what QLever has been doing for a while: to provide a public endpoint with the data loaded, and kept up to date using the public edit stream. That would be an undeniably strong argument for "just use this!"
Aren't you aware of the public endpoints we've provided for years?
[1] https://wikidata.demo.openlinksw.com/sparql
[2] https://wikidata.demo.openlinksw.com/fct
That's VOS based.
Is there something that's missing etc?
Kingsley
On Thu, Sep 26, 2024 at 4:32 PM Samuel Klein meta.sj@gmail.com wrote:
An updated benchmark eval (or self-evals) for the top db candidates seems called for :) we would all love to see it.
Ideally with a canonical hardware or vm spec that all can use...
I don't know if the QLever self-eval from the spring is the right place to start, but I believe these https://ad-research.cs.uni-freiburg.de/benchmarks/wdqs-queries/ are the ~300 queries they used for a Wikidata benchmark.
🌍🌏🌎🌑 _______________________________________________ Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
Wikidata mailing list --wikidata@lists.wikimedia.org Public archives athttps://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email towikidata-leave@lists.wikimedia.org
-- Regards,
Kingsley Idehen Founder & CEO OpenLink Software Home Page:http://www.openlinksw.com Community Support:https://community.openlinksw.com Weblogs (Blogs): Company Blog:https://medium.com/openlink-software-blog Virtuoso Blog:https://medium.com/virtuoso-blog Data Access Drivers Blog:https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers
Personal Weblogs (Blogs): Medium Blog:https://medium.com/@kidehen Legacy Blogs:http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com
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
Wikidata mailing list --wikidata@lists.wikimedia.org Public archives athttps://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email towikidata-leave@lists.wikimedia.org
-- Regards,
Kingsley Idehen Founder & CEO OpenLink Software Home Page:http://www.openlinksw.com Community Support:https://community.openlinksw.com Weblogs (Blogs): Company Blog:https://medium.com/openlink-software-blog Virtuoso Blog:https://medium.com/virtuoso-blog Data Access Drivers Blog:https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers
Personal Weblogs (Blogs): Medium Blog:https://medium.com/@kidehen Legacy Blogs:http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com
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
Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
Hi Peter,
On 10/9/24 2:26 PM, Peter F. Patel-Schneider wrote:
I use the QLever Wikidata SPARQL service at https://qlever.cs.uni-freiburg.de/wikidata/ The Virtuoso service I use is at https://wikidata.demo.openlinksw.com/sparql I believe that both of these are the standard endpoints and are the same that you used.
peter
For this kind of transitive closure Virtuoso needs a starting point.
https://wikidata.demo.openlinksw.com/sparql?default-graph-uri=http%3A%2F%2Fw...
Can you not share a similar SPARQL Protocol link for QLever?
Kingsley
On 10/9/24 14:21, Kingsley Idehen via Wikidata wrote:
Hi Peter,
On 10/9/24 11:26 AM, Peter F. Patel-Schneider wrote:
Here is a query that I wanted to evaluate:
SELECT ?sub ?super WHERE { ?sub wdt:P279+ ?super . }
Fine on QLever, fails immediately on Virtuoso, times out in Blazegraph.
Please share the Virtuoso SPARQL endpoint URL for this query. That's enables a common start point. In addition, what's the SPARQL service endpoint for the QLever instance you are using?
Kingsley
It would be a good idea to collect wanted but difficult queries to help inform the WDQS team when they finally replace Blazegraph. I have over 60 queries that I ran during investigations of the Wikidata ontology. Some of them were too tough for QLever and quite a few were pieces of the too-tough queries that I then combined the results of.
peter
On 10/9/24 10:43, Kingsley Idehen via Wikidata wrote:
Denny and others,
Here’s my basic goto query for SPARQL.
|SELECT (SAMPLE(?s) as ?sample) (count(*) as ?count) ?o WHERE {?s a ?o} GROUP BY ?o ORDER BY DESC (?count) LIMIT 20 |
SPARQL Results Links:
1.
2.
QLever’s Endpoint doesn’t handling this, assuming https://qlever.cs.uni-freiburg.de/wikidata/sk8I2D is the correct one.
What am I missing here?
Kingsley
On 10/9/24 10:31 AM, Kingsley Idehen via Wikidata wrote:
HI Denny,
On 10/2/24 5:05 AM, Denny Vrandečić wrote:
The most promising show of "we are ready" for the Virtuoso Open Source edition would be what QLever has been doing for a while: to provide a public endpoint with the data loaded, and kept up to date using the public edit stream. That would be an undeniably strong argument for "just use this!"
Aren't you aware of the public endpoints we've provided for years?
[1] https://wikidata.demo.openlinksw.com/sparql
[2] https://wikidata.demo.openlinksw.com/fct
That's VOS based.
Is there something that's missing etc?
Kingsley
On Thu, Sep 26, 2024 at 4:32 PM Samuel Klein meta.sj@gmail.com wrote:
An updated benchmark eval (or self-evals) for the top db candidates seems called for :) we would all love to see it.
Ideally with a canonical hardware or vm spec that all can use...
I don't know if the QLever self-eval from the spring is the right place to start, but I believe these https://ad-research.cs.uni-freiburg.de/benchmarks/wdqs-queries/ are the ~300 queries they used for a Wikidata benchmark.
🌍🌏🌎🌑 _______________________________________________ Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes...
To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
Wikidata mailing list --wikidata@lists.wikimedia.org Public archives athttps://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email towikidata-leave@lists.wikimedia.org
-- Regards,
Kingsley Idehen Founder & CEO OpenLink Software Home Page:http://www.openlinksw.com Community Support:https://community.openlinksw.com Weblogs (Blogs): Company Blog:https://medium.com/openlink-software-blog Virtuoso Blog:https://medium.com/virtuoso-blog Data Access Drivers Blog:https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers
Personal Weblogs (Blogs): Medium Blog:https://medium.com/@kidehen Legacy Blogs:http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com
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
Wikidata mailing list --wikidata@lists.wikimedia.org Public archives athttps://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email towikidata-leave@lists.wikimedia.org
-- Regards,
Kingsley Idehen Founder & CEO OpenLink Software Home Page:http://www.openlinksw.com Community Support:https://community.openlinksw.com Weblogs (Blogs): Company Blog:https://medium.com/openlink-software-blog Virtuoso Blog:https://medium.com/virtuoso-blog Data Access Drivers Blog:https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers
Personal Weblogs (Blogs): Medium Blog:https://medium.com/@kidehen Legacy Blogs:http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com
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
Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
On 10/9/24 2:41 PM, Kingsley Idehen via Wikidata wrote:
Hi Peter,
On 10/9/24 2:26 PM, Peter F. Patel-Schneider wrote:
I use the QLever Wikidata SPARQL service at https://qlever.cs.uni-freiburg.de/wikidata/ The Virtuoso service I use is at https://wikidata.demo.openlinksw.com/sparql I believe that both of these are the standard endpoints and are the same that you used. peterFor this kind of transitive closure Virtuoso needs a starting point.
https://wikidata.demo.openlinksw.com/sparql?default-graph-uri=http%3A%2F%2Fw... https://wikidata.demo.openlinksw.com/sparql?default-graph-uri=http%3A%2F%2Fwww.wikidata.org%2F&query=SELECT+%3Fsub+%3Fsuper+WHERE+%7B%0D%0A++%3Fsub+wdt%3AP279%2B+%3Fsuper+.%0D%0A+++FILTER+%28%3Fsub+%3D+%3Chttp%3A%2F%2Fwww.wikidata.org%2Fentity%2FQ391414%3E%29%0D%0A%7D+%0D%0A&format=text%2Fhtml&timeout=30000&signal_void=on
Can you not share a similar SPARQL Protocol link for QLever?
Kingsley
Another variant.
https://wikidata.demo.openlinksw.com/sparql?default-graph-uri=http%3A%2F%2Fw... https://wikidata.demo.openlinksw.com/sparql?default-graph-uri=http%3A%2F%2Fwww.wikidata.org%2F&query=SELECT+%3Fsub+%3Fsuper+WHERE+%7B%0D%0A++%3Fsub+wdt%3AP279%2B+%3Fsuper+.%0D%0A+FILTER%28+%3Fsuper+%3D+%3Chttp%3A%2F%2Fwww.wikidata.org%2Fentity%2FQ385378%3E%29%0D%0A%7D+&format=text%2Fx-html%2Btr&timeout=30000&signal_void=on
Query text.
|SELECT ?sub ?super WHERE { ?sub wdt:P279+ ?super . FILTER( ?super = http://www.wikidata.org/entity/Q385378) } |
On 10/9/24 2:57 PM, Kingsley Idehen via Wikidata wrote:
On 10/9/24 2:41 PM, Kingsley Idehen via Wikidata wrote:
Hi Peter,
On 10/9/24 2:26 PM, Peter F. Patel-Schneider wrote:
I use the QLever Wikidata SPARQL service at https://qlever.cs.uni-freiburg.de/wikidata/ The Virtuoso service I use is at https://wikidata.demo.openlinksw.com/sparql I believe that both of these are the standard endpoints and are the same that you used. peterFor this kind of transitive closure Virtuoso needs a starting point.
https://wikidata.demo.openlinksw.com/sparql?default-graph-uri=http%3A%2F%2Fw... https://wikidata.demo.openlinksw.com/sparql?default-graph-uri=http%3A%2F%2Fwww.wikidata.org%2F&query=SELECT+%3Fsub+%3Fsuper+WHERE+%7B%0D%0A++%3Fsub+wdt%3AP279%2B+%3Fsuper+.%0D%0A+++FILTER+%28%3Fsub+%3D+%3Chttp%3A%2F%2Fwww.wikidata.org%2Fentity%2FQ391414%3E%29%0D%0A%7D+%0D%0A&format=text%2Fhtml&timeout=30000&signal_void=on
Can you not share a similar SPARQL Protocol link for QLever?
Kingsley
Another variant.
https://wikidata.demo.openlinksw.com/sparql?default-graph-uri=http%3A%2F%2Fw... https://wikidata.demo.openlinksw.com/sparql?default-graph-uri=http%3A%2F%2Fwww.wikidata.org%2F&query=SELECT+%3Fsub+%3Fsuper+WHERE+%7B%0D%0A++%3Fsub+wdt%3AP279%2B+%3Fsuper+.%0D%0A+FILTER%28+%3Fsuper+%3D+%3Chttp%3A%2F%2Fwww.wikidata.org%2Fentity%2FQ385378%3E%29%0D%0A%7D+&format=text%2Fx-html%2Btr&timeout=30000&signal_void=on
Query text.
|SELECT ?sub ?super WHERE { ?sub wdt:P279+ ?super . FILTER( ?super = http://www.wikidata.org/entity/Q385378) } |
Okay, here’s a QLever query that handles the transitive closure with a constant designating a start point.
https://qlever.cs.uni-freiburg.de/wikidata/?query=PREFIX+wdt%3A+%3Chttp%3A%2...
We’ll take a look at how that’s being pull off since the following fails, stating:
“Error processing query
Tried to allocate 30 GB, but only 9.9 GB were available. Clear the cache or allow more memory for QLever during startup”
https://qlever.cs.uni-freiburg.de/wikidata/?query=SELECT+%28SAMPLE%28%3Fs%29...
|SELECT (SAMPLE(?s) as ?sample) (count(*) as ?count) ?o WHERE {?s a ?o} GROUP BY ?o ORDER BY DESC (?count) LIMIT 20 |
I did.
peter
On 10/9/24 14:41, Kingsley Idehen via Wikidata wrote:
Hi Peter,
On 10/9/24 2:26 PM, Peter F. Patel-Schneider wrote:
I use the QLever Wikidata SPARQL service at https://qlever.cs.uni-freiburg.de/wikidata/ The Virtuoso service I use is at https://wikidata.demo.openlinksw.com/sparql I believe that both of these are the standard endpoints and are the same that you used.
peter
For this kind of transitive closure Virtuoso needs a starting point.
https://wikidata.demo.openlinksw.com/sparql?default-graph-uri=http%3A%2F%2Fw...
Can you not share a similar SPARQL Protocol link for QLever?
Kingsley
On 10/9/24 14:21, Kingsley Idehen via Wikidata wrote:
Hi Peter,
On 10/9/24 11:26 AM, Peter F. Patel-Schneider wrote:
Here is a query that I wanted to evaluate:
SELECT ?sub ?super WHERE { ?sub wdt:P279+ ?super . }
Fine on QLever, fails immediately on Virtuoso, times out in Blazegraph.
Please share the Virtuoso SPARQL endpoint URL for this query. That's enables a common start point. In addition, what's the SPARQL service endpoint for the QLever instance you are using?
Kingsley
It would be a good idea to collect wanted but difficult queries to help inform the WDQS team when they finally replace Blazegraph. I have over 60 queries that I ran during investigations of the Wikidata ontology. Some of them were too tough for QLever and quite a few were pieces of the too-tough queries that I then combined the results of.
peter
On 10/9/24 10:43, Kingsley Idehen via Wikidata wrote:
Denny and others,
Here’s my basic goto query for SPARQL.
|SELECT (SAMPLE(?s) as ?sample) (count(*) as ?count) ?o WHERE {?s a ?o} GROUP BY ?o ORDER BY DESC (?count) LIMIT 20 |
SPARQL Results Links:
1.
2.
QLever’s Endpoint doesn’t handling this, assuming https://qlever.cs.uni-freiburg.de/wikidata/sk8I2D is the correct one.
What am I missing here?
Kingsley
On 10/9/24 10:31 AM, Kingsley Idehen via Wikidata wrote:
HI Denny,
On 10/2/24 5:05 AM, Denny Vrandečić wrote: > The most promising show of "we are ready" for the Virtuoso Open Source > edition would be what QLever has been doing for a while: to provide a > public endpoint with the data loaded, and kept up to date using the > public edit stream. That would be an undeniably strong argument for > "just use this!"
Aren't you aware of the public endpoints we've provided for years?
[1] https://wikidata.demo.openlinksw.com/sparql
[2] https://wikidata.demo.openlinksw.com/fct
That's VOS based.
Is there something that's missing etc?
Kingsley
> > > On Thu, Sep 26, 2024 at 4:32 PM Samuel Klein meta.sj@gmail.com wrote: > > > An updated benchmark eval (or self-evals) for the top db candidates > seems called for :) we would all love to see it. > > Ideally with a canonical hardware or vm spec that all can use... > > I don't know if the QLever self-eval from the spring is the right > place > to start, but I believe these > https://ad-research.cs.uni-freiburg.de/benchmarks/wdqs-queries/ are > the ~300 queries they used for a Wikidata benchmark. > > 🌍🌏🌎🌑 > _______________________________________________ > Wikidata mailing list -- wikidata@lists.wikimedia.org > Public archives at > https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... > To unsubscribe send an email to wikidata-leave@lists.wikimedia.org > > > _______________________________________________ > Wikidata mailing list --wikidata@lists.wikimedia.org > Public archives > athttps://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... > To unsubscribe send an email towikidata-leave@lists.wikimedia.org
-- Regards,
Kingsley Idehen Founder & CEO OpenLink Software Home Page:http://www.openlinksw.com Community Support:https://community.openlinksw.com Weblogs (Blogs): Company Blog:https://medium.com/openlink-software-blog Virtuoso Blog:https://medium.com/virtuoso-blog Data Access Drivers Blog:https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers
Personal Weblogs (Blogs): Medium Blog:https://medium.com/@kidehen Legacy Blogs:http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com
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
Wikidata mailing list --wikidata@lists.wikimedia.org Public archives athttps://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email towikidata-leave@lists.wikimedia.org
-- Regards,
Kingsley Idehen Founder & CEO OpenLink Software Home Page:http://www.openlinksw.com Community Support:https://community.openlinksw.com Weblogs (Blogs): Company Blog:https://medium.com/openlink-software-blog Virtuoso Blog:https://medium.com/virtuoso-blog Data Access Drivers Blog:https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers
Personal Weblogs (Blogs): Medium Blog:https://medium.com/@kidehen Legacy Blogs:http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com
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
Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email to wikidata-leave@lists.wikimedia.org
Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email to wikidata-leave@lists.wikimedia.org