<!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>Applying the Concept of Knowledge Blockchains to Ontologies</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Copyright held by the author(s). In A. Martin, K. Hinkelmann, A. Gerber</institution>
          ,
          <addr-line>D. Lenat, F. van Harmelen, P. Clark (Eds.)</addr-line>
          ,
          <institution>Proceedings of the AAAI 2019 Spring Symposium on Combining Machine Learning with Knowledge Engineering (AAAI-MAKE 2019). Stanford University</institution>
          ,
          <addr-line>Palo Alto, California</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Hans-Georg Fill Digitalization and Information Systems Group Department Informatics - University of Fribourg Boulevard de Pe ́rolles 90</institution>
          ,
          <addr-line>1700 Fribourg</addr-line>
          ,
          <country country="CH">Switzerland</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>In this position paper we would like to incite a discussion on how the concept of Knowledge Blockchains can be applied to ontologies. Knowledge Blockchains revert to blockchain technologies for enabling a transparent monitoring of knowledge evolution, for tracking the provenance of knowledge, for establishing delegation schemes, and for ensuring the existence of patterns in formal conceptualizations using zeroknowledge proofs. Based on their original application to enterprise models, we discuss which benefits arise from using the concept for ontologies. The paper concludes by outlining further research in this direction.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        The use of blockchains is currently discussed for many
application fields
        <xref ref-type="bibr" rid="ref15">(Iansiti and Lakhani 2017)</xref>
        . Based on the
success of Bitcoin and Ethereum, initiatives for
investigating potential use cases have been launched in industry as
well as in academia. Although the underlying technologies
have been available for quite some time, the combination
of a decentralized, tamper-proof storage together with
trustworthy and equally decentralized consensus mechanisms for
transactions has the potential to realize new forms of
collaboration and business models
        <xref ref-type="bibr" rid="ref15 ref2">(Aste, Tasca, and Di Matteo
2017)</xref>
        . Whereas public blockchains, which do not regulate
the access to the stored information, have contributed to the
prominence of the technology, many use cases found in
industry today focus on so-called permissioned blockchains,
e.g.
        <xref ref-type="bibr" rid="ref1">(Androulaki et al. 2018)</xref>
        . For this type of blockchains,
the aspect of decentralized storage and automated
consensus mechanisms is maintained whereas the access to the
blockchain is restricted to authenticated users. Permissioned
blockchains thus enable interactions between actors who do
not fully trust each other but still pursue common goals.
Due to the required identification of the participants, their
transactions can be traced back to physical persons thus
easing also legal compliance requirements such as
Know-YourCustomer (KYC) and Anti-Money-Laundering (AML)
principles
        <xref ref-type="bibr" rid="ref11 ref19">(Mo¨ser, Bo¨hme, and Breuker 2013)</xref>
        .
      </p>
      <p>
        In a recent publication it has been discussed how these
blockchain technologies can be applied to the domain of
enterprise modeling
        <xref ref-type="bibr" rid="ref8">(Fill and Ha¨rer 2018)</xref>
        . Thereby, the core
idea was to store the knowledge that has been made explicit
in the form of visual conceptual models on a decentralized
blockchain. The goals of this approach denoted as
Knowledge Blockchains are as follows. It shall permit to track who
has contributed which changes in the models and at what
time and how concepts in the models have thus evolved.
Further, the approach permits to establish delegation schemes
so that operations on models can be delegated to other
identities. Finally, the use of zero-knowledge proofs allows to
proof the existence of patterns in models without having to
disclose the content of the models, which is desirable for
sensitive information. In the following this idea is extended
to ontologies, which may be regarded as one type of
enterprise models that stands for a shared, agreed-upon,
formal, and machine-interpretable conceptualization of a
domain
        <xref ref-type="bibr" rid="ref12 ref23">(Fill 2017; Studer, Benjamins, and Fensel 1998)</xref>
        .
      </p>
      <p>The remainder of the paper is organized as follows. At
first, the concept of Knowledge Blockchains is briefly
described. Subsequently, we investigate, which of the
components used for Knowledge Blockchains have already been
discussed in the context of ontologies. Next, we illustrate
how Knowledge Blockchains could be applied to ontologies
and derive finally opportunities for further research
activities.</p>
    </sec>
    <sec id="sec-2">
      <title>Knowledge Blockchains</title>
      <p>
        The concept of Knowledge Blockchain has been first
