Mappings in most federated databases are conceptualized and implemented as black-box transformations between source schemas and a federated schema. This approach does not allow specific mappings to be declared once and reused in other situations. We present an alternative approach, in which data-level mappings are represented independent of source and federated schemas as a network between “contexts”. This compendious representation expedites the data federation process via mapping reuse and automated mapping composition from simpler mappings. We illustrate the benefits of mapping reuse and composition by using an example that incorporates equational mappings and the application of symbolic equation solving techniques.

This paper describes the facilities of PROBE, an object-oriented DBMS being developed at CCA (Dayal 1985, Dayal and Smith 1986). and how these facilities apply to the require ments of geographic information processing

Today's distributed computing environment presents a jungle of systems that use different object models, programming languages, and paradigms. Taking maximum advantage of these diverse resources requires that they be able to interoperate. We report on a series of experiments in a distributed object system that show how a flexible notion of dispatching can be used to integrate objects belonging to different models, systems, and paradigms.

This paper describes the coupling of contexts and ontologies for semantic integration in the ECOIN semantic interoperability framework. Ontological terms in ECOIN correspond to multiple related meanings in different contexts. Each ontology includes a context model that describes how a generic ontological term can be modified according to contextual choices to acquire specialized meanings. Although the basic ECOIN concepts have been presented in the past, this paper is the first to show how ECOIN addresses the case of "single-ontology with multiple contexts" with an example of semantic integration using our new prototype implementation.

Disclosed is a label or patch overlay dispensing apparatus having a storage reel for carrying a supply tape of adhesive overlays, a feed throat for receiving a document to which an overlay is to be attached and a contact for sensing a document in the feed throat and for causing the advancement of the document to a label attaching position. The device is responsive to the receipt of the document in the overlay attaching position for releasing an overlay or patch for attachment to the document and a pressure bonder for attaching the label is activated when the overlay is removed from the supply roll. As the overlay is attached the document is concurrently ejected from the device.

The data resources in a large enterprise typically exist as many separate islands of data. Each is maintained by a distinct community for its purposes, and is largely unusable by others. It is common to see whole data archipelagos comprised of thousands of separate resources [Ston00]. We would, of course, prefer to see one single integrated data resource usable by all. This is the “grand vision” of data integration: discovery of and access to all data, with multiple sources properly combined, delivered in a form that each consumer can interpret. Decentralized organizations such as the US Air Force might accept for now a slightly less ambitious dream – the ability to establish a connection between islands, a way to obtain any desired information from any other source.

Organizational factors—lifecycles, staff specialization and retraining, and participants' incentives—are too rarely considered in data integration research. We discuss how one can repackage the familiar tasks and research problems, to better fit organizations' needs. The goal is to obtain data integration tools that support an industrial process of data integration.

The World Wide Web is an increasingly important factor in planning for general distributed computing environments. This article surveys Web technologies that look to integrate aspects of object technology with the basic infrastructure of the Web.

This paper describes the Intermediary Architecture , a middleware architecture which interposes distributed object services between Web client and server. The architecture extends current Web architectures with a new kind of plug-in, making a new colleciton of Web applications easier to develop. Example services including Web annotations and Web performance monitoring are described.

This paper describes the Intermediary Architecture , a middleware architecture which interposes distributed object services between Web client and server. The architecture extends current Web architectures with a new kind of plug-in, making a new colleciton of Web applications easier to develop. Example services including Web annotations and Web performance monitoring are described.

The World Wide Web is becoming an increasingly important factor in planning for enterprise distributed computing environments, both to support external access to enterprise systems and information (e.g., by customers, suppliers, and partners), and to support internal enterprise operations. Organizations perceive a number of advantages in using the Web in enterprise computing, a particular advantage being that it provides an information representation which• supports interlinking of all kinds of content• is easy for end-users to access• supports easy content creation using widely-available toolsHowever, as organizations have attempted to employ the Web in increasingly sophisticated applications, these applications have begun to overlap in complexity the sorts of distributed applications for which distributed object architectures such as OMG's CORBA, and its surrounding Object Management Architecture (OMA) [Sol95] were originally developed. Since the Web was not originally designed to support such applications, Web application development efforts increasingly run into limitations of the basic Web infrastructure.If the Web is to be used as the basis of complex enterprise applications, it must provide generic capabilities similar to those provided by the OMA (although these may need to be adapted to the more open, flexible nature of the Web, and specific requirements of Web applications). This involves such things as providing database-like services (such as enhanced query and transaction support) and their composition in the Web. However, the basic data structuring capabilities provided by the Web (its "object model") must also be addressed, since the ability to define and apply powerful generic services in the Web, and the ability to generally use the Web to support complex applications, depends crucially on the ability of the Web's underlying data structuring facilities to support these complex applications and services.

A Transaction Specification and Management Environment (TSME) is a programmable system that supports implementation-independent specification of application-specific extended transaction models (ETMs) and configuration of transaction management mechanisms (TMMs) to enforce specified ETMs. The TSME can ensure correctness and reliability while allowing the functionality required by workflows and other advanced applications that require access to multiple heterogeneous, autonomous, and/or distributed (HAD) systems. To support ETM specification, the TSME provides a transaction specification language that describes dependencies between transactions. Unlike other ETM specification languages, TSME's dependency descriptors use a common set of primitives, and are enforceable, i.e., can be evaluated at any time during transaction execution to determine whether operations issued violate ETM specifications. To determine whether an ETM can be enforced in a specific HAD system environment, the TSME supports specification of the transactional capabilities of HAD systems, and comparison of these with ETM specifications to determine mismatches. To enforce ETMs that are more restrictive than those supported by the union of the transactional capabilities of HAD systems, the TSME provides a collection of transactional services. These services are programmable and configurable, i.e., they accept instructions that change their behavior as required by an ETM and can be combined in specific ways to create a run-time TMM capable of enforcing the ETM. We discuss the TSME in the context of a distributed object management system. We give ETM specification examples and describe corresponding TMM configurations for a telecommunications application.

article Free AccessInteroperability issues in large-scale distributed object systems Author: Frank Manola GTE Labs., Inc., Waltham, MA GTE Labs., Inc., Waltham, MAView Profile Authors Info & Claims ACM Computing SurveysVolume 27Issue 2June 1995 pp 268–270https://doi.org/10.1145/210376.210391Published:01 June 1995Publication History 16citation699DownloadsMetricsTotal Citations16Total Downloads699Last 12 Months30Last 6 weeks3 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF