2015
DOI: 10.1007/978-3-319-25007-6_1
|View full text |Cite
|
Sign up to set email alerts
|

SPARQL with Property Paths

Abstract: The original SPARQL proposal was often criticized for its inability to navigate through the structure of RDF documents. For this reason property paths were introduced in SPARQL 1.1, but up to date there are no theoretical studies examining how their addition to the language affects main computational tasks such as query evaluation, query containment, and query subsumption. In this paper we tackle all of these problems and show that although the addition of property paths has no impact on query evaluation, they… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
38
0

Year Published

2016
2016
2021
2021

Publication Types

Select...
6
3

Relationship

2
7

Authors

Journals

citations
Cited by 62 publications
(41 citation statements)
references
References 21 publications
0
38
0
Order By: Relevance
“…Data value tests in SPARQL are allowed using the FILTER operator, which enables one to test for data (in)equality in a set of CRPQ outputs. Determining the connection between SPARQL queries and graph languages is an important task and, as witnessed by the abundance of the literature on the problem [Libkin et al 2013b;Reutter et al 2015;Kostylev et al 2015b], one that is not solved easily. There are several challenges that we are facing.…”
Section: Future Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Data value tests in SPARQL are allowed using the FILTER operator, which enables one to test for data (in)equality in a set of CRPQ outputs. Determining the connection between SPARQL queries and graph languages is an important task and, as witnessed by the abundance of the literature on the problem [Libkin et al 2013b;Reutter et al 2015;Kostylev et al 2015b], one that is not solved easily. There are several challenges that we are facing.…”
Section: Future Workmentioning
confidence: 99%
“…To start with, RDF data is in several aspects different from graph databases, and thus, straightforward translations between the two settings are not always possible [Libkin et al 2013b]. Furthermore, property paths are not precisely equivalent to RPQs since they operate over an infinite alphabet of IRIs [Kostylev et al 2015b]. In addition, many graph constructions are not available in SPARQL due to the lack of a more general transitive closure operator.…”
Section: Future Workmentioning
confidence: 99%
“…There also already exists a proposal to extend the expressive power of PPs [11]. Other strands of research focus on studying properties of PPs such as containment [25] or supporting recursion in SPARQL [32]. However, the main assumption of all these navigational extensions of SPARQL is to work on a single, centralized RDF graph.…”
Section: Related Workmentioning
confidence: 99%
“…With the relation path extension definition in place, two interesting and basic analysis tasks that arise are the containment and equivalence problem, defined in databases query languages (see, e.g., [5] for details of a relational database context, and [3,21,10] for a graph database context). In a query scenario, if a relation path (i.e., 2RPQ) is equivalent to other with better computational properties (e.g., shorter, faster evaluation), then the initial relation path can be replaced for optimization purposes.…”
Section: Propositionmentioning
confidence: 99%