<!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>Storing and Attesting Conceptual Models on Blockchains</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Hans-Georg Fill</string-name>
          <email>hans-georg.fill@unifr.ch</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Felix Härer</string-name>
          <email>felix.haerer@unifr.ch</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Digitalization and Information Systems Group, University of Fribourg</institution>
          ,
          <country country="CH">Switzerland</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Model Storage using Purpose-Built Blockchains</institution>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2020</year>
      </pub-date>
      <abstract>
        <p>The IT-based storage and distribution of conceptual models is necessary for sharing the knowledge contained in them between diferent parties. This may include for example enterprise models that document the strategies, business processes or IT architectures of a company, software models that give insights into the software architecture of applications and services, or arbitrary types of domain-specific models for specific purposes. In this contribution we review approaches for using blockchain technologies in this context. This encompasses on the one hand the storage of models using purpose-built blockchains and on the other hand the so-called attestation of models using existing blockchain platforms. In addition, we discuss potential future research directions in this area. Today's commonly used public blockchain platforms such as Bitcoin or Ethereum are not designed to store large amounts of data. If one wishes to store the content of conceptual models entirely on a blockchain, purpose-built blockchains are necessary. This has been for example demonstrated in the approach of Knowledge Blockchains, where the content of conceptual models is stored on a blockchain together with detailed change permissions [FH18]. In</p>
      </abstract>
      <kwd-group>
        <kwd>Conceptual Model</kwd>
        <kwd>Blockchain</kwd>
        <kwd>Smart Contract</kwd>
        <kwd>Storage</kwd>
        <kwd>Attestation</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Motivation</title>
      <p>Conceptual models constitute today an important tool for business and information systems
engineering [Sa18]. Applications include business process and data modeling, simulation
and analysis, as well as enterprise and IT architecture management. Thereby, the storage
and distribution of models play an important role in persisting and transferring the
contained knowledge. In part, this aspect has been investigated in model versioning, where
model serialization determines the suitability of versioning requirements, e.g. for model
merging [ASW09]. Recently, the benefits blockchains can ofer in this context have been
researched. These technologies store information in a decentralized, distributed, immutable,
and transparent way [FM20], which permits to make the versioning of models transparent
and trace any changes to their originators via their public keys.
the course of a mining process, the permissions are checked decentrally against proposed
changes. The advantage of this approach is the transparent storage of model information in
a fully decentralized way.
3</p>
    </sec>
    <sec id="sec-2">
      <title>Attestation Using Existing Blockchain Platforms</title>
      <p>Another direction is the attestation of conceptual models using blockchains. Thereby, only
a hash value summarizing the content of a model is stored on a blockchain such that the
existence of the model is immutably documented. Due to the limited size, data can be stored
on existing platforms inside a smart contract, as it has been demonstrated for the Ethereum
platform in a first implementation of such an approach [ HF19]. The models involved are
distributed either by point-to-point transfer to specific parties or by distributed storage in
a network. E.g., models of course certificates might be sent to students and third-party
employers, while supply chain process models are shared by multiple companies. Attestation
with distributed storage is particularly relevant in any case where models are shared and
changed by multiple parties with partially opposing interests, such that control must not lie
solely in the hands of a single model owner. To achieve this, distributed storage is content
addressable, e.g. in IPFS [BD19]. I.e., a hash value in a smart contract is suficient to retrieve
a model that is stored by network participants, resulting in immutability and availability.
4</p>
    </sec>
    <sec id="sec-3">
      <title>Future Research Directions</title>
      <p>The storage of models on blockchains is still in its infancy. Further research regarding
the scalability of such approaches is necessary. This also applies to attestation approaches
where real-world use cases need to be investigated to further develop this direction.
[BD19]
[FH18]
[FM20]
[HF19]
[Sa18]
Benet, Juan; Dias, David: IPFS Architecture Overview. IPFS Specifications. 2019. URL:
https://github.com/ipfs/specs/blob/master/ARCHITECTURE.md, accessed 2020-01-23.</p>
      <p>Sandkuhl, Kurt et al.: From expert discipline to common practice: a vision and research
agenda for extending the reach of enterprise modeling. Business &amp; Information Systems
Engineering, 60(1):69–80, 2018.</p>
    </sec>
  </body>
  <back>
    <ref-list />
  </back>
</article>