A design space for RDF data representations

Tomer Sagi, Matteo Lissandrini, Torben Bach Pedersen, Katja Hose

Download a digital copy (PDF)

The final authenticated version is available online at 10.1007/s00778-021-00725-x.

Abstract:

The SCR Space
The SCR system design space for RDF stores: Subdivision, Compression, and Redundancy.
RDF triplestores’ ability to store and query knowledge bases augmented with semantic annotations has attracted the attention of both research and industry. A multitude of systems offer varying data representation and indexing schemes. However, as recently shown for designing data structures, many design choices are biased by outdated considerations and may not result in the most efficient data representation for a given query workload. To overcome this limitation, we identify a novel three-dimensional design space. Within this design space, we map the trade-offs between different RDF data representations employed as part of an RDF triplestore and identify unexplored solutions. We complement the review with an empirical evaluation of ten standard SPARQL benchmarks to examine the prevalence of these access patterns in synthetic and real query workloads. We find some access patterns, to be both prevalent in the workloads and under-supported by existing triplestores. This shows the capabilities of our model to be used by RDF store designers to reason about different design choices and allow a (possibly artificially intelligent) designer to evaluate the fit between a given system design and a query workload.
Different RDF data representations
Examples of data representations: (a) sorted file, (b) hash map, (c) property table, and (d) B+ tree.

Cite:

and
“A design space for RDF data representations.”
The VLDB Journal , 31 (): 347-373. 

@article{SagiLPH22,
  author    = {Tomer Sagi and
               Matteo Lissandrini and
               Torben Bach Pedersen and
               Katja Hose},
  title     = {A design space for {RDF} data representations},
  journal   = {VLDB J.},
  volume    = {31},
  number    = {2},
  pages     = {347--373},
  year      = {2022},  
  doi       = {10.1007/s00778-021-00725-x}  
}