article

Emancipating instances from the tyranny of classes in information modeling

Authors Info & Claims
Online:01 June 2000Publication History

Abstract

Database design commonly assumes, explicitly or implicitly, that instances must belong to classes. This can be termed the assumption of inherent classification. We argue that the extent and complexity of problems in schema integration, schema evolution, and interoperability are, to a large degree, consequences of inherent classification. Furthermore, we make the case that the assumption of inherent classification violates philosophical and cognitive guidelines on classification and is, therefore, inappropriate in view of the role of data modeling in representing knowledge about application domains.

As an alternative, we propose a layered approach to modeling in which information about instances is separated from any particular classification. Two data modeling layers are proposed: (1) an instance model consisting of an instance base (i.e., information about instances and properties) and operations to populate, use, and maintain it; and (2) a class model consisting of a class base (i.e., information about classes defined in terms of properties) and operations to populate, use, and maintain it. The two-layered model provides class independence. This is analogous to the arguments of data independence offered by the relational model in comparison to hierarchical and network models. We show that a two-layered approach yields several advantages. In particular, schema integration is shown to be partially an artifact of inherent classification that can be greatly simplified in designing a database based on a layered model; schema evolution is supported without the complexity of operations currently required by class-based models; and the difficulties associated with interoperability among heterogeneous databases are reduced because there is no need to agree on the semantics of classes among independent databases. We conclude by considering the adequacy of a two-layered approach, outlining possible implementation strategies, and drawing attention to some practical considerations.

