<!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>ArCo ontology network and LOD on Italian Cultural Heritage</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Ludovica Marinucci STLab</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>ISTC CNR Rome</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Italy ludovica.marinucci@istc.cnr.it</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Valentina Presutti STLab</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>ISTC CNR Rome</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Italy valentina.presutti@cnr.it</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Aldo Gangemi FICLIT Università di Bologna Bologna</institution>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Andrea Giovanni Nuzzolese STLab</institution>
          ,
          <addr-line>ISTC CNR Rome</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Chiara Veninata ICCD MiBAC Rome</institution>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Maria Letizia Mancinelli ICCD MiBAC Rome</institution>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>Valentina Anita Carriero STLab</institution>
          ,
          <addr-line>ISTC CNR Rome</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <fpage>97</fpage>
      <lpage>102</lpage>
      <abstract>
        <p>ArCo (Architecture of Knowledge) is a collaborative project that involves the institute of the Italian Ministry of Cultural Heritage ICCD (Institute of Catalogue and Documentation) and the Institute of Cognitive Sciences and Technologies of CNR (Italian National Research Council). ArCo aims at modelling the wide domain of Italian cultural heritage for two main purposes: (i) building a network of ontologies, compatible and aligned whenever possible with existing ontologies, that can be used as a de facto standard for representing cultural heritage data; (ii) publishing ICCD data as LOD: about 800.000 publishable files stored in the ICCD General Catalogue database. In this paper, we present ArCo structure, design methods and tools, its growing community, and we delineate its importance, quality, and impact in using semantic technologies in the fruition of Cultural Heritage.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>The cultural heritage domain has an intrinsic complexity, due to the high number of different types of cultural properties
that a cataloguer may record, e.g. anthropological material, coin, park, painting, traditional music. They have a lot of
shared information types (e.g. location, bibliography, dating), but also many peculiar characteristics (e.g. staircases and
floors in a building). Moreover, their description may be very detailed: for a cataloguer is possible to gather information
about measurements, exhibitions, documentation, authorship, inventories, relations between cultural properties, and so
forth.</p>
      <p>
        There are many projects and models developed in the context of cultural heritage (CH), to model, publish and
connect data on the web: CIDOC-CRM [
        <xref ref-type="bibr" rid="ref7 ref8">7,8</xref>
        ], EDM [
        <xref ref-type="bibr" rid="ref10 ref9">9,10</xref>
        ], Cultural-ON [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], Fentry [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] and OAEntry [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] ontologies
are some relevant examples. A recent paper [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] discusses the main requirements that a model representing cultural
heritage should address, based on an analysis of CIDOC and EDM. Although we build on the good practices of such
existing effort, our use case required a level of granularity and a diversity of cultural property types that needed new
modeling effort.
      </p>
      <p>
        To build ArCo, we directly reuse classes and properties from the core (roles, agents, locations) modules of OntoPiA
[
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], an ontology and controlled vocabulary network for Italian Public Administration, and from Cultural-ON, an
ontology that models cultural events and sites [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. We indirectly reuse patterns from existing ontologies, e.g. CIDOC
and Cultural-ON and include explicit alignments to them within ArCo.
3
      </p>
    </sec>
    <sec id="sec-2">
      <title>Methodology</title>
      <p>
        In the development of the project, we followed the principles of eXtreme Design (XD) [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ], an ontology engineering
methodology based on ontology design patterns [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. Fig. 1 depicts as XD applied to ArCo.
      </p>
      <p>
        During the project initiation and scoping, domain experts shared with the ontology engineers’ team their knowledge of
the domain, providing guidelines and data model regulations for interpreting their data. A generic timeline and a release
plan with priorities were defined. As recommended, we worked in tight collaboration with our main “customer”, i.e. the
ICCD. However, given that the ICCD data will be openly published and have high potential for reuse by several other
stakeholders, we decided to interact with some representative of them since the very beginning of the process. In addition
to domain experts, other agents, such as companies, were involved in the definition of ontology requirements, initially
expressed in the form of user stories. The same requirements are reused in the ontology testing phase. Extending XD,
four selected companies were also included in an “Early Adoption Program” (EAP) that worked with the incremental
unstable releases of ArCo ontologies and data to test them for e.g. publishing their data according to ArCo ontologies,
linking their data to ArCo. The EAP members and all the other interested stakeholders created an active community that
interacts by means of a dedicated mailing-list [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ], GitHub issues tracker [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ] and meetups [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ].
      </p>
      <p>
        Pattern-based ontology design plays a central role [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ]: by ontology design patterns we mean reusable successful
solution to a recurrent modeling problem [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ] [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ]. XD encourages the reuse of existing ODPs from online repositories
[
        <xref ref-type="bibr" rid="ref25">25</xref>
        ] as well as the development of new ODPs, when needed. Reused patterns are annotated with OPLa ontology [
        <xref ref-type="bibr" rid="ref26">26</xref>
        ], to
support users in identification, reuse and ontology mapping.
      </p>
      <p>Since XD is iterative and incremental, ArCo ontology modules and ICCD data are periodically published as unstable
releases: this allows us to involve customers and stakeholders in giving us continuous feedback on modeling and testing
activities, and to detect new emerging requirements at early stage.
4
4.1</p>
    </sec>
    <sec id="sec-3">
      <title>ArCo Ontology Network and LOD</title>
      <sec id="sec-3-1">
        <title>ArCo Release</title>
        <p>
          ArCo release consists of a docker container, available on GitHub [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ] and its running instance online [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ], which contains:
- the user guide accompanying the release, with diagrams and explanations on the content of the release and of
each ontology module;
- the ontologies, including their source code and a human-readable HTML documentation;
- a SPARQL endpoint storing the General Catalogue data in RDF format, generated according to our ontologies;
- examples of Competency Questions (CQs), with the corresponding SPARQL queries, for supporting the data
query from the community;
- a RDFizer tool converting XML data represented according to ICCD cataloguing standards to RDF.
        </p>
        <p>
          ArCo knowledge graph is also available on the MiBAC official portal [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ] with its SPARQL endpoint [
          <xref ref-type="bibr" rid="ref30">30</xref>
          ].
4.2
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>ArCo Ontology Network</title>
        <p>ArCo ontology network consists of seven ontology modules connected by owl:imports axioms. In Fig. 2, blue circles
depict ArCo modules; the green circle indicates directly reused ontologies; the orange circle indicates indirectly reused
and aligned ontologies. The network base namespace is https://w3id.org/arco/ontology/, and each module has its own
namespace (e.g. https://w3id.org/arco/ontology/core/).</p>
        <p>
          The arco module [
          <xref ref-type="bibr" rid="ref31">31</xref>
          ] represents the network, importing all the other modules. It models top-level concepts from the CH
domain, according to the ICCD cataloguing standards [
          <xref ref-type="bibr" rid="ref32">32</xref>
          ]. In particular, the hierarchy of the different types of cultural
properties is modeled as follows. The top-level class is :CulturalProperty, which has two
subclasses :TangibleCulturalProperty, and :IntangibleCulturalProperty. The first is further specialized
in :MovableCulturalProperty and :ImmovableCulturalProperty.
        </p>
        <p>
          More specific types of cultural properties are defined
as :DemoEthnoAnthropologicalHeritage, :ArchaeologicalProperty, :ArchitecturalOrLandscapeHeri
tage, :HistoricOrArtisticProperty, :MusicHeritage, :NaturalHeritage, :NumismaticProperty, :Pho
tographicHeritage, :ScientificOrTechnologicalHeritage, :HistoricOrArtisticProperty (see the
diagram [
          <xref ref-type="bibr" rid="ref33">33</xref>
          ] on Github).
        </p>
        <p>
          The core module [
          <xref ref-type="bibr" rid="ref34">34</xref>
          ] represents general concepts orthogonal to the whole network, which are imported by all other
ontology modules. This module reuses a number of patterns, such as the Part-of [
          <xref ref-type="bibr" rid="ref35">35</xref>
          ], the Classification [
          <xref ref-type="bibr" rid="ref36">36</xref>
          ] and the
Situation [
          <xref ref-type="bibr" rid="ref37">37</xref>
          ] patterns.
        </p>
        <p>
          The catalogue module [
          <xref ref-type="bibr" rid="ref38">38</xref>
          ] models concepts related to the ICCD Catalogue, and in particular catalogue records, that
is the XML files recording all data gathered by a cataloguer on a particular Italian cultural property. The Sequence [
          <xref ref-type="bibr" rid="ref39">39</xref>
          ]
pattern is reused to model the different versions of the same catalogue record, represented by the class a-cat:
CatalogueRecordVersion.
        </p>
        <p>
          The location module [
          <xref ref-type="bibr" rid="ref40">40</xref>
          ] is intended to cover spatial and geometry information. A cultural property may have
multiple locations, represented by the class a-loc:LocationType. In addition, the fact that a type of cultural property
location holds during a time interval is modeled by the a-loc:TimeIndexedTypeLocation, which implements and
specialises the TimeIndexedSituation [
          <xref ref-type="bibr" rid="ref41">41</xref>
          ] pattern.
        </p>
        <p>
          The denotative description module [
          <xref ref-type="bibr" rid="ref42">42</xref>
          ] encodes the characteristics of a cultural property observed during the
cataloguing process, e.g. measurements, materials, techniques, etc. To represent those characteristics we reused and
specialised the Description&amp;Situation [
          <xref ref-type="bibr" rid="ref43">43</xref>
          ] pattern for modeling both the technical status (a-dd:CulturalEntity
TechnicalStatus) and the technical description (a-dd:CulturalEntityTechnicalDescription) of a cultural
property.
        </p>
        <p>
          The context description module [
          <xref ref-type="bibr" rid="ref44">44</xref>
          ] represents the context of cultural properties, in a broad sense, including the
information related to: authors, collectors, copyright holders, inventories, bibliography, etc. For example, in order to
represent the concept of an a-cd:Archival-RecordSet, i.e. fonds, series, subseries, etc., we reuse the Born Digital
Archives [
          <xref ref-type="bibr" rid="ref45">45</xref>
          ] pattern.
        </p>
        <p>
          The cultural events module [
          <xref ref-type="bibr" rid="ref46">46</xref>
          ] is dedicated to cultural events and exhibitions involving a cultural property. It
extends, with some classes and properties (e.g. a-ce:Exhibition), the Cultural-ON ontology [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ].
4.3
        </p>
      </sec>
      <sec id="sec-3-3">
        <title>ArCo LOD</title>
        <p>
          ArCo knowledge graph currently counts: 7 ontology modules, 327 classes, 379 object properties, 154 datatype properties,
395 restrictions. It counts about 170M triples and provides 24,008 owl:sameAs axioms linking to other datasets, such as
DBpedia [
          <xref ref-type="bibr" rid="ref47">47</xref>
          ], Wikidata [
          <xref ref-type="bibr" rid="ref48">48</xref>
          ], the ULAN [
          <xref ref-type="bibr" rid="ref49">49</xref>
          ] and TGN [
          <xref ref-type="bibr" rid="ref50">50</xref>
          ] Getty Vocabularies, Zeri&amp;LODE [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ], YAGO [
          <xref ref-type="bibr" rid="ref51">51</xref>
          ],
Europeana [
          <xref ref-type="bibr" rid="ref52">52</xref>
          ], Geonames [
          <xref ref-type="bibr" rid="ref53">53</xref>
          ]. The Entity linking is performed with LIMES [
          <xref ref-type="bibr" rid="ref54">54</xref>
          ], and the LIMES configuration files
used in the linking process are available on Zenodo [
          <xref ref-type="bibr" rid="ref55">55</xref>
          ].
        </p>
        <p>Fig. 3 depicts an example of information of a painting with subject “Madonna con bambino” (tr.en. Madonna with
child). On the left side, there is the XML data, expressed as string and stored in the ICCD General Catalogue, and on the
right side there is the correspondent data in RDF format generated according to ArCo ontologies.
In order to involve different stakeholders, we have organised a series of meetups associated with the ArCo releases. So
far, we had 5 meetups, each attended by about 20 participants, and 1 webinar; we received 35 GitHub issues, and 27
people joined the mailing-list.</p>
        <p>ArCo has a potentially very strong impact on both Cultural Heritage and Digital Humanities fields and related
domains. At international level, ArCo ontologies allow to represent very detailed information on cultural heritage of many
different types and ArCo data can be aligned to other CH data, ensuring a high reliable provenance. These ontology
network and dataset will be used by institutions (such as museums, designated for cultural heritage preservation and
enhancement), which intend to publish their data as LOD and/or link them to ArCo, as well as by companies and
individual consumers (i.e. researchers, students, practitioners, citizens) that own and use CH data for different purposes.</p>
        <p>
          Good examples, among others, of ArCo early adopters are: Synapta team [
          <xref ref-type="bibr" rid="ref56">56</xref>
          ], which reuses ArCo ontologies for
representing musical instruments belonging to Sound Archives &amp; Musical Instruments Collection (SAMIC) [
          <xref ref-type="bibr" rid="ref57">57</xref>
          ], and
Ricostruzione Trasparente project [
          <xref ref-type="bibr" rid="ref58">58</xref>
          ], which aims at linking its data about areas of Italy damaged by the earthquakes in
2016 to ArCo data.
        </p>
        <p>Currently, an extraordinary amount of data on Italian cultural heritage, in the form of a LOD dataset, is available to
anyone interested in querying, consulting and reusing them. ArCo ontologies are released and adopted directly by ICCD,
which provides Italian regulations for cataloguing cultural properties. Therefore, ArCo has become, in LOD context, a
standard for Italian cultural institutions aiming at creating Linked Data, according to ministerial regulations.</p>
        <p>Since the valorization of cultural heritage through LOD enables sharing and reusing of cultural heritage data in an
open interconnected and multi-domain knowledge base on the Web, we plan to improve ArCo ontology network and
LOD. Future efforts will be directed to: (i) model peculiar information regarding natural heritage and information related
to archive and library domains, (ii) improve entity-linking, and (iii) provide tooling support for CH data owners in order
to encourage and simplify the adoption of ArCo and other ontologies by domain experts.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Hyvönen</surname>
          </string-name>
          , E.:
          <article-title>Semantic Portals for Cultural Heritage</article-title>
          . In: Staab S.,
          <string-name>
            <surname>Studer</surname>
            <given-names>R</given-names>
          </string-name>
          . (eds) Handbook on Ontologies.
          <source>International Handbooks on Information Systems</source>
          . pp.
          <fpage>757</fpage>
          -
          <lpage>778</lpage>
          , Springer, Berlin, Heidelberg (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <article-title>2. IBC-ER homepage</article-title>
          , https://ibc.regione.emilia-romagna.it/servizi-online/lod, last accessed
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Daquino</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mambelli</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Peroni</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tomasi</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vitali</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Enhancing Semantic Expressivity in the Cultural Heritage Domain: Exposing the Zeri Photo Archive as Linked Open Data</article-title>
          .
          <source>JOCCH</source>
          <volume>10</volume>
          (
          <issue>4</issue>
          ),
          <fpage>1</fpage>
          -
          <lpage>21</lpage>
          (
          <year>2017</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>Fondazione</given-names>
            <surname>Zeri</surname>
          </string-name>
          &amp;
          <article-title>LODE homepage</article-title>
          , http://data.fondazionezeri.unibo.it/, last accessed
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5. Europeana Project Homepage, https://pro.europeana.eu/page/linked-open-data,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>ArCo</given-names>
            <surname>Project</surname>
          </string-name>
          , http://wit.istc.cnr.it/arco, last accessed
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>CIDOC-CRM Homepage</surname>
          </string-name>
          , http://www.cidoc-crm.org/,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Doerr</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>The CIDOC Conceptual Reference Module: An Ontological Approach to Semantic Interoperability of Metadata</article-title>
          .
          <source>AI Magazine</source>
          <volume>24</volume>
          (
          <issue>3</issue>
          ),
          <fpage>75</fpage>
          -
          <lpage>92</lpage>
          (
          <year>2003</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>Europeana</given-names>
            <surname>Data</surname>
          </string-name>
          <article-title>Model (EDM) Documentation</article-title>
          , https://pro.europeana.eu/resources/standardization-tools/edm-documentation,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Charles</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Isaac</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tzouvaras</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Hennicke</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Mapping Cross-Domain Metadata to the Europeana Data Model (EDM)</article-title>
          . In: Aalberg T.,
          <string-name>
            <surname>Papatheodorou</surname>
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dobreva</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tsakonas</surname>
            <given-names>G.</given-names>
          </string-name>
          , Farrugia C.J. (eds) Research and
          <article-title>Advanced Technology for Digital Libraries</article-title>
          .
          <source>TPDL 2013. Lecture Notes in Computer Science</source>
          , vol
          <volume>8092</volume>
          , pp.
          <fpage>484</fpage>
          -
          <lpage>485</lpage>
          , Springer, Berlin, Heidelberg (
          <year>2013</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <article-title>Cultural-ON Ontology on MiBAC OpenData Website</article-title>
          , http://dati.beniculturali.it/lodview/cis/.html,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12. Fentry Ontology, https://essepuntato.github.io/fentry/current/fentry.html,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13. OAEntry Ontology, http://oaentry-ontology.sourceforge.net/index.html,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Dijkshoorn</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aroyo</surname>
          </string-name>
          , L.,
          <string-name>
            <surname>van Ossenbruggen</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schreiber</surname>
          </string-name>
          , G.:
          <article-title>Modeling cultural heritage data for online publication</article-title>
          .
          <source>Applied Ontology</source>
          <volume>13</volume>
          (
          <issue>4</issue>
          ),
          <fpage>255</fpage>
          -
          <lpage>271</lpage>
          (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15. OntoPia Ontology Network, https://github.com/italia/daf-ontologie
          <string-name>
            <surname>-</surname>
          </string-name>
          vocabolari-controllati/tree/master/Ontologie, last accessed
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Lodi</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Asprino</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nuzzolese</surname>
            ,
            <given-names>A. G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Presutti</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gangemi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reforgiato Recupero</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Veninata</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Orsini</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Semantic Web for Cultural Heritage Valorisation</article-title>
          . In:
          <string-name>
            <surname>Hai-Jew</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <article-title>(eds) Data Analytics in Digital Humanities</article-title>
          ,
          <source>Multimedia Systems and Applications</source>
          , pp.
          <fpage>3</fpage>
          -
          <lpage>37</lpage>
          , Springer, Cham (
          <year>2017</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17. eXtreme Design, http://extremedesign.sourceforge.net/,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Blomqvist</surname>
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Presutti</surname>
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Daga</surname>
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gangemi</surname>
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Experimenting with eXtreme Design</article-title>
          . In: Cimiano,
          <string-name>
            <given-names>P.</given-names>
            ,
            <surname>Pinto</surname>
          </string-name>
          , H.S. (eds)
          <article-title>Knowledge Engineering and Management by the Masses</article-title>
          ,
          <string-name>
            <surname>EKAW</surname>
          </string-name>
          <year>2010</year>
          .
          <article-title>LNCS</article-title>
          , vol.
          <volume>6317</volume>
          , pp.
          <fpage>120</fpage>
          -
          <lpage>134</lpage>
          , Springer, Berlin, Heidelberg (
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19. ArCo Google Groups, https://groups.google.com/forum/#!forum/arco-project,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20. ArCo Issues Tracker on Github, https://github.com/ICCD-MiBACT/ArCo/issues, last accessed
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21. Meetup Homepage, https://www.meetup.com/,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Presutti</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lodi</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nuzzolese</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gangemi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Peroni</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Asprino</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>The Role of Ontology Design Patterns in Linked Data Projects</article-title>
          . In:
          <string-name>
            <surname>Comyn-Wattiau</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tanaka</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Song</surname>
          </string-name>
          , IY.,
          <string-name>
            <surname>Yamamoto</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Saeki</surname>
            , M. (eds) Conceptual Modeling,
            <given-names>ER</given-names>
          </string-name>
          <year>2016</year>
          .
          <article-title>LNCS</article-title>
          , vol.
          <volume>9974</volume>
          , pp.
          <fpage>113</fpage>
          -
          <lpage>121</lpage>
          , Springer, Cham (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Gangemi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Catenacci</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ciaramita</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lehmann</surname>
          </string-name>
          , J.:
          <article-title>Modelling Ontology Evaluation and Validation</article-title>
          . In: Sure,
          <string-name>
            <given-names>Y.</given-names>
            ,
            <surname>Domingue</surname>
          </string-name>
          ,
          <string-name>
            <surname>J</surname>
          </string-name>
          . (eds) The Semantic Web: Research and Applications,
          <string-name>
            <surname>ESWC</surname>
          </string-name>
          <year>2006</year>
          .
          <article-title>LNCS</article-title>
          , vol.
          <volume>4011</volume>
          , pp.
          <fpage>140</fpage>
          -
          <lpage>154</lpage>
          , Springer, Berlin, Heidelberg (
          <year>2006</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>Hitzler</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gangemi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Janowicz</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krisnadhi</surname>
            ,
            <given-names>A.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Presutti</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          :
          <article-title>Ontology Engineering with Ontology Design Patterns: Foundations and Applications, Studies on the Semantic Web</article-title>
          , vol.
          <volume>25</volume>
          , IOS Press (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25. Ontology Design Pattern Homepage, http://ontologydesignpatterns.org/,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26.
          <article-title>OPLa ontology on ODP portal</article-title>
          , http://ontologydesignpatterns.org/opla/,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27. ArCo release on Github, https://github.com/ICCD-MiBACT/ArCo, last accessed
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28. ArCo homepage, http://wit.istc.cnr.it/arco, last accessed
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          29. ArCo on MiBAC OpenData, http://dati.beniculturali.it/progetto-arco
          <article-title>-architettura-della-conoscenza/</article-title>
          ,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          30. MiBAC Sparql Endpoint, http://dati.beniculturali.it/sparql, last accessed
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          31. ArCo Module Namespace, https://w3id.org/arco/ontology/arco, last accessed
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          32. MiBAC Cataloguing Standards, http://www.iccd.beniculturali.it/it/normative, last accessed
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          33. Cultural Properties Classification on Github, https://github.com/ICCD-MiBACT/ArCo/blob/master/ArCo-release/httpd/publichtml/img2/culturalproperty-classification.jpg,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref34">
        <mixed-citation>
          34. Core Module Namespace, https://w3id.org/arco/ontology/core/,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref35">
        <mixed-citation>
          35. Part Of Pattern, http://www.ontologydesignpatterns.org/cp/owl/partof.owl,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref36">
        <mixed-citation>
          36. Classification Pattern, http://www.ontologydesignpatterns.org/cp/owl/classification.owl,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref37">
        <mixed-citation>
          37. Situation Pattern, http://www.ontologydesignpatterns.org/cp/owl/situation.owl,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref38">
        <mixed-citation>
          38. Catalogue Module Namespace, https://w3id.org/arco/ontology/catalogue/,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref39">
        <mixed-citation>
          39. Sequence Pattern, http://www.ontologydesignpatterns.org/cp/owl/sequence.owl,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref40">
        <mixed-citation>
          40. Location Module Namespace, https://w3id.org/arco/ontology/location/,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref41">
        <mixed-citation>
          41. TimeIndexedSituation Pattern, http://www.ontologydesignpatterns.org/cp/owl/timeindexedsituation.owl,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref42">
        <mixed-citation>
          42. Denotative Description Module Namespace, https://w3id.org/arco/ontology/denotative-description/,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref43">
        <mixed-citation>
          43.
          <string-name>
            <surname>Description</surname>
          </string-name>
          &amp;Situation Pattern, http://www.ontologydesignpatterns.org/cp/owl/descriptionandsituation.owl,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref44">
        <mixed-citation>
          44. Context Description Module Namespace, https://w3id.org/arco/ontology/context-description/,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref45">
        <mixed-citation>
          45. Born Digital Archives Pattern, http://mklab.iti.gr/pericles/BornDigitalArchives_ODP.owl,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref46">
        <mixed-citation>
          46. Cultural Event Module Namespace, https://w3id.org/arco/ontology/cultural-event/,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref47">
        <mixed-citation>
          47. DBpedia Homepage, https://wiki.dbpedia.org/,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref48">
        <mixed-citation>
          48. Wikidata Homepage, https://www.wikidata.org/wiki/Wikidata:Main_Page, last accessed
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref49">
        <mixed-citation>
          49. ULAN Getty Vocabulary, http://www.getty.edu/research/tools/vocabularies/ulan/,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref50">
        <mixed-citation>
          50. TNG Getty Vocabulary, http://www.getty.edu/research/tools/vocabularies/tgn/,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref51">
        <mixed-citation>
          51. YAGO Knowledge Base, https://www.mpi-inf.mpg.de/departments/databases-and
          <string-name>
            <surname>-</surname>
          </string-name>
          information-systems/research/yagonaga/yago/,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref52">
        <mixed-citation>
          52. Europeana Linked Open Data, https://pro.europeana.eu/page/linked-open-data,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref53">
        <mixed-citation>
          53. Geonames Homepage, https://www.geonames.org/,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref54">
        <mixed-citation>
          54. LIMES Homepage, http://aksw.org/Projects/LIMES.html,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref55">
        <mixed-citation>
          55. ArCo Entity Linking on Zenodo, https://zenodo.org/record/2630565#.XNhq69MzYUs, last accessed
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref56">
        <mixed-citation>
          56. Synapta Homepage, https://synapta.it/, last accessed
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref57">
        <mixed-citation>
          57.
          <string-name>
            <surname>Sound</surname>
            <given-names>Archives</given-names>
          </string-name>
          &amp; Musical Instruments Collection Homepage, http://museopaesaggiosonoro.org
          <article-title>/sound-archives-musicalinstruments-collection-samic/</article-title>
          ,
          <source>last accessed</source>
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
      <ref id="ref58">
        <mixed-citation>
          58. Ricostruzione Trasparente Project, http://ricostruzionetrasparente.it/, last accessed
          <year>2019</year>
          /05/17.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>