<!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>Reassembling the Republic of Letters - A Linked Data Approach</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Jouni Tuominen</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Eetu Ma¨kela¨</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Eero Hyvo¨ nen</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Arno Bosse</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Miranda Lewis</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Howard Hotson</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Faculty of History, University of Oxford</institution>
          ,
          <addr-line>Oxford</addr-line>
          ,
          <country country="UK">UK</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>HELDIG - Helsinki Centre for Digital Humanities, University of Helsinki</institution>
          ,
          <country country="FI">Finland</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Semantic Computing Research Group (SeCo), Aalto University</institution>
          ,
          <country country="FI">Finland</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Between 1500 and 1800, a revolution in postal communication allowed ordinary men and women to scatter letters across and beyond Europe. This exchange helped knit together what contemporaries called the respublica litteraria, or Republic of Letters, a knowledge-based civil society, crucial to that era's intellectual breakthroughs, and formative of many modern European values and institutions. To enable effective Digital Humanities research on the epistolary data distributed in different countries and collections, metadata about the letters have been aggregated, harmonised, and provided for the research community through the Early Modern Letters Online (EMLO) catalogue. This paper discusses the idea and benefits of using Linked Data as the basis for a potential future framework for EMLO, and presents our experiences with a first demonstrator implementation of such a system.</p>
      </abstract>
      <kwd-group>
        <kwd>Semantic Web</kwd>
        <kwd>Linked Open Data</kwd>
        <kwd>Digital Humanities</kwd>
        <kwd>Early Modern</kwd>
        <kwd>Reconciliation</kwd>
        <kwd>Correspondence</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>The revolution in postal communication in the early modern period allowed scholars
and ordinary people to share their thoughts via letters in an efficient manner, in Europe
and beyond. This development was a vital requirement for the respublica litteraria,
or Republic of Letters, a knowledge-based civil society, crucial to that era’s
intellectual breakthroughs, and formative of many modern European values and institutions.
However, for the modern scholars of the subject the scattered nature of the letter poses
challenges, as the letter manuscripts are held in different libraries, archives, and private
collections around the world.</p>
      <p>Digital resources on early modern learned correspondence are proliferating rapidly
but without a common framework for sharing data, tools, and systems development.
Such resources include Europeana4, Kalliope5, The Catalogus Epistularum
Neerlandi4 http://www.europeana.eu
5 http://kalliope.staatsbibliothek-berlin.de
carum6, Electronic Enlightenment7, ePistolarium8, the Mapping the Republic of Letters
project9, and Early Modern Letters Online (EMLO)10. To reassemble the material and
to facilitate its efficient study, coordinated discussions amongst librarians and archivists,
scholars, IT and media experts are needed to collectively plan a shared digital
infrastructure for publishing, reconciling, visualising, and analysing correspondence. Many
of these conversations have been taking place over the last three years under the
auspices of the EU COST Action IS1310 ’Reassembling the Republic of Letters’11.</p>
      <p>This paper presents a Linked Data approach for such an infrastructure, using the
Early Modern Letters Online (EMLO) collection as a pilot dataset. EMLO is a
collaboratively populated union catalogue of sixteenth-, seventeenth-, and eighteenth-century
letters, created by the Cultures of Knowledge project12 at the University of Oxford. It
brings manuscript, print, and electronic resources together in one space, increasing
access to and awareness of them, and allows disparate and connected correspondences to
be cross-searched, combined, analysed, and visualised.</p>
      <p>The paper is organized as follows. First, the general vision and process
description in our case study of creating, aggregating, and utilizing distributed epistolary data
about letters is outlined, based on a Linked Data approach. After this, the underlying
data models, data conversion, ontology services, tooling, and use of the data service in
research are discussed.
2</p>
    </sec>
    <sec id="sec-2">
      <title>A Distributed Publishing Model</title>
      <p>
        6 http://picarta.pica.nl/DB=3.23/
7 http://www.e-enlightenment.com
8 http://ckcc.huygens.knaw.nl/epistolarium/
9 http://republicofletters.stanford.edu
10 http://emlo.bodleian.ox.ac.uk
11 http://republicofletters.net
12 http://www.culturesofknowledge.org
13 http://ldf.fi
14 Due to IP restrictions the data is currently not freely available, but access is being negotiated
with the metadata owners.
1. Data aggregation. The RDF data model underlying the Semantic Web and Web of
Data15 is very flexible and simple for combining heterogeneous data from multiple
data silos.
2. Support for sharing ontologies. Ontologies used in populating the metadata, such
as historical people and places, can be shared within the community using ontology
services [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
3. Crowdsourcing. When cataloguing, new resources created in the distributed content
creation network can be shared, as suggested in [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
4. Support tooling. SPARQL endpoint provides a flexible standard API for creating
tools for data cleaning, entity linking, ontology mapping, etc.
5. Open application development. In the same vein, the SPARQL API can be used
in a standardized way for creating rich internet applications (RIA). No server side
programming and data management is needed, if the API is available, which can
simplify application development substantially and make it possible to virtually
anyone.
      </p>
      <p>The dashed arrows in Fig. 1 illustrate the fact, that the Linked Data service can
be used not only in application development, but also during the data cataloguing
process in the participating organizations. Using shared up-to-date ontology services,
disambiguated identifiers for, e.g., persons and places can be assigned more easily and
15 http://www.w3.org/2013/data/
duplication of work is avoided. Also tooling for, e.g., data cleaning, reconciliation, and
duplicate checking can be shared in this way, saving human resources of the community
as a whole and leading to more accurate and interoperable metadata from the outset.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Data Models and Linked Data Conversion</title>
      <p>
        In order to allow scholars to efficiently study the vast amount of epistolary data from
different data sources as a whole, the data has to be made semantically interoperable,
either by mapping different data models (e.g., by using Dublin Core16 and the
DumbDown Principle17), or by providing a harmonised data model to transform the datasets
into linked data [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. We are suggesting the use of a shared data model for all the datasets.
Unlike many other manuscript genres, letters share readily identifiable basic features
(sender, recipient, date of sending and arrival, place of origin and destination) which
facilitate the formation of a common data model.
      </p>
      <p>
        In the context of EMLO, we have converted the original relational database via a
straightforward conversion process using a script18 into an RDF format. The conversion
retains EMLO’s internal data model, and thus follows a simple attribute-based
modeling approach. A letter is represented as an instance of the class ”Letter”, and it has
properties, such as ”created” (inverse property), ”was addressed to”, ”was sent from”,
”was sent to”, ”has time-span” (date), ”original calendar”, ”language”, ”repository”,
”shelfmark”, ”printed edition details”, and ”source” (the catalogue the letter belongs
to). The data model utilises CIDOC CRM19 [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] (for time spans, people, and places),
Dublin Core (for language, date, description, and subject), FOAF20 (for person names
and gender), and SKOS21 (for labels) vocabularies.
      </p>
      <p>
        In addition to purely epistolary data, EMLO contains prosopographical infomation
related to the people in the database, modeled as events and social relationships. Events
cover activities that the people have participated in during their lives, such as birth
and death, ecclesiastic and educational activities, creations of works, travels and
residences. The event metadata includes the event name, type, participants and their roles,
time span, location, and source information. We converted the prosopographical data
into RDF format using CIDOC CRM for the event-based modeling and W3C’s PROV
model [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] for representing the roles of participants in the events.
      </p>
      <p>
        As a continuation of this work, we have also developed Bio CRM22 [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], a
semantic data model for harmonising and interlinking heterogeneous biographical
information from different data sources. It is a domain specific extension of CIDOC CRM,
effectively providing compatibility with other cultural heritage information as well. The
data model includes structures for basic data of people, personal relations, professions,
16 http://dublincore.org/documents/dcmi-terms/
17 https://github.com/dcmi/repository/blob/master/mediawiki_wiki/
      </p>
      <p>
        Glossary/Dumb-Down_Principle.md
18 http://github.com/jiemakel/anything2rdf
19 http://cidoc-crm.org
20 http://xmlns.com/foaf/spec/
21 http://www.w3.org/TR/skos-reference/
22 http://ldf.fi/schema/bioc/
and events with participants in different roles. One of the novelties of Bio CRM is the
VIVO/BFO-inspired23 [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], intuitive, and simple approach for the modeling of roles in
different contexts – unitary roles, binary relationships, and events.
4
      </p>
    </sec>
    <sec id="sec-4">
      <title>Ontologies and Ontology Services</title>
      <p>For authority control, shared ontologies of people, places, and other relevant entity
types, such as events, are needed. A natural starting point for creating such
ontologies are the existing authority files, listings, and databases used in the data sources. In
our use case, we converted the people and places used in EMLO into RDF format, using
CIDOC CRM classes E21 Person and E53 Place. The idea is to store them in their own
graphs in a public triple-store, where they can be queried and utilized by the community
using SPARQL.</p>
      <p>In cases where a data source uses a shared, established authority database, it can
be used as such with a Linked Data approach. A number of authority sources such
as VIAF24, Getty ULAN25, and CERL Thesaurus26 already provide their data in RDF
format, which further simplifies their utilisation.</p>
      <p>
        For efficient use of the shared ontologies, we have developed the Federated SPARQL
Search Widget27, a user interface component that can be integrated into, e.g., letter
cataloguing systems. Using such an approach, the different data providers already receive
strong identifiers for the people and places as part of the data input process [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], with no
need to reconcile the data later. Fig. 2 depicts an example of a SPARQL search widget
for Finnish historical people, with contextual information supporting the selection of
the correct person, including a person’s photograph, short biographical description, and
the places of activity visualised on a map.
5
      </p>
    </sec>
    <sec id="sec-5">
      <title>Tooling for Reconciliation</title>
      <p>When combining data from different sources, support tooling for reconciling the data
into a harmonised format is needed. In the context of EMLO, there already exists a
network of contributors – including scholars working on a specific collection or
edition of correspondence, librarians, and publishers. These contributors provide metadata
pertaining to the correspondence for ingestion into EMLO. The metadata can be input
using a custom spreadsheet or via the EMLO-Collect online web form. Names of both
authors and recipients (people), and origins and destinations (places) are included in the
provided metadata. When inputting this data into EMLO, these people and places have
to be matched to existing person and place records in the EMLO database or else
assigned new person and place IDs. A semi-automatic tool, Recon28, has been developed
to assist with this matching process.
23 http://vivoweb.org
24 http://viaf.org/viaf/data/
25 http://vocab.getty.edu
26 http://www.cerl.org/resources/cerl_thesaurus/linkeddata
27 http://github.com/SemanticComputing/federated-sparql-search-widget
28 http://github.com/jiemakel/recon</p>
      <p>
        Recon is designed for digital humanities scenarios where trusted accuracy is of
paramount importance. This means that: a) the matching cannot be done entirely
automatically; b) the tool has to return as many potential matches as possible for the user
to consult and consider a ’match’; and c) the user has to be supported in the manual
verification process with the provision of contextual information concerning the match
candidates. Compared to reconciliation tools such as Silk [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] and OpenRefine [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ],
Recon focuses on a manual review of potential match candidates, using a browser-based
user interface to afford a simple, fast, and intuitive workflow.
      </p>
      <p>The Recon user interface is depicted in Fig. 3. The tool reads a spreadsheet of