References

  1. ANGELES, P. A. 1981. Dictionary of Philosophy. Harper Perennial, New York, NY.Google ScholarGoogle Scholar
  2. BATINI, C., CERI, S., AND NAVATHE, S., EDS. 1992. Conceptual Database Design: An Entity-Relationship Approach. Benjamin-Cummings Publ. Co., Inc., Redwood City, CA. Google ScholarGoogle ScholarDigital LibraryDigital Library
  3. BERTINO,E.AND GUERRINI, G. 1995. Objects with multiple most specific classes. In Proceedings of the Ninth European Conference on Object-Oriented Programming (ECOOP '95, Aarhus, Denmark, Aug.). Springer-Verlag, New York, NY, 102-126. Google ScholarGoogle ScholarDigital LibraryDigital Library
  4. BOOCH, G. 1994. Object-Oriented Analysis and Design with Applications. 2nd ed. Benjamin-Cummings Publ. Co., Inc., Redwood City, CA. Google ScholarGoogle ScholarDigital LibraryDigital Library
  5. BJORNSTEDT,A.AND HULTEN, C. 1989. Version control in an object-oriented architecture. In Object-Oriented Concepts, Databases, and Applications, W. Kim and F. H. Lochovsky, Eds. ACM Press Frontier Series. ACM Press, New York, NY, 451-485. Google ScholarGoogle ScholarDigital LibraryDigital Library
  6. BORGIDA, A., BRACHMAN,R.J.,MCGUINNESS,D.L.,AND RESNICK, L. A. 1989. CLASSIC: a structural data model for objects. SIGMOD Rec. 18, 2 (June), 58-67. Google ScholarGoogle ScholarDigital LibraryDigital Library
  7. BUNGE, M. 1977. Treatise on Basic Philosophy: Vol. 3: Ontology I: The Furniture of the World. D. Reidel Publishing Co., Inc., New York, NY.Google ScholarGoogle Scholar
  8. BUNGE, M. 1979. Treatise on Basic Philosophy: Vol. 4: Ontology II: A World of Systems.D. Reidel Publishing Co., Inc., New York, NY.Google ScholarGoogle Scholar
  9. CHEN, P. P. 1976. The entity-relationship model: Toward a unified view of data. ACM Trans. Database Syst. 1, 1, 9-36. Google ScholarGoogle ScholarDigital LibraryDigital Library
  10. COAD,P.AND YOURDON, E. 1991. Object-Oriented Analysis. 2nd ed. Yourdon Press Computing Series. Yourdon Press, Upper Saddle River, NJ. Google ScholarGoogle ScholarDigital LibraryDigital Library
  11. CONNOLLY,T.M.,BEGG,C.E.,AND STRACHAN, A. D. 1996. Database Systems: A Practical Approach to Design, Implementation and Management. Addison-Wesley Publishing Co., Inc., Redwood City, CA. Google ScholarGoogle ScholarDigital LibraryDigital Library
  12. DEUX, O. 1991. The 02 system. Commun. ACM 34, 10 (Oct.), 34-48. Google ScholarGoogle ScholarDigital LibraryDigital Library
  13. ELMASRI,R.AND NAVATHE, S. B. 1994. Fundamentals of Database Systems. 2nd ed. Benjamin-Cummings Publ. Co., Inc., Redwood City, CA. Google ScholarGoogle ScholarDigital LibraryDigital Library
  14. GOTTLOB, G., SCHREFL, M., AND ROCK, B. 1996. Extending object-oriented systems with roles. ACM Trans. Inf. Syst. 14, 3, 268-296. Google ScholarGoogle ScholarDigital LibraryDigital Library
  15. HALL, P., OWLETT, J., AND TODD, S. 1976. Relations and entities. In Modelling in Data Base Management Systems, G. Nijssen, Ed. North-Holland Publishing Co., Amsterdam, The Netherlands, 201-220.Google ScholarGoogle Scholar
  16. HAMMER,M.AND MCLEOD, D. 1981. Database description with SDM: A semantic database model. ACM Trans. Database Syst. 6, 3 (Sept.), 351-386. Google ScholarGoogle ScholarDigital LibraryDigital Library
  17. KENT, W. 1979. Limitations of record-based information models. ACM Trans. Database Syst. 4, 1 (Mar.), 107-131. Google ScholarGoogle ScholarDigital LibraryDigital Library
  18. KHOSHAFIAN,S.N.AND COPELAND, G. P. 1986. Object identity. In Proceedings of the Conference on Object-Oriented Programming Systems, Languages and Applications (OOP-LSA '86, Portland, OR, Sept. 29-Oct. 2), N. Meyrowitz, Ed. ACM Press, New York, NY, 406-416. Google ScholarGoogle ScholarDigital LibraryDigital Library
  19. KIM, W., CHOI, I., GALA, S., AND SCHEEVEL, M. 1995. On resolving schematic heterogeneity in multidatabase systems. In Modern Database Systems: The Object Model, Interoperability, and Beyond, W. Kim, Ed. ACM Press/Addison-Wesley Publ. Co., New York, NY, 521-550. Google ScholarGoogle ScholarDigital LibraryDigital Library
  20. LAKOFF, G. 1987. Women, Fire, and Dangerous Things: What Categories Reveal about the Mind. University of Chicago Press, Chicago, IL.Google ScholarGoogle Scholar
  21. LANG,S.M.AND LOCKEMANN, P. C. 1998. Behaviorally adaptive objects. Theor. Pract. Object Syst. 4, 3, 169-182. Google ScholarGoogle ScholarDigital LibraryDigital Library
  22. MARK,L.AND ROUSSOPOULOS, N. 1986. Metadata management. IEEE Computer 19, 12 (Dec.), 26-36. Google ScholarGoogle ScholarDigital LibraryDigital Library
  23. MEDIN,D.AND SMITH, E. 1984. Concepts and concept formation. Ann. Rev. Psychol. 35, 113-138.Google ScholarGoogle ScholarCross RefCross Ref
  24. O'NEILL, P. 1994. Database: Principles, Programming, Performance. Morgan Kaufmann, San Mateo, CA. Google ScholarGoogle ScholarDigital LibraryDigital Library
  25. PARSONS, J. 1996. An information model based on classification theory. Manage. Sci. 42,10 (Oct.), 1437-1453.Google ScholarGoogle Scholar
  26. PARSONS,J.AND WAND, Y. 1997a. Choosing classes in conceptual modeling. Commun. ACM 40, 6, 63-69. Google ScholarGoogle ScholarDigital LibraryDigital Library
  27. PARSONS,J.AND WAND, Y. 1997b. Using objects for systems analysis. Commun. ACM 40, 12, 104-110. Google ScholarGoogle ScholarDigital LibraryDigital Library
  28. PERNICI, B. 1990. Objects with roles. SIGOIS Bull. 11, 2 and 3 (Apr.), 205-215. Google ScholarGoogle ScholarDigital LibraryDigital Library
  29. ROSCH, E. 1996. On the internal structure of perceptual and semantic categories. In Cognitive Development and the Acquisition of Language, T. Moore, Ed. Academic Press, Inc., New York, NY, 111-144.Google ScholarGoogle Scholar
  30. ROSCH, E. 1978. Principles of categorization. In Cognition and Categorization, E. Rosch and B. Lloyd, Eds. Lawrence Erlbaum Associates Inc., Hillsdale, NJ, 27-48.Google ScholarGoogle Scholar
  31. RUMBAUGH, J., BLAHA, M., PREMERLANI, W., EDDY, F., AND LORENSEN, W. 1991. Object-Oriented Modeling and Design. Prentice-Hall, Inc., Upper Saddle River, NJ. Google ScholarGoogle ScholarDigital LibraryDigital Library
  32. SHETH,A.P.AND LARSON, J. A. 1990. Federated database systems for managing distributed, heterogeneous, and autonomous databases. ACM Comput. Surv. 22, 3 (Sept.), 183-236. Google ScholarGoogle ScholarDigital LibraryDigital Library
  33. SHIPMAN, D. W. 1981. The functional data model and the data language DAPLEX. ACM Trans. Database Syst. 6, 1, 140-173. Google ScholarGoogle ScholarDigital LibraryDigital Library
  34. SMITH, E. 1988. Concepts and thoughts. In The Psychology of Human Thought, R. Sternberg, and E. Smith, Eds. Cambridge University Press, New York, NY.Google ScholarGoogle Scholar
  35. SMITH,E.AND MEDIN, D. 1981. Categories and Concepts. Cambridge University Press, New York, NY.Google ScholarGoogle Scholar
  36. TEOREY,T.J.,YANG, D., AND FRY, J. P. 1986. A logical design methodology for relational databases using the extended entity-relationship model. ACM Comput. Surv. 18, 2 (June), 197-222. Google ScholarGoogle ScholarDigital LibraryDigital Library
  37. WAND, Y., STOREY,V.C.,AND WEBER, R. 1999. An ontological analysis of the relationship construct in conceptual modeling. ACM Trans. Database Syst. 24, 4 (Dec.), 494-528. Google ScholarGoogle ScholarDigital LibraryDigital Library
  38. WAND, Y. 1989. A proposal for a formal model of objects. In Object-Oriented Concepts, Databases, and Applications, W. Kim and F. H. Lochovsky, Eds. ACM Press Frontier Series. ACM Press, New York, NY, 537-559. Google ScholarGoogle ScholarDigital LibraryDigital Library

Index Terms

  1. Emancipating instances from the tyranny of classes in information modeling

          Reviews

          Jaroslav Pokorny

          With the advent of integrated heterogeneous information sources, there is a renewed interest in information modeling (IM). The authors emphasize that most of the previous approaches to IM are based on the assumption of inherent classification, that is, the first modeling step is usually to identify the classes or types of things needed to describe the domain. The goal of the paper is to show that this assumption is inappropriate in many tasks of IM. The authors propose a two-layered approach to IM. The first layer represents the existence of things with properties, independent of the classes to which the things belong. The second layer consists of class definitions based on sets of properties. In Section 2, some undesirable consequences of inherent classification are discussed. On the schema design level, the authors explain problems of multiple classification, view integration, schema evolution, and interoperability. Other problems arise in database operation. They include handling exceptional instances, reclassifying instances, adding and removing instances, and removing and redefining a class. Section 3 attempts to describe the theoretical foundations of classifications, with the help of ontology and epistemology. The authors use Bunge's simple ontological model, which dates to the 1970s. They conclude that both ontology and classification theory recognize that instances exist independent of any classes. The authors adapt these ideas in a two-layered approach in Section 4. They draw two partial conclusions: recognizing the existence of things should precede classifying them, and there is no single “correct” set of classes to model a given domain of instances and properties. The particular choice of classes (a view) depends on the application. The two-layered approach consists of the instance model and class model. In the former, instances and properties are represented. Instances can be queried and modified by primitive operations. Similar operations are designed for the class model. In Section 5 the authors present various implications of the two-layered model. They show that many problems connected with the assumption of inherent classification disappear in this approach. Section 6 discusses how to combine this approach with other models, particularly with the entity-relationship (ER) model and object models. Section 7 addresses some issues related to the implementation, efficiency, and practicality of the model. The most interesting part concerns querying a database. The authors present queries that are not available in traditional class-based databases, such as relational databases. For example, we can obtain identifiers of all read cars stored in a database, regardless of the database columns in which they are placed. The chapter concludes with a detailed discussion of how to implement the two-layered approach. The rest of the paper summarizes the main ideas of the model, points out its advantages, and gives a context for its application. Obviously, many other classical database issues can be reformulated and solved in this new paradigm. The paper is well-arranged and sound. It offers an interesting approach to IM, which can make many contributions and has many consequences for the development of future database architectures.

          Access critical reviews of Computing literature here

          Become a reviewer for Computing Reviews.

          Comments

          Login options

          Check if you have access through your login credentials or your institution to get full access on this article.

          Sign in

          Full Access

          PDF Format

          View or Download as a PDF file.

          PDF

          eReader

          View online with eReader.

          eReader
          About Cookies On This Site

          We use cookies to ensure that we give you the best experience on our website.

          Learn more

          Got it!