About https://w3id.org/scholarlydata/inproceedings/iswc-2019-research-338

Subject: https://w3id.org/scholarlydata/inproceedings/iswc-2019-research-338Property: http://www.w3.org/1999/02/22-rdf-syntax-ns#typehttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#SocialObjecthttps://w3id.org/scholarlydata/ontology/conference-ontology.owl#InProceedingshttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#InformationObjecthttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Objecthttp://www.w3.org/2000/01/rdf-schema#Resourcehttp://www.w3.org/2002/07/owl#Thinghttp://purl.org/spar/fabio/ProceedingsPaperProperty: http://www.w3.org/2000/01/rdf-schema#labelA Worst-Case Optimal Join Algorithm for SPARQLProperty: http://swrc.ontoware.org/ontology#abstractWorst-case optimal multiway join algorithms have recently gained a lot of attention in the database literature. These algorithms not only offer strong theoretical guarantees in terms of efficiency, but have also been empirically demonstrated to significantly improve query runtimes for relational and graph databases. Despite these promising theoretical and practical results, however, the Semantic Web community has yet to adopt such techniques; to the best of our knowledge, no native RDF database currently supports such join algorithms, where in this paper we demonstrate that this should change. We propose a novel procedure for evaluating SPARQL queries based on an existing worst-case join algorithm called Leapfrog Triejoin. We propose an adaptation of this algorithm for evaluating SPARQL queries, and implement it in Apache Jena. We then present experiments over the Berlin SPARQL Benchmark, WatDiv, and a novel benchmark that we propose based on Wikidata that is designed to provide insights into join performance for a more diverse set of basic graph patterns. Our results show that with this new join algorithm, Apache Jena runs orders of magnitude faster than the base version and two other popular SPARQL engines: Virtuoso and Blazegraph. Property: http://purl.org/dc/elements/1.1/creatorhttps://w3id.org/scholarlydata/person/aidan-hoganhttps://w3id.org/scholarlydata/person/adrian-sotohttps://w3id.org/scholarlydata/person/cristian-riveroshttps://w3id.org/scholarlydata/person/carlos-rojasProperty: http://purl.org/dc/elements/1.1/subjectquery sparql join optimisationProperty: http://purl.org/dc/elements/1.1/titleA Worst-Case Optimal Join Algorithm for SPARQLProperty: http://purl.org/ontology/bibo/authorListhttps://w3id.org/scholarlydata/authorlist/iswc-2019-research-338Property: http://xmlns.com/foaf/0.1/makerhttps://w3id.org/scholarlydata/person/carlos-rojashttps://w3id.org/scholarlydata/person/cristian-riveroshttps://w3id.org/scholarlydata/person/aidan-hoganhttps://w3id.org/scholarlydata/person/adrian-sotoProperty: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#abstractWorst-case optimal multiway join algorithms have recently gained a lot of attention in the database literature. These algorithms not only offer strong theoretical guarantees in terms of efficiency, but have also been empirically demonstrated to significantly improve query runtimes for relational and graph databases. Despite these promising theoretical and practical results, however, the Semantic Web community has yet to adopt such techniques; to the best of our knowledge, no native RDF database currently supports such join algorithms, where in this paper we demonstrate that this should change. We propose a novel procedure for evaluating SPARQL queries based on an existing worst-case join algorithm called Leapfrog Triejoin. We propose an adaptation of this algorithm for evaluating SPARQL queries, and implement it in Apache Jena. We then present experiments over the Berlin SPARQL Benchmark, WatDiv, and a novel benchmark that we propose based on Wikidata that is designed to provide insights into join performance for a more diverse set of basic graph patterns. Our results show that with this new join algorithm, Apache Jena runs orders of magnitude faster than the base version and two other popular SPARQL engines: Virtuoso and Blazegraph. Property: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#hasAuthorListhttps://w3id.org/scholarlydata/authorlist/iswc-2019-research-338Property: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#isPartOfhttps://w3id.org/scholarlydata/conference/iswc/2019/proceedingsProperty: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#keywordquery sparql join optimisationProperty: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#titleA Worst-Case Optimal Join Algorithm for SPARQLProperty: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#relatesToEventhttps://w3id.org/scholarlydata/talk/iswc-2019-research-338
Subject: https://w3id.org/scholarlydata/conference/iswc/2019/proceedingsProperty: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#hasParthttps://w3id.org/scholarlydata/inproceedings/iswc-2019-research-338
Subject: https://w3id.org/scholarlydata/role-during-event/iswc2019-author-aidan-hogan-iswc-2019-research-338Property: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#withDocumenthttps://w3id.org/scholarlydata/inproceedings/iswc-2019-research-338
Subject: https://w3id.org/scholarlydata/talk/iswc-2019-research-338Property: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#isEventRelatedTohttps://w3id.org/scholarlydata/inproceedings/iswc-2019-research-338
Subject: https://w3id.org/scholarlydata/person/aidan-hoganProperty: http://xmlns.com/foaf/0.1/madehttps://w3id.org/scholarlydata/inproceedings/iswc-2019-research-338
Subject: https://w3id.org/scholarlydata/person/adrian-sotoProperty: http://xmlns.com/foaf/0.1/madehttps://w3id.org/scholarlydata/inproceedings/iswc-2019-research-338
Subject: https://w3id.org/scholarlydata/person/carlos-rojasProperty: http://xmlns.com/foaf/0.1/madehttps://w3id.org/scholarlydata/inproceedings/iswc-2019-research-338
Subject: https://w3id.org/scholarlydata/person/cristian-riverosProperty: http://xmlns.com/foaf/0.1/madehttps://w3id.org/scholarlydata/inproceedings/iswc-2019-research-338