Versioning schemas of JSON-based conventional and temporal big data through high-level operations in the τJSchema framework

Abstract

Some rights reserved. The terms and conditions for the reuse of this version of the manuscript are specified in the publishing policy. For all terms of use and more information see the publisher's website. This is the final peer-reviewed author's accepted manuscript (postprint) of the following publication:This item was downloaded from IRIS Università di Bologna (https://cris.unibo.it/).When citing, please refer to the published version.

JUpdate: A JSON Update Language

“…In [51], we have used the high-level JSON update operations of JUpdate to define the operational semantics and to provide a basis for the implementation of the high-level JSON Schema change operations of our JSON Schema change language previously proposed in [52], based on the fact that a JSON Schema [3,53] file is also a plain JSON [1] file.…”

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

“…As an example of RenameMember HLO, we can consider changing the name of the "devices" object to "products", also valid from 2022-05-25. 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.…”