Advertisement

Knowledge management by example

  • Levent V. Orman
Intelligent Databases
Part of the Lecture Notes in Computer Science book series (LNCS, volume 689)

Abstract

Knowledge has many components such as data, constraints, queries, transactions, and derivation rules. Data is the only component that can be managed effectively in large quantities. All other components are in their infancy in terms of tools and techniques for efficient storage and retrieval, implementation and execution, and user specification and design. One approach to manage all components of knowledge in large quantities is to reduce them all to data. Many components of knowledge can be expressed in terms of examples, and examples are data. As such, all these components can be stored and retrieved efficiently in large quantities, their execution reduces to data comparison and can be done in parallel, and they can be specified, designed, and modified by end users since examples are more intuitive and easy to manipulate than general procedures.

Keywords

Knowledge engineering Knowledge base management Knowledge representation Database constraints Integrity maintenance Rule base 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Bibliography

  1. 1.
    Goldstein, R.C., Storey V.C., Unraveling IS-A Structures. Information Systems Research 3, 2, 1992.Google Scholar
  2. 2.
    Hammer, M., McLeod D., Database Description With SDM: A Semantic Data Model, Transactions on Database Systems, 6, 3, 351–386, 1981.Google Scholar
  3. 3.
    Hull, R., Yap C.K., The Format Model: A Theory of Database Organization, Journal of ACM, 31, 3, 518–537, 1984.Google Scholar
  4. 4.
    Lochovsky, F.H., Tsichritzis, D.C., Data Models, Prentice Hall, 1982.Google Scholar
  5. 5.
    Morgenstem, M., Constraint Equations: Declarative Expression of Constraints with Automatic Enforcement, VLDB 33-42,1984.Google Scholar
  6. 6.
    Nicholas, J.M., Logic for Improving Integrity Checking in Relational Databases, Acta Informatica 18, 227–253,1982.Google Scholar
  7. 7.
    Orman, L.V., Functional Development of Database Applications, Transactions on Software Engineering 14, 9,1280–1292,1988.Google Scholar
  8. 8.
    Orman, L.V., Constraint Maintenance as a Database Design Criterion, Computer Journal 34, 1, 73–79, 1991.Google Scholar
  9. 9.
    Shephard, A., Kerschberg, L., PRISM: A Knowledge Based System for Semantic Integrity Specification and Enforcement in Database Systems, Proceedings of SIGMOD Conference 307–315, 1984.Google Scholar
  10. 10.
    Stonebraker, M., et al., The Postgres Rules System, Transactions on Software Engineering 14, 7, 1988.Google Scholar
  11. 11.
    Tansel, A.U., Arkun, M.E., Ozsoyoglu G., Time By Example Query Language for Historical Databases, Transactions on Software Engineering 15, 4, 464–478,1989.Google Scholar
  12. 12.
    Tsur, S., Zaniolo C., A Logic-Based Data Language, VLDB, 1986.Google Scholar
  13. 13.
    Ullman, J.D., Principles of Data and Knowledge Base Systems, Computer Science Press, 1989.Google Scholar
  14. 14.
    Urban, S.D., Delcambre, L.M.L., Constraint Analysis: Specifying Operations on Objects, Transactions on Knowledge and Data Engineering 2, 4, 391–400, 1990.Google Scholar
  15. 15.
    Weber, R., EDP Auditing, McGraw Hill, 1982.Google Scholar
  16. 16.
    Zloof, M.M., Query by Example: A Database Language, IBM Systems Journal 16, 4,1977.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1993

Authors and Affiliations

  • Levent V. Orman
    • 1
  1. 1.Cornell UniversityIthaca

Personalised recommendations