names of people or places, possibly with contextual information, such as the years
in which a person was active (floriat). Working through the data rows, Recon runs
SPARQL queries to a triple-store containing people and places extracted from the
current EMLO database. For each person or place in the spreadsheet, a list of potential
candidate matches is offered to the user, based on the string similarity of the name, and
potentially other criteria based on the SPARQL query used in the matching process. For
example, the years of activity of a person can be used to rank candidates with suitable
birth and death years higher than those similarly named people who have lived at some
other time period. The user has the option to specify whether there is a match or not, or
to leave a query open in case there is an uncertainty; this query might request further
investigation be carried out. When the spreadsheet has been processed, Recon re-exports
to the user the original data supplemented with the EMLO IDs of the matched people
or places. Where no matches have been identified, new EMLO records are created and
their IDs inserted. Following this, the revised dataset can be ingested into EMLO using
this complete list of people and place IDs.</p>
      <p>For pre-processing tabular letter metadata into a more efficient format before Recon
is used, a complementary tool called Mare29 has been developed. Mare is a map/reduce
user interface for tables. The tool is used in the EMLO spreadsheet workflow to collect
all unique people and place names from a correspondence dataset with contextualizing
information, such as the years of activity based on the dates of the letters that involve
particular people or places. A sample output of Mare is depicted in Fig. 4.</p>
      <p>In addition to using Recon for the semi-automated matching of newly contributed
datasets, the tool has been piloted to enable the identification and linking of records for
the same letters contained in separate catalogues within EMLO. To achieve this, Recon
is configured to run SPARQL queries across the EMLO dataset to identify potential
’matching’ letters, i.e., letters that have the same sender and recipient, and share similar
or exact data in other metadata fields, in particular repository and shelfmark references,
or printed edition details, dates, and places of origin and destination. The tool ranks the
potential duplicate matches for a given letter by taking into account the proximity of
the dates, string similarities of textual metadata fields, etc. The EMLO editors are then
able to assess whether the entries provided by different contributors in different letter
collections (whether they be listings of an early modern individual’s correspondence or
of a thematic collection) refer to the same letter; if the same letter has been entered by
different contributors, a bridge link between the two ’interpretations’ of the same letter
can be inserted in EMLO.
29 http://github.com/jiemakel/mare</p>
      <p>Whilst working with Recon, EMLO’s editors are able to call up records to identify
matches allowing them to review people, place, and letter records in different
combinations and to view the correspondence metadata ’from different angles’. In consequence,
errors are spotted and corrected more easily, as well as partial matches, and can be
cleaned and augmented in tandem, as appropriate.
6</p>
    </sec>
    <sec id="sec-6">
      <title>Visualisation and Analysis Tools</title>
      <p>
        The epistolary data published in a structured format can be conveniently visualised
