<!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>A Decentralized Provenance Network for Linked Open Data</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>n Kirst</string-name>
          <email>fabian.kirstein@fokus.fraunhofer.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Weizenbaum Institute for the Networked Society</institution>
          ,
          <addr-line>Berlin, Germany Fraunhofer FOKUS, Berlin</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>With the growing availability of Linked Open Data (LOD) and the consequential generation of derived and aggregated data, the need for trustworthy, reproducible and accessible provenance information has increased. Yet, no consistent mechanism has been established to manage provenance data of LOD on a global dataset-level. Decentralized networks and peer-to-peer mechanisms have made their revival in the last years with blockchain and similar distributed ledger technologies. We propose a novel approach to track and store provenance information for LOD on a dataset-level by sharing an immutable, common state between data providers. The basic architecture will not disrupt existing methodologies and standards for publishing LOD, but will be transparently integrated into existing ecosystems as an additional layer to foster broad acceptance. We will investigate the application of emerging blockchain technologies and established Linked Data specifications for building this decentralized anchor of truth. We are actively involved in the design and implementation of LOD and Open Data platforms and will evaluate our approach in real-world scenarios regarding feasibility, governance, scalability and usability.</p>
      </abstract>
      <kwd-group>
        <kwd>Provenance Distributed Ledger Blockchain Open Data</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        The Linked Open Data (LOD) movement is a global phenomenon, driven by the
fact that additional value is generated by interlinking structured data. LOD is
Linked Data, which can be distributed by everyone anytime without any
restrictions. An active community has evolved around the publication and generation
of LOD. A popular publisher is WikiData, which freely offers comprehensive
data, completely serialized in the Resource Description Framework (RDF). [
        <xref ref-type="bibr" rid="ref25">25</xref>
        ]
Other issuers release only metadata as LOD, referencing and describing in detail
the actual data inventory, which usually consists of a variety of data formats.
      </p>
      <p>
        Our work focuses on the latter approach, which is typically applied by Open
Data portals, aggregating public data, published by public administrations or
research organizations. Well-known examples are OpenAIRE [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] for research
data and the European Data Portal (EDP) [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] for data of public authorities in
Copyright © 2019 for this paper by its authors. Use permitted under Creative Commons License Attribution 4.0 International (CC BY 4.0).
Europe. In fact, many more publishers of LOD exist: The Linked Open Data
Cloud1 lists more than 1300 datasets.
      </p>
      <p>
        The widespread distribution and availability of Open Data leads to the creation
