This Article 
 Bibliographic References 
 Add to: 
A Persistent Store for Large Shared Knowledge Bases
March 1991 (vol. 3 no. 1)
pp. 33-41

A knowledge-base management system (KBMS) with the following goals is proposed: (1) to allow a knowledge engineer to update a knowledge base and have these updates persist on secondary storage, (2) to allow multiple knowledge engineers to have shared access to a knowledge base and modify the knowledge base concurrently, and (3) to maintain consistency of the shared knowledge base as it evolves. At the heart of the KBMS is the version store, which is a persistent storage structure that maintains multiple versions of a knowledge base. Retrieve and update operations are defined on the version store to efficiently access and modify any version. Objects in the version store are clustered to support efficient access of an entire version or some subparts of it. To store the effects of an update requires space proportional to the size of the update and which is independent of the size of the knowledge base. The additional cost of maintaining multiple versions is within a small constant factor of maintaining a single version.

[1] E. Mays, C. Apte, J. Griesmer, and J. Kastner, "Organizing knowledge in a complex financial domain,"IEEE Expert, 1987.
[2] E. Mays, C. Apte, J. Griesmer, and J. Kastner, "Experience with k-rep: An object-centered knowledge representation language," inProc. IEEE Conf. AI Appl., San Diego, CA, Mar. 1988.
[3] R. Brachman and J. Schmolze, "An overview of the kl-one knowledge representation system,"Cognitive Sci., vol. 9, Apr. 1985.
[4] J. D. Ullman,Database and Knowledge-base Systems. Rockville, MD: Computer Science Press, 1988.
[5] R. Agrawalet al., "Efficient management of transitive relationships in large data and knowledge bases," in [42], pp. 253-262, 1989.
[6] J. Driscoll, N. Sarnak, D. Sleator, and R. Tarjan, "Making data structures persistent,"J. Comput. Syst. Sci., vol. 38, pp. 86-124, 1989.
[7] R. Katz and T. Lehman, "Database support for version and alternatives of large design files,"IEEE Trans. Software Eng., 1984.
[8] H.-T. Chou and W. Kim, "A unifying framework for versions in a CAD environment," inProc. Int. Conf. Very Large Data Bases, Kyoto, Japan, Aug. 1986.
[9] D. Beech and B. Mahbod, "Generalized version control in an object-oriented database, "inProc. IEEE Data Eng. Conf., Feb. 1988.
[10] H.-T. Chou and W. Kim, "Versions and change notification in an object-oriented data-base system," inProc. 25th ACM/IEEE Design Automat. Conf., June 1988.
[11] R. Katz and E. Chang, "Managing change in a computer-aided design database," inProc. VLDB, 1987.
[12] P.A. Bernstein, V. Hadzilacos, and N. Goodman,Concurrency Control and Recovery in Database Systems, Addison-Wesley, Reading, Mass., 1987.
[13] Symbolics,Statice, 11 Cambridge Center, Cambridge, MA 02142, Aug. 1988.
[14] S. Lanka, E. Mays, B. Dionne, and R. Weida, "Supporting concurrent knowledge base development," Tech. Rep., IBM, 1990.

Index Terms:
persistent store; large shared knowledge bases; knowledge-base management system; knowledge engineer; multiple knowledge engineers; version store; persistent storage structure; database management systems; knowledge based systems; knowledge representation
E. Mays, S. Lanka, B. Dionne, R. Weida, "A Persistent Store for Large Shared Knowledge Bases," IEEE Transactions on Knowledge and Data Engineering, vol. 3, no. 1, pp. 33-41, March 1991, doi:10.1109/69.75886
Usage of this product signifies your acceptance of the Terms of Use.