Schema versioning

The technological impact of the Internet gave birth to telemedicine that provides both the digitalization of patient's medical records, and the coordination between different healthcare actors. Work in this domain has shown that the standard XML is one of solid supports for the specification of the structure and of the semantic of clinical information, especially XML also ensures publishing medical

During the life cycle of an XML application, both schemas and queries may change from one version to another. Schema evolu- tions may affect query results and potentially the validity of pro- duced data. Nowadays, a challenge is to assess and accommodate the impact of these changes in evolving XML applications. Such questions arise naturally in XML static analyzers. These

We consider the problem of XML Schema evolution. In the ever-changing context of the web, XML schemas continuously change in order to cope with the natural evolution of the entities they describe. Schema changes have important consequences. First, existing documents valid with respect to the original schema are no longer guaranteed to fulfill the constraints described by the evolved schema.

Schema versioning is a powerful tool not only to ensure reuse of data and continued support of legacy applications after schema changes, but also to add a new degree of freedom to database designers, application developers and final users. In fact, different schema versions actually allow one to represent, in full relief, different points of view over the modelled application reality. The key to such an improvement is the adoption of a multi-pool implementation solution, rather that the single-pool solution usually endorsed by other authors. In this paper, we show some of the application potentialities of the multi-pool approach in schema versioning through a concrete example, introduce a simple but comprehensive logical storage model for the mapping of a multi-schema database onto a standard relational database and use such a model to define and exemplify a multi-schema query language, called MSQL, which allows one to exploit the full potentialities of schema versioning under the m...

Abstract. In this paper, an analysis of the schema evolution process in object ori-ented databases is made using an object oriented data model that supports temporal features and versions definition - the Temporal Versions Model. A meta schema structure is defined to store information ...

Advanced object-oriented applications require the man- agement of schema versions, in order to cope with changes in the structure of the stored data. Two types of version- ing have been separately considered so far: branching and temporal. The former arose in application domains like CAD/CAM and software engineering, where different so- lutions have been proposed to support design schema ver-

Dynamic evolution and adaptation of workflow models due to process (re)engineer ing activities and dynamic changing situations of the real process is one of the most important challenges in workflow management. In this paper, we present an approach for the management of evolving workflow specifications which copes with the evolution of a w orkflow schema and the dynamic modification of

Data warehouses are fast becoming a norm for a standard company. XML has emerged as a standard for communication and storage of data. A distributed data warehouse having data format as XML i.e., XML warehouses have gained much popularity. Data warehouses have emerged as an important aid in decisionmaking and in what-if-analysis. To achieve this purpose, the presence of historical data is essential. Versioning plays an important role particularly in maintaining historical data. Research and implementation of document versioning have been carried out on many fronts, but the issue of schema versioning is still in its early stage. In this paper, we have concentrated on both content versioning as well as schema versioning. Earlier work on schema versioning has largely taken the view of versioning on attributes. We have versioned the schema on a new approach taking the dimension level. To maneuver the challenging task of schema versioning we have also taken an example case study that has been used to describe the scenario in a better manner. Also, to portray our work, we have made a prototype using the .NET framework that depicts both schema versioning as well as content versioning. The approach is user-centric and therefore it allows the user to generate versions of schema according to their need specified in an XML document called" Version Specification Document" (appended to this paper). As an additional characteristic, it also allows validation of document files against the schema files.