and publication of derivative or edited datasets. Data from different sources and
origins is copied, aggregated, converted and/or enriched. Furthermore, claims
and conclusions are inferred from (combinations of) these datasets. The
traceability and repeatability of such data and its processing is critical for maintaining
trust and accountability. A central foundation for that is the presence of
expressive and valid provenance information for each dataset in an LOD processing
chain. No unified mechanism is established to record and track the
provenance of LOD on a dataset-level. The very nature of LOD causes
barriers in establishing appropriate measures. The intrinsic reason for this claim is:
LOD ecosystems constitute highly distributed and decentralized systems, where
data is acquired and aggregated across distinct organizational and technical
levels. An illustrating example for this is the harvesting process of LOD published
by public services. Typically, harvesting is conducted in a bottom-up form, where
municipal data providers publish data independently. This is followed by an
aggregation towards the next higher organizational level and so forth, e.g., towards
data portals of cities, federal states, etc. [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] Users and processors may fetch the
data at any point in the hierarchy. A similar process is applied for scientific
publications, where data is published by individual research organizations and
aggregated in central hubs for scientific publications [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
      </p>
      <p>This methodology and the design of LOD leads to major challenges with respect
to tracking the provenance of a single dataset: Firstly, there is no established
approach for uniquely and persistently identifying a distinct dataset. Although the
Linked Data principles require the use of Uniform Resource Identifiers (URIs) as
unique identifiers, they can be easily reassigned and the DNS itself is transient.</p>
      <p>
        Especially in the domain of research data, the application of Digital Object
Identifiers (DOIs) as a centralized workaround is established. Secondly, provenance
information is often not set, fragmentary or not correctly forwarded in an
acquisition and processing chain. Expressive and rich specifications for encoding
provenance are available, foremost the W3C PROV [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. Still, its successful
adoption requires correct handling of it by each participant. Additionally, provenance
information represented as plain metadata allows tampering and manipulation
by malicious partners.
      </p>
      <p>These limitations could be solved by establishing and agreeing on a central
management system for provenance and identifier information. However, the very
character of LOD is decentralization and sovereignty, involving multiple
stakeholders and heterogeneous infrastructures. This environment makes the
successful implementation of a centralized system infeasible. This leads to the essential
hypotheses of this dissertation: An additional, immutable and
decentralized network can help to overcome current drawbacks in LOD
provenance tracking and incentivize its broad application. The recent
developments in blockchain systems and related peer-to-peer (P2P) technologies will</p>
    </sec>
    <sec id="sec-2">
      <title>1 https://www.lod-cloud.net</title>
      <p>be an important foundation for implementing such a network.</p>
      <p>This approach can accomplish both: The management of provenance
information through a homogeneous system and the protection of the independence of
the data providers. This will support the fact that from an organizational point
of view, LOD forms a highly decentralized system, which requires a single point
of truth in order to ensure integrity and trust.
2</p>
      <sec id="sec-2-1">
        <title>Relevancy</title>
        <p>
          Due to the ongoing worldwide digitization, data has become a most valid asset
and the basis of many value-added processes and business models. Although our
work focuses on LOD, this is true for both, public domain data and proprietary
data. The relevance of trustworthy information about the provenance and
lineage of data will continue to increase. Simmhan et al. write "With a growing
number of datasets available in the public domain beyond the confines of a single
organization, it has become increasingly important to determine the veracity and
quality of these datasets." [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ] As of today, more than 2600 Open Data portals
exist in the world. [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ] Although they do not all serve LOD, it shows a clear
tendency of increasing significance in the domain. This data is used, processed,
aggregated and re-published by multiple user groups, e.g., journalists, scientists,
businesses, citizens, etc. These groups will benefit highly from improved
provenance information, since it will enable reproducibility and increase trust. This
"proof of origin" will improve the overall quality of the data for the data
consumers. This is especially true for the research community, where traceability is
an ethical and legal requirement. With regard to the Open Science movement
and the increasing publication of raw scientific data, provenance information
will become essential. Within the LOD community, efforts for harmonization
are intrinsic and serve the idea of a global interlinked knowledge graph.
Wellknown examples are the Linked Open Vocabularies project [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ] and the Linked
Data Platform specification [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ]. Integrating a trustable, decentralized
provenance mechanism can strengthen Linked Data as core layer for the growing data
economy, not limited to LOD, and broaden its adoption. After all, the
Semantic Web Stack is missing a trust layer, where provenance will be one essential
building block.
3
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>Related Work</title>
        <p>
          A lot of research was conducted in the relevant fields of our work. Our approach
crosses established research of provenance for LOD with blockchain and
distributed ledger technologies, which has been already examined to some degree.
In general, data provenance has been widely studied with respect to its use,
subject, representation, storing and dissemination and a variety of software
solutions have been developed for managing provenance. These approaches mainly
focus on local data, typically generated by a particular scientific domain, e.g.,
Physics, Earth Sciences, etc. [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ] An extensive literature review and overview
of provenance on the Web, including the Semantic Web, was published by Luc
Moreau. [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]
3.1
        </p>
        <sec id="sec-2-2-1">
          <title>Provenance for Linked (Open) Data</title>
          <p>
            Early work on provenance for Linked Data focused on modelling RDF
vocabularies and ontologies, which can be used to describe the provenance of published
RDF data and query it respectively. [
            <xref ref-type="bibr" rid="ref7">7</xref>
            ] Since then, the W3C has developed
PROV, a set of specifications and data models for publishing provenance
information. It is widely established as interchange format for provenance data.
The standard is not limited to Linked Data, but offers multiple serializations,
including an OWL ontology. [
            <xref ref-type="bibr" rid="ref13">13</xref>
            ] Extensive research was conducted for
effectively attaching provenance information to RDF. Common approaches include
the concept of annotated RDF [
            <xref ref-type="bibr" rid="ref23">23</xref>
            ], where each triple is associated with
metadata. Wylot et al. introduced a high-performance triplestore, allowing to store
provenance-enriched RDF and executing queries, including close-grained
provenance information. [
            <xref ref-type="bibr" rid="ref31">31</xref>
            ] Little work exists on making provenance information
centrally and globally available. ProvStore is such a central service, allowing to
store and publish provenance information of data, based on the PROV standard.
[
            <xref ref-type="bibr" rid="ref8">8</xref>
            ] No approach exists in managing provenance information in a globally shared
state.
3.2
          </p>
        </sec>
        <sec id="sec-2-2-2">
          <title>Linked Data and Distributed Ledgers</title>
          <p>
            First research exists on the connection of distributed ledgers/blockchain
technologies and Linked Data/Semantic Web, spanning multiple aspects. English et
al. endorse the notion of improving the persistent identification of RDF resources
with blockchain. [
            <xref ref-type="bibr" rid="ref5">5</xref>
            ] Third et al. investigate several stages of extension of storing
Linked Data in a distributed ledger, from a simple verification layer to a pure
storage layer. [
            <xref ref-type="bibr" rid="ref21">21</xref>
            ] The InterPlanetary Linked Data (IPLD) project follows a
disruptive approach, by completely lifting the data management to a decentralized
network. IPLD offers a custom data structure, which is globally addressable and
supports interlinking. [
            <xref ref-type="bibr" rid="ref17">17</xref>
            ] Sicilia et al. propose an immutable, decentralized
storage for raw LOD based on the P2P System Interplanetary File System (IPFS)
to overcome issues of availability. [
            <xref ref-type="bibr" rid="ref19">19</xref>
            ] An opposed approach makes
decentralized data on the Ethereum blockchain available via Semantic Web technology,
by mapping the blockchain data structures to Linked Data. [
            <xref ref-type="bibr" rid="ref22">22</xref>
            ] Applying a
distributed ledger as an additional layer for provenance tracking in the domain of
LOD was not proposed yet.
3.3
          </p>
        </sec>
        <sec id="sec-2-2-3">
          <title>Blockchain and Beyond</title>
          <p>
            Blockchain and related technologies are vivid topics of research, where most
work focuses on privacy and security aspects. [
            <xref ref-type="bibr" rid="ref33">33</xref>
            ] The most defining and
relevant work is the P2P cash system Bitcoin. [
            <xref ref-type="bibr" rid="ref15">15</xref>
            ] However, many different areas
of application have evolved. A general indicator for applying a blockchain is the
presence of a decentralized environment, with multiple (untrusted) participants
and the need for transparency. [
            <xref ref-type="bibr" rid="ref32">32</xref>
            ] Some is related to our proposed approach,
but set in different domains with other emphasises. Rohrer et al. propose a
blockchain-based system for decentralized and transparent storing of citation
and reference provenance for journalistic articles on the Web. [
            <xref ref-type="bibr" rid="ref18">18</xref>
            ] Liang et al.
implemented an additional provenance layer based on a blockchain network for
the open source cloud solution ownCloud, which tracks every file transaction
with only little overhead. [
            <xref ref-type="bibr" rid="ref11">11</xref>
            ] Other relevant work includes the vibrant ecosystem
of open source blockchain projects. Ethereum is a multi-purpose, decentralized
and transaction-based state machine. It includes smart contract functionality
and allows to build private or public blockchain systems. [
            <xref ref-type="bibr" rid="ref30">30</xref>
            ] Hyperledger
Fabric enables the creation of permissioned blockchains based on general-purpose
programming languages and custom consensus mechanisms. [
            <xref ref-type="bibr" rid="ref2">2</xref>
            ] Finally, a lot
of up-to-date research is conducted regarding consensus protocols for enduring
Byzantine failures and ensuring a unique and correct state of a network. Cachin
et al. give a comprehensive overview on the recent developments. [
            <xref ref-type="bibr" rid="ref3">3</xref>
            ]
4
          </p>
        </sec>
      </sec>
      <sec id="sec-2-3">
        <title>Research Questions</title>
        <p>Based on the problem statement, the related work and the recent impact of
distributed ledger technologies, new approaches for addressing provenance of
LOD will emerge. Our work will focus on an additional, decentralized layer,
accompanying existing solutions for publishing LOD. Therefore, we formulate
the following research questions, where RQ1 represents the overall question.</p>
        <p>RQ1: Can we manage the provision, management and traceability of
provenance information for LOD datasets by applying an additional, decentralized
layer?</p>
        <p>RQ2: How can we persistently identify and represent provenance information
of LOD in a globally unique way?</p>
        <p>RQ3: What consensus and governance mechanisms can be applied to ensure
the integrity of such a system?</p>
        <p>RQ4: Which paradigms and tools are suitable to implement the proposed
approach, considering expectations in flexibility, scalability and usability?
5</p>
      </sec>
      <sec id="sec-2-4">
        <title>Hypotheses</title>
        <p>The following hypotheses relate to the aforesaid research questions. H1 depicts
the overall hypothesis of the proposed thesis.</p>
        <p>H1: A decentralized network, which holds a globally shared state for all data
providers will improve the tracking and storing of provenance information of
LOD in comparison to locally published provenance data.</p>
        <p>H2: An immutable and transparent global database will improve the
persistent and unique identification and management of provenance information over
established transient approaches and enables a long-term preservation.</p>
        <p>H3: An authority-based governance model and voting-based consensus
mechanism will ensure a consistent state of the network and prevent misuse.</p>
        <p>H4: Blockchain and related technologies can serve as a technical foundation
for the proposed decentralized network.
6</p>
      </sec>
      <sec id="sec-2-5">
        <title>Preliminary Results</title>
        <p>In this section, we present first results and experiences from previous and
ongoing work in the LOD and distributed ledger domains.</p>
        <p>
          Our work on the EDP [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] has given us valuable insights into the process of LOD
acquisition, processing and re-publishing. We collect Linked Data from more
than 70 data publishers, in total more than 800.000 datasets. The data
publishers themselves gather the data from lower organizational levels. It has been
proven extremely difficult to uniquely identify a dataset in this ecosystem and to
track its provenance. The required metadata simply does not exist or is
incomplete. In addition, close communication with the data publisher has shown that
there is an aspiration for autonomy and sovereignty. Rapid changes in existing
methodologies and technologies are not endorsed. We came to the conclusion that
an additional and simple to integrate solution has higher chances for adoption.
In our project Policy Compass2, we developed a platform for mixing, extending,
interpreting and visualizing Open Data. A use case is the assessment of outcome
and impact of governmental policies through analyzing public available data.
[
          <xref ref-type="bibr" rid="ref10">10</xref>
          ] We integrated several data sources, e.g. the EDP, Eurostat3 and DBpedia4.
The project has shown us a clear need for traceability and reproducibility,
especially in the domain of policy evaluation and derived recommended actions.
We implemented basic traceability support, by linking datasets to its original
source and indicating the local provenance in derived assets. However, due to
the heterogeneity of the data sources, the implementation of a more general and
global provenance mechanism has proven unfeasible.
        </p>
        <p>
          We have conducted several practical case studies with blockchain and distributed
ledger technologies to classify their opportunities and challenges. Based on the
public Ethereum blockchain we have implemented a decentralized digital
identity management system. It allows human users to acquire a persistent
identifier and link public properties, like date of birth, to it. The work is based
on Ethereum smart contracts and the Decentralized Identifiers (DIDs)
specification. [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ] Furthermore, we used the permissioned blockchain infrastructure
Hyperledger Fabric [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ] for implementing a track and trace system for physical
assets. It demonstrates how a decentralized network can enable data sharing and
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>2 https://policycompass.eu</title>
    </sec>
    <sec id="sec-4">
      <title>3 https://ec.europa.eu/eurostat</title>
    </sec>
    <sec id="sec-5">
      <title>4 https://wiki.dbpedia.org</title>
      <p>cooperation beyond organizational borders. We acquired fundamental knowledge
about governance, scalability and representing custom data in such a
decentralized environment.
7</p>
      <sec id="sec-5-1">
        <title>Approach</title>
        <p>The overall approach is divided into four steps. Steps 1 and 2 refer to RQ2/H2,
step 3 to RQ3/H3 and step 4 to RQ4/H4. The overall outcome relates to
RQ1/H1.</p>
        <p>LOD and the Semantic Web follow a decentralized methodology, still some
aspects require a central authority to be most effective and accurate. An indicator
for that are various approaches to harmonize LOD by some kind of central
stewardship, e.g., Linked Open Vocabularies (LOV) or GeoNames.org.5 Our
approach is the establishment of a decentralized network, which holds a globally
shared state for all data providers and acts as an anchor of truth about
provenance information. It is a single point of access for this global information, which
simplifies management and traceability. Each participant of the ecosystem will
act as distributed database node. The central premise is not to disrupt
existing methodologies and standards, but to transparently integrate into existing
ecosystems. Fig. 1 illustrates an exemplary high-level process for LOD
aggregation, processing and use, including the decentralized provenance network. An
LOD provider holds metadata and data and publishes a reference of them to the
network. (here illustrated as hash values and a persistent identifier) An LOD
aggregator copies only the metadata and extends the original reference accordingly.
(indicated as sameAs) An LOD processor creates new data based on the original
data and adds a new reference to the network, including a derivedFrom
indication. Finally, a data publisher creates a visualization of the data, linking it to the
reference in the network, allowing a clear tracking of the provenance of the data.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>5 https://www.geonames.org</title>
      <p>
        1. Formal definition of a dataset: LOD constitutes a set of triples (aka
statements), forming a multigraph. Our work does not base upon this smallest entity
of LOD. Typically, a distinct subset of triples forms a self-contained information
unit, restricted by pre-defined boundaries. Concepts like named graphs reflect
this approach. [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] In the first step we will derive a formal definition of what can
be considered a distinct dataset. This includes a URI schema, graph constraints
and publication guidelines. We contemplate to base it on well-established
standards and best practices. The Data Catalogue Vocabulary (DCAT) [
        <xref ref-type="bibr" rid="ref26">26</xref>
        ] will act
as a principle recommendation for describing the metadata. The Linked Data
Platform (LDP) specification [
        <xref ref-type="bibr" rid="ref27">27</xref>
        ] offers a reference for publishing the datasets
on the Web. A validation mechanism will be based on the Shapes Constraint
Language (SHACL) [
        <xref ref-type="bibr" rid="ref28">28</xref>
        ]. The result of this step will be a practical tool set to
publish valid datasets and the groundwork for the following steps.
2. Definition of the identifier and provenance data models: Published datasets
from a provider can be considered local, since they are initially confined to the
providers network and are addressed via a transient URL. The proposed
decentralized network forms a global context, since it is shared by many data providers
and leverages all available datasets. In this step, we will essentially model and
define the mapping from a local to a global context. This includes two aspects:
Firstly, the global representation of a persistent identifier and its linking to the
actual local dataset will be modelled. It is important here to consider changes
and relocations of the local identifier and to provide the means to perform a
mapping of the identifiers multi-directionally. Existing decentralized identifier
concepts will act as guidance here. Secondly, the actual global provenance data
model will be designed. Based on the global identifiers, we will provide a
compact and basic model to represent the provenance of a dataset. It will utilize a
subset of the methodology and ontology of W3C PROV and its core concepts
Entity, Agent and Activity. [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] The outcome of this will be a comprehensive
specification of the data models, alongside a proof-of-concept implementation.
3. Design of the decentralized network methodology: In this step, we will
design the fundamental architecture of the decentralized provenance network,
essentially regarding agent management, governance model, security aspects and
consensus mechanisms. Essentially, a change in the globally shared state needs
corporative validation and confirmation of the network. Only thereby the
correctness and integrity can be guaranteed. We think that an authority-based
governance model and voting-based consensus mechanism will ensure a consistent
state of the network. Every LOD data provider will have a verifiable identity,
authorizing them as a valid member of the network. This authority will be granted
by a proof of ownership, e.g., of a local LOD endpoint. A state change of the
network can be issued by each participant, but requires approval by the
majority of the other authorized participants. Hence, a voting is performed, ensuring
that not a single participant can publish defective or wrong data. Eventually,
the transparency of the decentralized network will offer an additional layer of
governance. It enables an open and immediate quality assessment and increases
the barrier for publishing faulty information.
      </p>
      <p>
        We will evaluate these assumptions against real-world LOD ecosystems and
publication schemes. The outcome will lead to accurate guidelines about who will
be allowed to add what data when in the shared store, formed by the network.
Especially, the on-boarding process in this decentralized environment needs to
be investigated. These assumptions will be evaluated with practical artifacts,
either based on existing technologies or individually implemented.
4. Implementation and evaluation of the provenance network: In the final step,
we will implement the network and apply it in a production environment. With
blockchain and similar distributed ledger technologies, decentralized networks
and peer-to-peer mechanisms have made their revival in the last years. A variety
of tools offer improved possibilities for sharing a common state and reaching
consensus in a decentralized environment. Multiple implementations exist for
building customized decentralized networks with desired characteristics: from
public, permissionless to private, permissioned networks, including custom
security and consensus protocols. These recent developments can operate as a
technical foundation for the proposed decentralized network. Yet, your work will
not be limited to blockchain and distributed ledger technologies, but will also
consider traditional peer-to-peer mechanisms and implementations.
The work here will be mainly conducted on two levels. (1) Providing the means
for actually creating the network. This includes a deployable node and a proper
on-boarding process to become a participant in the network. The setup of a
node is envisioned to be as straight-forward as possible. Container technologies,
like Docker, might be suitable approaches here. [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] We will put an emphasis
on scalability and performance and take into account typical data volumes and
throughputs of LOD systems. (2) Create an approach and implementation for
effectively interacting with the network. A straight-forward and easy
integration into existing LOD publication concepts is desired here. The most native
method here constitutes SPARQL. We think that the least disruptive
integration approach would be a proxy for a standard SPARQL endpoint, allowing
users to annotate publication queries with provenance information. The proxy
will extract these annotations, process them and trigger a change of state in the
network, when necessary. It has to be noted that the operators of (1) and (2)
can be disjoint, so not every data provider has to provide a node and vice versa.
The outcome of this step will be a fully working prototype.
8
      </p>
      <sec id="sec-6-1">
        <title>Evaluation Plan</title>
        <p>We plan to evaluate our hypotheses with the following four approaches.
1. Working prototype: Based on a proof-of-concept system, we will test and
evaluate the fundamental functionality of our approach. Test data will be generated
in real-world volumes. Synthetic, but representative stakeholders and actors will
use the network. We will use the results and findings for improving our approach
in an iterative manner.
2. Application in a production environment: We are actively involved in the
implementation of LOD portals, like the EDP. Hence, we will apply our solution
in a production environment and monitor its qualities and possible adoption. A
cooperation with external stakeholders, like original data publishers and data
users are requested.
3. Practical usefulness: We will measure and qualify multiple characteristics
of the synthetic and the production system. This includes overall performance,
throughput, maximum load and scalability. Since no system for comparison
exits, we will evaluate the findings on established expectations for central solutions,
especially for provenance tracking.
4. User studies: The rate of adoption of such a system, is highly dependent on
user acceptance. We will conduct user studies within two different user groups:
(1) Data providers will be asked to join the network by integrating it into their
systems. (2) Data consumers will use the provided information to express
provenance statements about given datasets. It is planned to conduct the user studies
twice, with a working prototype and a production version.
9</p>
      </sec>
      <sec id="sec-6-2">
        <title>Reflections</title>
        <p>To the best of our knowledge, the proposed research questions and the proposed
approach is a novelty. There does not exist an established solution for a
tamperproof and globally accessible ledger for provenance information about LOD. The
recent developments and successful real-world applications of blockchain and
similar networks have demonstrated the success and acceptance of a globally
shared state-machine. However, we think that blockchain still has a long way to
go and are aware of its current limitations. A complete migration from
established centralized systems and architectures, especially in LOD, is improbable.
An additional, decentralized layer, respecting established mechanisms and
standards will have a much better chance for adoption. We are actively involved in
many production LOD, Open Data and Open Science projects. Among others,
this includes the development of the EDP and the design and installation of a
research data platform for the Weizenbaum Institute for the Networked Society.
This allows us to work closely with many relevant stakeholders and consider their
needs and requirements, e.g., the data providers, users or system administrators.
10</p>
      </sec>
      <sec id="sec-6-3">
        <title>Acknowledgements</title>
        <p>This work has been funded by the Federal Ministry of Education and Research
of Germany (BMBF) under grant no. 16DII111 ("Deutsches Internet-Institut")
and is supervised by Prof. Manfred Hauswirth.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Anderson</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <string-name>
            <surname>Docker</surname>
          </string-name>
          [Software engineering].
          <source>IEEE Software 32(3)</source>
          ,
          <fpage>102</fpage>
          -
          <lpage>c3</lpage>
          (May
          <year>2015</year>
          ). https://doi.org/10.1109/MS.
          <year>2015</year>
          .62
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <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>De Caro</surname>
            ,
            <given-names>A.</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>
          ,
          <string-name>
            <surname>Manevich</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Muralidharan</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Murthy</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nguyen</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sethi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Singh</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Smith</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sorniotti</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stathakopoulou</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vukolić</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cocco</surname>
            ,
            <given-names>S.W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yellick</surname>
          </string-name>
          , J.:
          <article-title>Hyperledger Fabric: A Distributed Operating System for Permissioned Blockchains</article-title>
          .
          <source>Proceedings of the Thirteenth EuroSys Conference on - EuroSys '</source>
          18 pp.
          <fpage>1</fpage>
          -
          <lpage>15</lpage>
          (
          <year>2018</year>
          ). https://doi.org/10.1145/3190508.3190538
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Cachin</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vukolić</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Blockchain Consensus Protocols in the Wild</article-title>
          .
          <source>arXiv:1707</source>
          .
          <year>01873</year>
          [cs] (
          <year>Jul 2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Carroll</surname>
            ,
            <given-names>J.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bizer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hayes</surname>
            ,
            <given-names>P.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stickler</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Named graphs</article-title>
          .
          <source>Journal of Web Semantics</source>
          <volume>3</volume>
          ,
          <fpage>247</fpage>
          -
          <lpage>267</lpage>
          (
          <year>2005</year>
          ). https://doi.org/10.1016/j.websem.
          <year>2005</year>
          .
          <volume>09</volume>
          .001
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>English</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Auer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Domingue</surname>
          </string-name>
          , J.:
          <article-title>Block chain technologies &amp; the semantic web: A framework for symbiotic development</article-title>
          . In: Computer Science Conference for University of Bonn Students,
          <string-name>
            <given-names>J.</given-names>
            <surname>Lehmann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Thakkar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Halilaj</surname>
          </string-name>
          , and R. Asmat, Eds. pp.
          <fpage>47</fpage>
          -
          <lpage>61</lpage>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>European</given-names>
            <surname>Data</surname>
          </string-name>
          <article-title>Portal: The European Data Portal: Opening up Europe's public data</article-title>
          , https://www.europeandataportal.eu/sites/default/files/edp_ factsheet_what_is_edp_project_online.pdf,
          <source>(Accessed: 12.04</source>
          .
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Hartig</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhao</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          :
          <article-title>Publishing and Consuming Provenance Metadata on the Web of Linked Data</article-title>
          . In: McGuinness,
          <string-name>
            <given-names>D.L.</given-names>
            ,
            <surname>Michaelis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.R.</given-names>
            ,
            <surname>Moreau</surname>
          </string-name>
          ,
          <string-name>
            <surname>L</surname>
          </string-name>
          . (eds.)
          <article-title>Provenance and Annotation of Data and Processes</article-title>
          . pp.
          <fpage>78</fpage>
          -
          <lpage>90</lpage>
          . Lecture Notes in Computer Science, Springer Berlin Heidelberg (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Huynh</surname>
          </string-name>
          , T.D.,
          <string-name>
            <surname>Moreau</surname>
          </string-name>
          , L.:
          <article-title>ProvStore: A Public Provenance Repository</article-title>
          . In: Ludäscher,
          <string-name>
            <given-names>B.</given-names>
            ,
            <surname>Plale</surname>
          </string-name>
          ,
          <string-name>
            <surname>B</surname>
          </string-name>
          . (eds.)
          <article-title>Provenance and Annotation of Data and Processes</article-title>
          . pp.
          <fpage>275</fpage>
          -
          <lpage>277</lpage>
          . Lecture Notes in Computer Science, Springer International Publishing (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Kirstein</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dittwald</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dutkowski</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Glikman</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schimmler</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hauswirth</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Linked Data in the European Data Portal: A Comprehensive Platform for Applying DCAT-AP</article-title>
          . In:
          <fpage>EGOV2019</fpage>
          - Joint
          <string-name>
            <surname>Conference</surname>
          </string-name>
          EGOV-CeDEM-EPART
          <year>2019</year>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Kokkinakos</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Koutras</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Markaki</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Koussouris</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Trutnev</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Glikman</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          :
          <article-title>Assessing Governmental Policies' Impact Through Prosperity Indicators and Open Data</article-title>
          .
          <source>In: Proceedings of the 2014 Conference on Electronic Governance and Open Society: Challenges in Eurasia</source>
          . pp.
          <fpage>70</fpage>
          -
          <lpage>74</lpage>
          . EGOSE '14,
          <string-name>
            <surname>ACM</surname>
          </string-name>
          , New York, NY, USA (
          <year>2014</year>
          ). https://doi.org/10.1145/2729104.2729134
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Liang</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shetty</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tosh</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kamhoua</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kwiat</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Njilla</surname>
          </string-name>
          , L.:
          <article-title>ProvChain: A Blockchain-Based Data Provenance Architecture in Cloud Environment with Enhanced Privacy and Availability</article-title>
          .
          <source>In: 2017 17th IEEE/ACM International Symposium on Cluster, Cloud and Grid Computing (CCGRID)</source>
          . pp.
          <fpage>468</fpage>
          -
          <lpage>477</lpage>
          (May
          <year>2017</year>
          ). https://doi.org/10.1109/CCGRID.
          <year>2017</year>
          .8
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Manghi</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Manola</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Horstmann</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Peters</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>An Infrastructure for Managing EC Funded Research Output: The OpenAIRE Project</article-title>
          .
          <source>The Grey Journal (TGJ) : An International Journal on Grey Literature</source>
          <volume>6</volume>
          (
          <issue>1</issue>
          ),
          <fpage>31</fpage>
          -
          <lpage>39</lpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Missier</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Belhajjame</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cheney</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>The W3C PROV Family of Specifications for Modelling Provenance Metadata</article-title>
          .
          <source>In: Proceedings of the 16th International Conference on Extending Database Technology</source>
          . pp.
          <fpage>773</fpage>
          -
          <lpage>776</lpage>
          . EDBT '13,
          <string-name>
            <surname>ACM</surname>
          </string-name>
          , New York, NY, USA (
          <year>2013</year>
          ). https://doi.org/10.1145/2452376.2452478
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Moreau</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>The Foundations for Provenance on the Web</article-title>
          .
          <source>Foundations and Trends in Web Science</source>
          <volume>2</volume>
          ,
          <fpage>99</fpage>
          -
          <lpage>241</lpage>
          (
          <year>Nov 2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Nakamoto</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , et al.:
          <article-title>Bitcoin: A peer-to-peer electronic cash system (</article-title>
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <article-title>OpenDataSoft: A Comprehensive List of 2600+ Open Data Portals around the World</article-title>
          , https://www.opendatasoft.
          <article-title>com/ a-comprehensive-list-of-all-open-data-portals-</article-title>
          <string-name>
            <surname>around-</surname>
          </string-name>
          the-world/, (Accessed:
          <fpage>11</fpage>
          .
          <fpage>04</fpage>
          .
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Protocol</surname>
          </string-name>
          <article-title>Labs: IPLD - The Data Model of the Content-Addressable Web</article-title>
          , https: //ipld.io/, (Accessed:
          <fpage>15</fpage>
          .
          <fpage>04</fpage>
          .
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Rohrer</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Heidel</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tschorsch</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Webchain: Verifiable Citations and References for the World Wide Web</article-title>
          . https://doi.org/10.14279/depositonce-8376
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Sicilia</surname>
            ,
            <given-names>M.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sánchez-Alonso</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>García-Barriocanal</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          :
          <article-title>Sharing Linked Open Data over Peer-to-Peer Distributed File Systems: The Case of IPFS</article-title>
          .
          <source>In: Research Conference on Metadata and Semantics Research</source>
          . pp.
          <fpage>3</fpage>
          -
          <lpage>14</lpage>
          . Springer (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Simmhan</surname>
            ,
            <given-names>Y.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Plale</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gannon</surname>
            ,
            <given-names>D.:</given-names>
          </string-name>
          <article-title>A survey of data provenance techniques</article-title>
          .
          <source>No. IUB-CS-TR618. (September</source>
          <year>2005</year>
          ) p.
          <fpage>25</fpage>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Third</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Domingue</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>LinkChains: Exploring the Space of Decentralised Trustworthy Linked Data</article-title>
          .
          <source>DeSemWeb@ISWC</source>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Third</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Domingue</surname>
          </string-name>
          , J.:
          <article-title>Linked Data Indexing of Distributed Ledgers</article-title>
          .
          <source>In: Proceedings of the 26th International Conference on World Wide Web Companion - WWW '17 Companion</source>
          . pp.
          <fpage>1431</fpage>
          -
          <lpage>1436</lpage>
          . ACM Press, Perth, Australia (
          <year>2017</year>
          ). https://doi.org/10.1145/3041021.3053895
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Udrea</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Recupero</surname>
            ,
            <given-names>D.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Subrahmanian</surname>
            ,
            <given-names>V.S.</given-names>
          </string-name>
          :
          <article-title>Annotated RDF</article-title>
          .
          <source>ACM Trans. Comput. Logic</source>
          <volume>11</volume>
          (
          <issue>2</issue>
          ),
          <volume>10</volume>
          :
          <fpage>1</fpage>
          -
          <lpage>10</lpage>
          :
          <fpage>41</fpage>
          (Jan
          <year>2010</year>
          ). https://doi.org/10.1145/1656242.1656245
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>Vandenbussche</surname>
          </string-name>
          , P.Y.,
          <string-name>
            <surname>Atemezing</surname>
            ,
            <given-names>G.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Poveda-Villalón</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vatant</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Linked Open Vocabularies (LOV): a gateway to reusable semantic vocabularies on the Web</article-title>
          .
          <source>Semantic Web</source>
          <volume>8</volume>
          (
          <issue>3</issue>
          ),
          <fpage>437</fpage>
          -
          <lpage>452</lpage>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>Vrandečić</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krötzsch</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <string-name>
            <surname>Wikidata</surname>
            :
            <given-names>A Free</given-names>
          </string-name>
          <string-name>
            <surname>Collaborative</surname>
          </string-name>
          <article-title>Knowledgebase</article-title>
          .
          <source>Commun. ACM</source>
          <volume>57</volume>
          (
          <issue>10</issue>
          ),
          <fpage>78</fpage>
          -
          <lpage>85</lpage>
          (
          <year>Sep 2014</year>
          ). https://doi.org/10.1145/2629489
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26.
          <article-title>W3C: Data Catalog Vocabulary (DCAT)</article-title>
          , https://www.w3.org/TR/vocab-dcat/
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27. W3C:
          <article-title>Linked Data Platform 1.0</article-title>
          , https://www.w3.org/TR/ldp/
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28.
          <article-title>W3C: Shapes Constraint Language (SHACL)</article-title>
          , https://www.w3.org/TR/shacl/
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          29. W3C Community Group:
          <article-title>Decentralized Identifiers (DIDs) v0</article-title>
          .
          <fpage>12</fpage>
          , https:// w3c-ccg.github.io/did-spec/
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          30.
          <string-name>
            <surname>Wood</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Ethereum: a Secure Decentralised Generalised Transaction Ledger (</article-title>
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          31.
          <string-name>
            <surname>Wylot</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cudré-Mauroux</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hauswirth</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Groth</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          : Storing, Tracking, and
          <article-title>Querying Provenance in Linked Data</article-title>
          .
          <source>IEEE Transactions on Knowledge and Data Engineering</source>
          <volume>29</volume>
          (
          <issue>8</issue>
          ),
          <fpage>1751</fpage>
          -
          <lpage>1764</lpage>
          (
          <year>Aug 2017</year>
          ). https://doi.org/10.1109/TKDE.
          <year>2017</year>
          .2690299
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          32.
          <string-name>
            <surname>Wüst</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gervais</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Do you Need a Blockchain</article-title>
          .
          <source>In: 2018 Crypto Valley Conference on Blockchain Technology (CVCBT)</source>
          . vol.
          <year>2017</year>
          , pp.
          <fpage>45</fpage>
          -
          <lpage>54</lpage>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          33.
          <string-name>
            <surname>Yli-Huumo</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ko</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Choi</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Park</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Smolander</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          : Where Is Current Research on Blockchain Technology?
          <article-title>-A Systematic Review</article-title>
          .
          <source>PLOS ONE</source>
          <volume>11</volume>
          (
          <issue>10</issue>
          ),
          <source>e0163477 (Oct</source>
          <year>2016</year>
          ). https://doi.org/10.1371/journal.pone.0163477
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>