W. Kim. Object-oriented databases: Definition and research directions. IEEE Transactions on Knowledge and Data Engineering, 2(3):327-341 (1990).  Home/Search   Document Not in Database   Summary   Related Articles   Check

....derived instance inherited properties can be represented and retrieved in the same way as usual properties. Keywords: instance inheritance, type information, context, inference rules, conceptual modeling, object oriented modeling. 1 Introduction In semantic and object oriented data models [8, 16, 19, 25], a class refers collectively to a set of objects, called its instances, that are similar in some respect. For example, in Figure 1, Car factory is a class that refers collectively to all particular car factories. Each class has one or more typing properties that associate it to other classes, and ....

W. Kim, Object-Oriented Databases:Definition and Research Directions, IEEE Transactions on Knowledge and Data Engineering, 2(3), 327-341 (1990).

....be that the DBA role changes from day to day. It may even be that there is a team working as the DBA or that any user of the system is allowed to perform a DBA function. This organic aspect is particularly relevant to the recently emerged (but still 7 evolving) object oriented database model [Kim 90] Here, the schema, far from being a rigid artefact created at day zero of the database s life time, is allowed to evolve. Such evolution comes under the auspices of the DBA but in a groupworking environment it may become a group responsibility. Appropriate support in the form of group ....

Kim, W.:"Object-Oriented Databases: Definitions and Research Directions", IEEE Transactions on Knowledge and Data Engineering, 2 (3), September 1990.

....its superclasses (lines 3 10) Step Two Define Primary Horizontal Fragments of Classes The quantitative database information required is the cardinality of each class. Both qualitative and An example of a graph depicting dependency information is the class composition hierarchy shown in Kim [11]. Algorithm 3.1 (Linkgraph captures the inheritance hierarchy) Algorithm Linkgraph input: Cd : set of classes in the database; C l : set of leaf classes and C l Cd . LT: Class lattice of the database showing subclass superclass relationships. output: LG: The Link graph for the database ....

....to primary for a class that has no primary fragments due to application access pattern. 4 Complex Attributes and Simple Methods that support a class composition hierarchy using simple method invocations. The algorithm first uses the attribute link information from the class composition hierarchy [11] to fragment classes according to the fragmentation of their contained classes. The class composition hierarchy is used to define the link graph showing the dependencies between any two classes. If class C i has class C j as part of it there is a link from class C j to class C i in the link ....

W. Kim. Object-oriented databases: Definition and research directions. IEEE Transactions on knowledge and Data Engineering, 2(3), Sept. 1990.

