A Version Management Framework for RDF Triple Stores

Abstract

RDF is widely used as an ontology language for representing the metadata in Semantic Web, knowledge management system and E-commerce. Since ontologies model the knowledge in a particular domain, they may change over time. Furthermore, ontologies are usually developed and controlled in a distributed and collaborative way. Thus, it is very important to be able to manage multiple versions for RDF data. Earlier studies on RDF versions have focused on providing the accesses to different versions (i.e. snapshots) and computing the differences between those two versions. However, the existing approaches suffer from the space overhead for large scale data, since all snapshots should be redundantly kept in a repository. Moreover, it is very time consuming to compute the delta between two specific versions, which is very common in RDF applications. In this paper, we propose a framework for RDF version management in relational databases. It stores the original version and the deltas between two consecutive versions, thereby reducing the space requirement considerably. The other benefit of our approach is appropriate for change queries. On the flip side, in order to answer a query on a specific logical version, version should be constructed on the fly by applying the deltas between the original version and the logical version. This can slow down query performance. In order to overcome this, we propose a compression technique for deltas, called Aggregated Delta, to create a logical version directly rather than executing the sequence of deltas. An experimental study with real life RDF data sets shows our framework maintains multiple versions efficiently.

Efficient management and storage of a multiversion OWL 2 DL domain ontology

“…Im et al () proposed a version management framework for RDF triple stores. It is based on storing intermediate deltas and a snapshot of the current version.…”

“…To cope with temporal versioning, he augmented the RDFS ontology triples with temporal timestamps. Im et al (2012) proposed a version management framework for RDF triple stores. It is based on storing intermediate deltas and a snapshot of the current version.…”

“… Change‐based (CB) approach (Im, Lee, & Kim, ) consists in storing just the root and/or the last version as well as the deltas between each two consecutive versions (see Figure ). The deltas are differences between two successive versions in terms of change operations.…”

Automating Data Citation: The eagle-i Experience

“…[21] proposes a relational database-based version management framework for RDF stores. To reduce space, they store the original version and the deltas between two consecutive versions in a database.…”

DesignSpace

“…Those ontologies are typically developed and controlled in a distributed and collaborative fashion (e.g., OntoEdit [13]). Several works have been conducted on reasoning [14], versioning [15] or comparing versions [16] of ontologies. Nevertheless, a constructed ontology only provides syntactical consistency, its contents still can be semantically inconsistent.…”