eXolutio: Methodology for Design and Evolution of XML Schemas Using Conceptual Modeling

Klímek, Jakub; Malý, Jakub; Nečaský, Martin; Holubová, Irena

doi:10.15388/informatica.2015.58

Cited by 8 publications

(9 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Rather, when devising frameworks, we may want to turn to related work on frameworks for handling schema evolution in XML (e.g. [9]) or object-oriented databases (e.g. [26]) for inspiration on what has shown to be feasible.…”

Section: Discussionmentioning

confidence: 99%

“…We used BigQuery 9 to identify relevant open source repositories on GitHub, as of September 4th, 2018. We consider a repository (which we synonymously refer to as a project) relevant if it contains Java import statements for Objectify or Morphia.…”

Section: Contextmentioning

confidence: 99%

“…We state the minimum and maximum number of entity-classes throughout the project history, as well as the total number of lines of code between the first and last analyzed commit (measured with cloc 11 and reported in thousands). 9 Google BigQuery is a commercial cloud service. This data warehousing tool allows for querying the GitHub open data collection, mostly non-forked projects with an open source license: https://cloud.google.com/bigquery/.…”

Section: Contextmentioning

confidence: 99%

See 2 more Smart Citations

An Empirical Study on the Design and Evolution of NoSQL Database Schemas

Scherzinger¹,

Sidortschuck²

2020

Preprint

View full text Add to dashboard Cite

We study how software engineers design and evolve their domain model when building applications against NoSQL data stores. Specifically, we target Java projects that use object-NoSQL mappers to interface with schema-free NoSQL data stores. Given the source code of ten real-world database applications, we extract the implicit NoSQL database schema. We capture the sizes of the schemas, and investigate whether the schema is denormalized, as is recommended practice in data modeling for NoSQL data stores. Further, we analyze the entire project history, and with it, the evolution history of the NoSQL database schema. In doing so, we conduct the so far largest empirical study on NoSQL schema design and evolution.

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Contextmentioning

confidence: 99%

Section: Contextmentioning

confidence: 99%

See 1 more Smart Citation

An Empirical Study on the Design and Evolution of NoSQL Database Schemas

Scherzinger¹,

Sidortschuck²

2020

Preprint

View full text Add to dashboard Cite

show abstract

“…In the realm of information systems, XML has been largely adopted as a semi-structured data model and XML schema as a semi-structured data modeling formalism (Abiteboul et al , 2011; Aiken and Allen, 2004; Chaudhri et al , 2003). In this context, although a lot of research work has been done on XML schema evolution (Klettke, 2007; Guerrini and Mesiti, 2008; Cavalieri et al , 2011; Domínguez et al , 2011; Nečaský et al , 2012; Amavi et al , 2014; Klímek et al , 2015) and on XML schema versioning (Dyreson et al , 2006; Brahmia and Bouaziz, 2008; Snodgrass et al , 2008; Malý et al , 2011; Baqasah et al , 2014; Brahmia et al , 2014a, 2016b, 2018a), none of such approaches has dealt with changes involving XML schema design styles.…”

Section: Related Work Discussionmentioning

confidence: 99%

“…Among the most important requirements of these actors, we find those concerning application maintenance (application source code correction, application extension, XML schema changes, etc.). In general, changes performed on XML schema files are error-prone and time consuming tasks (Klímek et al , 2015), since they should be accomplished manually, as there is often no technical support (e.g. stand-alone or IDE-embedded computer-aided engineering tools) for performing them.…”

Section: Introductionmentioning

confidence: 99%

Conversion of XML schema design styles with StyleVolution

Brahmia

Grandi

Bouaziz

2019

IJWIS

View full text Add to dashboard Cite

Purpose Any XML schema definition can be organized according to one of the following design styles: “Russian Doll”, “Salami Slice”, “Venetian Blind” and “Garden of Eden” (with the additional “Bologna” style actually representing absence of style). Conversion from a design style to another can facilitate the reuse and exchange of schema specifications encoded using the XML schema language. Without any computer-aided engineering support, style conversions must be performed very carefully as they are difficult and error-prone operations. The purpose of this paper is to efficiently deal with such XML schema design style conversions. Design/methodology/approach A general approach, named StyleVolution, for automatic management of XML schema design style conversions, is proposed. StyleVolution is equipped with a suite of seven procedures: four for converting a valid XML schema from any other design style to the “Garden of Eden” style, which has been chosen as a normalized XML schema format, and three for converting from the “Garden of Eden” style to any of the other desired design styles. Findings Procedures, algorithms and methods for XML schema design style conversions are presented. The feasibility of the approach has been shown through the encoding (using the XQuery language) and the testing (with the Altova XMLSpy 2019 tool) of a suite of seven ready-to-use procedures. Moreover, four test procedures are provided for checking the conformance of a given input XML schema to a schema design style. Originality/value The proposed approach implements a new technique for efficiently managing XML schema design style conversions, which can be used to make any given XML schema file to conform to a desired design style.

show abstract