Versioning

A Propagation Mechanism for Populated Schema Versions

Authors: 
Lautemann, SE
Year: 
1997
Venue: 
Proc. 13th Int. Conf. on Data Engineering (ICDE), 1997

Object-oriented database systems (OODBMS) offer powerful modeling concepts as required by advanced application domains like CAD/CAM/CAE or office automation. Typical applications have to handle large and complex structured objects which frequently change their value and their structure. As the structure is described in the schema of the database, support for schema evolution is a highly required feature. Therefore, a set of schema update primitives must be provided which can be used to perform the required changes, even in the presence of populated databases and running applications.

An introduction to schema versioning in OODBMS

Authors: 
Lautemann, SE
Year: 
1996
Venue: 
Proc. 7th Int. Workshop on Database and Expert Systems Applications (DEXA)

Object oriented database management systems (OODBMS) have enormous advantages in comparison to relational systems in modeling highly complex and dynamic application scenarios. Still they lack some flexibility which could help their promotion into widely spread industrial use. Especially engineering environments frequently require schema changes to handle evolving designs. The main contribution of the paper is twofold: firstly, we give an overview of schema evolution mechanisms, describing the state of the art in research.

Schema evolution in OODBs using class versioning

Authors: 
Monk, S; Sommerville, I
Year: 
1993
Venue: 
ACM SIGMOD Record

Designing XML Formats: Versioning vs. Extensibilty

Authors: 
Obasanjo, Dare
Year: 
0

Designers of XML formats have to face the problem of how to design their formats to be extensible and yet be resilient to changes due revisions of the format. This presentation covers various techniques and considerations for versioning XML formats.

How to version schemas

Authors: 
Gabriel, Jim
Year: 
2004
Venue: 
XML Conference, XMLUSA, 2004

Version and source control for schemas and schema objects is badly needed by us all, especially in complex, multi-enterprise development situations. This paper describes how to support true versioning of schemas and fine-grained schema objects. An important conclusion is that schema evolution and schema development are essentially synonymous, in that the applicable techniques and requisite technology are the same for both.

Management Of Schema Evolution In Databases

Authors: 
Andany, J.; Lonard, M.; Palisser, C.
Year: 
1991
Venue: 
VLDB 1991

This paper presents a version model which handles database schema changes and which takes evolution into account. Its originality is in allowing the development of partial schema versions, or views of a schema. These versions are created in the same database from a common schema. We define the set of authorised modifications on a schema and the rules which guarantee its coherence after transformation. Mechanisms allowing data to be associated with each version are also integrated in the model.

A Taxonomy for Schema Versioning Based on the Relational and Entity Relationship Models

Authors: 
Roddick, John F.; Craske, Noel G.; Richards, Thomas J.
Year: 
1993
Venue: 
Proc. ER 1993: 137-148

Recently there has been increasing interest in both the problems and the potential of
accommodating evolving schema in databases, especially in systems which necessitate a
high volume of structural changes or where structural change is difficult. This paper
presents a taxonomy of changes applicable to the Entity-Relationship Model together with
their effects on the underlying relational model expressed in terms of a second taxonomy
relevant to the relational model.

A Survey of Schema Versioning Issues for Database Systems

Authors: 
Roddick, J.F.
Year: 
1995
Venue: 
Information and Software Technology, 37(7):383393, 1995. http://citeseer.ist.psu.edu/roddick95survey.html

Schema versioning is one of a number of related areas dealing with the same general problem - that
of using multiple heterogeneous schemata for various database related tasks. In particular, schema
versioning, and its weaker companion, schema evolution, deal with the need to retain current data
and software system functionality in the face of changing database structure. Schema versioning
and schema evolution offer a solution to the problem by enabling intelligent handling of any
temporal mismatch between data and data structure. This survey discusses the modelling,

XML Schema Versioning

Authors: 
Stinnett, Mickey
Year: 
2001

It is clear that XML schemas will evolve over time and it is important to capture the
schema’s version. This write-up summarizes two cases for schema changes and some
options for schema versioning. It then provides some ‘best practice’ guidelines for XML
schema versioning.

Ontology Versioning in an Ontology Management Framework

Authors: 
Noy, Natalya Fridman; Musen, Mark A.
Year: 
2004
Venue: 
IEEE Intelligent Systems 19(4): 6-13 (2004)

Best practices for Web Services versioning

Authors: 
Brown, K.; Ellis, M.
Year: 
2004
Venue: 
www.ibm.com/developerworks/webservices/library/ws-version , Jan. 2004

API versioning is a common problem in the design of any distributed system, and Web services are unfortunately no exception. In this article, Kyle Brown and Michael Ellis will outline the scope of the versioning difficulties facing Web services developers, provide some template solutions, and discuss architectures and best practices for addressing the problem.

Versions of Schema for Object-Oriented Databases

Authors: 
Kim, W.; Chou, H.
Year: 
1988
Venue: 
Proc. 14th VLDB, 148-159.

Version control is one of the important database require-
ments for design environments. Various models of ver-
sions have been proposed and implemented. However,
research in versions has been focused exclusively on
versioning single design objects. In a multi-user design
environment where the schema (definition) of the design
objects may undergo dynamic changes, it is important to
be able to version the schema, as well as version the
single design objects. In this paper, we propose a model
of versions of schema by extending our model of versions

Syndicate content