This is an archive of an inactive wiki and cannot be modified.

This is one of the possible Use Cases.

1. Abstract

Facts from several Web sources, e.g. about businesses, are to be integrated. Rules can be used for creating an integration view of the sources. An individual, e.g. a specific business, can be identified across the sources via rule-based URI normalization. Classes can be aligned employing taxonomic reasoning. The rules and taxonomies often again require integration. Optionally, integrity constraints help to maintain the consistency, completeness, etc. of the sources and the integration result via (normative) rules.

2. Status

3. Links to Related Use Cases

4. Relationship to OWL/RDF Compatibility

OWL Compatiblity can be achieved as in SWRL or, with Hybrid Rules, as in the Realistic Architecture. RDF Compatiblity can be achieved via translation of URI-identified businesses to RDF 'about' descriptions and the direct use of RDFS sector/category taxonomies.

5. Examples of Rule Platforms Supporting this Use Case

6. Benefits of Interchange

7. Requirements on the RIF

An instantiation of this use case was implemented with POSL rules as NBBizKB and tested in OO jDREW. The need to construct such integration rules through iterative refinement with human experts implies the requirement of a human-readable syntax.

In this use case, the identity criterion for businesses across the Web sources is a problem if no URI is provided or URI normalization cannot be done: normalized phone numbers needed to be used in NBBizKB. This implies the requirement to 'webize' the language with URIs and interface it to the newest official URI normalization algorithm.

Given that the same business can be identified in both sources, and assuming it is correctly classified w.r.t. their respective taxonomies, an alignment between the two taxonomic classes can be hypothetically established, which becomes the stronger the more such business-occurrence pairs can be found in both sources. This implies the requirement to combine rules with taxonomies and to permit uncertainty handling, as explored in Fuzzy RuleML.

8. Breakdown

8.1. Actors and their Goals

8.2. Main Sequence

  1. Providers make their Web sources available
  2. Fact Integrators create an integration view dynamically, when need arise
  3. Customers use sources in a uniform way
  4. Rule Integrators dynamically integrate the Fact Integrators' rules

8.3. Alternate Sequences

Like Main Sequence except:

  1. Fact Integrators create an integration view statically, once and for all

9. Narratives

Government analysts, venture capitalists, or entrepreneurs want to monitor the progress of business development in some region XY. Facts about XY businesses are available from two Web sources, S1 and S2. While S1 contains detailed information, it has not been updated since time T. S2 contains less information but continues to be updated after T. As part of the information, a classification of the sector or category of each business is given in the two sources, using two respective taxonomies.

A Web Service is to create an integration view using all business information from S1 except where it is overwritten by S2, adding new entries for businesses only occurring in S2. For integrating the classifications, corresponding sectors or categories need to be determined and aligned in the taxonomies.

10. Commentary

"Links to Related Use Cases" should also point to several other Information Integration Use Cases, which together make a strong argument for a RIF.