presented in a recent publication by
        <xref ref-type="bibr" rid="ref8">(Fill and Ha¨rer 2018)</xref>
        . The
main goal of Knowledge Blockchains is to store and process
the knowledge that is made explicit in the form of various
types of enterprise models using blockchain technologies.
Enterprise models in this context are understood as
schemabased information structures that are typically represented
in a visual format and are specified in a semi-formal or
formal manner
        <xref ref-type="bibr" rid="ref17 ref5">(Bork and Fill 2014)</xref>
        . Through the
decentralized nature of blockchains, knowledge can thus be easily
distributed. Based on the digital signatures used for signing
information on a blockchain, it can be further traced who
has contributed what to the enterprise models and at what
time. In the case of permissioned blockchains this can be
restricted to authenticated users and model information may
even be encrypted to prevent unauthorized access.
      </p>
      <p>For storing information about the status of models,
Knowledge Blockchains use a Merkle-tree-based structure
together with the files that contain the model information
in a format that can be interpreted by modeling tools. For
this purpose, the attribute values of every model entity are
hashed. Furthermore, all model entities are assigned a
universally unique identifier (UUID) which is also hashed. The
UUID permits to identify any model element that is
created independently from other elements in decentrally stored
copies of the blockchain. The concatentation of the two
resulting hashes is hashed again and the resulting hash
further concatenated with hashes resulting from other model
entities and hashed until arriving at one single hash value,
i.e. the Merkle root. The use of Merkle trees permits on the
one hand to easily identify any changes that have occurred
in the models. At the same time it enables the execution of
so-called zero-knowledge proofs. Thereby, it can be proven
that certain information parts are contained in an enterprise
model without revealing the content of the model. To
accomplish this, the information parts to be searched for in the
model have to be hashed in the same way as described
before. Subsequently, the hash values can be compared with
the hash values in the Merkle tree of the models.</p>
      <p>In addition to the model information, Knowledge
Blockchains also store information for permission models.
These specify the rights for creating, modifying or deleting
model information based on the digital signatures of actors
contributing to the Knowledge Blockchain. In addition, they
permit to delegate these rights to other actors. Permission
models are hashed in the same way as described above.</p>
      <p>
        The block header in Knowledge Blockchains then
contains essentially the Merkle root hashes for the enterprise
models and the permission models, the model and
permission models themeselves, a timestamp, and the header
signature. In the case of non-permissioned blockchains, a nonce
can be added to the header as well. In the course of the
mining it is checked whether the permissions specified in
the previous permission model permit the intended
operations. The approach has been realized as a prototype using
the ADOxx metamodeling platform
        <xref ref-type="bibr" rid="ref11">(Fill and Karagiannis
2013)</xref>
        . For details on the mining algorithm and the
implementation we refer to
        <xref ref-type="bibr" rid="ref8">(Fill and Ha¨rer 2018)</xref>
        .
      </p>
    </sec>
    <sec id="sec-3">
      <title>Related Work</title>
      <p>In the following we review approaches in the area of
ontologies that are similar to the concepts used for Knowledge
Blockchains. This will be followed by a discussion on how
ontologies may be represented in Knowledge Blockchains.</p>
      <p>
        Due to their nature as shared conceptualizations,
ontologies are typically created in multi-user environments. This
has traditionally been accomplished using platforms such as
Stanford Prote´ge´ or ContentCVS that permit the
collaborative editing of ontologies and the tracking of changes
        <xref ref-type="bibr" rid="ref16 ref24">(Tudorache et al. 2008; Jime´nez-Ruiz et al. 2009)</xref>
        . In the
according change records, the metadata on ontology changes
is stored. This includes for example information about which
user performed a change, a timestamp, or the entities on
which the changes were performed
        <xref ref-type="bibr" rid="ref28">(Walk et al. 2015)</xref>
        .
Today, this is accomplished using web-based environments,
which eases the technical realization of multi-user
collaboration platforms
        <xref ref-type="bibr" rid="ref13">(Horridge et al. 2018)</xref>
        . The availability of
the data about changes in ontologies is essential for
analyzing their evolution and deriving according strategies, e.g. for
validating changes and their impacts
        <xref ref-type="bibr" rid="ref29">(Zablith et al. 2013)</xref>
        .
      </p>
      <p>
        The use of digital signatures for signing ontologies
has been discussed for RDF graphs, e.g.
        <xref ref-type="bibr" rid="ref6">(Carroll 2003)</xref>
        .
Thereby, it can be verified who has created or modified a
certain RDF document, which is essential to trace its
provenance. Closely related to this is the hashing and
subsequent signing of XML documents for determining which
parts of an XML document have been updated
        <xref ref-type="bibr" rid="ref18 ref3">(Maruyama,
Tamura, and Uramoto 2000; Bartel et al. 2013)</xref>
        . This
approach may also be extended by using one-way hash
functions and Merkle trees for applying zero-knowledge proofs
to XML documents
        <xref ref-type="bibr" rid="ref7">(Devanbu et al. 2001)</xref>
        . Thereby, the
existence of information in XML documents can be proven
without revealing their content. The same procedures could
be used for many ontology formats that are based on XML.
      </p>
      <p>
        Another direction for the unique identification of
resources has been proposed in
        <xref ref-type="bibr" rid="ref17 ref5">(Kuhn and Dumontier 2014)</xref>
        .
Here, cryptographic hash values are included in unique
resource identifiers (URIs) for enabling the identification and
verification of resources or parts thereof on the web. As the
cryptographic hash value is directly added to the URI, it does
not require any additional data structures but can be easily
processed. This approach thus does not regard XML
documents or ontologies as a whole but is able to identify single
resources.
      </p>
      <p>
        In the context of Semantic Web, the use of blockchains
has been proposed by Iancu and Sandu to realize the trust
layer in the traditional semantic web stack
        <xref ref-type="bibr" rid="ref10 ref14">(Iancu and Sandu
2016)</xref>
        . However, in their paper they just store the entire
ontology information as a file on the Openchain blockchain
without making use of the typical data structures used for
blockchains in the form of hash trees. Similarly, an
approach for semantic internet of things reverts to the
Hyperledger infrastructure for storing ontology information on a
blockchain
        <xref ref-type="bibr" rid="ref20">(Ruta et al. 2017)</xref>
        . By extending the underlying
APIs, semantic matchmaking and reasoning could thus be
added to a blockchain-based application.
      </p>
      <p>
        One of the most recent developments concerning the
integration of ontologies and blockchains is the proposal of
GraphChain
        <xref ref-type="bibr" rid="ref21">(Sopek et al. 2018)</xref>
        . In this work, the authors
propose the creation of a linked chain of RDF graphs based
on a computation of RDF digests with SHA-256 hash
functions. The RDF digests are then stored in triple stores and
the changes broadcasted to other nodes. Although the data
structure strongly resembles the one in other blockchain
approaches, consensus mechanisms or chain update strategies
were not discussed.
      </p>
      <p>In summary, previous approaches have already discussed
the integration of ontologies and technologies necessary
for blockchains. This concerns in particular approaches for
hashing and signing RDF graphs and the identification of
ontology resources. What is missing so far is the use of
blockchain mechanisms such as consensus protocols
re1..n</p>
      <p>Class
- UUID : UUID
- Name : String
- containedInModel : UUID
- isClass : boolean = true</p>
      <p>owl:Class
- IRI : IRI
- SubClassOf : IRI+
- SubClassOfUUID : UUID+
1..n</p>
      <p>Relationclass
- UUID : UUID
- Name : String
- from : UUID
- to : UUID
- containedInModel : UUID
- isRelationClass : boolean =
true</p>
      <p>OWL Object Property
- domain : IRI+
- range : IRI+
- domainUUID : UUID+
- rangeUUID : UUID+
spectively mining algorithms for automatically determining
whether concepts should be added. Furthermore, the
multiuser-oriented design of ontologies and zero-knowledge
proofs has so far not been yet considered in this context.</p>
    </sec>
    <sec id="sec-4">
      <title>Ontologies and Knowledge Blockchains</title>
      <p>Based on the insights gained in the previous two sections
it will now be discussed how the concept of Knowledge
Blockchains could contribute to the domain of ontologies.
For this purpose, it first needs to be answered how ontologies
can be represented as models according to the approach of
Knowledge Blockchains. As shown in the upper part of
Figure 1, Knowledge Blockchains extend the meta-metamodel
constructs model type, class, and relationclass with UUID
attributes.</p>
      <p>Extended Meta-Metamodel Constructs
1..n</p>
      <p>Model type
- UUID : UUID
- Name : String
- isModel : boolean = true
1..n
Subset
of Ontology
Model Data</p>
      <p>H
UUID</p>
      <p>H</p>
      <p>H
Attribute</p>
      <p>Data</p>
      <p>H</p>
      <p>Model-Merkle-Root</p>
      <p>H</p>
      <p>H</p>
      <p>H
UUID</p>
      <p>H
Attribute</p>
      <p>Data
…
…</p>
      <p>H Hash-Function applied to Child-Node(s)</p>
      <p>With the thus extended attributes of the ontology model
elements, the hash values for the UUID of every element
as inherited from the meta-metamodel - and the hash value
of the attribute data can be represented in a Merkle tree as
shown in Figure 2. This will be the basis for conducting
zero-knowledge proofs on the contents of the ontology.</p>
      <p>Based on these data structures we will regard four areas
of Knowledge Blockchains that could be beneficial for
ontologies and that are not yet covered by previous approaches.
These are: the monitoring of the evolution of ontologies and
the tracking of the provenance of concepts, the use of
permission and delegation schemes for the distributed design of
ontologies, and the use of zero-knowledge proofs.</p>
      <sec id="sec-4-1">
        <title>Monitoring Ontology Evolution and Tracking the</title>
      </sec>
      <sec id="sec-4-2">
        <title>Provenance of Concepts</title>
        <p>Due to their nature as immutable and distributed ledgers,
blockchains seem well suited to act as a foundation for
monitoring the evolution of ontologies and for tracking the
provenance of the contained concepts. With the approach
of Knowledge Blockchains, this can be accomplished in the
folllowing ways. As every proposal for a modification in a
Knowledge Blockchain must be digitally signed, it can be
tracked who added which change and at what time. In case
of qualified electronic signatures1, these even refer to actual
physical persons including all legal responsibilities. By
using UUIDs for identifying elements in the ontology models,
even different versions of the same IRIs may be stored so
that alternative proposals for the realization of concepts can
be recorded. At the same time, the UUIDs permit to
unambiguously specify a particular version of a conceptualization
and to track over time in the blockchain whether this version
has been changed. For this purpose, the Merkle trees allow
for an efficient identification of changes in ontology models
based on the comparison of the hash values.</p>
        <p>The decentralized nature of a blockchain further requires
to establish so-called mining algorithms that decide upon the
1See for example the eIDAS regulation in the European Union:
https://eur-lex.europa.eu/legal-content/
EN/TXT/HTML/?uri=CELEX:32014R0910&amp;from=EN#
d1e791-73-1.</p>
        <p>OWL Ontology Model
- IRI : IRI</p>
        <p>Extended OWL Ontology Model Type Constructs</p>
        <p>
          From these meta-metamodel constructs we can derive the
elements for OWL ontologies as shown exemplarily in the
lower part of the figure. The representation of OWL
ontologies in this way has been described earlier in more detail,
e.g.
          <xref ref-type="bibr" rid="ref12">(Fill 2017)</xref>
          . However, as Knowledge Blockchains make
use of UUIDs for identifying elements, the according
reference attributes required in OWL ontologies have to be
extended in this way as well. This is illustrated in the figure for
the SubClassOf as well as the domain and range attributes.
Instead of just using lists of IRIs (denoted as IRI+),
Knowledge Blockchains would require lists of UUIDs in addition
to take into account that several versions may exist for an
element with the same IRI, e.g. due to an evolution of a class.
inclusion of new blocks. Here, the mining algorithm
originally proposed for Knowledge Blockchains could be
extended for the case of ontologies to conduct certain sanity
checks on the ontology before adding a block, e.g. to filter
out changes that could lead to an inherent or inconsistent
ontology or that do not satify certain domain or
applicationspecific constraints, cf.
          <xref ref-type="bibr" rid="ref29">(Zablith et al. 2013)</xref>
          .
        </p>
      </sec>
      <sec id="sec-4-3">
        <title>Establishing Permission and Delegation Schemes</title>
        <p>
          In contrast to other approaches for aligning blockchains and
ontologies, Knowledge Blockchains offer a mechanism for
specifying who has which kind of access to which parts of
a model - for details on these permission models we refer
to
          <xref ref-type="bibr" rid="ref8">(Fill and Ha¨rer 2018)</xref>
          . This means, it can be defined who
can edit which parts of an ontology as well as who is
allowed to delegate rights to other persons. In this way, a chain
of trust between different actors can be established. This
could subsequently be aligned with previous approaches for
defining ontologies that rely on multiple parties for deciding
about the inclusion of concepts, e.g. (
          <xref ref-type="bibr" rid="ref26">Vrandecˇic´ et al. 2005</xref>
          ).
        </p>
      </sec>
      <sec id="sec-4-4">
        <title>Using Zero-Knowledge Proofs</title>
        <p>Zero-Knowledge proofs are typically used in blockchains
for efficiently verifying the existence of information or
transactions in a blockchain without having to reveal the
actual data. For example, in cryptocurrency blockchains, this
mechanism may be used to check that a particular
transaction has been accomplished and is thus part of the current
branch of the blockchain. The actual transaction data does
however not need to be disclosed.</p>
        <p>In Knowledge Blockchains, zero-knowledge proofs can
be used to verify that certain patterns exist in models
without having to give away the actual model data. This may be
similarly applied to ontologies, e.g. to prove to an external
actor that a confidential ontology contains certain elements
without having to disclose the ontology. A use case for this
could be to ensure the compliance of an ontology to legal
regulations in a domain, e.g. that classes describing persons
actually do require the specification of a social security
number.</p>
        <p>http://www.unifr.ch/ : OWL Ontology Model
IRI : IRI = http://www.unifr.ch/
UUID : UUID = e3874776-3398-42ec-bdf7-4c4cc6f2f646
Name : String = http://www.unifr.ch/
isModel : boolean = true</p>
        <p>Animal : owl:Class
IRI : IRI = http://www.unifr.ch/#Animal
SubClassOf : IRI+ = http://www.unifr.ch/#Thing
SubClassOfUUID : UUID+ = 77965e01-3aef-490b-8875-5760d28659a9
UUID : UUID = 7e381016-810a-49c5-aacf-662353843940
Name : String = Animal
containedInModel : UUID = e3874776-3398-42ec-bdf7-4c4cc6f2f646
isClass : boolean = true</p>
        <p>For illustrating the basic working of this mechanism we
present example instances of an OWL ontology model in</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Opportunities for Further Research</title>
      <p>
        Although this position paper only intends to incite a
discussion on using the approach of Knowledge Blockchains for
ontologies, we can derive several opportunities for further
research. First, it needs to be investigated in detail which
data structures are most adequate for the representation of
ontologies in the context of blockchains, cf.
        <xref ref-type="bibr" rid="ref10 ref14">(Fill and
Johannsen 2016)</xref>
        . This is closely related to the application of
zero-knowledge proofs and which advantages can be gained
from their application. In this respect, additional benefits
may arise from a combination of zero-knowledge proofs and
reasoning, e.g. to automatically expand the scope of matches
when searching for a concept in a Merkle tree based on
information derived throuh reasoning.
      </p>
      <p>
        Second, the use of UUIDs may not be an optimal
solution for ontologies although they provide several benefits in
terms of a distributed and thus independent creation of
elements. For this purpose it would be a next step to evaluate
whether the approach described by
        <xref ref-type="bibr" rid="ref17 ref5">(Kuhn and Dumontier
2014)</xref>
        for Trusty URIs could be used instead.
      </p>
      <p>Third, for realizing the application of Knowledge
