Skip to main content
Log in

Knowledge management by example

  • Published:
Journal of Intelligent Information Systems Aims and scope Submit manuscript

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.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Similar content being viewed by others

References

  • Goldstein, R.C. & Storey, V.C. (1992). Unraveling IS-A Structures,Information Systems Research 3, 12–16.

    Google Scholar 

  • Hammer, M. & McLeod, D. (1981). Database Description with SDM: A semantic Data Model,Transactions on Database Systems, 6, 351–386.

    Google Scholar 

  • Hull, R. & Yap, C.K. (1984). The Format Model: A Theory of Database Organization,Journal of the ACM, 31, 518–537.

    Google Scholar 

  • Lochovsky, F.H. & Tsichritizis, D.C. (1982).Data Models, Enslewood, Cliff, NJ: Prentice-Hall.

    Google Scholar 

  • Morgenstern, M. (1984). Constraint Equations: Declarative Expression of Constraints with Automatic Enforcement,VLDB, 33–42.

  • Nicholas, J.M. (1982). Logic for Improving Integrity Checking in Relational Database,Acta Informatica, 18, 227–253.

    Google Scholar 

  • Orman, L.V. (1988). Functional Development of Database Applications,Transactions on Software Engineering, 14, 1280–1292.

    Google Scholar 

  • Orman, L.V. (1991). Constraint Maintenance as a Database Design Criterion,Computer Journal, 34, 73–79.

    Google Scholar 

  • Shephard, A. & Kerschberg, L. (1984). PRISM: A Knowledge Based System for Semantic Integrity Specification and Enforcement in Database Systems,Proceedings of SIGMOD Conference, 307–315.

  • Stonebraker, M., et al. (1988). The Postgres Rules System,Transactions on Software Engineering, 14, 7.

    Google Scholar 

  • Tansel, A.U., Arkum, M.E., & Ozsoyoglu, G. (1989). Time By Example Query Language for Historical Databases,Transactions on Software Engineering, 15, 464–478.

    Google Scholar 

  • Tsur, S. & Zaniolo C. (1986). A Logic-Based Data Language,VLDB.

  • Ullman, J.D. (1989).Principles of Data and Knowledge Base Systems, Computer Science Press.

  • Urban, S.D. & Delcambre, L.M.L. (1990). Constraint Analysis: Specifying Operations on Objects,Transactions on Knowledge and Data Engineering, 2, 391–400.

    Google Scholar 

  • Weber, R. (1982).EDP Auditing, McGraw Hill.

  • Zloof, M.M. (1977). Query by Example: A Database Language,IBM Systems Journal, 16, 4.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

About this article

Cite this article

Orman, L.V. Knowledge management by example. J Intell Inf Syst 2, 207–223 (1993). https://doi.org/10.1007/BF00962068

Download citation

  • Issue Date:

  • DOI: https://doi.org/10.1007/BF00962068

Keywords

Navigation