....2 (e.g. dates, names) text (e.g. diagnosis related text) information extracted from images by automated or computer assisted image analysis, modality and image file header information (e.g. ACR NEMA [2] etc. Such data can be viewed as forming either multimedia documents [3] or objects [4]. Important considerations in the design and implementation of IDB systems are: image feature extraction, image content representation and organization of stored information, search and retrieval strategies, and user interface design. Traditional database concepts such as data independence, data ....

....to the images stored in the physical database. Prior to storing physical images, image compression techniques [36] can be applied to reduce storage requirements. Recent proposals regarding the design of IDB systems and the management of image data are influenced by the object oriented approach [37, 4, 38, 39]. This approach offers a framework within which different types of entities (e.g. different kinds of image data) and operations (e.g. image processing functions, image access mechanisms etc. may be uniformly represented as objects . An object, is defined as either a primitive or composite ....

[Article contains additional citation context not shown here]

Won Kim. Object Oriented Databases: Definitions and Research Directions. IEEE Transactions on Knowledge and Data Engineering, 2(3):327--341, September 1990.

....user interface design. Traditional database concepts such as data independence, data integrity, and control of shared information are also of great significance. Recent proposals regarding the design of IDB systems and the management of image data are influenced by the object oriented approach [1, 2]. This approach offers a framework 1 Image and Vision Computing, No. 11, Vol. 8, pp. 504 521, October 1993. within which different types of entities (e.g. different kinds of image data) and operations (e.g. image processing functions, image access mechanisms etc. may be uniformly represented ....

Won Kim. Object Oriented Databases: Definitions and Research Directions. IEEE Transactions on Knowledge and Data Engineering, 2(3):327--341, September 1990.

....1 (e.g. dates, names) text (e.g. diagnosis related text) information extracted from images by automated or computer assisted image analysis, modality and image file header information (e.g. ACR NEMA) etc. Such data can be viewed as forming either multimedia documents [2] or objects [3]. The retrieval capabilities of an IDB must be embedded in its query language. On the other hand, query responses depend highly on query type, specificity, complexity, amount of on line image analysis required and the size of the search. Query formulation needs to be iterative and flexible, ....

....modeling concepts (e.g. class definition and hierarchies) to assist application modeling. In particular, in developing an IDB system which satisfies the need for a hierarchical database organization, takes advantage of the property of inheritance, and is extensible, the object oriented approach [3] seems to be more appropriate. All database entities (e.g. various types of data) will be defined as either primitive or complex objects, while system functions (e.g. image processing and retrieval func9 tions) will be defined as methods encapsulated within the same representation with the above ....

Won Kim. Object Oriented Databases: Definitions and Research Directions. IEEE Transactions on Knowledge and Data Engineering, 2(3):327--341, 1990.

.... form of text, image, etc; hence the need arises for support of multi media information; see Akscyn et al. (1988) The most efficient paradigm that could support this variety of information and facilitate the representation of multi media in a consistent way seems to be the object oriented one; see Kim (1990). In order for a database management system to be object oriented it should satisfy the basic features of a DBMS like: persistence, i.e. the ability of objects to persist in different programme invocations; transactions, i.e. execution units that are executed either entirely or not at all; ....

.... same database object; integrity, i.e. the predicates that specify and define consistent states of persistent databases; security, i.e. the mechanism that control the user access rights; and performance issues, i.e. constructs and strategies for the enhancement of response time and throughput; see Kim (1990). These features, however, should be implemented using the major object oriented characteristics like: composite objects; user definable types; object identity; encapsulation; types classes; type class hierarchies; overloading, overriding and late binding; and computational completeness; see ....

Kim, W. (1990) Object Oriented Databases: Definitions and Research Directions, IEEE Transactions on Knowledge and Data Engineering, pp. 327-340.

....Recently, object oriented database system (OODB) has become popular, because many advanced data intensive applications such as CAD CAM and multimedia data bases have employed this technique. Many papers have discussed about what object oriented means and what an object oriented database is[1] 2] 3][4]. A new transaction model for object oriented database system was proposed in paper [5] It is clear that object oriented databases have great potential to be used widely because of their object oriented design model and flexible data model. The lost update and the uncommitted dependency are two ....

W.Kim, "Object-oriented database: Definition and research directions," IEEE Trans. Knowledge and Data Engineering, Vol. 2, No. 3, pp.327-340, Sept. 1990.

.... requirements of mechanical and VLSI CAD CAM applications (Rieu, 1992; Nguyen, 1991) It elaborates on knowledge representation techniques found in AI and data models found in the database area (Minsky, 1975) It also imports recent advances in object oriented databases and programming languages (Kim, 1990; Gabriel, 1991) It includes such notions as meta classes, methods, inferences, and dependencies. They are merged in a powerful and flexible data model which is currently tested on full size applications in mechanical engineering design. SHOOD is implemented in Le Lisp TM on Sun SPARCstation ....

....be the basis for a powerful method combination mechanism (Keene, 1989) 2.3 SEMANTIC RELATIONSHIPS A critical issue in design application is the support for user defined relationships between objects. Whereas many object oriented systems now provide some form of composite objects (Keller, 1991; Kim, 1990), an open question is the implementation of versatile semantic relationships. Semantic networks and knowledge representation languages like SRL (Fox, 1986) provide powerful mechanisms for this aspect. It is clear that the usual inheritance relationship is not sufficient to model complex artifacts. ....

Kim W. 1990. Object-oriented databases : definition and research directions. IEEE Trans. on Knowledge and Data Engineering. 2(3).

....and the inheritance hierarchy information. The output expected from this fragmentation process is the set of horizontal fragments for all classes in the database. Four steps are required. 4 An example of a graph depicting dependency information is the class composition hierarchy shown in Kim [17]. A Distributed Object Based Design Technique 13 3.1 Classes Consisting of Simple Attributes and Simple Methods The four steps required to fragment this class model are. For purposes of easy reference, this algorithm is called HorizontalFrag. Step 1: Generate Link Graph: With this class model, ....

....and Simple Methods This section sketches an algorithm for horizontally fragmenting classes consisting of complex attributes that support class composition hierarchy using simple method invocations. The algorithm first uses the attribute links between classes using the class composition hierarchy [17]. The class composition hierarchy is used to define the link graph showing the dependencies between any two classes. If class C i has class C j as part of it there is a link from class C j to class C i in the link graph. The first iteration invokes the Horizontal Fragmentation algorithm described ....

W. Kim. Object-oriented databases: Definition and research directions. IEEE Transactions on knowledge and Data Engineering, 2(3), Sept. 1990.

....c fl1998 Elsevier Science Ltd Key words: Property Inheritance, Semantics, Inference Rules, Schema Derivations, Conceptual Modelling, Object Oriented Modelling 1. INTRODUCTION Specialization and inheritance are well established mechanisms in object oriented modelling and in conceptual modelling [8, 17, 20, 25]. Inheritance typically takes place from classes to instances: a class is a container of information common to its instances and each instance inherits a number of properties by class membership [22] Specialization hierarchies, on the other hand, allow the organization of classes in a way that a ....

....of property inheritance. To establish a framework for the comparison of our model with related ones, we briefly review the type concept and we distinguish two categories of data models with respect to their treatment of property inheritance. In object oriented systems and some extensible systems [20, 8], a type is a set of properties and types are related through the subtype relationship in a type hierarchy [7] A type T is a subtype of a type T 0 iff T supports all properties of T 0 with the same or more refined value (property refinement) T may have additional properties. Properties of T ....

W. Kim. Object-oriented databases: Definition and research directions. IEEE Transactions on Knowledge and Data Engineering, 2(3):327-341 (1990).

....objects which need composition hierarchy and objectspecific operations. Therefore, object oriented databases are considered as a possible alternative because of their power in behavioral modeling and behavior inheritance, complex objects support, type hierarchy, behavior encapsulation, and so on [4]. Despite these powerful features, OODBMS is still not sufficient for video data management especially with respect to editing and production. We believe that meaningful video sequences are identified and associated with their describing data incrementally and dynamically after the video objects ....

Won Kim. "Object-Oriented Databases: Definition and Research Directions." IEEE Trans. on Knowledge and Engineering, Vol. 2, No. 3, pp.327-341, 1990.

....a warranty that the database is supplying the correct values. As such, it is not surprising that much attention has been paid to the maintenance of integrity in relational databases. Object oriented databases are rapidly gaining popularity, and show a promise of supplanting relational databases [15]. It is therefore imperative that we explore the maintenance of integrity in object oriented databases. By virtue of object orientation, some integrity constraints are represented naturally and maintained for free in an object oriented database, in that they are directly captured by the type ....

W. Kim, "OBJECT-Oriented Databases: Definition and Research Directions," IEEE Transactions on Knowledge and Data Engineering, June 1990, pp. 327-341.

....and situations. Object oriented databases extend these ideas by combining data items with functionality to produce encapsulated objects, and defining relationships between them; and active databases also provide a model that allows activity and processing functionality to be added to data items [Kim, 1990; Paton and Diaz, 1999] In many ways, these reflect a set of concerns similar to those that have shaped the Placeless Documents design. However, other criteria have also influenced our design, and have led to significant differences from the traditional database approach. The first of these is ....

Kim, W. (1990). Object-Oriented Databases: Definition and Research Directions. IEEE Transactions on Knowledge and Data Engineering, 2(3), 327-341.

....special cases. For example, the following LDL rules are also ROL rules: int(s(X) int(X) ancestor(X; Y ) parent(X; Y ) ancestor(X; Y ) parent(X; Z) ancestor(Z; Y ) book deal(fX; Y; Zg) book(X; Px) book(Y; Py) book(Z; P z) X 6= Y; X 6= Z; Y 6= Z; Px Py P z 100 In Orion [22], O 2 [17] ODMG 93 [11] Fibonacci [4] IQL [6] IQL2 [2] and LOGRES [12] an object identifier together with all its attribute values are viewed as an object, which differs from the notion of object in ROL. 3. Classes, Instances, and Attribute Declarations Objects often share common ....

W. Kim. Object-oriented databases: Definition and research direction. IEEE Transactions on Knowledge and Data Engineering, 2(3):327--341, 1990.

....operations is not at all straight forward. Not having a formal definition of completeness makes it difficult to evaluate and compare object oriented query languages objectively. Many opinions have been expressed about the central and fundamental issues of objectoriented query languages [Ban89, Kim89, Kim92, BNPS92] Relevant inputs can also be found from sources taking a slightly different standpoint. For example, an evaluation framework for query algebras is proposed in [YO91] and many of the criteria are applicable to high level query languages. Language facilities for multimedia data are ....

....broken down into smaller and more comprehensible subqueries. 3.3 Related Issues The previous discussion focuses on query language features without addressing the impact of data model on query languages. There has been much discussion about the advantages and disadvantages of supporting extents [Kim89, ABD 90] Extents create security problem as all instances of a class can be accessed via the class extent and access control on individual objects is difficult and prohibitively expensive. Application modelling often does not require the use of class extents. The provision of class extents ....

W. Kim. Object-Oriented Databases: Definition and Research Directions,. IEEE Transactions on Knowledge and Data Engineering, 4(3):327--341, September 1989.

No context found.

W. Kim. Object-oriented databases: Definition and research directions. IEEE Transactions on Knowledge and Data Engineering, 2(3):327-341 (1990).

No context found.

Kim, W. Object-oriented databases: Definition and research directions. IEEE Transactions on Knowledge and Data Engineering 2, 3 (1990), 327--341.

No context found.

Kim, W. "Object-Oriented Databases: Definition and Research directions" IEEE Transactions on knowledge and data engineering, Vol. 2 No. 3, September 1990

No context found.

W. Kim, Object-Oriented Databases:Definition and Research Directions, IEEE Transactions on Knowledge and Data Engineering, 2(3), 327-341, (1990).

No context found.

W. Kim, Object-Oriented Databases:Definition and Research Directions, IEEE Transactions on Knowledge and Data Engineering, 2(3), 327-341 (1990).

No context found.

Won Kim. Object-oriented databases: Definition and research directions. IEEE Transactions on Knowledge and Data Engineering, 2(3):327--341, September 1990.

No context found.

W.Kim. (1990). Object-oriented database: Definition and research directions, IEEE Trans. Knowledge and Data Engineering, Vol. 2, No. 3, pp.327-340, Sept. 1990.

No context found.

W. Kim, "Object-oriented databases: Definition and research directions," IEEE Trans. on Knowledge and Data Engineering, vol. 2, no. 3, pp. 327--341, 1990.

No context found.

W. Kim, Object-Oriented Databases: Definition and Research Directions, IEEE Transactions on Knowledge and Data Engineering,vol. 2, No. 3, September 1990, pp. 327-341.

First 50 documents  Next 50

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC