METU interoperable database system

Doğaç, Asuman; Halıcı, Uğur; Kilic, Ebru; Ozhan, Gokhan; Özcan, Fatma; Nural, Sena; Dengi, Cevdet; Mancuhan, Sema; Arpinar, Budak; Koksal, Pinar; Evrendilek, Cem

doi:10.1145/211990.212017

Cited by 24 publications

(5 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Ontology languages used in existing projects include AI representation languages such as Loom (SIMS [27]) and description logic (OBSERVER [28]), a datalog-like language (Infomaster [2]) and the Object Data Management Group's Object Definition Language (ODL) (DISCO [29], MIND [30,31]). The Infosleuth project [1] uses a meta-modelling approach to allow new ontology representation languages to be defined and used to model data sources.…”

Section: Query Processingmentioning

confidence: 99%

Information Systems Architecture

Kurbel¹

2008

The Making of Information Systems

View full text Add to dashboard Cite

The Department of Information Science is one of six departments that make up the Division of Commerce at the University of Otago. The department offers courses of study leading to a major in Information Science within the BCom, BA and BSc degrees. In addition to undergraduate teaching, the department is also strongly involved in postgraduate research programmes leading to MCom, MA, MSc and PhD degrees. Research projects in spatial information processing, connectionist-based information systems, software engineering and software development, information engineering and database, software metrics, distributed information systems, multimedia information systems and information systems security are particularly well supported.The views expressed in this paper are not necessarily those of the department as a whole. The accuracy of the information presented in this paper is the sole responsibility of the authors. CopyrightCopyright remains with the authors. Permission to copy for research or teaching purposes is granted on the condition that the authors and the Series are given due acknowledgment. Reproduction in any form for purposes other than research or teaching is forbidden unless prior written permission has been obtained from the authors. CorrespondenceThis paper represents work to date and may not necessarily form the basis for the authors' final conclusions relating to this topic. It is likely, however, that the paper will appear in some form in a journal or in conference proceedings in the near future. The authors would be pleased to receive correspondence in connection with any of the issues raised in this paper, or for subsequent publication details. Please write directly to the authors at the address provided below. (Details of final journal/conference publication venues for these papers are also provided on the Department's publications web pages: http://divcom.otago.ac.nz:800/COM/INFOSCI/Publctns/home.htm). Any other correspondence concerning the Series should be sent to the DPS Coordinator. Department of Information Science AbstractThis paper describes an architecture for building distributed information systems from existing information resources, based on distributed object and software agent technologies. This architecture is being developed as part of the New Zealand Distributed Information Systems (NZDIS) project.An agent-based architecture is used: information sources are encapsulated as information agents that accept messages in an agent communication language (the FIPA ACL). A user agent assists users to browse ontologies appropriate to their domain of interest and to construct queries based on terms from one or more ontologies. One or more query processing agents are then responsible for discovering (from a resource broker agent) which data source agents are relevant to the query, decomposing the query into subqueries suitable for those agents (including the translation of the query into the specific ontologies implemented by those agents), executing the subqueries and translating and combini...

show abstract

Section: Query Processingmentioning

confidence: 99%

Information Systems Architecture

Kurbel¹

2008

The Making of Information Systems

View full text Add to dashboard Cite

show abstract

“…Split the entire query into individual sub queries and send them to the corresponding databases. We directly use the concepts developed in the literature [4,10], for decomposing a global query in to sub queries. A detailed description of the algorithm is given in [10].…”

Section: Sydbql Java Api and Implementationmentioning

confidence: 99%

“…Most of the multidatabase systems such as MIND [4,10], Pegasus [1], do not have a constraint checker module in built in their system. Instead they have a transaction control manager which is responsible for rolling back a transaction in case of a violation of a constraint.…”

Section: Related Work and Conclusionmentioning

confidence: 99%

A Java API for global querying and updates for a system of databases

Sunderraman

Doğdu

Madiraju

et al. 2005

Proceedings of the 43rd Annual Southeast Regional Conference - Volume 1

View full text Add to dashboard Cite

In this paper, we present the design of system of databases (SyDb). We also give the design and implementation of a Java API for global querying and updates on the SyDb. The databases may be heterogeneous. The API allows for queries and updates that have global references to schema elements of multiple databases to be executed in a seamless manner. The API can be used to develop collaborative applications that need access to several independent databases on the network. One such collaborative application, called the Calendar application, is illustrated in the paper. In this application each individual keeps their schedule information in their personal database. The users can schedule meetings with others, view others schedules, cancel meetings, etc. We implement the API using direct JDBC connections to databases.

show abstract

“…Another interesting research system is the MIND system (METU Interoperable DBMS) [29,30]. MIND is a global schema approach multidatabase system that uses CORBA as its underlying distributed computing platform.…”

Section: Existing Data Mediator Systems and Other Related Workmentioning

confidence: 99%

The COIL data mediator definition language

Och¹,

Osborne²,

Todd³

et al. 2001

Concurrency and Computation

View full text Add to dashboard Cite

SUMMARYModern persistent applications typically run on top of numerous (often hundreds) of distributed, heterogeneous databases. Integrating data from various data sources in order to provide uniform, homogeneous, and consistent access to the data from the underlying data sources while preserving the integrity and autonomy of preexisting data sources is a huge problem, especially in evolving environments. The main issue that a global information sharing system has to address is heterogeneity on all levels of the participating data sources: the data might be stored in heterogeneous data sources, using different data models and access/middleware technologies. Another major type of heterogeneity that has to be addressed by a global information sharing system is due to differences in the semantics of the data from the data source participating in the integration process. In particular, the resolution of potential conflicts due to structural and semantic heterogeneity of the integrated data is an essential part of the integration process performed by a data integration environment.The COIL data mediator definition language supports the definition of the integration process and its semantics on a high level of abstraction. The language provides powerful language components which can be used to resolve potential conflicts due to structural and semantic heterogeneity, and to define the integration process in general. The semantics of a specific integration process are defined in a COIL data mediator definition (COIL program). The COIL compiler uses those specifications expressed in the COIL language to generate a standard Java object which captures the semantics of the integration process defined in the COIL mediator definition. The generated Java object is called a COIL data mediator. In general, a COIL data mediator is a user-defined, customized object/component which can be used like any other normal object in the Java development environment. A COIL data mediator presents a well-defined interface which may be used to access and configure the mediator at runtime. Therefore it is possible to change the data mediator's behavior and the semantics of the integration process in general at runtime. We present a detailed description of the COIL data mediator definition language and its language components, along with a detailed discussion of how COIL data mediators are used to overcome different heterogeneity problems.

show abstract

METU interoperable database system

Cited by 24 publications

References 5 publications

Information Systems Architecture

Information Systems Architecture

A Java API for global querying and updates for a system of databases

The COIL data mediator definition language

Contact Info

Product

Resources

About