using general-purpose data visualisation and exploration tools, such as Palladio30 [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ],
RAW31, or SPARQL Faceter [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. Palladio can not only ingest data from a spreadsheet,
but the data can also be loaded directly from a SPARQL endpoint. This allows for
the creation of live visualisations without the need to export data manually each time.
Palladio can be used, e.g., for graph, timeline, or map-based visualisations. SPARQL
Faceter allows a scholar to interactively examine a dataset by filtering it using different
facets, such as sender, recipient, origin, destination, date, or catalogue.
      </p>
      <p>Fig. 5 visualises the temporal distribution of the catalogues included in EMLO,
using the RAW data visualization framework. One can see that EMLO contains
different catalogues (colour-coded) of letters from the time period 1500–1800, with the
highest peak representing correspondence activity in the 1640’s. Fig. 6 visualises the
social relationships of Samuel Hartlib based on the prosopographical data in EMLO
30 http://hdlab.stanford.edu/palladio/
31 http://app.rawgraphs.io
(connections of two steps from Hartlib), using Palladio. The map shows the
connections Hartlib had to various locations around Europe (the size of a circle represents the
amount of connections), and from the timeline one can see, e.g., that Hartlib was most
active in the 1640’s. Further visualizations of Hartlib’s network using extended
prosopographical data not yet integrated into EMLO may be viewed and queried via a pilot
Shiny/R dashboard32.
This paper presented the idea of using Linked Data as a basis for aggregating,
harmonising, publishing, and using epistolary data in a distributed setting. To test and
demonstrate the ideas, the existing EMLO service data was re-used, transformed into Linked
Data, and published as a “5-star”33 Linked Data service. On top of the SPARQL
endpoint provided by the data service, further tools were created which could be utilised
32 https://idn.web.ox.ac.uk/article/cultures-knowledge-case-study
33 http://5stardata.info
by the scholarly community. The Mare and Recon tools are already in active use by
EMLO’s editors at the University of Oxford. We also demonstrated the potential of
application development on top of the linked data service, by using Palladio and RAW for
visualising the epistolary data from a digital humanities research perspective.</p>
      <p>
        This paper focused on epistolary data only, but the Republic of Letters is of course
not only about letters, but scholarly communications and the exchange of knowledge
more broadly, including books, essays, artifacts, etc. A major benefit of the Linked
Data approach in the future is that the model is flexible enough for representing
different kind of forms of scholarly and cultural heritage content in an interoperable, machine
“understandable” (semantic) way, including both tangible and intangible aspects of
culture and history [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Based on semantic representations of knowledge, new kind of
services based on, e.g., intelligent data analysis, Artificial Intelligence, and Knowledge
Discovery can be conceived and created.
      </p>
      <p>
        However, the envisioned potential and benefits also have a price tag. Legacy systems
already in use do not yet support Linked Data, and the technology is new and not
consistently established in IT departments. The most important challenge is, however, that
using the new model requires greater collaboration and mutual agreements between the
participating organizations, which complicates the process. One has to take into
consideration the shared ontologies and vocabularies used by the community, not only one’s
own preferred standards and practices. However, since in this case the final goal of the
community is to create a global view of the Republic of Letters, it is a better idea to
avoid interoperability problems before they arise by a Linked Data infrastructure than
to try to solve them afterwards when the damage is already done [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. As Alfred Einstein
put it: Intellectuals solve problems, geniuses prevent them.
      </p>
      <p>Acknowledgements Our work is part of the EU COST Action project Reassembling
the Republic of Letters34 and the Cultures of Knowledge project, funded by The
Andrew W. Mellon Foundation. The work is also part of the Open Science and Research
Programme35, funded by the Ministry of Education and Culture of Finland.
34 http://www.republicofletters.net
35 http://openscience.fi</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Andert</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berger</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Molitor</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ritter</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>An optimized platform for capturing metadata of historical correspondence</article-title>
          .
          <source>Digital Scholarship in the Humanities</source>
          <volume>30</volume>
          (
          <issue>4</issue>
          ),
          <fpage>471</fpage>
          -
          <lpage>480</lpage>
          (
          <year>2015</year>
          ), https://doi.org/10.1093/llc/fqu027
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Doerr</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>The CIDOC CRM-an ontological approach to semantic interoperability of metadata</article-title>
          .
          <source>AI</source>
          Magazine
          <volume>24</volume>
          (
          <issue>3</issue>
          ),
          <fpage>75</fpage>
          -
          <lpage>92</lpage>
          (
          <year>2003</year>
          ), https://doi.org/10.1609/aimag. v24i3.
          <fpage>1720</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Edelstein</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Findlen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ceserani</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Winterer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Coleman</surname>
          </string-name>
          , N.:
          <article-title>Historical research in a digital age: Reflections from the mapping the republic of letters project</article-title>
          .
          <source>The American Historical Review</source>
          <volume>122</volume>
          (
          <issue>2</issue>
          ),
          <fpage>400</fpage>
          -
          <lpage>424</lpage>
          (
          <year>2017</year>
          ), https://doi.org/10.1093/ahr/122. 2.
          <fpage>400</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Heath</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bizer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Linked Data: Evolving the Web into a Global Data Space (1st edition)</article-title>
          .
          <source>Synthesis Lectures on the Semantic Web: Theory and Technology</source>
          , Morgan &amp; Claypool (
          <year>2011</year>
          ), http://linkeddatabook.com/editions/1.0/
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5. Hyvo¨nen, E.:
          <article-title>Preventing interoperability problems instead of solving them</article-title>
          .
          <source>Semantic Web Journal</source>
          <volume>1</volume>
          (
          <issue>1-2</issue>
          ),
          <fpage>33</fpage>
          -
          <lpage>37</lpage>
          (
          <year>December 2010</year>
          ), http://www.semantic
          <article-title>-web-journal.net/content/ preventing-interoperability-problems-instead-solving-them</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6. Hyvo¨nen, E.:
          <article-title>Publishing and using cultural heritage linked data on the semantic web</article-title>
          . Morgan &amp; Claypool, Palo Alto, CA (
          <year>2012</year>
          ), https://doi.org/10.2200/ S00452ED1V01Y201210WBE003
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7. Hyvo¨nen, E.,
          <string-name>
            <surname>Tuominen</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ikkala</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          , Ma¨kela¨, E.:
          <article-title>Ontology services based on crowdsourcing: Case national gazetteer of historical places</article-title>
          .
          <source>In: Proceedings of the ISWC</source>
          <year>2015</year>
          <article-title>Posters &amp; Demonstrations Track</article-title>
          .
          <string-name>
            <surname>CEUR-WS Proceedings</surname>
          </string-name>
          (
          <year>2015</year>
          ), http://www.ceur-ws.
          <source>org/</source>
          Vol-
          <volume>1486</volume>
          /paper_45.pdf, vol
          <volume>1486</volume>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8. Hyvo¨nen, E.,
          <string-name>
            <surname>Tuominen</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Alonen</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , Ma¨kela¨, E.:
          <article-title>Linked data Finland: A 7-star model and platform for publishing and re-using linked datasets</article-title>
          .
          <source>In: Proceedings of the ESWC 2014 Demo and Poster Papers</source>
          . Springer-Verlag (
          <year>2014</year>
          ), https://doi.org/10.1007/ 978-3-
          <fpage>319</fpage>
          -11955-7_
          <fpage>24</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Koho</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Heino</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          , Hyvo¨nen, E.:
          <article-title>SPARQL Faceter-Client-side Faceted Search Based on SPARQL</article-title>
          .
          <source>In: Joint Proceedings of the 4th International Workshop on Linked Media and the 3rd Developers Hackshop. CEUR Workshop Proceedings</source>
          (
          <year>2016</year>
          ), http://ceur-ws.
          <source>org/</source>
          Vol-
          <volume>1615</volume>
          /semdevPaper5.pdf, vol
          <volume>1615</volume>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Lebo</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sahoo</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <string-name>
            <surname>PROV-O: The PROV Ontology</surname>
          </string-name>
          (
          <year>2013</year>
          ), http: //www.w3.org/TR/2013/REC-prov-o-
          <volume>20130430</volume>
          /, W3C Recommendation 30 April 2013
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Smith</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Almeida</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bona</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brochhausen</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ceusters</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Courtot</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dipert</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Goldfain</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grenon</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hastings</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hogan</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jacuzzo</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Johansson</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mungall</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Natale</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Neuhaus</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Overton</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Petosa</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rovetto</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ruttenberg</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ressler</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rudniki</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          , Seppa¨la¨,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Schulz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Zheng</surname>
          </string-name>
          , J.:
          <source>Basic formal ontology 2</source>
          .0
          <article-title>- specification and user's guide (</article-title>
          <year>2015</year>
          ), https://github.com/BFO-ontology/BFO/raw/master/ docs/bfo2-reference/BFO2-Reference.pdf, June 26
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Tuominen</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Frosterus</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Viljanen</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          , Hyvo¨nen, E.:
          <article-title>ONKI SKOS server for publishing and utilizing SKOS vocabularies and ontologies as services</article-title>
          .
          <source>In: Proceedings of the 6th European Semantic Web Conference (ESWC</source>
          <year>2009</year>
          ). pp.
          <fpage>768</fpage>
          -
          <lpage>780</lpage>
          . Springer-Verlag (
          <year>2009</year>
          ), https://doi.org/10.1007/978-3-
          <fpage>642</fpage>
          -02121-3_
          <fpage>56</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Tuominen</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , Hyvo¨nen, E.,
          <string-name>
            <surname>Leskinen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <string-name>
            <surname>Bio</surname>
            <given-names>CRM</given-names>
          </string-name>
          :
          <article-title>A data model for representing biographical data for prosopographical research</article-title>
          .
          <source>In: Biographical Data in a Digital World (BD2017)</source>
          (
          <year>2017</year>
          ), https://doi.org/10.5281/zenodo.1040712
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Verborgh</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          , De Wilde,
          <string-name>
            <given-names>M.</given-names>
            :
            <surname>Using OpenRefine. Packt Publishing</surname>
          </string-name>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Volz</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bizer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gaedke</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kobilarov</surname>
          </string-name>
          , G.:
          <article-title>Discovering and maintaining links on the web of data</article-title>
          .
          <source>In: Proceedings of the 8th International Semantic Web Conference (ISWC</source>
          <year>2009</year>
          ). pp.
          <fpage>650</fpage>
          -
          <lpage>665</lpage>
          . Springer-Verlag (
          <year>2009</year>
          ), https://doi.org/10.1007/ 978-3-
          <fpage>642</fpage>
          -04930-9_
          <fpage>41</fpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>