Blockchains to ontologies, existing editors either from the
area of ontologies or conceptual modeling would need to be
adapted. In particular, it needs to be evaluated how the
requirements for a multi-user-based editing of ontologies can
be optimally aligned with the concept of permission
models. In the current conception of permission models only the
level of model elements is considered. As a lot of essential
information in ontologies is stored in the level of attributes,
it may need to be taken into account to expand the
permission and delegation specification to attributes.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <surname>Androulaki</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Barger</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Bortnikov</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Cachin</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Christidis</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Caro</surname>
            ,
            <given-names>A. D.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Enyeart</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Ferris</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Laventman</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ; Manevich,
          <string-name>
            <given-names>Y.</given-names>
            ;
            <surname>Muralidharan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            ;
            <surname>Murthy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            ;
            <surname>Nguyen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            ;
            <surname>Sethi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ;
            <surname>Singh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            ;
            <surname>Smith</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            ;
            <surname>Sorniotti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ;
            <surname>Stathakopoulou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            ;
            <surname>Cocco</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. W.</given-names>
            ; and
            <surname>Yellick</surname>
          </string-name>
          ,
          <string-name>
            <surname>J.</surname>
          </string-name>
          <year>2018</year>
          .
          <article-title>Hyperledger fabric: a distributed operating system for permissioned blockchains</article-title>
          .
          <source>In Proceedings of 13th EuroSys Conf</source>
          .,
          <fpage>1</fpage>
          -
          <lpage>15</lpage>
          . ACM.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <string-name>
            <surname>Aste</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Tasca</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ; and
          <string-name>
            <given-names>Di</given-names>
            <surname>Matteo</surname>
          </string-name>
          ,
          <string-name>
            <surname>T.</surname>
          </string-name>
          <year>2017</year>
          .
          <article-title>Blockchain Technologies: The Foreseeable Impact on Society and Industry</article-title>
          . IEEE Computer (September):
          <fpage>18</fpage>
          -
          <lpage>28</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <string-name>
            <surname>Bartel</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Boyer</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Fox</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>LaMacchia</surname>
          </string-name>
          , B.; and
          <string-name>
            <surname>Simon</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <year>2013</year>
          .
          <article-title>XML Signature Syntax</article-title>
          and
          <source>Processing Version 1.1. Report, W3C Recommendation.</source>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          https://www.w3.org/TR/xmldsig-core/ (accessed 2018-
          <volume>11</volume>
          - 02).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <string-name>
            <surname>Bork</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Fill</surname>
          </string-name>
          , H.-G.
          <year>2014</year>
          .
          <article-title>Formal Aspects of Enterprise Modeling Methods: A Comparison Framework</article-title>
          .
          <source>In 47th Hawaii International Conference on System Sciences</source>
          ,
          <fpage>3400</fpage>
          -
          <lpage>3409</lpage>
          . IEEE.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <string-name>
            <surname>Carroll</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <year>2003</year>
          .
          <article-title>Signing RDF Graphs</article-title>
          . In Fensel, D.;
          <string-name>
            <surname>Sycara</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ; and
          <string-name>
            <surname>Mylopoulos</surname>
          </string-name>
          , J., eds.,
          <source>International Semantic Web Conference</source>
          , volume LNCS
          <volume>2870</volume>
          ,
          <fpage>369</fpage>
          -
          <lpage>384</lpage>
          . Springer.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          <string-name>
            <surname>Devanbu</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Gertz</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Kwong</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Martel</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Nuckolls</surname>
          </string-name>
          , G.; and
          <string-name>
            <surname>Stubblebine</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <year>2001</year>
          .
          <article-title>Flexible authentication of xml documents</article-title>
          .
          <source>In 8th ACM conference on Computer and Communications Security</source>
          ,
          <fpage>136</fpage>
          -
          <lpage>145</lpage>
          . ACM.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          <string-name>
            <surname>Fill</surname>
            , H.-G., and Ha¨rer,
            <given-names>F.</given-names>
          </string-name>
          <year>2018</year>
          .
          <article-title>Knowledge Blockchains: Applying Blockchain Technologies to Enterprise Modeling</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          <source>In 51st Hawaiian International Conference on System Sciences</source>
          ,
          <fpage>4045</fpage>
          -
          <lpage>4054</lpage>
          . AIS.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          <string-name>
            <surname>Fill</surname>
          </string-name>
          , H.-G., and
          <string-name>
            <surname>Johannsen</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          <year>2016</year>
          .
          <article-title>A Knowledge Perspective on Big Data by Joining Enterprise Modeling and Data Analyses</article-title>
          . In IEEE HICSS'
          <year>2016</year>
          . IEEE.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          <string-name>
            <surname>Fill</surname>
          </string-name>
          , H.-G., and
          <string-name>
            <surname>Karagiannis</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <year>2013</year>
          .
          <article-title>On the Conceptualisation of Modelling Methods Using the ADOxx Meta Modelling Platform</article-title>
          .
          <source>Enterprise Modelling and Information Systems Architecture</source>
          <volume>8</volume>
          (
          <issue>1</issue>
          ):
          <fpage>4</fpage>
          -
          <lpage>25</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          <string-name>
            <surname>Fill</surname>
          </string-name>
          , H.-G.
          <year>2017</year>
          .
          <article-title>SeMFIS: A Flexible Engineering Platform for Semantic Annotations of Conceptual Models</article-title>
          .
          <source>Semantic Web</source>
          <volume>8</volume>
          (
          <issue>5</issue>
          ):
          <fpage>747</fpage>
          -
          <lpage>763</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          <string-name>
            <surname>Horridge</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Goncalves</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ; Nyulas,
          <string-name>
            <given-names>C.</given-names>
            ;
            <surname>Tudorache</surname>
          </string-name>
          ,
          <string-name>
            <surname>T.</surname>
          </string-name>
          ; and Musen,
          <string-name>
            <surname>M. A.</surname>
          </string-name>
          <year>2018</year>
          .
          <article-title>WebProte´ge´ 3.0 Collaborative OWL Ontology Engineering in the Cloud</article-title>
          . In Van Erp,
          <string-name>
            <given-names>M.</given-names>
            ;
            <surname>Atre</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ;
            <surname>Lopez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            ;
            <surname>Srinivas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            ; and
            <surname>Fortuna</surname>
          </string-name>
          , C., eds.,
          <source>ISWC 2018 Posters &amp; Demonstrations, Industry and Blue Sky Ideas Tracks</source>
          , volume Vol-
          <volume>2180</volume>
          . CEUR-WS.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          <string-name>
            <surname>Iancu</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Sandu</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          <year>2016</year>
          .
          <article-title>A Cryptographic Approach for Implementing Semantic Webs Trust Layer</article-title>
          . In Bica, I., and
          <string-name>
            <surname>Reyhanitabar</surname>
          </string-name>
          , R., eds.,
          <source>Int. Conf. for Information Technology and Communications</source>
          ,
          <volume>127</volume>
          -
          <fpage>136</fpage>
          . Springer.
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          <string-name>
            <surname>Iansiti</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Lakhani</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <year>2017</year>
          .
          <article-title>The truth about blockchain</article-title>
          .
          <source>Harvard Business Review (JanuaryFebruary)</source>
          :
          <fpage>119</fpage>
          -
          <lpage>127</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          <article-title>Jime´nez-</article-title>
          <string-name>
            <surname>Ruiz</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Grau</surname>
            ,
            <given-names>B. C.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Horrocks</surname>
            ,
            <given-names>I.;</given-names>
          </string-name>
          and Llavori,
          <string-name>
            <surname>R. B.</surname>
          </string-name>
          <year>2009</year>
          .
          <article-title>Building ontologies collaboratively using contentcvs</article-title>
          .
          <source>Description Logics</source>
          <volume>477</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          <string-name>
            <surname>Kuhn</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Dumontier</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <year>2014</year>
          .
          <article-title>Trusty URIs: Verifiable, Immutable, and Permanent Digital Artifacts for Linked Data</article-title>
          . In
          <string-name>
            <surname>Presutti</surname>
          </string-name>
          , V.;
          <string-name>
            <surname>D'Amato</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Gandon</surname>
          </string-name>
          , F.;
          <string-name>
            <surname>D'Aquin</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Staab</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ; and
          <string-name>
            <surname>Tordai</surname>
          </string-name>
          , A., eds.,
          <source>European Semantic Web Conference</source>
          , volume LNCS
          <volume>8465</volume>
          ,
          <fpage>395</fpage>
          -
          <lpage>410</lpage>
          . Springer.
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          <string-name>
            <surname>Maruyama</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Tamura</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ; and
          <string-name>
            <surname>Uramoto</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          <year>2000</year>
          .
          <article-title>Digest Values for DOM (DOMHASH). Report, Internet Engineering Task Force (IETF)</article-title>
          . https://www.ietf.org/rfc/rfc2803.txt (accessed
          <year>2018</year>
          -
          <volume>10</volume>
          -08).
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          <string-name>
            <surname>Mo</surname>
          </string-name>
          ¨ser, M.; Bo¨hme, R.; and
          <string-name>
            <surname>Breuker</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <year>2013</year>
          .
          <article-title>An inquiry into money laundering tools in the Bitcoin ecosystem</article-title>
          .
          <source>In APWG eCrime Researchers Summit</source>
          . IEEE.
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          <string-name>
            <surname>Ruta</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Scioscia</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Ieva</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ; Capurso, G.; and
          <string-name>
            <given-names>Di</given-names>
            <surname>Sciascio</surname>
          </string-name>
          ,
          <string-name>
            <surname>E.</surname>
          </string-name>
          <year>2017</year>
          .
          <article-title>Semantic Blockchain to Improve Scalability in the Internet of Things</article-title>
          .
          <source>Open Journal of Internet of Things</source>
          <volume>3</volume>
          (
          <issue>1</issue>
          ):
          <fpage>46</fpage>
          -
          <lpage>61</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          <string-name>
            <surname>Sopek</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Gradzki</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Kosowski</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Kuzinski</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ; Trojczak, R.; and Trypuz,
          <string-name>
            <surname>R.</surname>
          </string-name>
          <year>2018</year>
          .
          <article-title>GraphChain A Distributed Database with Explicit Semantics and Chained RDF Graphs</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          <source>In World Wide Web Conference - Workshop on Linked Data &amp; Distributed Ledgers</source>
          ,
          <fpage>1171</fpage>
          -
          <lpage>1178</lpage>
          . ACM.
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          <string-name>
            <surname>Studer</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ; Benjamins, R.; and
          <string-name>
            <surname>Fensel</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <year>1998</year>
          .
          <article-title>Knowledge Engineering: Principles and methods</article-title>
          .
          <source>Data &amp; Knowledge Engineering</source>
          <volume>25</volume>
          :
          <fpage>161</fpage>
          -
          <lpage>197</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          <string-name>
            <surname>Tudorache</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Noy</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Tu</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ; and Musen,
          <string-name>
            <surname>M. A.</surname>
          </string-name>
          <year>2008</year>
          .
          <article-title>Supporting Collaborative Ontology Development in Prote´ge´.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          <source>In International Semantic Web Conference, volume LNCS 5318</source>
          . Springer.
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          <string-name>
            <surname>Vrandecˇic´</surname>
          </string-name>
          , D.;
          <string-name>
            <surname>Pinto</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Tempich</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ; and Sure,
          <string-name>
            <surname>Y.</surname>
          </string-name>
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          <article-title>The diligent knowledge processes</article-title>
          .
          <source>Journal of Knowledge Management</source>
          <volume>9</volume>
          (
          <issue>5</issue>
          ):
          <fpage>85</fpage>
          -
          <lpage>96</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          <string-name>
            <surname>Walk</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ; Singer,
          <string-name>
            <given-names>P.</given-names>
            ;
            <surname>Noboa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            ;
            <surname>Tudorache</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            ;
            <surname>Musen</surname>
          </string-name>
          ,
          <string-name>
            <surname>M. A.</surname>
          </string-name>
          ; and Strohmaier,
          <string-name>
            <surname>M.</surname>
          </string-name>
          <year>2015</year>
          .
          <article-title>Understanding How Users Edit Ontologies: Comparing Hypotheses About Four RealWorld Projects</article-title>
          . In International Semantic Web Conference, volume LNCS
          <volume>9366</volume>
          ,
          <fpage>551</fpage>
          -
          <lpage>568</lpage>
          . Springer.
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          <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>
          ; Kondylakis,
          <string-name>
            <given-names>H.</given-names>
            ;
            <surname>Motta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            ;
            <surname>Plexousakis</surname>
          </string-name>
          ,
          <string-name>
            <surname>D.</surname>
          </string-name>
          ; and Sabou,
          <string-name>
            <surname>M.</surname>
          </string-name>
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          <article-title>Ontology evolution: a process-centric survey. The knowledge engineering review 30(1</article-title>
          ):
          <fpage>45</fpage>
          -
          <lpage>75</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>