Implicit JSON Schema Versioning Driven by Big Data Evolution in the τJSchema Framework

Abstract

The series "Lecture Notes in Networks and Systems" publishes the latest developments in Networks and Systems-quickly, informally and with high quality. Original research reported in proceedings and post-proceedings represents the core of LNNS.Volumes published in LNNS embrace all aspects and subfields of, as well as new challenges in, Networks and Systems.The series contains proceedings and edited volumes in systems and networks, spanning the areas of Cyber-

$\tau\text{JOWL}$: A Systematic Approach to Build and Evolve a Temporal OWL 2 Ontology Based on Temporal JSON Big Data

“…stored big data. A JSON data update could be either conservative [34,35] or non-conservative [43][44][45] .…”

“…It is worth mentioning that, for the implementation of the "Big Data Instance Update" module, the algorithm named "ApplyUpdatesWithImplicitSchemaVersioning", previously presented in Ref. [43] (Fig. 1), can be used.…”

“…We will use the new tool to experimentally evaluate the effectiveness, usability, and scalability of our approach, and to compare its performance with similar approaches. Its design is currently in progress and is based on the extension and integration of the previously developed prototypes JSchema-Manager [43,44] and OWL-Manager [37,45,65] . In order to evaluate the effectiveness of our approach, we will test the accuracy of the results produced by our tool starting from real examples.…”

JUpdate: A JSON Update Language

“…Whereas the statements dealing with (possibly complex) values are modeled on the SQL DML INSERT/DELETE/UPDATE statements (as shown in the five HLOs above), the JUpdate statements acting on JSON objects are modeled on the SQL ALTER DDL statement (as shown in the six HLOs below), where members of an object in a JSON document are assimilated to columns in a relational table. In fact, modifications that involve members deal with the structure of objects and, thus, can be considered for all intents (implicit) schema changes [26,27].…”

$${\tau }$$JUpdate: A Temporal Update Language for JSON Data

“…Notice that such an operation could be more properly considered as a conventional JSON schema change, as it acts on metadata rather than on data and, thus, could be better eected using the high-level JSON schema change operation RenameProperty, acting on the conventional JSON schema, we previously dened in [5], which is automatically propagated to extant conventional JSON data. However, as part of τ JUpdate, we can also consider it a JSON data update that propagates indeed to the JSON schema by means of the implicit JSON schema change mechanism that we have proposed in [4] The result of this HLO sequence is the new temporal JSON document shown in Fig. 6 with the new slice shown in Fig.…”