<!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>Reflections on KOS based data integration</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Douglas Tudhope</string-name>
          <email>douglas.tudhope@southwales.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ceri Binding</string-name>
          <email>ceri.binding@southwales.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Hypermedia Research Group, University of South Wales</institution>
          ,
          <country country="UK">UK</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This paper briefly reviews two contrasting case studies by the authors on semantic data integration within the archaeology field and reflects on some of the key issues encountered, relevant to the NKOS Workshop theme on strategies for alignment of metadata to KOS linked data. Both projects involved diverse datasets with different schema and which employed different terminology. Both projects combined datasets with information extracted from archaeological reports via natural language processing (NLP). In both cases, the semantic framework that afforded data integration was a combination of metadata element sets organised by an ontology with a relevant value vocabulary (eg thesauri and term lists). Ontologies and value vocabularies have been seen as complementary resources for this purpose [1, 2].</p>
      </abstract>
      <kwd-group>
        <kwd>knowledge organization systems</kwd>
        <kwd>semantic data integration</kwd>
        <kwd>natural language processing</kwd>
        <kwd>Getty Art &amp; Architecture Thesaurus</kwd>
        <kwd>CIDOC Conceptual Reference Model</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        The STAR project case study [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] combined different archaeological thesauri (eg the
Thesaurus of Monument Types and the Archaeological Objects Thesaurus) and various
glossaries on the vocabulary side, subsequently most available as linked data [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. The
ontology for the study was the CRM-EH extension [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] of the CIDOC CRM [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], which
specializes the CRM with additional elements for archaeological purposes. English
language archaeological datasets focusing mainly on the Roman period were selected,
together with an extract from the Archaeology Data Service grey literature library of
reports. The Demonstrator [detailed scenarios are given in 7] explored the integration of
KOS in cross search over RDF data representations. Binding et al. [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] discuss the
pattern-based data extraction methods, the production of linked data and provide
examples.
      </p>
      <p>
        The more recent case study (part of the ARIADNE FP7 archaeological infrastructure
project [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]) combined the Getty Art and Architecture Thesaurus (AAT) with a set of
high level classes from the CIDOC CRM. Again both KOS are available as linked open
data [
        <xref ref-type="bibr" rid="ref10 ref11">10, 11</xref>
        ]. The data was selected following a broad theme of wooden material,
objects and samples dated via dendrochronological analysis. The investigation was
conducted as an advanced data integration case study for ARIADNE, with the datasets
and reports provided by Dutch, English and Swedish ARIADNE partners. A detailed
description of the study, including a review of relevant literature and scenarios from the
Demonstrator [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] is provided in Binding et al. [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ].
      </p>
      <p>
        In both projects, rule-based NLP pipelines were developed using the GATE platform
[
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] supported by relevant archaeological glossaries and thesauri. STAR focused on
English language grey literature reports, while the ARIADNE study processed English,
Dutch and Swedish language reports. Subject metadata was derived from named entity
recognition of archaeological concepts, such as object, material, together with
archaeological contexts and periods (STAR) and numeric date ranges (ARIADNE). The
Dutch and Swedish vocabulary resources were mapped intellectually to the AAT
providing a multilingual capability for the ARIADNE study. The sequential pipeline
architecture starts with domain independent components, such as a tokeniser, sentence
splitter and part of speech tagger, proceeding with domain specific rules applied to
vocabulary matches in the text. This produces XML format output which is transformed
to the RDF format employed for the data extraction in each study. Vlachidis et al. [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]
give a detailed description of the NLP methods for the English language STAR study,
together with an evaluation of the performance of various NLP pipeline options. A
description of the NLP work for the ARIADNE study is provided in [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ].
      </p>
      <p>
        Both projects developed different query builder user interfaces to shield the user
from some of the complexity of the metadata framework and from the underlying
SPARQL (RDF) implementation. In the ARIADNE case study, the same template
based tool [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] was used for data conversion of extracts from the archaeological
datasets and also the data resulting from the NLP information extraction in the second
project. Query expansion was provided in the demonstrator, based on the AAT's
hierarchical relationships and specialised associative relationships.
3
      </p>
    </sec>
    <sec id="sec-2">
      <title>Reflections</title>
      <p>As with all projects, KOS-based development efforts involve design choices.
Inevitably, with finite resources it is usually impractical to develop parallel implementations
to compare major design alternatives and thus not easy to know the consequences of
one design choice over another. We reflect on some major design decisions encountered
during the two projects, with a view to informing future work.</p>
      <p>These include:
- the level of application detail to model in the integration, how much of the source
datasets and reports should be extracted, aligned to KOS and expressed as linked data.
Should it be a subset or as much as possible?
- the appropriate balance of that application modeling detail, expressed between the
ontology and the vocabulary side. How much to handle via the ontology and how much
to handle via the thesaurus (or other vocabulary)? How much detail is it worthwhile to
model?
- how to mitigate the possibility of creating alternative (valid) ontology mapping
expressions of the same underlying semantics from different sources and thus make cross
search and interoperability difficult?
- should the native schema of the source datasets be maintained in the resulting
integration, or replaced (via the alignment) by the new semantic framework?
- both projects required substantial data cleansing. How should the resulting new
information be modeled, what is the relationship with the source dataset, how should it be
expressed?
- how to express the information extracted via NLP from texts in an RDF framework.
How much certainty to associate with the derived data, what kinds of elements are
represented (archaeological texts often refer to types of object or material rather than
named specific individual items)?
- how to express results from search over both data and reports, how to express the
provenance of the subject metadata extracted and also the method by which it was
extracted?</p>
      <p>The issues relating to the above points will be outlined and illustrated in the
workshop presentation and opened for discussion.</p>
    </sec>
    <sec id="sec-3">
      <title>Acknowledgements</title>
      <p>This work was supported by the UK Arts and Humanities Research Council [grant
numbers AH/D001528/1, AH/H037357/1] and the European Commission under the
Community’s Seventh Framework Programme, contract no.
FP7INFRASTRUCTURES-2012-1-313193 (the ARIADNE project).
** Open Access versions of Hypermedia Research Group’s KOS papers are available from
https://bit.ly/2ocaHC6</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. ISO 25964-2:
          <fpage>2013</fpage>
          .
          <article-title>Information and documentation - Thesauri and interoperability with other vocabularies - Part 2: Interoperability with other vocabularies</article-title>
          . https://www.niso.org/schemas/iso25964#part2,
          <source>last accessed</source>
          <year>2018</year>
          /08/26.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Isaac</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Waites</surname>
            <given-names>W</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Young</surname>
            <given-names>J</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zeng</surname>
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Eds</surname>
          </string-name>
          . Library Linked Data Incubator Group:
          <article-title>Datasets, value vocabularies, and metadata element sets</article-title>
          .
          <source>W3C Incubator Group Report</source>
          . (
          <year>2011</year>
          ), http://www.w3.org/2005/Incubator/lld/XGR-lld-vocabdataset/,
          <source>last accessed</source>
          <year>2018</year>
          /08/26.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>STAR</given-names>
            <surname>Project</surname>
          </string-name>
          . http://hypermedia.research.southwales.ac.uk/kos/star/,
          <source>last accessed</source>
          <year>2018</year>
          /08/26.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Heritagedata</surname>
          </string-name>
          .
          <article-title>Linked Data Vocabularies</article-title>
          . http://www.heritagedata.org/,
          <source>last accessed</source>
          <year>2018</year>
          /08/26.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Cripps</surname>
            <given-names>P</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Greenhalgh</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fellows</surname>
            <given-names>D</given-names>
          </string-name>
          ,
          <string-name>
            <surname>May</surname>
            <given-names>K</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Robinson</surname>
            <given-names>D.</given-names>
          </string-name>
          <article-title>Ontological modelling of the work of the Centre for Archaeology</article-title>
          .
          <source>CIDOC CRM Technical Paper</source>
          . (
          <year>2004</year>
          ) http://old.cidoc-crm.org/docs/Ontological_Modelling_
          <source>Project_Report_ Sep2004.pdf, last accessed</source>
          <year>2018</year>
          /08/26.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Crofts</surname>
            <given-names>N</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Doerr</surname>
            <given-names>M</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gill</surname>
            <given-names>T</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stead</surname>
            <given-names>S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stiff</surname>
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Eds</surname>
          </string-name>
          .
          <source>Definition of the CIDOC Conceptual Reference Model, v5.0</source>
          .4. (
          <year>2011</year>
          ), http://www.cidoc-crm.org/sites/default/files/cidoc_crm_
          <source>version_5.0</source>
          .4.pdf,
          <source>last accessed</source>
          <year>2018</year>
          /08/26.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Tudhope</surname>
            <given-names>D</given-names>
          </string-name>
          ,
          <string-name>
            <surname>May</surname>
            <given-names>K</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Binding</surname>
            <given-names>C</given-names>
          </string-name>
          ,
          <article-title>Vlachidis A. Connecting archaeological data and grey literature via semantic cross search</article-title>
          .
          <source>Internet Archaeology</source>
          ,
          <volume>30</volume>
          , (
          <year>2011</year>
          ), https://doi.org/10.11141/ia.30.5 (open access),
          <source>last accessed</source>
          <year>2018</year>
          /08/26.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Binding</surname>
            <given-names>C</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Charno</surname>
            <given-names>M</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jeffrey</surname>
            <given-names>S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>May</surname>
            <given-names>K</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tudhope</surname>
            <given-names>D</given-names>
          </string-name>
          .
          <article-title>Template based semantic integration: From legacy archaeological datasets to linked data</article-title>
          .
          <source>International Journal on Semantic Web and Information Systems</source>
          ,
          <volume>11</volume>
          (
          <issue>1</issue>
          ),
          <fpage>1</fpage>
          -
          <lpage>29</lpage>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9. ARIADNE. ARIADNE Project. http://www.ariadne-infrastructure.eu,
          <source>last accessed</source>
          <year>2018</year>
          /08/26.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>CIDOC</surname>
          </string-name>
          <article-title>CRM linked data</article-title>
          . https://github.com/erlangen-crm/ecrm, last accessed
          <year>2018</year>
          /08/26.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11. AAT.
          <article-title>Getty Vocabularies as Linked Open Data, Getty Vocabulary Program</article-title>
          , http://vocab.getty.edu/, last accessed
          <year>2018</year>
          /08/26.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Demonstrator</surname>
          </string-name>
          .
          <article-title>Demonstrator for dendrochronological data integration case study</article-title>
          . http://ariadne-lod.isti.cnr.it/description.html,
          <source>last accessed</source>
          <year>2018</year>
          /08/26.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Binding</surname>
            <given-names>C</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tudhope</surname>
            <given-names>D</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vlachidis</surname>
            <given-names>A</given-names>
          </string-name>
          .
          <article-title>A study of semantic integration across archaeological data and reports in different languages</article-title>
          .
          <source>Journal of Information Science</source>
          , (
          <year>2018</year>
          ), https://doi.org/10.1177/0165551518789874, last accessed
          <year>2018</year>
          /08/26.. An open access 'author accepted version' is available at https://pure.southwales.ac.uk/files/2683350/Archaeology_integration_JISauthorversion2.docx).
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Cunningham</surname>
            <given-names>H</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maynard</surname>
            <given-names>D</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bontcheva</surname>
            <given-names>K</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tablan</surname>
            <given-names>V</given-names>
          </string-name>
          .
          <article-title>GATE: A framework and graphical development environment for robust NLP tools and applications</article-title>
          .
          <source>In: Proceedings of 40th Annual Meeting of Association for Computational Linguistics</source>
          , pp
          <fpage>168</fpage>
          -
          <lpage>175</lpage>
          . New Brunswick (
          <year>2002</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Vlachidis</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tudhope</surname>
            <given-names>D.</given-names>
          </string-name>
          <article-title>A knowledge-based approach to information extraction for semantic interoperability in the archaeology domain</article-title>
          .
          <source>Journal of the Association for Information Science and Technology</source>
          <volume>67</volume>
          (
          <issue>5</issue>
          ),
          <fpage>1138</fpage>
          -
          <lpage>1152</lpage>
          (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16. STELETO. STELETO open source code, https://github.com/cbinding/steleto/,
          <source>last accessed</source>
          <year>2018</year>
          /08/26.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>