<?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">Empowering e-services through the Semantic Web</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Raffaella</forename><forename type="middle">Maria</forename><surname>Aracri</surname></persName>
							<email>aracri@istat.it</email>
							<affiliation key="aff0">
								<orgName type="institution">Italian National Institute of Statistics (ISTAT)</orgName>
								<address>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Dario</forename><surname>Frisardi</surname></persName>
							<email>dario.frisardi@istat.it</email>
							<affiliation key="aff0">
								<orgName type="institution">Italian National Institute of Statistics (ISTAT)</orgName>
								<address>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Roberta</forename><surname>Radini</surname></persName>
							<email>radini@istat.it</email>
							<affiliation key="aff0">
								<orgName type="institution">Italian National Institute of Statistics (ISTAT)</orgName>
								<address>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Valerio</forename><surname>Santarelli</surname></persName>
							<email>santarelli@obdasystems.com</email>
							<affiliation key="aff1">
								<orgName type="institution">OBDA Systems s.r.l</orgName>
								<address>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Empowering e-services through the Semantic Web</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">2810312CFD934F994C085C1F57EE13AB</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T16:56+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>
			<textClass>
				<keywords>
					<term>PPAA</term>
					<term>PNRR</term>
					<term>Semantic Web</term>
					<term>e-service</term>
					<term>ontology</term>
					<term>controlled vocabulary</term>
					<term>data schema</term>
					<term>OBDM</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>This article illustrates how to enhance data interoperability among Public Administrations (PPAA) by leveraging the publication of e-services based on Semantic Web (SW) technologies such as ontologies, controlled vocabularies, and data schemas, which, through standard languages like OWL <ref type="table">[6], RDF[12], and SPARQL [5]</ref>, ensure harmonization, integrability, and unique semantics for representing administrative data. Furthermore, the potential benefits of implementing semantic e-services through Ontology-based Data Management (OBDM), a data governance methodology that enables data services through ontologies, decoupling their implementation from the physical data sources of PPAA, are discussed. Additionally, the advantages for PPAA of data exchange through semantic e-services utilizing concepts published in the Schema platform, developed by the National Data Catalog project funded through PNRR funds, will be highlighted in the presented use case.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>As part of the investment initiatives delineated within the National Recovery and Resilience Plan (PNRR), which is part of the Next Generation EU (NGEU) program, a measure concerning the digital transition of Public Administrations (PPAA) in data management and interoperability has been designated referred to as the National Digital Data Platform (PDND). This platform acts as the tool to centralize the authentication and authorization methods for data exchange among parties. Therefore, PDND manages the authorization phase of accessing the Application Program Interfaces (APIs), while PPAA set up their automatic connectors to make data accessible and interoperable, promoting their sharing among administrations, as well as between citizens and enterprises. Particularly, this approach avoids citizens from having to provide the same information multiple times to various administrations.</p><p>Additionally, investments aimed at enhancing data interoperability within the PDND also encompass the development of Schema, the National Catalog of data for semantic interoperability, which provides semantic clarity to administrative data through an extensive network of Ontologies, Controlled Vocabularies, and data schemas <ref type="bibr" target="#b6">[7]</ref>. These are facilitated by standard languages such as OWL, RDF, and SPARQL, ensuring harmonization, integrability, and a unified semantics to represent administrative data information.</p><p>The adoption of these standards ensures the accessibility, reusability, and inferential capacities across data originating from various sources, processes, and domains. To fully realize the benefits of these technologies, data ideally should be accessible via standard data access protocols, such as SPARQL <ref type="bibr" target="#b4">[5]</ref>, the W3C's reference language for querying RDF datasets and OWL ontologies. Among the solutions to ensure adherence to these protocols is the Ontology-based Data Management (OBDM) paradigm <ref type="bibr" target="#b7">[8]</ref>, which advocates for a virtual approach to data governance, and consequently, data access, through ontologies.</p><p>The rest of this paper is structured as follows. In Section 2, we will introduce Schema, the National Data Catalog for semantic interoperability, and explain how the semantic assets published therein can assist PPAA in the implementation of semantic eservices according to data schemas, leading to full data interoperability. Section 3 will illustrate the potential benefits of implementing e-services through OBDM, primarily by decoupling the service layer from the data layer. In Section 4, we will provide an example, through a use case, of the benefits guaranteed to individuals by data interoperability.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Schema and the semantic e-services</head><p>Within the framework of semantic interoperability enhancement, as delineated and overseen by the National Data Catalog (NDC) project <ref type="bibr" target="#b6">[7]</ref>, the development of the portal, Schema, aims to make the semantic resources of PPAA available. Schema catalogs semantic assets, such as ontologies, controlled vocabularies, and data schemas, making them searchable, reusable, and thus fostering interoperability. The semantic structures of Schema enable the definition of a unified semantics that harmonizes data representation and facilitates information exchange for Italian PPAA. For further information about Schema and the available semantic assets, additional online resources can be found in Appendix A. By leveraging ontology semantics, coherence and consistency in data are ensured, significantly enhancing interoperability. Within ontologies, there is uniformity in the description and referencing of entities present, supported by cardinality constraints that govern the relationships among them.</p><p>Data schemas become an essential tool for PPAA to expose their data and facilitate communication through shared channels, exploiting the fundamental principle of a unified semantics. The strength of data schemas lies in their ability to expose the data structure and enforce type and format constraints, ensuring not only syntactic but also semantic interoperability, targeting entities and concepts defined within ontologies and controlled vocabularies <ref type="bibr" target="#b9">[10]</ref>.</p><p>In the context of e-services, the accurate definition of data schemas plays a fundamental role in ensuring data coherence and complete interoperability. Establishing a shared ontological semantics, therefore, becomes crucial to guarantee a uniform interpretation of data by all involved parties. Through a proper implementation of data schemas, e-services become essential tools for promoting the effective utilization of semantic technologies within the realm of public administration.</p><p>The data schema format for the e-service must adhere to the specifications of a YAML file <ref type="bibr" target="#b1">[2]</ref> (if version 3.0 of OpenAPI is utilized, the YAML file should be named with an extension oas3.yaml).</p><p>Within the e-service data schema, the main components of the service in question must be defined, taking into account the semantic references of ontologies and controlled vocabularies. An example of how the data schema should be structured to define the concept of "Person" is provided below, showcasing some of the key commands: where the type is reported, as well as the URI pointing to the semantic resource is included in description. All the properties, whether required or necessary for the service, are inserted after specifying the corresponding semantic reference. Thus, it can be observed how data schemas incorporate format and type constraints, as well as references to other components (e.g., tax_code), which will then reference a semantic resource defining its concept. Currently, JSON-LD standard <ref type="bibr" target="#b13">[13]</ref> does not allow to define in a unique way the context for primitive values, i.e. string, and in such cases it is necessary to adopt an ad-hoc shared strategy. More detailed data schemas are available in Appendix A.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Implementation of e-services with OBDM</head><p>The Ontology-based Data Management (OBDM) <ref type="bibr" target="#b3">[4,</ref><ref type="bibr" target="#b7">8,</ref><ref type="bibr" target="#b8">9]</ref> is a paradigm introduced and promoted by the Department of Computer, Control, and Management Engineering "Antonio Ruberti" (DIAG) at Sapienza University of Rome and by OBDA Systems 1 . Its aim is the integration and governance of data stored in an organization's information system through an ontology. The purpose of this approach is to create a single conceptual access point to the organization's information assets, enabling the conceptual realization of all data governance services within a complex system. Indeed, OBDM can be viewed as a form of virtual data integration. However, it is based on the notion of replacing the global schema, which represents the unified view of the domain, with a conceptual and formal representation formulated through an ontology expressed in a logical language. This choice ensures that the integrated view offered by an OBDM system is not limited to a structure accommodating data from sources but constitutes a semantically rich description of the relevant concepts within the domain of interest and the relationships between them. Similarly to how it occurs in data integration systems, conceptual relationships, or mappings, are utilized to establish semantic correspondences between the global schema and the data in the sources.</p><p>When seeking information, a query is expressed on the ontology (rather than on the information system's databases), and the correspondences established between the data and the ontology's concepts enable the ontological reasoning engine <ref type="bibr" target="#b10">[11,</ref><ref type="bibr" target="#b2">3]</ref> to derive the response. This relieves the user from the necessity of understanding the technical aspects of data storage and the specifics of where and how data is storage. Similarly, when carrying out a data governance task (such as quality assessment, re-engineering, data cleaning, etc.), direct access to the informational sources is bypassed, and the appropriate functions are performed through the domain ontology.</p><p>The latter aspect not only formally describes the enterprise's information model but also serves as a means to embrace a declarative approach to data governance. Through the explicit delineation of the domain representation, knowledge reusability is achieved, a feat not achieved when the global schema merely provides a unified description of the underlying sources.</p><p>OBDM systems generally have a common structure divided into three layers or tiers: ontology, mappings, and data sources. The distinction between ontology and data sources reflects the separation between the conceptual or semantic level, which is presented to users, and the logical and physical level of the information system, stored in the sources, 1 www.obdasystems.com with mappings serving the role of reconciliation between these levels. In this scenario, the ontology and corresponding mappings to the sources provide not only a tool for data access but also a common basis for documenting an enterprise's information assets. This approach brings significant benefits for governance and management of the information system.</p><p>E-services represent an opportunity to leverage the wealth of shared ontological models and controlled vocabularies in Schema, not only as tools for conceptual sharing, but also as a means of semantically accessing data according to standardized and shared models. The value added by implementing e-services through OBDM techniques is two-fold.</p><p>Firstly, it resides in the capability to decouple the implementation of e-services from the physical sources of repositories that host the data of PPAA. In this scenario, the realization of e-services could potentially be accomplished solely through the articulation of requirements or queries on the ontological models published on Schema by the data-owning PPAA. This approach delegates the task of mediating with the data structures of individual PPAA to the mappings, while the ontological reasoning engine is entrusted with leveraging ontologies and mappings to translate the ontological requirement into queries on the physical data.</p><p>Secondly, OBDM provide the possibility to access data using SPARQL <ref type="bibr" target="#b4">[5]</ref>, the W3C standard language for querying ontologies and RDF datasets, without the implementation of data transformation and migration processes from their sources, typically consisting relational DBMS, to triple stores for formatted RDF data. Given the complexity and the volume of such data commonly managed by the information systems of PPAA, such processes naturally require significant efforts, including infrastructural ones. OBDM, on the other hand, offers a solution distinct from this scenario, favoring a virtual approach to data access, where queries expressed in SPARQL on the ontology are transformed into SQL queries on the physical sources at query time.</p><p>The decision to employ OBDM presents clear advantages both in terms of e-service implementation, utilizing standard Semantic Web languages for querying ontologies, i.e. SPARQL, and in terms of their maintenance and evolution.</p><p>The decoupling from the physical layer would allow isolating the e-service layer from the usual dynamics of reorganization, restructuring, distribution, or replication typically encountered by databases in information systems, particularly in the case of large organizations. In light of these developments, adjustments to ensure the consistency of data sharing services would be confined to the mapping layer, thus modifying the assertions that express the correspondences between elements of the data layer and those of the semantic layer.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">A use case of semantic interoperability</head><p>Based on what has been introduced in the previous sections, we aim to introduce an illustrative use case of data interoperability among PPAA and a valuable aid to citizens by implementing the principle of once only <ref type="bibr" target="#b0">[1]</ref>. It can be hypothesized that the Ministry of Culture, MiC, intends to offer a promotional service for the enjoyment of cultural assets (such as certain museums) by high-level education students from the local area, i.e., their municipality of residence. This use case involves an exchange of information between e-services exposed by the relevant PPAA. For its modeling, as introduced in Section 2, a portion of the Schema semantic network is utilized, particularly the core Location (CLV), People (CPV), and Organization (COV) ontologies, along with domain-specific ontologies, such as the Italian Learning Ontology (Learning), Resident Population Ontology (RPO), and the Cultural Heritage Ontology (CulturalHeritage). All the reported ontologies are available in Appendix A, while in Figure <ref type="figure" target="#fig_0">1</ref> there is a portion of the semantic network. To achieve this, the Ministry of Culture, MiC, can provide an e-service, S12, to a cultural institution (e.g., a museum), which, given the unique identifier of a person (tax code) and the municipality where the cultural asset subject to promotion is located, retrieves:</p><p>i. an e-service, S1, exposed by the National Register of the Resident Population (ANPR) system, which returns a confirmation if the person's current municipality of residence matches that of the cultural asset; ii. an e-service, S2, provided by the Ministry for Universities and Research (MUR), confirming that the person is a student enrolled in a High-Level Education course.</p><p>The e-service S12, after retrieving the validations returned by the e-services S1 and S2, returns to the requesting institution the authorization for the promotion for the individual.</p><p>An example of the YAML code configuration for the e-service S1 is provided below, with the key commands: components : schemas : R e g i s t e r e d R e s i d e n t P e r s o n : x−j s o n l d −c o n t e x t : RPO: h t t p s : / / w3id . o r g / i t a l i a / onto /RPO/ tax_code : h t t p s : / / w3id . o r g / i t a l i a / onto /CPV/ taxCode c u r r e n t l y _ r e g i s t e r e d _ r e s i d e n c e : " @id " : "RPO: c u r r e n t l y H a s R e g i s t e r e d R e s i d e n c e I n " " @context " : " @base " : " h t t p s : / / w3id . o r g / i t a l i a / c o n t r o l l e d − v o c a b u l a r y / t e r r i t o r i a l − c l a s s i f i c a t i o n s / c i t i e s " type : o b j e c t d e s c r i p t i o n : h t t p s : / / w3id . o r g / i t a l i a / onto /RPO/ R e g i s t e r e d R e s i d e n t P e r s o n r e q u i r e d : − tax_code p r o p e r t i e s : taxCode :</p><p>$ r e f : "#/components / schemas / TaxCode " c u r r e n t l y _ r e g i s t e r e d _ r e s i d e n c e : type : s t r i n g enum : [ . . . ] example : '058103 −(1871 −01 −15) ' TaxCode : type : s t r i n g d e s c r i p t i o n : h t t p s : / / w3id . o r g / i t a l i a / onto /CPV/ taxCode</p><p>The addressing to the tax code concept is ensured by the URI identifying the concept (https://w3id.org/italia/onto/CPV/taxCode), similarly to the use of the controlled vocabulary of cities (https://w3id.org/italia/controlled-vocabulary/ territorial-classifications/cities) for current registered residence. Therefore, unique semantics emerge as a fundamental tool that, in the reported use case, enables interoperability among the 3 e-services.</p><p>In Figure <ref type="figure" target="#fig_1">2</ref> there is an illustration depicting the main components, and their connections through e-services, in the use case. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Conclusions</head><p>As previously outlined, the use of e-services represents a pivotal element in automating data exchange among PPAA. Their implementation can play a crucial role as the driving force for achieving data interoperability, facilitated by a common semantics represented by the data schemas provided by the Schema platform.</p><p>Managing data access through the OBDM technique is an area worth investing in the short term, as it allows for the decoupling of the physical data layer from the semantic one and enables the application of these innovative techniques even on existing data structures without the need for re-conversion. Furthermore, based on a logical language, these techniques also provide Artificial Intelligence services that infer knowledge from data and facilitate quality management.</p><p>The proposed solutions move in this direction, highlighting that much work still needs to be done. Only the commitment of PPAA to implement semantic interconnection of concepts, and conse-quently data, can fully achieve the objective of "digitalization, innovation and security in the Public Administration." This could be the prompting for the digitalization of the entire Italian country.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: Extract of Schema's semantic network.</figDesc><graphic coords="4,89.29,430.02,203.37,144.84" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2: Use case representation.</figDesc><graphic coords="5,89.29,215.25,203.37,161.23" type="bitmap" /></figure>
		</body>
		<back>
			<div type="annex">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>A. Online Resources</head><p>The National Data Catalog (NDC) platform:</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>• Schema</head><p>The sources for data schemas in Schema:</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>• INAIL • INPS</head><p>The mentioned ontologies in Section 4:</p></div>			</div>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<author>
			<persName><surname>Agid</surname></persName>
		</author>
		<ptr target="https://docs.italia.it/italia/piano-triennale-ict/pianotriennale-ict-doc/it/2024-2026/index.html" />
		<title level="m">Piano Triennale per l&apos;informatica nella Pubblica Amministrazione 2024 -2026. Agenzia per l&apos;Italia Digitale</title>
				<meeting><address><addrLine>Rome, Italy</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<title level="m" type="main">YAML ain&apos;t markup language version 1</title>
		<author>
			<persName><forename type="first">Oren</forename><surname>Ben-Kiki</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Clark</forename><surname>Evans</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Ingy</forename><surname>Döt</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Net</forename></persName>
		</author>
		<ptr target="http://yaml.org/spec/1.2/spec.html" />
		<imprint>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">The MASTRO system for ontology-based data access</title>
		<author>
			<persName><forename type="first">Diego</forename><surname>Calvanese</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Giuseppe</forename><forename type="middle">De</forename><surname>Giacomo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Domenico</forename><surname>Lembo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Maurizio</forename><surname>Lenzerini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Antonella</forename><surname>Poggi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Mariano</forename><surname>Rodriguez-Muro</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Riccardo</forename><surname>Rosati</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Marco</forename><surname>Ruzzi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Domenico</forename><forename type="middle">Fabio</forename><surname>Savo</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Semantic Web</title>
		<imprint>
			<biblScope unit="volume">2</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="43" to="53" />
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Tractable reasoning and efficient query answering in description logics: The DL-Lite family</title>
		<author>
			<persName><forename type="first">Diego</forename><surname>Calvanese</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Giuseppe</forename><forename type="middle">De</forename><surname>Giacomo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Domenico</forename><surname>Lembo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Maurizio</forename><surname>Lenzerini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Riccardo</forename><surname>Rosati</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of Automated reasoning</title>
		<imprint>
			<biblScope unit="volume">39</biblScope>
			<biblScope unit="page" from="385" to="429" />
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<title level="m" type="main">SPARQL 1.1 Query Language</title>
		<author>
			<persName><forename type="first">Steve</forename><surname>Harris</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Andy</forename><surname>Seaborne</surname></persName>
		</author>
		<ptr target="https://www.w3.org/TR/sparql11-query/" />
		<imprint>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">OWL 2 web Ontology Language Primer</title>
		<author>
			<persName><forename type="first">Pascal</forename><surname>Hitzler</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Markus</forename><surname>Krötzsch</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Bijan</forename><surname>Parsia</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Peter</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Sebastian</forename><surname>Patel-Schneider</surname></persName>
		</author>
		<author>
			<persName><surname>Rudolph</surname></persName>
		</author>
		<ptr target="https://www.w3.org/TR/owl2-primer/" />
	</analytic>
	<monogr>
		<title level="j">W3C recommendation</title>
		<imprint>
			<biblScope unit="volume">27</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page">123</biblScope>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<author>
			<persName><surname>Istat</surname></persName>
		</author>
		<ptr target="https://www.istat.it/it/archivio/293230" />
		<title level="m">Trasformazione digitale della pubblica amministrazione. Metodi per l&apos;interoperabilità per lo sviluppo di e-service</title>
				<imprint>
			<date type="published" when="2024">2024</date>
		</imprint>
		<respStmt>
			<orgName>Istituto nazionale di statistica</orgName>
		</respStmt>
	</monogr>
	<note>Letture statistiche -Metodi</note>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Ontology-based data management</title>
		<author>
			<persName><forename type="first">Maurizio</forename><surname>Lenzerini</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 20th ACM international conference on Information and knowledge management</title>
				<meeting>the 20th ACM international conference on Information and knowledge management</meeting>
		<imprint>
			<date type="published" when="2011">2011</date>
			<biblScope unit="page" from="5" to="6" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Managing data through the lens of an ontology</title>
		<author>
			<persName><forename type="first">Maurizio</forename><surname>Lenzerini</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">AI Magazine</title>
		<imprint>
			<biblScope unit="volume">39</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="65" to="74" />
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Tight integration of web APIs with Semantic Web</title>
		<author>
			<persName><forename type="first">Barry</forename><surname>Nouwt</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">SEMANTiCS</title>
				<meeting><address><addrLine>Workshops</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Linking data to ontologies</title>
		<author>
			<persName><forename type="first">Antonella</forename><surname>Poggi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Domenico</forename><surname>Lembo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Diego</forename><surname>Calvanese</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Giuseppe</forename><forename type="middle">De</forename><surname>Giacomo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Maurizio</forename><surname>Lenzerini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Riccardo</forename><surname>Rosati</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Journal on data semantics X</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2008">2008</date>
			<biblScope unit="page" from="133" to="173" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title/>
		<author>
			<persName><forename type="first">Guus</forename><surname>Schreiber</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Yves</forename><surname>Raimond</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Frank</forename><surname>Manola</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Eric</forename><surname>Miller</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Brian</forename><surname>Mcbride</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">RDF</title>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="page">1</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<monogr>
		<ptr target="https://www.w3.org/TR/rdf11-primer/" />
		<title level="m">World-Wide Web Consortium</title>
				<imprint>
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
	<note>Primer</note>
</biblStruct>

<biblStruct xml:id="b13">
	<monogr>
		<author>
			<persName><forename type="first">Manu</forename><surname>Sporny</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Dave</forename><surname>Longley</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Gregg</forename><surname>Kellogg</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Markus</forename><surname>Lanthaler</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Niklas</forename><surname>Lindström</surname></persName>
		</author>
		<ptr target="https://www.w3.org/TR/json-ld11/" />
		<title level="m">JSON-LD 1.1. W3C Recommendation</title>
				<imprint>
			<date type="published" when="2020-07">Jul, 2020</date>
		</imprint>
	</monogr>
</biblStruct>

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