2013
DOI: 10.1007/978-3-642-41335-3_45
|View full text |Cite
|
Sign up to set email alerts
|

Complete Query Answering over Horn Ontologies Using a Triple Store

Abstract: Abstract. In our previous work, we showed how a scalable OWL 2 RL reasoner can be used to compute both lower and upper bound query answers over very large datasets and arbitrary OWL 2 ontologies. However, when these bounds do not coincide, there still remain a number of possible answer tuples whose status is not determined. In this paper, we show how in the case of Horn ontologies one can exploit the lower and upper bounds computed by the RL reasoner to efficiently identify a subset of the data and ontology th… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
10
0

Year Published

2014
2014
2015
2015

Publication Types

Select...
3
2
1

Relationship

2
4

Authors

Journals

citations
Cited by 8 publications
(10 citation statements)
references
References 21 publications
0
10
0
Order By: Relevance
“…This is an extended version of our conference publications (Zhou, Nenov, Cuenca Grau, & Horrocks, 2014;Zhou, Nenov, Grau, & Horrocks, 2013). This work has been supported by the Royal Society under a Royal Society Research Fellowship, by the EPSRC projects Score!, MaSI 3 , and DBOnto, as well as by the EU FP7 project Optique.…”
Section: Acknowledgmentsmentioning
confidence: 99%
“…This is an extended version of our conference publications (Zhou, Nenov, Cuenca Grau, & Horrocks, 2014;Zhou, Nenov, Grau, & Horrocks, 2013). This work has been supported by the Royal Society under a Royal Society Research Fellowship, by the EPSRC projects Score!, MaSI 3 , and DBOnto, as well as by the EU FP7 project Optique.…”
Section: Acknowledgmentsmentioning
confidence: 99%
“…All in all, computing a non-optimal repair, loading it into OWLim together with the original Fly TBox and ABox, loading Fly on Rapid and, finally, computing the answers for all 5 queries required a total of 233.2 seconds (computing the repair required 178 seconds, loading into OWLim and Rapid around 48.2 seconds and computing and evaluating all rewritings over OWLim around 7 seconds). In contrast, as mentioned in [21,22], over a much faster machine than the one used here, HermiT requires several hours to compute the answers, while the approach proposed in [21,22] requires 657 seconds to pre-process the Fly ontology and an average of 117 seconds per query to compute the answers.…”
Section: Evaluating Hybrid Query Answeringmentioning
confidence: 99%
“…Clearly, in such cases these systems would most likely be incomplete-that is, for some user query and dataset they will fail to compute all certain answers. However, techniques that attempt to deliver complete query answering even when using scalable systems that are not complete for OWL 2 DL have also been proposed [8,9].…”
Section: Introductionmentioning
confidence: 99%