<rdf:RDF xmlns:community="http://www.bibsonomy.org/ontologies/2008/05/community#" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:admin="http://webns.net/mvcb/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:cc="http://web.resource.org/cc/" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns:swrc="http://swrc.ontoware.org/ontology#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xml:base="http://www.bibsonomy.org/user/gravity/integration"><owl:Ontology rdf:about=""><rdfs:comment>BibSonomy publications for /user/gravity/integration</rdfs:comment><owl:imports rdf:resource="http://swrc.ontoware.org/ontology/portal"/></owl:Ontology><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/22636802d129dbf10d3dc35bdfdc6efb6/gravity"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/22636802d129dbf10d3dc35bdfdc6efb6/gravity"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Article"/><owl:sameAs rdf:resource="http://portal.acm.org/citation.cfm?doid=27633.27634"/><swrc:date>Sun Dec 23 15:38:40 CET 2007</swrc:date><swrc:address>New York, NY, USA</swrc:address><swrc:journal>ACM Comput. Surv.</swrc:journal><swrc:number>4</swrc:number><swrc:pages>323--364</swrc:pages><swrc:publisher><swrc:Organization swrc:name="ACM"/></swrc:publisher><swrc:title>A comparative analysis of methodologies for database schema integration</swrc:title><swrc:volume>18</swrc:volume><swrc:year>1986</swrc:year><swrc:keywords>database schema integration comparison </swrc:keywords><swrc:abstract>One of the fundamental principles of the database approach is that a database allows a nonredundant, unified representation of all data managed in an organization. This is achieved only when methodologies are available to support integration across organizational and application boundaries. Methodologies for database design usually perform the design activity by separately producing several schemas, representing parts of the application, which are subsequently merged. Database schema integration is the activity of integrating the schemas of existing or proposed databases into a global, unified schema. The aim of the paper is to provide first a unifying framework for the problem of schema integration, then a comparative review of the work done thus far in this area. Such a framework, with the associated analysis of the existing approaches, provides a basis for identifying strengths and weaknesses of individual methodologies, as well as general guidelines for future improvements and extensions.</swrc:abstract><swrc:hasExtraField><swrc:Field swrc:value="0360-0300" swrc:key="issn"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="http://doi.acm.org/10.1145/27633.27634" swrc:key="doi"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="C. Batini"/></rdf:_1><rdf:_2><swrc:Person swrc:name="M. Lenzerini"/></rdf:_2><rdf:_3><swrc:Person swrc:name="S. B. Navathe"/></rdf:_3></rdf:Seq></swrc:author></rdf:Description></rdf:RDF>