<!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>Towards an Interface for User-Friendly Linked Data Generation Administration?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Anastasia Dimou</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Pieter Heyvaert</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Wouter Maroy</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Laurens De Graeve</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ruben Verborgh</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Erik Mannens</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Ghent University - iMinds</institution>
          ,
          <country country="BE">Belgium</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Linked Data generation and publication remain challenging and complicated, in particular for data owners who are not Semantic Web experts or tech-savvy. The situation deteriorates when data from multiple heterogeneous sources, accessed via di erent interfaces, is integrated, and the Linked Data generation is a long-lasting activity repeated periodically, often adjusted and incrementally enriched with new data. Therefore, we propose the rmlworkbench, a graphical user interface to support data owners administrating their Linked Data generation and publication work ow. The rmlworkbench's underlying language is rml, since it allows to declaratively describe the complete Linked Data generation work ow. Thus, any Linked Data generation work ow speci ed by a user can be exported and reused by other tools interpreting rml.</p>
      </abstract>
      <kwd-group>
        <kwd>Linked Data Generation</kwd>
        <kwd>Linked Data Workbench</kwd>
        <kwd>[R2]RML</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Administrating the integration of the ever-increasing amounts of data from
multiple sources in di erent formats into a common knowledge domain remains
challenging and complicated, in particular for data owners who are not
Semantic Web experts or tech-savvy [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Generating Linked Data requires dealing with
data that can originally (i) reside on diverse, distributed locations, (ii) be
approached using di erent access interfaces, and (iii) be expressed in heterogeneous
structures and formats [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. As the Linked Data generation becomes a long-lasting
activity, which is repeated periodically and is incrementally adjusted with new
data, administrating the di erent components becomes di cult.
      </p>
      <p>
        To minimize the e ort and knowledge that data owners need to administrate
their data and the overall Linked Data generation and publication work ow,
we developed a multi-user browser application, the rmlworkbench. This demo
shows how data owners can use the rmlworkbench. Depending on their assigned
roles, data owners can view and manage di erent sources for retrieving raw data
and the corresponding mappings to generate Linked Data, in contrast to our
earlier work on the rmleditor [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] which only focuses on editing mapping rules. A
screencast of the rmlworkbench, is available at https://youtu.be/8UkI01nQNxc.
? The research activities described in this paper were funded by Ghent University, iMinds, the
Institute for the Promotion of Innovation by Science and Technology in Flanders (IWT), the
Fund for Scienti c Research-Flanders (FWO-Flanders) and the European Union.
      </p>
    </sec>
    <sec id="sec-2">
      <title>State of the Art</title>
      <p>The FluidOps Information Workbench1, Ultrwrap2 and LinDa workbench3 are
gui tools supporting data owners to generate Linked Data. However, the latter
two only support tabular data, while the former, even though it supports more
data sources, does not allow specifying di erent access interfaces. Most
importantly though, none of them allows users to export their speci ed Linked Data
generation work ow in a declarative, complete and interoperable way that allows
to replicate the same Linked Data generation by other tools.</p>
      <p>Linked Pipes4, and its predecessor Uni ed Views5, are general-purpose tools
that allow users to administrate, execute, debug, monitor and share Linked Data
processing tasks, for smooth and e cient management. However, they are not
focused on Linked Data generation. They perform direct mappings which are
afterwards processed via sparql construct queries. Moreover, they only allow to
export the di erent processes descriptions, using their own custom descriptions.</p>
      <p>The Silk Workbench6 follows a similar approach as the rmlworkbench. Even
though it is a gui supporting users to administrate rdf dataset linking, it also
requires corresponding aspects to be speci ed. Its function relies on projects which
consist of linkage rules associated with data sources (data dumps or sparql
endpoints) constituting altogether linkage tasks, as mapping rules are associated
with data sources constituting generation tasks in the case of the rmlworkbench.
3</p>
    </sec>
    <sec id="sec-3">
      <title>The RML Workbench Interface</title>
      <p>
        The rmlworkbench design principles are generic, following the classical
multitier client-server architecture. Its underlying language to declaratively de ne the
Linked Data generation work ow speci ed by the user is rml. rml [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] is a
generalization of the w3c recommended r2rml mapping language [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], which is de ned
to specify rules to generate Linked Data from data in relational databases. rml
extends r2rml to also specify rules from data in any semi-structured format,
e.g., csv, xml, or json. rml was furthermore aligned with di erent
vocabularies, e.g., dcat7, csvw8, or Hydra9, to specify how to access data used to
generate the desired Linked Data. The rmlworkbench considers rml as its
underlying language, since it is the only one able to declaratively describe the
complete Linked Data generation work ow, independently of data sources and
formats [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Thus, all mapping rules, including the aligned data sources
description may be exported and re-used by other tools beyond the rmlworkbench to
replicate the generation of same Linked Data.
1 https://www.fluidops.com/en/portfolio/information_workbench/
2 https://capsenta.com/
3 https://github.com/LinDA-tools/LindaWorkbench
4 http://etl.linkedpipes.com/
5 http://unifiedviews.eu/
6 https://github.com/silk-framework/silk/blob/master/doc/Workbench.md
7 https://www.w3.org/TR/vocab-dcat/
8 https://www.w3.org/TR/tabular-metadata/
9 https://www.hydra-cg.com/spec/latest/core/
      </p>
      <p>The rmlworkbench consists of ve panels: Access, Retrieve, Generate, Publish
and Schedule. In the remaining of this section, each panel is brie y presented.
Access panel. Users can manage their own sources, which can be accessed through
interfaces for local les, databases or Web sources. The descriptions are
annotated using di erent vocabularies, e.g., dcat, csvw or Hydra. For instance, a
user speci es a database accessed via a certain jdbc, and labels it \DB Source"
and a dataset published on a dcat catalog, which he labels \Catalog Source".
Retrieve panel. Not all data which appear in a data source are required to
generate the desired Linked Data. Distinct subsets may be considered separately for
generating di erent Linked Data sets. The Retrieve panel allows users to specify
which exact data is retrieved for each selection. For instance, via the Retrieve
panel, the aforementioned user speci es the exact tables, which are eventually
considered to generate certain Linked Data. The user speci es the \Singers"
and \Albums" tables of the \DB source" and labels them as \Singer data"
and \Album data" respectively. Moreover, the same user speci es and labels as
\Performance data", among the di erent datasets of the \Catalog source", the
dataset about performances, and precisely its xml distribution.</p>
      <p>Generate panel. To generate the desired Linked Data, the users need to specify
sets of mapping rules. The rmlworkbench allows users to (i) upload a mapping
document, (ii) specify a Web source with mapping rules, or (iii) directly edit
them via its interface. Di erent sets of mapping rules may be associated with the
same data, generating thus di erent Linked Data views. Once the set of mapping
rules is associated with some raw data, the users can execute the mapping and
generate the desired Linked Data (\Execute" button, as shown in the following
gure). The dataset is then listed among the datasets available for publishing, or
the users are noti ed if the generation was not successful. The users can specify
mapping rules, for instance the sets of \Singer mappings" and \Performance
mappings". Once the mapping rules are listed among the available sets, the users
can associate them with the corresponding data (\Add Logical Source" button),
in our example the \Singer data" and \Performance data". Furthermore, the
users may desire to generate another Linked Data set with the same data. In
that case, another set of mapping rules is added, e.g., the \Person mappings",
and the user associates it with the \Singer data" as well.</p>
      <p>Publish panel. A frequent activity after generating Linked Data is its
publication. The rmlworkbench supports users to easily accomplish this activity. In our
example, the Linked Data is published via an ldf server10. Nevertheless, the
administrator can easily con gure other interfaces, for instance sparql endpoints.
The users can then choose one or more of them to publish their Linked Data.
Schedule panel. In most cases, the Linked Data generation and publication is a
recurring activity. Data owners periodically regenerate their Linked Data set to
keep it up-to-date with the original data. The rmlworkbench allows data owners
to schedule the Linked Data generation and publication activities.</p>
      <p>
        To summarize, the rmlworkbench allows data owners to specify their
complete Linked Data generation work ow, without being restricted by the tool. In
the future, the rmleditor [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] will be integrated with the rmlworkbench and users
can then directly use the rmleditor to edit their mapping rules.
10 https://github.com/LinkedDataFragments/Server.js
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>S.</given-names>
            <surname>Das</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Sundara</surname>
          </string-name>
          , and
          <string-name>
            <given-names>R.</given-names>
            <surname>Cyganiak</surname>
          </string-name>
          .
          <article-title>R2RML: RDB to RDF Mapping Language</article-title>
          . Working Group Recommendation, W3C, Sept.
          <year>2012</year>
          . http://www.w3.org/TR/r2rml/ .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>A.</given-names>
            <surname>Dimou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. Vander</given-names>
            <surname>Sande</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Colpaert</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Verborgh</surname>
          </string-name>
          , E. Mannens, and R. Van de Walle.
          <article-title>RML: A Generic Language for Integrated RDF Mappings of Heterogeneous Data</article-title>
          .
          <source>In Workshop on Linked Data on the Web</source>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>A.</given-names>
            <surname>Dimou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Verborgh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. Vander</given-names>
            <surname>Sande</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Mannens</surname>
          </string-name>
          , and R. Van de Walle.
          <article-title>Machine-Interpretable Dataset and Service Descriptions for Heterogeneous Data Access and Retrieval</article-title>
          .
          <source>In SEMANTiCS</source>
          <year>2015</year>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>P.</given-names>
            <surname>Heyvaert</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Dimou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.-L.</given-names>
            <surname>Herregodts</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Ruben</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Dimitri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Erik</surname>
          </string-name>
          , and V. de Walle Rik.
          <article-title>RMLEditor: A Graph-Based Mapping Editor for Linked Data Mappings</article-title>
          .
          <source>In The Semantic Web: ESWC 2016</source>
          . Springer,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>