Schema evolution is the increasingly important ability to adapt deployed schemas to
changing requirements. Effective support for schema evolution is challenging since schema …

After more than two decades of its use, XML is not only a standard format for exchanging
data between different (Web) applications but also a model for a family of some emerging or …

Although NoSQL databases are claimed to be schemaless, several NoSQL database
vendors have chosen JSON as agile data representation format and provide a JSON-based …

Abstract tXSchema (Currim et al., 2004) is a framework (a language and a suite of tools) for
the creation and validation of time-varying XML documents. A tXSchema schema is …

The JSON Schema language lacks explicit support for defining time-varying schemas of
JSON documents. Moreover, existing JSON NoSQL databases (eg, MongoDB, CouchDB) …

In information systems, not only do data change over time, but also database schemata
evolve frequently as a response to evolving application requirements. In the literature …

With the deluge in the amount and variety of data in the world, it is rare for data that
describes an entity to be completely contained and managed by a single data source. As a …

Although multi-temporal XML databases supporting schema versioning are used in several
domains, like e-commerce, e-health, and e-government, existing database management …

In JSON-based NoSQL data stores, Big Data instance documents and their JSON schemas
must evolve over time to reflect changes in the real world. When a JSON instance document …

If past versions of XML documents are retained, what of the various integrity constraints
defined in XML Schema on those documents? This paper describes how to interpret such …