<!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>Qualitative Analysis of Vocabulary Evolution on the Linked Open Data Cloud</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Mohammad Abdel-Qader</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ansgar Scherp</string-name>
          <email>a.scherp@zbw.eu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Christian-Albrechts University</institution>
          ,
          <addr-line>Kiel</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Leibniz Information Centre for Economics</institution>
          ,
          <addr-line>Kiel</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>We analyse the evolution of vocabularies on the Linked Open Data cloud. Based on the recent statistics of the LOD cloud, we have selected the twelve most dominant vocabularies in terms of their use in di erent pay-level domains. The number of versions we found for these vocabularies range between 2 to 11. While some ontologies exist for more than 10 years (e.g., FOAF) others are only online since a few years (like DCAT). Our analysis shows that many changes occurred on annotation properties. This re ects a need for more clari cation of the terms, especially at early versions of the vocabularies. The majority of changes in the vocabularies are due to changes in other, imported vocabularies. Thus, there is a co-evolution of di erent vocabularies. This insight has practical impacts to ontology engineers. They not only need to consider the evolution of the vocabularies they directly use, but also those they import and indirectly depend on.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        The Semantic Web main objective is to give data in the web a well-de ned
meaning. Those meanings can be represented using ontologies, which can be de ned
as a descriptive form for the concepts and items in a speci c eld or domain
and provides speci cations for those items and its relations to other concepts
[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. The ontologies are subject to change (evolve) over time for many reasons,
such as changes in the ontology's domain, resolving errors appeared in the
current or previous versions of the ontology, changes in its external vocabularies
that are used to establish those ontologies, or any other reasons for updating the
ontology.
      </p>
      <p>
        Creating a new version of an ontology requires processes to handle and
manage multiple versions of that ontology [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Many research focused on analysing
the evolution of some ontologies, and does not focus on the core of establishing
those ontologies; the vocabularies. We mean by vocabulary, a collection of basic
terms (types and properties) that have a broad meaning. Those vocabularies
can be general (suitable for all domains) or speci c (some domains or a single
domain).
      </p>
      <p>Copyright held by the authors.</p>
      <p>In this paper, we focus on analysing the changes that occurred on a selected
set of vocabularies. We analyse them from di erent perspectives and observe how
vocabularies are in uenced by changes made in their dependency vocabularies.
Furthermore, we analyse the types of changes that occurred in vocabularies
terms (classes and properties). Those changes can be additions, deletions,
modications, or renaming of vocabulary terms. Other changes such as splits/merges
can be considered as additions/ deletions processes.</p>
      <p>We clari ed the percentage of changes occurred on the examined
vocabularies that caused by the external vocabularies they depend on establishing their
vocabularies, and which vocabularies are depend on their terms on establishing
and evolving the vocabulary. All those analyses are useful for ontology engineers
when they are establishing a new ontology or updating an existing one by
having a clear idea about dependencies and relations between vocabularies to choose
vocabularies terms that meet their needs.</p>
      <p>The remainder of the paper is organized as follows: In Section 2, we present
and discuss related work. We present our methodology for analysing vocabularies
in Section 3. In Section 4 we give an overview for the examined vocabularies. In
Section 5 we make a discussion of vocabularies evolution. Conclusion and future
work in presented in Section 6.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <p>
        Current research focused on measuring what are the changes in the LOD cloud,
but not how they are changed. For example, Dividino et al. [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] proposed a
framework to measure the evolution of the data in a dataset over time. They applied
their dynamics functions on 84 weekly snapshots from DyLDO dataset, which
results a number that can be used to represent how data in the dataset are
evolved. Furthermore, Dividino et al. [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] analysed the usage of vocabularies on
the LOD cloud over time and observed how they are changed according to their
usage. They analysed the combination of classes and properties that describe a
resource and applied their analysis on a dataset by taking 53 weekly snapshots
from DyLDO dataset. Over six months, Kfer et al. [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] observed the documents
retrieved from DyLDO dataset they created. They analysed those documents
using di erent factors, their lifespan, the availability of those documents and their
change rate. Also, they analysed the RDF content that are frequently changed
(added or removed). Finally they observed how links between documents are
evolved overtime (either increased or decreased). To keep track what are the
changes happened when publishing a new version of ontology, Neubert [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]
compared the SKOS vocabulary versions les and found the di erences between
them and then stored those di erences into two separated named graphs;
insertions and deletions. Then he used the version history graph to link the insertion
and deletion graphs with vocabulary versions les. Walk et al. [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] studied and
analysed the user behaviour during editing ontologies to support the ontologies'
editing tools. They derived nine hypotheses to describe the users' change
behaviour, and then applied those hypotheses on four real-world ontology projects.
They found that the hierarchical structure hypothesis had the highest in uence
on the editing behaviourr. Furthermore, Walk et al. [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] analysed the collection of
actions in the change-logs les that made by users in the collaborative ontology
engineering environment, to increase the quality of ontologies they design. They
applied Markov chains into the International Classi cation of Diseases (Revision
11) dataset. Zablith et al. [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] published a survey presenting an ontology
evolution cycle, trying to gather researchers' work in ontology evolution community.
Furthermore, they analyse the di erent approaches of each stage in the ontology
evolution process. They suggest to integrate the tools used for ontology
evolution, and share the research in this eld using Web portals, beside sharing some
common use cases that needs to evolve.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Methodology</title>
      <p>
        Schmachtenberg et al.[
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] published a report that provides a detailed statistics
about the LOD cloud. They analysed a subset of the Linked Data Web. The
subset is based on crawling seed URIs from the datahub.io1 dataset, BTC 2012
dataset2, and public-lod@w3.org3 mailing list.
      </p>
      <p>
        Based on their report, we selected the top used vocabularies in their crawled
subset of the LOD Cloud and have di erent available versions to download. Our
methodology can be expressed in the following steps:
{ Selection criteria: We chose the vocabularies that have been used in more
than ve datasets (0.49% of 1014 datasets used in the statistics [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]).
{ Exclusion: We excluded the vocabularies that have been used in less than
ve datasets because they are rarely used as shown in the previous
statistics. Furthermore, we exclude some of the upper level ontologies like RDF,
RDFS and OWL. For RDF and RDFS there are only one downloadable
version for each of them. For OWL vocabulary, we excluded it because all
our selected vocabularies and in all their versions use the same entities from
it, and they are ve Annotation properties (backwardCompatibleWith,
deprecated, incompatibleWith, priorVersion, and versionInfo) beside "Thing"
class. Therefore, we decided not to include them in this paper.
{ Selection result: Based on our criteria in selecting the vocabularies, we
examined 62 vocabularies that have been used in more than ve datasets.
We found twelve vocabularies from the 62 vocabularies had more than one
version and can be downloaded. We tried to collect vocabularies that cover
all the topical domains in the LOD Cloud.
{ Downloading: We downloaded the available versions for the selected
vocabularies using Linked Open Vocabularies (LOV) observatory4 and the o cial
1http://datahub.io/dataset?tags=lod
2http://km.aifb.kit.edu/projects/btc-2012/
3http://lists.w3.org/Archives/Public/public-lod/
4http://lov.okfn.org/dataset/lov
sites of some vocabularies. By using Protege 4.3.01, we extracted the di
erences between each version to capture the evolution of those vocabularies.
Table 1 shows the number of downloaded versions for each vocabulary, the
period from the rst to latest version for those vocabularies, the evolution
duration in years/months, and the average number of changes per year.
{ Analysing: We analysed the changes that occurred in di erent versions of
the vocabularies (creating, deleting, modifying, or renaming). Those changes
can be on classes, properties (with di erent types), datatypes, or individuals.
We analysed the changes using di erent classi cations. First, we count the
number of changes for each type of entities, i.e., classes and properties.
Subsequently, we observed the percentage of internal changes versus external
changes. Internal changes are changes that occurred on the entities (classes
and properties) that originally introduced and developed by ontology
engineers of the examined vocabulary. On the contrary, external changes are
changes on the vocabularies' entities from other vocabularies that are used
to establish the examined vocabulary.
      </p>
    </sec>
    <sec id="sec-4">
      <title>Overview of the Vocabularies from LOD Cloud</title>
      <p>
        In the following gures and tables, we summarize the statistics of the selected
vocabularies and their di erent versions. According to the 1014 datasets crawled
in the State of the LOD Cloud report (Version 0.4, 08/30/2014) [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], the examined
vocabularies in our study were used in multiple topical domains.
      </p>
      <p>
        Table 2 shows the topical domains for our selected vocabularies. In addition,
we show the percentage of the datasets crawled in [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] that use these
vocabularies. The table shows twelve vocabularies. Please remind that we selected those
vocabularies based on the availability of their versions (if they have) to
download. Any vocabulary that does not have versions, or their previous versions are
not available to download, are excluded from our analysis. We found that 65%
of the 62 examined vocabularies just have one version, and 15% of those 62
vocabularies have more than one version but they are not available to download.
Therefore, we excluded them from our study. In Table 2, we can see that two
vocabularies (FOAF and DCterm) are used in more than 50% of datasets crawled
in [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. In addition, half of the selected vocabularies are classi ed as cross-domain
vocabularies.
Fig 1 represent the total number of each change type, i.e. created, deleted,
modi ed, or renamed classes, object properties, data properties, annotation
properties, for all vocabularies we included in our analysis. From gure 1c, we
can observe that most of the changes are related to the modi cation changes
type, especially in object properties and classes. Also, the second most changes
are the creating changes type, mostly in the annotation properties ( gure 1a).
      </p>
      <p>Table 3 shows the external vocabularies that are used in establishing each
vocabulary in our study. From the external vocabularies listed in this table,
we can note two things: First, there are three vocabularies (FOAF, DCterm and
SWC) stuck on their external vocabularies list that used in establishing their rst
edition until the recent one. Second, we can note that there are two vocabularies
(a) Total number of created entities
(b) Total number of deleted entities
(c) Total number of modi ed entities
(d) Total number of renamed entities
(GN and ORG) have many changes on their external vocabularies list during
their evolution period. GN partially changed its external vocabularies ve times
during six years, and ORG four times during approximately four years.</p>
      <p>The percentage of internal changes compared to external changes in the
vocabularies versions are shown in Table 4. We calculate the total percentage for all
internal changes occurred through the vocabulary evolution overall its versions;
from rst to latest version. We can see that three vocabularies with more than
90% of internal changes (DCterm, GN, and PROV). Furthermore, there is just
one vocabulary (Cube) with a percentage of internal changes less than 50%.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Discussion of Vocabularies Evolution</title>
      <p>We observe that most of the vocabularies if they evolves, most of the changes
occurred on annotation properties for more explanations (metadata) to clarify
classes, properties or individuals. This can be expressed as a need for more
clearance for terms, especially between the early versions. Another observation
is that vocabularies are highly static w.r.t. the number of external vocabularies
used to establish and develop them. We can conclude that the topical domains
are fully covered with terms in the existing vocabularies, and if there is a need
of change, ontology engineers can modify the existing vocabularies.</p>
      <p>In most of the examined vocabularies, the terms that changed were internal
terms, i.e. the terms that were created for the examined ontology by ontology
engineers, not the terms that are imported from external vocabularies during
establishing or evolving the vocabulary. On the other hand, some vocabularies
such as Cube, bibo, DCAT, and ORG are changed because some changes in their
external vocabularies occurred. For example, in the Cube vocabulary, the
percentage of the internal change is 43%, and the remaining percentage of change
is caused by other external terms over its four published versions of this
vocabulary. The rst version from the Cube vocabulary was published in 27.11.2010,
and some of its external vocabularies are DCterm and FOAF. DCterm
published its latest version in 14.06.2012, before the next version of Cube (was in
02.03.2013) was published.</p>
      <p>Another example is the bibo ontology. Analysing ten versions from that
vocabulary, we conclude that 35% of changes are caused by external vocabularies.
bibo uses many external vocabularies such as DCterm and SKOS, and both of
them had versions between the two published versions of bibo ( rst version was
in 03.06.2008 and the latest version was in 04.11.2009).</p>
      <p>Vocabularies such as DCterm, GN, and PROV are dependent on their own
terms, and most of the changes are made on those terms. For example, in the
GN ontology, we analysed eleven versions, and the percentage of internal changes
are 97%, which means that when the ontology engineers needs to change, they
change their own terms. Another observation in DCterm and PROV vocabularies
is that their external vocabularies as shown in Table 4 are small, and they are
organized as upper level ontologies.</p>
      <p>Cube dcterm/foaf/owl/rdf/rdfs/</p>
      <p>scovo/skos/void/xml/xsd
bibo Address/dc/dcterm/event/foaf/owl/rdf/rdfs/
skos/time/vann/vs/ wgs84 pos/xml/xsd
Event/foaf/ns/owl prism/rdf/rdfs/schema/
skos/dcterm/vann/xml/xsd
DCAT dcterm/owl/rdf/rdfs/xml/xsd
dc/dcterm/dctype/foaf/owl/rdf/rdfs/
schema/skos/vcard/vann/voaf/xml/xsd
GN skos/owl/rdf/rdfs/xml/xsd</p>
      <p>The vocabularies in our study are di erent in their evolution period and the
number of versions published so far. In our study, we are trying to analyse the
evolution behaviour for those vocabularies. Some vocabularies such as FOAF,
SKOS, GN, and ORG have many versions; 10, 8, 11, and 10, respectively. GN
has eleven versions in the period from 05.10.2006 to 29.10.2012, and ORG have
ten versions in the period from 06.06.2010 to 12.04.2014. We think this large
number of versions is caused by their topical domain they are used in, especially
in social web ontologies.</p>
      <p>The last observation is that the vocabularies used in publications, geographic,
social web, and government topical domains have the largest number of changes,
this is obvious from Fig 1 using SKOS, GN, SWC, FOAF, and PROV
vocabularies number of changes. For example, PROV added 29 classes and 62 object
properties, and modi ed 51 classes and 80 object properties during its evolution
period (Three versions published from 03.05.2012 to 11.01.2015). Another
example is SWC, the ontology engineers modi ed 110 classes and 25 object properties
through the three published versions.
6</p>
    </sec>
    <sec id="sec-6">
      <title>Conclusion and Future Work</title>
      <p>Analysing the change behaviour of vocabularies can help ontology engineers
in establishing new ontologies and evolve existing ones. This study can give a
clear view about ontology dependencies (External vocabularies), and the relation
between change in ontologies and their external ones.</p>
      <p>Changes are mostly made for internal terms if they compared by external
terms percentage. Furthermore, most of the vocabularies have a static number
of external ontologies to depend on during the evolution period, and if they add
or remove some vocabularies, the number of those additions and deletions is
small.</p>
      <p>Topical domains such as publications, geographic, social web, and government
have a high percentage for change if they compared with other domains.</p>
      <p>As a future work, we will analyse the usage of vocabularies' in the Dynamic
Linked Data Observatory (DyLDO) dataset. We will select the vocabularies
that have a version before and after a speci c snapshot of a DyLDO crawl (the
rst snapshot was in 06.05.2012, the latest is until today). Furthermore, we
will include the vocabularies not considered so far in this study. Establishing
a framework for ontologies' concepts history tracking system will be useful for
ontology engineers.</p>
      <p>Acknowledgement This work was supported by the EU's Horizon 2020
programme under grant agreement H2020-693092 MOVING.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Eder</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Koncilia</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          (
          <year>2004</year>
          , January).
          <article-title>Modelling changes in ontologies</article-title>
          .
          <source>In On the Move to Meaningful Internet Systems</source>
          <year>2004</year>
          :
          <article-title>OTM 2004 Workshops</article-title>
          (pp.
          <fpage>662</fpage>
          -
          <lpage>673</lpage>
          ). Springer Berlin Heidelberg.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Dividino</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gottron</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Scherp</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Grner</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          (
          <year>2014</year>
          ).
          <article-title>From Changes to Dynamics: Dynamics Analysis of Linked Open Data Sources</article-title>
          .
          <source>In PROFILES14: Proceedings of the Workshop on Dataset Pro Iling and Federated Search for Linked Data.</source>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Dividino</surname>
            ,
            <given-names>R. Q.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Scherp</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grner</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Grotton</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          (
          <year>2013</year>
          ).
          <article-title>Change-a-LOD: Does the Schema on the Linked Data Cloud Change or Not?</article-title>
          .
          <source>In COLD.</source>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Kfer</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Abdelrahman</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Umbrich</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , OByrne,
          <string-name>
            <given-names>P.</given-names>
            , &amp;
            <surname>Hogan</surname>
          </string-name>
          ,
          <string-name>
            <surname>A.</surname>
          </string-name>
          (
          <year>2013</year>
          ).
          <article-title>Observing linked data dynamics</article-title>
          .
          <source>In The Semantic Web: Semantics and Big Data</source>
          (pp.
          <fpage>213</fpage>
          -
          <lpage>227</lpage>
          ). Spring-er Berlin Heidelberg.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Klein</surname>
            ,
            <given-names>M. C.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Fensel</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          (
          <year>2001</year>
          ,
          <article-title>July)</article-title>
          .
          <article-title>Ontology versioning on the Semantic Web</article-title>
          . In SWWS (pp.
          <fpage>75</fpage>
          -
          <lpage>91</lpage>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Neubert</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          (
          <year>2015</year>
          )
          <article-title>: Leveraging SKOS to trace the overhaul of the STW Thesaurus for Eco-nomics</article-title>
          ,
          <source>In: Proceedings of the International Conference on Dublin Coreand Metadata Appli-cations</source>
          <year>2015</year>
          ,
          <string-name>
            <given-names>So</given-names>
            <surname>Paulo</surname>
          </string-name>
          (Forthcoming)
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Schmachtenberg</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bizer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Paulheim</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          (
          <year>2014</year>
          ).
          <article-title>State of the LOD Cloud 2014</article-title>
          . URL: http://linkeddatacatalog. dws. informatik. unimannheim. de/state.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Walk</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Singer</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Noboa</surname>
            ,
            <given-names>L. E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tudorache</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Musen</surname>
            ,
            <given-names>M. A.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Strohmaier</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          (
          <year>2015</year>
          ).
          <article-title>Understanding how users edit ontologies: comparing hypotheses about four real-world pro-jects</article-title>
          .
          <source>In The Semantic WebISWC</source>
          <year>2015</year>
          (pp.
          <fpage>551</fpage>
          -
          <lpage>568</lpage>
          ). Springer International Publishing.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Walk</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Singer</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Strohmaier</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Helic</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Noy</surname>
            ,
            <given-names>N. F.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Musen</surname>
            ,
            <given-names>M. A.</given-names>
          </string-name>
          (
          <year>2015</year>
          ).
          <article-title>How to apply Markov chains for modeling sequential edit patterns in collaborative ontology-engineering projects</article-title>
          .
          <source>International Journal of Human-Computer Studies</source>
          ,
          <volume>84</volume>
          ,
          <fpage>51</fpage>
          -
          <lpage>66</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Zablith</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Antoniou</surname>
          </string-name>
          , G.,
          <string-name>
            <surname>d'Aquin</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Flouris</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kondylakis</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Motta</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          , ... &amp;
          <string-name>
            <surname>Sabou</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          (
          <year>2015</year>
          ).
          <article-title>Ontology evolution: a process-centric survey</article-title>
          .
          <source>The Knowledge Engineering Review</source>
          ,
          <volume>30</volume>
          (
          <issue>01</issue>
          ),
          <fpage>45</fpage>
          -
          <lpage>75</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>