τJSchema: A Framework for Managing Temporal JSON-Based NoSQL Databases

Temporal JSON Schema Versioning in the JSchema Framework

“…In this paper, we have extended our TJSchema framework [21] to support temporal schema versioning, by; i) proposing an approach for creating and evolving temporal JSON schemas;…”

“…Before defining the primitives acting on a temporal JSON schema [21], we need first to know the structure of such a schema. To that end, we have defined the schema (TJSSchema.json) for the temporal JSON Schema; it is provided in Fig.…”

“…Similarly to the logics followed in the subsection 4.3, we need first to know the structure of a temporal JSON document [21] before defining the primitives acting on it. For this purpose, we have defined the schema (TJDSchema.json) for the temporal JSON document; it is provided in Fig.…”

“…In this paper, we aim at filling this gap by proposing an approach for temporal schema versioning in a temporal NoSQL database. More specifically, we extend to schema versioning the JSchema framework that we have introduced in [21]. Such a framework allows developers and users to manage the definition and evolution of temporal JSON documents within a temporal JSON-based document-oriented NoSQL database, via the use of a temporal JSON schema.…”

“…Temporal logical characteristics allow the specification of which components of a JSON document can vary over time, whereas temporal physical characteristics allow the specification of how the timevarying aspects are represented in the temporal JSON document. Temporal JSON instances are obtained by applying both temporal logical and temporal physical characteristics to conventional JSON instances which are valid to the conventional JSON Schema. In its initial formulation [21], JSchema only supports temporal versioning of temporal JSON instance documents and, thus, provides for the maintenance of a complete data history and yet it does not support schema changes. We aim at enhancing our framework so that not only is changing temporal JSON instances allowed but also changing the temporal JSON schema (i.e., changing the conventional JSON schema and/or the temporal logical/ physical characteristics), in order to guarantee the bookkeeping of a complete history of both temporal JSON instances and temporal JSON schema.…”