D. Heimbigner and D. McLeod. A Federated Architecture for Information Management. ACM Transactions on Oce Information Systems, 3(3):253-278, 1985.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....details of particular data integration architectures depend on many factors such as the requirements of the target system and the characteristics of the data sources in terms of heterogeneity and autonomy of operation. Earlier projects focussed on the specific problem of database integration e.g. [10, 30]. More recent research has tended to address the more general problem of integration across many forms of information sources inclusive of databases, knowledge bases, digital libraries and web documents as described in [5, 35] While these architectures may vary greatly in terms of complexity, ....

D. Heimbigner and D. McLeod. A Federated Architecture for Information Management. ACM Transactions on O#ce Information Systems, pages 253--278, 1985.

.... will be adapted to allow profile data to continue to reside in widely distributed networks and locations, while information about where to find the profile data will be easily accessible, e.g. from a centralized meta data manager analogous to the Napster server) Third, federated data management [8, 18, 25] techniques will be adapted to the special ized context of profile data management. Various other technologies used in the ( UP star framework include technologies around XML, access control, data replication and synchronization. The key contribution of this paper is identifying profile ....

D. Heimbigner and D. McLeod. A federated architecture for information management. TOIS, 1985.

....The currently most applicable solutions are based on loosely coupled federated database systems in connection with a multi database language and mediator based systems. A federated database system is a distributed system consisting of different heterogeneous database systems or local file clusters [13]. Good overviews are given in [8] and [4] Query languages supporting the integration of heterogeneous sources are for instance multi database languages like MSQL [11] and SchemaSQL [14] Examples of system implementations are federated database systems like IRODB [10] Pegasus [1] or IBM ....

D. Heimbigner and D. McLeod. A Federated Architecture for Information Management. ACM Transactions on Office Information Systems, 3(3):253--278, July 1985.

....three papers assigned represent three different approaches to database integration. Multibase [Dayal Hwang 84] represents a global schema approach, where the local schemas for different databases are merged into a global schema, against which the user makes his queries. Federated Architecture [Heimbigner McLeod 85 represents a locally global schema approach, where there is no single global schema but each database imports objects from other databases and then constructs its own global schema that integrates them with its own schema. MRDSM iLltwin Abdellatif 86] represents a multidatabase language ....

.... and McLeod for resolving the representation differences are: Object equality function 12 Type Derivation Operators: concatenate, substraction, cross product, subtype Map Derivation Operators: composition, inversion, extension, restriction, discrimination, projection, selection cross product, Heimbigner McLeod 85] provides a description for each of these constructs (pp. 262 265) which I will not repeat here except for those used for illustration below. The discussion below will be brief because the constructs used to resolve the representation differences in this approach are essentially the same as ....

Heimbigner, D. & McLeod, D. "A Federated Architecture for Information Management." ACM Trans. on Office Information System. 3(3). July 1985, pp.253-278.

....is one of the major tasks in the development of digital libraries. Concepts from the area of information system integration are adopted to this usage scenario. A federated database system is a distributed system consisting of different heterogeneous database systems or local file clusters [HM85] The currently most applicable solutions are based on loosely coupled federated database systems in connection with a multi database language and mediator based systems. Good overviews are given in [DD99,BKLW99] Query languages supporting the integration of heterogeneous sources are for ....

D. Heimbigner and D. McLeod. A Federated Architecture for Information Management. ACM Transactions on Office Information Systems, 3(3):253--278, July 1985.

....details of particular data integration architectures depend on many factors such as the requirements of the target system and the characteristics of the data sources in terms of heterogeneity and autonomy of operation. Earlier projects focussed on the specific problem of database integration e.g. [9, 23]. More recent research has tended to address the more general problem of integration across many forms of information sources inclusive of databases, knowledge bases, digital libraries and web documents e.g. 28, 5] While these architectures may vary greatly in terms of complexity, scope and ....

D. Heimbigner and D. McLeod. A Federated Architecture for Information Management. ACM Transactions on O#ce Information Systems, pages 253--278, 1985.

....is one of the major tasks in the development of digital libraries, concepts from the area of information system integration are adopted 2 to this usage scenario. A federated database system is a distributed system consisting of different heterogeneous database systems or local file clusters [HM85] These cooperating but autonomous local systems are coupled by the federated database management system. The FDBS provides a uniform and transparent interface to the heterogeneous and distributed data sources of independently developed local systems. The FDBS communicates with the local systems ....

D. Heimbigner and D. McLeod. A Federated Architecture for Information Management. ACM Transactions on Office Information Systems, 3(3):253--278, July 1985.

