<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Tax and Revenue Service scenario for Ontology Matching</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Stefano Brida</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Marco Combetto</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Silvano Frasson</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Paolo Giorgini</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>D.I.S.I., University of Trento</institution>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Informatica Trentina S.p.A.</institution>
          ,
          <addr-line>Trento</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Trentino Riscossioni S.p.A.</institution>
          ,
          <addr-line>Trento</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>In this paper we present a scenario for ontology matching posed by the Trentino Riscossioni S.p.A data integration system focusing the opportunity to enhance the level of data integration over a large set of Tax and Revenue industry-specific data sources. Introduction. The mission of Trentino Riscossioni S.p.A1, a company owned by the Autonomous Province of Trento, is to promote simplification processes and harmonize the activity of more than 250 public entities in the province, creating policies for fair taxation and for operating costs reduction. The need for consistent and contextual use of the heterogeneous information sources between its offices, the municipalities and the other public bodies is a fundamental requirement for the implementation of an accurate and balanced taxation system. In this paper we want to focus on the possibility offered by matching technology [1] to enhance the in the present day data integration architecture and increase its flexibility in managing hundreds of new data sources with reduced software development for each new sources added. Besides, even if the data integration has been extensively studied in the database community, according to some recent research works [2,3,4,5], the issue to improve the automatic schema matching in a data integration scenario for the Tax and Revenue market is a relative new ground of application. The contribution of this paper includes a specific scenario focusing several of the basic requirements that have to be considered in order to build a data integration system capable to support dynamically hundreds of data sources. Scenario. The scenario is to make possible the insertion, management and deletion of new data sources (e.g., new data source from a new provincial database). The inclusion of a new data source would result in the census of syntactic and semantic information related to the attributes of the source and in an automatic mapping of these attributes over the proper attributes of the destination database schema. If the attributes are not present in the destination schema, the system must support the design of a schema extension. The source information is collected in a knowledge base. The search results will be available for at least 2 types of applications: (i) the business intelligence application that enables the monitoring, tracking and management of the data quality [6] of the integrated database and four (ii) missioncritical applications focusing specific business-strategic tasks: assessment revenue, territory mapping, planning support, final users services. As depicted hereafter in Figure 1, the information coming from the external data sources is processed through the SSMB (Semantic Schema/data Matching Box). The SSMB must be able to calculate the new system status n + 1 through a function based on the previous states</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Business</title>
    </sec>
    <sec id="sec-2">
      <title>Applications</title>
      <sec id="sec-2-1">
        <title>Integrated</title>
      </sec>
      <sec id="sec-2-2">
        <title>Database</title>
        <p>assessment revenue
territory mapping
planning support
final users services</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Data</title>
    </sec>
    <sec id="sec-4">
      <title>Quality</title>
    </sec>
    <sec id="sec-5">
      <title>Information</title>
    </sec>
    <sec id="sec-6">
      <title>Engineer</title>
      <p>C
o
n
f</p>
    </sec>
    <sec id="sec-7">
      <title>SSMB GUI ETL</title>
      <p>Source</p>
    </sec>
    <sec id="sec-8">
      <title>Cadastre</title>
    </sec>
    <sec id="sec-9">
      <title>Business</title>
    </sec>
    <sec id="sec-10">
      <title>Activities</title>
      <p>(n, n-1) in order to support a GUI tool that will provide the interface to the required
information to the Information Engineer and to the calculated matching suggestions
enabling to integrate the sources more rapidly than currently. There are about 10
different data sources for each municipality and 7-8 for each provincial data source.
In the next 2 years, the plan is to integrate about 200 municipalities and other
significant sources.</p>
      <p>MTorancitkoirningg,, Municipality 1</p>
      <sec id="sec-10-1">
        <title>Quality Notifications - Up-channel</title>
      </sec>
    </sec>
    <sec id="sec-11">
      <title>Municipality N</title>
    </sec>
    <sec id="sec-12">
      <title>Car Taxes Authority DB</title>
    </sec>
    <sec id="sec-13">
      <title>Power Authority</title>
    </sec>
    <sec id="sec-14">
      <title>Water Authority</title>
      <p>
        DB DB DB
The process analysis and breakdown provides confidence to motivate an
implementation based on the use of a schema matching workbench like the
HARMONY[
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] integration workbench. In fact, beside the other advantages this
approach enables the interoperation and the selection between different and various
prototypes and commercial tools for schema matching and enables the sharing a
common knowledge repository.
      </p>
      <p>Conclusions and future works. We presented the business scenario for a solution
that leverages on matching technology in order to scale-out over hundreds of data
sources. Future works proceed in the following directions: (i) formalization of the
scenario, (ii) evaluation and test of the HARMONY workbench features, and (iii)
development of a specific working prototype for Trentino Riscossioni S.p.A.
Acknowledgments. This work has been supported by Trentino Riscossioni S.p.A and
by Informatica Trentina S.p.A.-TasLab Network Project funded by the EU FSE under
the act n. 1637 (30.06.2008) of the Autonomous Province of Trento.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>J.</given-names>
            <surname>Euzenat</surname>
          </string-name>
          and
          <string-name>
            <given-names>P.</given-names>
            <surname>Shvaiko</surname>
          </string-name>
          . Ontology matching. Springer,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>A.</given-names>
            <surname>Bitterer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. A.</given-names>
            <surname>Beyer</surname>
          </string-name>
          , and
          <string-name>
            <given-names>T.</given-names>
            <surname>Friedman</surname>
          </string-name>
          .
          <article-title>Magic Quadrant for Data Integration Tools</article-title>
          . Gartner,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>P.</given-names>
            <surname>Shvaiko</surname>
          </string-name>
          and
          <string-name>
            <given-names>J.</given-names>
            <surname>Euzenat</surname>
          </string-name>
          .
          <article-title>Ten Challenges for Ontology Matching</article-title>
          .
          <source>In Proc. of ODBASE</source>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>K.</given-names>
            <surname>Smith</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Mork</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Seligman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Rosenthal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Morse</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Wolf</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Allen</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.</surname>
          </string-name>
          <article-title>Li: The Role of Schema Matching in Large Enterprises</article-title>
          .
          <source>In Proc. of CIDR</source>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Asnar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Giorgini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Ciancarini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Moretti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Sebastianis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Zannone</surname>
          </string-name>
          .
          <article-title>Evaluation of Business Solutions in Manufacturing Enterprises</article-title>
          . In
          <source>International Journal on Business Intelligence and Data Mining, Inderscience</source>
          ,
          <year>2008</year>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Jeffery</surname>
            <given-names>G.</given-names>
          </string-name>
          <string-name>
            <surname>Watson</surname>
          </string-name>
          .
          <source>Data Quality Essentials. Uni. of Wisconsin-Madison</source>
          ,
          <year>2006</year>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>P.</given-names>
            <surname>Mork</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Seligman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Rosenthal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Korb</surname>
          </string-name>
          , and
          <string-name>
            <given-names>C.</given-names>
            <surname>Wolf</surname>
          </string-name>
          .
          <article-title>The Harmony Integration Workbench</article-title>
          .
          <source>Journal on Data Semantics</source>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>