2021
DOI: 10.1016/j.eswa.2020.113772
|View full text |Cite
|
Sign up to set email alerts
|

Discovery and diagnosis of wrong SPARQL queries with ontology and constraint reasoning

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
4
0

Year Published

2021
2021
2024
2024

Publication Types

Select...
5
2

Relationship

0
7

Authors

Journals

citations
Cited by 12 publications
(4 citation statements)
references
References 39 publications
0
4
0
Order By: Relevance
“…5 The remote execution is also linked to the originating endpoint using lsqv:endpoint. 6 Given that these meta-data constitute provenance for the query, we use the PROV Ontology (PROV-O) [51] for modelling the time, date and agent involved in the remote execution.…”
Section: Stadler Et Al / Lsq 20: a Linked Dataset Of Sparql Query Logsmentioning
confidence: 99%
See 2 more Smart Citations
“…5 The remote execution is also linked to the originating endpoint using lsqv:endpoint. 6 Given that these meta-data constitute provenance for the query, we use the PROV Ontology (PROV-O) [51] for modelling the time, date and agent involved in the remote execution.…”
Section: Stadler Et Al / Lsq 20: a Linked Dataset Of Sparql Query Logsmentioning
confidence: 99%
“…'s of interest). 6 Although there exist properties called "endpoint" -such as void:sparqlEndpoint or sd:endpoint -the domains of these properties were not query executions, but rather VoID datasets (i.e., sets of RDF triples), or SPARQL services. Though it would be possible to define properties such as lsqv:dataset or lsqv:service and then link a query execution <x> to an endpoint URL <e> with <x> lsqv:dataset [void:sparqlEndpoint <e>], or alternatively <x> lsqv:service [sd:endpoint <e>], this would introduce O(n) additional triples to the LSQ 2.0 dataset, for n the number of remote query executions (in LSQ 2.0, n = 43,952,379).…”
Section: Publicationmentioning
confidence: 99%
See 1 more Smart Citation
“…These tests not only explored the potential of leveraging linked data from diverse datasets but also assessed the intricacies and challenges associated with executing complex SPARQL queries. In doing so, the tests aimed to identify and rectify common errors and shortcomings, contributing to the refinement and optimization of the overall system [20].…”
mentioning
confidence: 99%