<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Tax and Revenue Service scenario for Ontology Matching</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Stefano</forename><surname>Brida</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">Trentino Riscossioni S.p.A</orgName>
								<address>
									<settlement>Trento</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Marco</forename><surname>Combetto</surname></persName>
						</author>
						<author>
							<persName><forename type="first">Silvano</forename><surname>Frasson</surname></persName>
							<affiliation key="aff1">
								<orgName type="institution">Informatica Trentina S.p.A</orgName>
								<address>
									<settlement>Trento</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Paolo</forename><surname>Giorgini</surname></persName>
							<affiliation key="aff2">
								<orgName type="department">D.I.S.I</orgName>
								<orgName type="institution">University of Trento</orgName>
								<address>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Tax and Revenue Service scenario for Ontology Matching</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">9361773DEB7F0F30D535A3A5273402BA</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T12:30+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><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.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Introduction. The mission of Trentino Riscossioni S.p.A<ref type="foot" target="#foot_0">1</ref> , 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 <ref type="bibr" target="#b0">[1]</ref> 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 <ref type="bibr" target="#b1">[2,</ref><ref type="bibr" target="#b2">3,</ref><ref type="bibr" target="#b3">4,</ref><ref type="bibr" target="#b4">5]</ref>, 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 <ref type="bibr" target="#b5">[6]</ref> 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 <ref type="figure">1</ref>, 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 (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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Figure 1 -The scenario description</head><p>The process analysis and breakdown provides confidence to motivate an implementation based on the use of a schema matching workbench like the HARMONY <ref type="bibr" target="#b6">[7]</ref> 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. 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. </p></div>			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">http://www.trentinoriscossionispa.it</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><p>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></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title level="m" type="main">Ontology matching</title>
		<author>
			<persName><forename type="first">J</forename><surname>Euzenat</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Shvaiko</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2007">2007</date>
			<publisher>Springer</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<title level="m" type="main">Magic Quadrant for Data Integration Tools</title>
		<author>
			<persName><forename type="first">A</forename><surname>Bitterer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Beyer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Friedman</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2008">2008</date>
			<publisher>Gartner</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Ten Challenges for Ontology Matching</title>
		<author>
			<persName><forename type="first">P</forename><surname>Shvaiko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Euzenat</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. of ODBASE</title>
				<meeting>of ODBASE</meeting>
		<imprint>
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">The Role of Schema Matching in Large Enterprises</title>
		<author>
			<persName><forename type="first">K</forename><surname>Smith</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Mork</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Seligman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Rosenthal</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Morse</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Wolf</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Allen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Li</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. of CIDR</title>
				<meeting>of CIDR</meeting>
		<imprint>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Evaluation of Business Solutions in Manufacturing Enterprises</title>
		<author>
			<persName><forename type="first">Y</forename><surname>Asnar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Giorgini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Ciancarini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Moretti</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Sebastianis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Zannone</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">International Journal on Business Intelligence and Data Mining</title>
		<imprint>
			<date type="published" when="2008">2008</date>
			<publisher>Inderscience</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<monogr>
		<title level="m" type="main">Data Quality Essentials</title>
		<author>
			<persName><forename type="first">G</forename><surname>Jeffery</surname></persName>
		</author>
		<author>
			<persName><surname>Watson</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2006">2006</date>
		</imprint>
		<respStmt>
			<orgName>Uni. of Wisconsin-Madison</orgName>
		</respStmt>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">The Harmony Integration Workbench</title>
		<author>
			<persName><forename type="first">P</forename><surname>Mork</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Seligman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Rosenthal</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Korb</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Wolf</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal on Data Semantics</title>
		<imprint>
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
