Randy H. Katz

EECS Department
University of California, Berkeley
Technical Report No. UCB/CSD-88-484
December 1988

http://www2.eecs.berkeley.edu/Pubs/TechRpts/1988/CSD-88-484.pdf

Support for computer-aided design data has been of increasing interest to database system architects. In this survey, we concentrate on one aspect of such support, namely version modeling, i.e., how best to describe the structure of a complex design artifact as it evolves across its multiple representations and over time. An operational model is also needed to describe how artifact descriptions are created and modified. While there has been much work in proposing new models and mechanisms for supporting version concepts in a database, it is our purpose not merely to describe such proposals but to attempt to unify them. It is not our goal to propose yet another model, but rather to provide a common terminology and a common collection of mechanisms that should underlie all version models. The key remaining challenge is to construct a single framework, based on these mechanisms, which can be tailored for the needs of a given version environment.

BibTeX citation:

@techreport{Katz:CSD-88-484,
    Author = {Katz, Randy H.},
    Title = {Towards A Unified Framework for Version Modeling},
    Institution = {EECS Department, University of California, Berkeley},
    Year = {1988},
    Month = {Dec},
    URL = {http://www2.eecs.berkeley.edu/Pubs/TechRpts/1988/6062.html},
    Number = {UCB/CSD-88-484},
    Abstract = {Support for computer-aided design data has been of increasing interest to database system architects. In this survey, we concentrate on one aspect of such support, namely version modeling, i.e., how best to describe the structure of a complex design artifact as it evolves across its multiple representations and over time. An operational model is also needed to describe how artifact descriptions are created and modified. While there has been much work in proposing new models and mechanisms for supporting version concepts in a database, it is our purpose not merely to describe such proposals but to attempt to unify them. It is not our goal to propose yet another model, but rather to provide a common terminology and a common collection of mechanisms that should underlie all version models. The key remaining challenge is to construct a single framework, based on these mechanisms, which can be tailored for the needs of a given version environment.}
}

EndNote citation:

%0 Report
%A Katz, Randy H.
%T Towards A Unified Framework for Version Modeling
%I EECS Department, University of California, Berkeley
%D 1988
%@ UCB/CSD-88-484
%U http://www2.eecs.berkeley.edu/Pubs/TechRpts/1988/6062.html
%F Katz:CSD-88-484