Elisa Bertino. Integration of heterogeneous data repositories by using object oriented views. In First Workshop on Interoperability in Multidatabase Systems, pages 22-29. IEEE, April 1991.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....of a concrete warehouse configuration. 3. 1 The Global Data Model The SIRIUS global data model is based on the object oriented data model of the Object Database Management Group (ODMG) standard [5] Similar to other projects focusing on data integration in heterogeneous environments [22, 26, 2, 19], we exploit the rich semantic expressiveness of object oriented data models for representing the structure of operational data in the SIRIUS intermediate layer residing between operational sources and the DWH. Moreover, choosing the ODMG model as the global model of SIRIUS allows us to take ....

E. Bertino. Integration of Heterogeneous Data Repositories by Using Object-Oriented Views. Proc. of the 1st Intl. Workshop on Interoperability in Multidatabase Systems, Kyoto, Japan, April 1991.

....in their stock trading systems. Also [LMR90] and [MR87] recognize that increased flexibility is required in heterogeneous system and as a solution they propose methods for the development of self describing databases . Recent projects on heterogeneous database systems (e.g. A 91, Ber91, K 93] have applied object oriented (OO) data models to the problem of database integration. OEM differs from these and other OO data models in several ways. First, OEM is an information exchange model. OEM does not specify how objects are stored at the source. OEM does specify how objects ....

.... well structured conventional databases exist (e.g. A 91, K 93, BLN86, LMR90, T 90, Gup89, FLNS88, ACHK93] and recently systems for the integration of sources with minimal structure have also appeared [Fre, RJR94, S 93] we do not know of view definition based systems ( A 91, Ber91, CWN94, FLNS88] and others) that handle the whole spectrum of information sources simultaneously, and with MSL s flexibility. Note, MedMaker performs integration by working with the structures of the source objects. Semantic information is effectively encoded in the MSL rules that do the ....

[Article contains additional citation context not shown here]

E. Bertino. Integration of heterogeneous data repositories by using object-oriented views. In Proc Intl Workshop on Interoperability in Multidatabase Systems, pages 22--29, Kyoto, Japan, 1991.

.... attribute of Persons has the same semantics as the author# attribute of Books, one can define an extension view of class Books, holding an additional function written by, that returns the authors of books [SLT91,SW91, SWS91] A similar technique, called the multiview approach has been published by [Bert91]. This approach of stepwise integration of databases by defining views that extend the local schema combines the advantages of the static integration approach (transparency) with those of the multidatabase approach, and avoids the problem of generating a possibly large federated schema. Books ....

E. Bertino. Integration of Heterogeneous Data Repositories by Using Object-Oriented Views. In Proc. IMS Workshop, 1991.

....and keys. Figure 5.5 presents the metaschema for the description of relational schemas. 5.3. 3 Mediators In the context of our research we have defined mediators as a special type of object having knowledge from the semantic metadata model and supporting structural and operational mappings [2, 3]. Structural mappings define correspondences between the local schemas and the structural features of the canonical model, such as class and property. Structural mappings result in a direct translation from the GCS into a local query language statement (i.e. SQL) 1] Structural mappings in ....

Bertino, E., "Integration of Heterogeneous Data Repositories by Using ObjectOriented Views," Proceedings of the First International Workshop on Interoperability in Multidatabase Systems, Kyoto, Japan, April 1991

....into composite global ones. This integration process includes reconciling the conflicts discovered during the analysis phase [COL91, DAY84, DOG95, HAY90, MOT83, MOT87, QUT92, QUT93, NAV96a] Alternatively in this approach, several tailored global schemas may be defined instead of one global schema [BER91, CLE93, FAH94, 5 LIM94a, ZHA91]. This has the advantages of supporting customisability, potentially reducing the size of the global schema as seen by users, minimising the integrator s efforts, permitting a large number of databases to join and leave the MDB, and allowing different sets of integration rules to be applied to the ....

....type of an inter schema assertion, an integration rule will be fired in these methods. For example, an equivalence assertion between a set of local objects will cause them to be merged into one global object. In the second group, a view definition facility is provided for integrating local objects [BER91, FAH94, KAU90, LI91, SCH94]. The main difference between this and the MDB language approach to sharing data (see Section 1.2.2) is that integration solutions are sharable by different users and local conflicts are resolved in advance in this approach. Thirdly, the integration operators based group covers the approaches ....

[Article contains additional citation context not shown here]

