Figure 1 - uploaded by Alin Deutsch
Content may be subject to copyright.
Community-Based Integration Architecture their reviews so that her data are always visible to the query. On the other hand, she wants to restrict the amount of published information in order to minimize the cleaning effort associated with publishing. In that case she may willingly give up self-sufficiency, settling for a "complementary" registration that relies on other, trusted sources. For instance assume that the retailer collects thirdparty reviews in the form of text blurbs. Cleaning them up for publication (spell-checking, language censorship, etc.) is an expensive process requiring human involvement. Therefore the retailer needs to know whether another trusted source (e.g. a book publisher) provides reviews, so that she relies on this source for reviews and provides herself only book ads, thus saving the cleaning effort. Avoid inconsistency. Since every owner registers her sources independently, she may easily register data that contradict those from other registered sources. For instance, a publisher and a retailer may list different authors for the same book (identified by its ISBN). Inconsistencies correspond to wrong data and should be avoided. It is therefore important for an owner to know when her registration may create inconsistencies in the integration system.
Source publication
Modern Internet communities need to integrate and query structured information. Employing current information integration infrastructure, data integration is still a very costly effort, since source registration is performed by a central authority which becomes a bottleneck. We propose the community-based integration paradigm which pushes the sourc...