....only export a subset of their data that can be used by other systems of the federation. It is up to the users of the federation to access the data they are interested in using the interface that is provided there. The localisation of data can be supported by a dictionary at the federated level [HeMc85]. 5 Since both approaches are fundamentally different from each other, the few integrity control concepts that have been suggested so far are only applicable to the class of federations they have been developed for. In particular, loosely coupled systems cannot guarantee the same degree of ....

D. Heimbigner and D. McLeod. A Federated Architecture for Information Management. ACM Transactions on Office Information Systems, Vol. 3, No. 3, Jul. 1985, 253-278.

.... products) may be considered a specialized form of work ow management [6, 20, 5] Within this area, considerable attention had been given recently to the application of work ow management techniques to virtual organizations [9, 8] Finally, in the area of data modeling, federated database models [11, 17, 16, 15] may be considered as predecessors of VirtuE. A federated database provides an environment in which information may be exchanged among 1 Often the members of such an enterprise reside in the same geographical area. A notable example is the Saxon region in Germany [4] 3 autonomous or ....

D. Heimbigner and D. McLeod. A federated architecture for information management. ACM Transactions on Oce Information Systems, 3(3):253-278, July 1985.

....of data. Databases serve two roles in interoperability: they may be used as a medium for achieving interoperability (e.g. a shared repository) or multiple databases may themselves interoperate as in a federated database system. 4.3. 1 Federated Database Systems A federated database system [31] is a set of database systems, called component database systems, that operate independently but also cooperate and share data. For example, the databases of all major airlines en masse may be considered a federated database system, since they often permit queries on one another. The component ....

Heimbigner, Dennis, and McLeod, D. A federated architecture for information management. ACM Transactions on Office Information Systems 3, 3 (July 1985), 253--278.

....data models. Although the existence of a unified global schema provides complete transparency to data access, the global system scaling is an unsolved problem. Federate Databases. In these systems, there is no unified global schema; each local component has both an import and an export schemas (HEIMBIGNER, 1985; PU, 1987) The import schema is a description of the information shared between the local component and the global system. The import schema is a description of the origin and representation of the data from the remote nodes that can be globally accessed. The integration of the schemas is ....

HEIMBIGNER, D., MCLEOD, D., 1985, "A Federated Architecture for Information Management". In: ACM Trans. Office Information Systems, v.3(3), pp. 253-278.

....group work and adaptability to change. However, it is somewhat unique in its strong reliance on the integrated model PPM, which sets it apart from heterogeneous federation architectures such as the ARPA I 3 Reference Architecture [4] and TSIMMIS [1] or database federation architectures such as [3, 9, 18]. The JTF (Joint Task Force) Reference Architecture [11] is conceptually related to ours, although a four tier architecture was chosen. Based on a CORBA object bus, JTF layers generic services, applications and user environments. JTF integrates legacy data sources as coarse grained objects, ....

D. Heimbigner and D. McLeod. A Federated Architecture for Information Management. ACM Transactions on Office Information Systems, 3 (1985), pp. 253--278.

....to information that is stored within different systems, to make programs that create or manipulate information cooperate (i.e. invoke each other to retrieve data or perform services) Interoperability has been particulary studied in the area of database systems. Federated database systems [1] , 2] and multidatabases [3] are examples of interoperability. Interoperability between object oriented systems is addressed by the OMG (Object Management Group) work. The OMG has defined an architecture allowing several 2 Interoperability between a Distributed System and a Database System ....

....but if the O 2 indexing facility is used, the programmer can also take benefits from implementing small collections in O 2 . 6 Conclusions 6. 1 Related Work There are some similarities between the proposed architecture and the federated database architecture proposed by Heimbinger and McLeod in [1]. This architecture provides mechanisms for interconnecting database systems into a loosely coupled federation in order to share and exchange information. The challenge of the proposed model is to balance two conflicting requirements: components autonomy and information sharing. Guide is not a ....

D. Heimbigner and D. McLeod, A Federated Architecture for Information Management, ACM Transactions on Office Information Systems, Vol. 3 (No. 3 ), pp. 253-278, July 1985.

....to run rules, whereas logic programming uses unification of head terms for that purpose. How these differences affect composition is yet to be determined. The subject of composition of various heterogeneous databases has been widely discussed in the literature on federated database systems [Heimbigner and McLeod 1985], and some solutions to certain issues have already been proposed [Hammer and McLeod 1993] This work will not try to replicate their results, rather try to focus on the detection of potential mismatches found when composing transactional database centric systems with other system(s) 51 Some ....