E. Bertino. Integration of Heterogeneous Data Repositories by Using Object-Oriented Views. In Proc. 1st International Workshop on Interoperability in Multidatabase Systems, pages 22--29, Kyoto, Japan, 1991.

.... model [GUPTA90] LARSON83] Calida is designed to enable CODASYL and hierarchical databases to participate as component databases in a relational model based integrating system [LITWIN90] Many database integrations use an object oriented model to abstract the underlying databases [AHAD88][BERTIN91][CONNER88] CZEJDO91] LI91] but there seems to be little consensis about what constitutes an object oriented database. Object orientation implies 11 diversity in the objects being described, whereas more traditional databases deal with data describing large quantities of like entities. ....

Bertino, E., "Integration of Heterogeneous Data Repositories by Using Object-Oriented Views", IMS 91, IEEE Comp. Soc. Press, 1991, pp. 22-29. ................ 10

.... conventional databases exist (e.g. A 91, K 93, BLN86, LMR90, T 90, Gup89, FLNS88, ACHK93] and recently systems for the integration of sources with minimal structure have also appeared [Fre, RJR94, S 93] we do not know of view definition based systems ( LM93, A 91, Ber91, CWN94, FLNS88] and others) that handle the whole spectrum of information sources simoultaneously, and with MSL s flexibility. Note, MedMaker performs integration by working with the structures of the source objects. Semantic information is effectively encoded in the MSL rules that do the ....

....of the source objects. Semantic information is effectively encoded in the MSL rules that do the integration. There are 9 [KLK91] has also proposed an interesting mixing of schema and data information for the relational data model. many projects that follow MedMaker s structural approach [Ber91, DH86, B 86] as well as many projects that follow a semantic approach [HM93, H 92, FN92] We believe that the power of the structural approach, along with the flexibility, generality, and conciseness of OEM and MSL make the structural approach a better candidate for the integration of ....

E. Bertino. Integration of heterogeneous data repositories by using object-oriented views. In Proceedings of the 1st International Workshop on Interoperability in Multidatabase Systems, pages 22--29, Kyoto, Japan, April 1991.

....the extent of UnivLibrary Book as the target of his query. This leads us to the following definition of the belong to relation: Definition 2 An object belongs to a class if it is an instance of that class or of any of its subclasses. The belong to relation is similar to the members of relation [Ber91, PM90] Under Definition 2, the extent of the class UnivLibrary Book is the union of the extent of all its subclasses. One can therefore express the above request as a query with the extent of UnivLibrary Book as its target. Definition 2 is valid, since an instance of a subclass has at least the ....

Elisa Bertino. Integration of Heterogeneous Data Repositories by Using Object-Oriented Views. In Proceedings of the First International Workshop on Interoperability in Multidatabase Systems, pages 22--29, April 1991.

.... provide transparent schema evolution, preserving existing views through schema change [11] Because the object oriented paradigm offers a more powerful model for integration than the relational one, several papers discuss the integration of heterogeneous data repositories via object oriented views [3, 2, 7]. 1 This work was supported in part by the NSF RIA grant #IRI 9309076, NSF NYI grant #IRI 94 57609, and the University of Michigan Faculty Award Program, Intel, and AT T. Harumi Kuno is also grateful for support from the NASA Graduate Student Researchers Program. 1.1 View System Evaluation A ....

E. Bertino. Integration of heterogeneous data repositories by using object-oriented views. International Workshop on Interoperability in Multidatabase Systems, pages 22-- 29, April 1991.

....decade, automatic generation of mapping from the integrated schema to the participating schemas has not been well explored. Schema level incompatibilities can be categorized into domain mismatch, schema mismatch and constraint mismatch. Approaches to resolve schema level incompatibilities include [3, 4]. 2. Instance level Incompatibility: This refers to the conflicts that arise when the data stored in multiple databases, modeling same real world entities, has to be merged. Two problems that occur are the entity identification and the attribute value conflict resolution problems. The first is ....

E. Bertino. Integration of heterogeneous data repositories by using object-oriented views. In Proc. of the 1st Int'l Workshop on Interoperability in Multidatabase Systems, 1991.

.... OEM [5] in fact, is a self describing model [31] where each data item has an associated descriptive label and without a strong typing system; semantic informations are effectively encoded in the MSL rules that do the integration. There are many projects following the structural approach [10, 16, 11]. Let us introduce some fundamental arguments in favour of the structural approach (considering TSIMMIS as a target system) 1. the power, along with the flexibility, generality and coinciseness of OEM and MSL make the structural approach a good candidate for the integration of widely ....

E. Bertino.. Integration of heterogeneous data repositories by using object-oriented views. In Proc. Intl Workshop on Interoperability in Multidatabase Systems, pages 22-29, Kyoto, Japan,1991.

....used a self describing object model for exchange of information in their stock trading systems. In [12] and [13] self describing databases are proposed as a solution to obtaining the increased flexibility required by heterogeneous systems. Recent projects on heterogeneous database systems (e.g. [1,3,10]) have applied object oriented (OO) data models to the problem of database integration. OEM differs from these and other OO data models in several ways. First, OEM is an information exchange model. OEM does not specify how objects are stored at the source. OEM does specify how objects are received ....

E. Bertino. Integration of heterogeneous data repositories by using object-oriented views. In Proceedings of the 1st International Workshop on Interoperability in Multidatabase Systems, pages 22--29, Kyoto, Japan, April 1991.

....fact, the resulting schema meets all schema invariants. Based on these concepts, we are implementing a Schema Version Removal (SVR) tool for TSE GemStone [4] 2 Related Work Several other approaches towards transparent schema evolution using views have been recently presented in the literature [2, 3]. Differences between our transparent schema evolution approach and those reported in the literature include among other features the use of a powerful, fully materialized object oriented view system, automation of several of the version generation steps, the support of a comprehensive set of ....

....in practice. In SVR the context is somewhat different because classes are not arbitrarily or explicitly deleted from the schema by the user. Instead, a class will only be deleted when this class is not used in any view schema (i.e. no user has access to this class) Like other view systems [2], MultiView assumes closed view schemas [11] The closure criterion ensures that all classes that are being used by the type interface of any class in a view schema are also defined within the view. With this assumption, if a class A is not defined in any view schema, that means that no other ....

E. Bertino. Integration of heterogeneous data repositories by using object-oriented views. International Workshop on Interoperability in Multidatabase Systems, pages 22--29, April 1991.

.... provide transparent schema evolution, preserving existing views through schema change [13] Because the object oriented paradigm offers a more powerful model for integration than the relational one, several papers discuss the integration of heterogeneous data repositories via objectoriented views [3, 2, 6]. While researchers have begun to study view mechanisms in the context of object oriented databases (OODBs) 1, 15, 14] little work has been done regarding the implementation of object oriented views or object oriented view materialization. Furthermore, of the few research papers that discuss ....

E. Bertino. Integration of heterogeneous data repositories by using object-oriented views. Int. Workshop on Interoperability in Multidatabase Systems, pages 22--29, April 1991.

....is virtual, diverse applications can use views to customize shared data objects, even adding new extrinsic properties and behavior without affecting other applications perceptions of the data. Materialized database views are a recognized means for achieving interoperability among applications [2, 3, 6, 13, 17, 18]. View materialization enables a schema designer to include classes from a remote database into a local schema in a customized manner without suffering any penalty for queries upon the imported data [18] The complication of view materialization is that updates must be propagated to affected ....

E. Bertino. Integration of heterogeneous data repositories by using object-oriented views. Int. Workshop on Interoperability in Multidatabase Systems, pages 22--29, April 1991.

....and knowledge engineering communities have been very active in researching and building systems for accessing data stored in distributed and heterogeneous database systems. These systems are called heterogeneous database management systems, multi database systems, or federated database systems [1, 3, 6, 13, 15, 19, 22, 29] depending on the tightness of schema integration and the degree of local autonomy that is allowed. The emphasis of these existing systems is to achieve the sharing of data managed by heterogeneous database management systems (DBMSs) Other efforts have been made to tackle various technical ....

E. Bertino, "Integration of Heterogeneous data Repositories by Using Object-oriented Views," Proceedings of the 1st International Workshop on Interoperability in Multidatabase Systems, Kyoto, Japan, April 1991, pp. 22-29.

....of TSE GemStone [15, 16] Finally, we report our evaluation studies that validate our approach and demonstrate its impact on the performance of the TSE system. 2 Related Work Several other approaches towards transparent schema evolution using views have been recently presented in the literature [3, 4]. However, none have considered the schema removal problem as characterized in this paper. Like other view systems presented in the literature [19] in the formal model of views described in [8] the virtual classes are not integrated in the global schema. Therefore, removal of a virtual class in ....