D. Heimbigner and D. McLeod, "A Federated Architecture for Information Management," ACM Transactions on Office Information Systems, vol. 3, no. 3, July 1985, pp. 253-278.

....There is no communication between two federations. However, one database can participate in different federations (overlapping) sharing a distinct set of data in each of these federations. The idea of using federations is to provide privacy of the shared data and avoid the need for negotiation [1, 2, 4, 6], in order to access identified data between the requester of the data and the owner (access rights) Inside a federation the databases are organised into groups. The idea of groups is to make the universe of search smaller, facilitating the information discovery process. A group of databases is ....

D. Heimbigner and D. McLeod. A federated architecture for information management. ACM Transaction on Office Information Systems, 3(3):253--278, July 1985.

....with a large number of database systems this assumption is not reliable. Other approaches use centralised structures, like repositories and dictionaries, with information related to the available data and their location. Examples are found in Remote Exchange approach [7] federated architecture [8], and Mariposa [13] However, in an environment with a large number of database systems a centralised structure generates potential bottlenecks, is prone to failures, violates the autonomy of the database systems, and does not guarantee privacy and confidentiality of the shared data. In an effort ....

....to the health care network. In section 5 we describe some implementation comments. Section 6 summarises the result and suggests some future work. 2 The System Architecture In order to assist with the discovery process we describe an architecture that shares some features with previous work [7, 8, 9, 11, 12]. The architecture is based on a client server architecture where each database system is extended to accept the requests of the users, to locate requested data and to perform query translations. The database systems are organised into federations. Figure 1 presents two federations containing ....

[Article contains additional citation context not shown here]

D. Heimbigner and D. McLeod. A federated architecture for information management. ACM Transaction on Office Information Systems, 3(3):253--278, July 1985.

....Various architectures and methodologies have been proposed in the literature addressing the problem of manipulating and accessing heterogeneous databases. Some of these architectures use a global schema integrating the databases [1, 6, 16, 17] Other architectures avoid the use of a global schema [3, 5, 7, 8, 10, 11, 12, 13, 15] making the databases interoperable. Based on the existing architectures we propose an approach to the problem of interoperating with a large number of autonomous heterogeneous databases. The architecture aims to permit users of different databases to access local data and data from other ....

....the data that is known to be relevant, but to determine which data is relevant and where it is located. Some of the approaches proposed in the literature use a centralised structure like dictionaries and or repositories, containing information about the objects that are exported by the components [5, 7, 8, 10]. However, when dealing with a large number of databases the use of dictionaries and repositories is not suitable. They violate databases autonomy and do not guarantee privacy and confidentiality of the components. The databases have to notify all data that they export into it. A centralised ....

[Article contains additional citation context not shown here]

D. Heimbigner and D. McLeod. A federated architecture for information management. ACM Transaction on Office Information Systems, 3(3):253--278, July 1985.

....and changes in one tend to affect another. 8 Conclusion and Future Work In this paper we demonstrate the feasibility of using a distributed information discovery process that supports the sharing and exchange of data between naive users, in a number of autonomous hospital databases. Unlike [5, 7, 8, 13], the approach aims to avoid the use of integrated schemas and centralised structures. It also permits dynamic evolution of the system. The process is assisted by dynamic hierarchical structures composed of special terms. This terms are used to identify the databases related to a query. The idea ....

D. Heimbigner and D. McLeod. A federated architecture for information management. ACM Transaction on Office Information Systems, 3(3):253--278, July 1985.

No context found.

D. Heimbigner and D. McLeod. A Federated Architecture for Information Management. ACM Transactions on Oce Information Systems, 3(3):253-278, 1985.

No context found.

D. Heimbigner and D. McLeod. A Federated Architecture for Information Management. ACM Transactions on Oce Information Systems, 3(3):253{ 278, 1985.

No context found.

Heimbigner, D., McLeod, D.: A Federated Architecture for Information Management. ACM Transactions on Information Systems (TOIS) 3 (1985) 253--278

No context found.

D. Heimbigner and D. McLeod. A federated architecture for information management. Proceedings of the IEEE International Conference on Data Engineering, 3(3), July 1985.

No context found.

D. M. Heimbigner and D. McLeod. A Federated Architecture for Information Management. ACM Transactions on Office Information Systems, 3:253--278, 1985.

No context found.

Heimbigner, D., McLeod, D.: A Federated Architecture for Information Management. ACM Transactions on Information Systems (TOIS) 3 (1985) 253--278

No context found.

D. M. Heimbigner and D. McLeod. A Federated Architecture for Information Management. ACM Transactions on Office Information Systems, 3:253--278, 1985.

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