E. Bertino. Integration of heterogeneous data repositories by using object-oriented views. International Workshop on Interoperability in Multidatabase Systems, pages 22--29, April 1991.

....used a self describing object model for exchange of information in their stock trading systems. In [13] and [14] self describing databases are proposed as a solution to obtaining the increased flexibility required by heterogeneous systems. Recent projects on heterogeneous database systems (e.g. [1,3,11]) have applied object oriented (OO) data models to the problem of database integration. OEM differs from these and other OO data models in several ways. First, OEM is an information exchange model. OEM does not specify how objects are stored at the source. OEM does specify how objects are received ....

E. Bertino. Integration of heterogeneous data repositories by using object-oriented views. In Proceedings of the 1st International Workshop on Interoperability in Multidatabase Systems, pages 22--29, Kyoto, Japan, April 1991.

....grant #IRI 9309076, NSF NYI grant #IRI 94 57609, and the University of Michigan Faculty Award Program. We would also like to thank our industrial sponsors, in particular, IBM, AT T, Illustra, and Intel. idiosyncrasies of component systems to be integrated into one unified, yet federated system [1, 3, 4, 13]. In addition to the more traditional uses of views, new application domains that can benefit from view technology have arisen. Examples of this include the transparent evolution of databases by simulating schema change via views [27] Because the object oriented paradigm offers a more powerful ....

.... evolution of databases by simulating schema change via views [27] Because the object oriented paradigm offers a more powerful model for integration than the relational one, the integration of heterogeneous data repositories via objectoriented views has been studied by numerous researchers [3, 13]. Maintaining materialized (possibly self maintainable) views can be exploited for optimizing workflow systems, for answering queries efficiently by using precomputed views, and for analyzing data in a data warehouse [37] Given the rising interest in view technology, we report in this paper on ....

E. Bertino. Integration of heterogeneous data repositories by using object-oriented views. International Workshop on Interoperability in Multidatabase Systems, pages 22--29, April 1991.

....identification process. We propose a new approach in section 4. Conclusion is given in section 5. 2 Background The task of integrating pre existing autonomous databases has to resolve the logical heterogeneity that arises when the participating databases are designed independently of one another [2]. Logical heterogeneity can occur at two levels, namely schema level and instance level. The resolution of schema level heterogeneity is known as schema integration. The resolution of instance level heterogeneity is known as instance integration. At the time of instance integration, schemas are ....

E. Bertino. Integration of heterogeneous data repositories by using object-oriented views. In Proc. of the 1st Int'l Workshop on Interoperability in Multidatabase Systems, 1991.

.... systems that integrate well structured conventional databases exist (e.g. A 91, K 93, BLN86, LMR90, T 90, Gup89] and recently systems for the integration of sources with minimal structure have also appeared [Fre, S 93] we do not know of view definition based systems ( A 91, Ber91, CWN94] and others) that handle the whole spectrum of information sources simultaneously, and with MSL s flexibility. Note, MedMaker performs integration by working with the structures of the source objects. Semantic information is effectively encoded in the MSL rules that do the integration. ....

....simultaneously, and with MSL s flexibility. Note, MedMaker performs integration by working with the structures of the source objects. Semantic information is effectively encoded in the MSL rules that do the integration. There are many projects that follow MedMaker s structural approach [Ber91, DH86, B 86] as well as many projects that follow a semantic approach [HM93, H 92] We believe that the power of the structural approach, along with the flexibility, generality, and conciseness of OEM and MSL make the structural approach a better candidate for the integration of widely ....

E. Bertino. Integration of heterogeneous data repositories by using object-oriented views. In Proc Intl Workshop on Interoperability in Multidatabase Systems, pages 22--29, Kyoto, Japan, 1991.

No context found.

Elisa Bertino. Integration of heterogeneous data repositories by using object oriented views. In First Workshop on Interoperability in Multidatabase Systems, pages 22-29. IEEE, April 1991.

No context found.

Elisa Bertino. Integration of Heterogeneous Data Repositories by Using Object-Oriented Views. In [KRS91], pages 22--29. IEEE Computer Society Press, 1991.

No context found.

Elisa Bertino. Integration of heterogeneous data repositories by using object oriented views. In First Workshop on Interoperability in Multidatabase Systems, pages 22-29. IEEE, April 1991.

No context found.

Bertino, E. (1991). Integration of heterogeneous data repositories by using object-oriented views. 1st Int. Workshop on Interoperability in Multidatabase Systems: pp. 22-29.

First 50 documents

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