<!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>Reflections on: DCAT-AP Representation of Czech National Open Data Catalog and its Impact?</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Software Engineering, Faculty of Mathematics and Physics, Charles University</institution>
          ,
          <addr-line>Malostranské náměstí 25, 118 00 Praha 1</addr-line>
          ,
          <country>Czech</country>
          <addr-line>Republic https://jakub.klímek.com</addr-line>
        </aff>
      </contrib-group>
      <abstract>
        <p>Open data is now a heavily discussed topic around the world and in the European Union. In the Czech Republic, open data is a term anchored in legislation, which includes the requirement of registration of all open data in the Czech National Open Data Portal (NODC). In the journal paper [5] we describe the NODC, its architecture, dataset registration processes including the harvesting of Local Open Data Catalogs (LODCs), proprietary XML API and its obsolete dataset viewer. Next we describe the process of transformation of the NODC metadata to the DCAT-AP v1.1 RDF representation from the data model point of view and from the technical environment point of view. We describe the dataset quality measurements computed using the new data representation and its further impact on the Linked Open Data (LOD) environment including the harvesting of the metadata by the European Data Portal (EDP). Finally, we evaluate the data transformation and publishing environment from the usability, portability, availability and performance perspectives.</p>
      </abstract>
      <kwd-group>
        <kwd>open data</kwd>
        <kwd>catalog</kwd>
        <kwd>DCAT-AP</kwd>
        <kwd>Linked Data</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Open data is currently a hot topic among institutions of public administration
and data users around the world. From the political point of view, publishing
open data is important for public administration institutions to show that they
are transparent and open to citizens. From the legal point of view it is
important that the data is published using an open license, permitting users to use
the data freely. From the technical point of view, it is important that the data
is published as machine readable data in an open format, accessible on the web
with minimal effort. From the point of view of potential open data users it is
important that the data can be searched for and found. Finally, from the economic
? This work was supported by the Czech Science Foundation (GAČR), grant number
19-01641S.
point of view, open data is expected to support creation of new services and new
business models1. At the intersection of all of these points of view lay open data
portals of the data publishing institutions, which typically include open data
catalogs where datasets can be found along with the metadata describing them.
The metadata descriptions contain the necessary information about the licenses
of datasets, formats of their distributions, and the textual descriptions, all of
which can be used for dataset search. This results in a number of open data
catalogs, typically one per each institution willing to publish open data. Therefore,
a problem with discoverability of the data catalogs and the individual datasets
described in them arises, and along with it a need for aggregate views over
multiple data catalogs. To address this need, a standard for representation of dataset
metadata, the Data Catalog Vocabulary (DCAT) [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], was developed by the W3C
to enable dataset metadata exchange among data catalogs, and specifically to
support hierarchies of catalogs. In the European Union, an application profile of
DCAT, the DCAT-AP v1.12, has been developed, further specifying for instance
controlled vocabularies to be used to describe datasets and their distributions.
At the same time, a top level European data catalog, the European Data Portal
(EDP)3, has been developed with the intent of aggregating data catalogs from
the whole EU.
      </p>
      <p>In the Czech Republic, the Ministry of the Interior (MoI) is in charge of the
open data agenda. The NODC is run by the MoI, and the public administration
institutions can either register their datasets directly in the NODC, or,
preferably, they can run their own Local Open Data Catalog (LODC) which, after
registration, gets automatically harvested to the NODC. Unfortunately, until
now, the MoI did not consider DCAT-AP v1.1 as a metadata publishing format.
The NODC internal data model was inspired by the DCAT-AP v1.0, however,
it is XML based and accessible only via a proprietary XML API. In addition,
the metadata registered in the NODC was only viewable to users via a rather
unfriendly user interface.</p>
      <p>
        As the NODC became known and used, new requirements on its functionality
arose, mainly the need to monitor dataset metadata quality, and the need to
be harvested by the EDP. To address these requirements, we first transform the
current NODC metadata to the DCAT-AP v1.1 RDF representation and publish
it. Then we use this new representation to compute the dataset metadata quality
measurements and to facilitate the harvesting of the NODC metadata by the
EDP. Similar requirements are identified also elsewhere, e.g. in Serbia [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], as
requirements to implement the revised European Directive on the Public Sector
Information (2013/37/EU) emphasizing the role of the Linked Data approach
for improved interoperability and re–use.
1 https://www.europeandataportal.eu/en/highlights/
      </p>
      <p>economic-benefits-open-data
2 https://joinup.ec.europa.eu/release/dcat-ap-v11
3 https://www.europeandataportal.eu</p>
    </sec>
    <sec id="sec-2">
      <title>Contributions</title>
      <p>
        In the journal paper [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] we describe the NODC and its architecture, data
input, data model, its API and the mechanism of harvesting the metadata from
LODCs to the NODC. We describe how we transform the current metadata
to the DCAT-AP v1.1 RDF representation both from the data model point of
view and from the technical environment point of view. We show the metadata
quality measures that we compute using the DCAT-AP v1.1 representation and
we evaluate further impact this new metadata representation has, including a
new frontend for viewing the dataset metadata and the effects it has on the
Linked Open Data (LOD) environment. Finally, we evaluate the data
transformation environment from the usability, portability, availability and performance
perspectives.
1.2
      </p>
    </sec>
    <sec id="sec-3">
      <title>Outline</title>
      <p>
        The rest of this extended abstract is structured according to the original paper
[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], providing an outline of the paper by summarizing the contents of each of the
sections.
      </p>
      <p>In Section 2 we describe the NODC, its architecture, the processes of
harvesting LODCs, and its proprietary XML API. In Section 3 we describe the
data transformation to DCAT-AP v1.1 and the linking to related datasets and
code lists. In Section 4 we describe the technical environment used for the data
transformation and publication process. In Section 5 we describe data
quality measures which we compute based on the transformed data. In Section 6
we show additional impact of the published dataset by presenting some of the
known usages of the published data, which include harvesting by the European
Data Portal. In Section 7 we evaluate the data transformation and publishing
environment according to various criteria. Finally we survey related work and in
Section 8 we conclude.
2</p>
      <sec id="sec-3-1">
        <title>Czech National Open Data Catalog (NODC)</title>
        <p>The institutions in the Czech public administration are required to register their
published data in the Czech National Open Data Catalog (NODC) before they
can call it open data. There are two ways of registering to the NODC. For
smaller institutions such as village councils there is the possibility of registering
individual datasets directly in the NODC using a form to fill in all the necessary
metadata. For larger institutions such as ministries or city councils, there is the
possibility of registering their own local Open Data catalog (LODC), as there is
an assumption that such institutions will have their own data portals anyway.
Once a LODC is registered, the metadata from it is automatically and regularly
harvested by the NODC, giving the institutions more flexibility in their dataset
management. The registered datasets can be viewed in a rather unfriendly web
user interface, which does not provide many features known from wide-spread
data catalog implementations such as CKAN4 and DKAN5.
3</p>
      </sec>
      <sec id="sec-3-2">
        <title>Data modeling and transformations</title>
        <p>
          Our goal is to publish the dataset metadata from the NODC according to the
DCAT-AP v1.1 specification. The proprietary NODC XML API will serve as our
data source. In this section of the original paper [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] the RDF vocabularies used
in the transformed data and the legacy code lists and data items are showed and
mapped to the European Union Metadata Registry Named Authority Lists (EU
MDR NALs), now parts of EU Vocabularies6, and the RTIAR.
4
        </p>
        <p>
          Data transformation and publishing environment
In this section of the paper [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] we describe the technical environment used to
transform the data from the original NODC proprietary XML API to a
DCATAP v1.1 dataset published as Linked Open Data. The environment is built on
open-source tools.
        </p>
        <p>
          The transformation is done using LinkedPipes ETL [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ], which needs Java7
and Node.js8 to run, and Git9 and Apache Maven10 to build the source code
from the GitHub repository11.
        </p>
        <p>
          LinkedPipes ETL is an open-source ETL tool for production and
consumption of Linked Data, which is in use by multiple organizations in the Czech
public administration. It is also used in the OpenBudgets.eu platform [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ] for
publication and transformation of fiscal data. It runs the data transformation
process as a so called pipeline. The process is run daily, as that corresponds
to the periodicity of updates of the source NODC data. The pipeline has the
following principal steps:
1. Get metadata from the proprietary NODC XML API
2. Get the data box ID to publisher IRI and name mapping from the List of
public administration authorities dataset
3. Transform the metadata using an XSLT [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ] template
4. Map the ISO8601 frequencies to the Frequency EU MDR NAL
5. Add the File Type EU MDR NAL items based on distribution MIME Types
6. Get the previous DCAT-AP v1.1 dump and compare with the current version
to generate statistics about new, changed and deleted datasets using the
RDF Data Cube Vocabulary (DCV) [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]
4 https://github.com/ckan/ckan
5 https://getdkan.org/
6 https://publications.europa.eu/en/web/eu-vocabularies
7 https://www.oracle.com/java/index.html
8 https://nodejs.org
9 https://git-scm.com/
10 https://maven.apache.org/
11 https://github.com/linkedpipes/etl
7. Compute metadata of the DCAT-AP v1.1 dataset itself
8. Load an index to Apache Solr
9. Load the metadata records to Apache CouchDB
10. Load the RDF TriG dump to a web server
11. Load the RDF data to the SPARQL endpoint
12. Run the pipelines computing data quality measurements (see Section 5)
5
        </p>
      </sec>
      <sec id="sec-3-3">
        <title>Metadata quality measures</title>
        <p>
          In this section of the paper [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] we describe quality measures monitored using the
NODC loaded in a SPARQL endpoint. We distinguish two types of measures,
one is based solely on what can be found in the metadata itself. The second type
uses the metadata registered in NODC to try to access the linked resources, i.e.
licenses, schemas, documentation and the distributions themselves, and check
whether they are served correctly, e.g. with a correct Media Type. To compute
both types of quality measures, pipelines in LinkedPipes ETL are used. Since
the quality measures are based on the DCAT-AP v1.1 specification, they are
directly reusable for other DCAT-AP v1.1 compliant datasets.
5.1
        </p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Metadata based quality measures</title>
      <p>Since there is no validation of input data in the current NODC harvester of
LODCs, there are metadata records violating DCAT-AP v1.1 constraints or
constraints dictated by the Czech legislation. The first part of the quality
measures in this section aims at detecting such anomalies. In addition, there are
measures aiming at providing an overview of common practice. The results of
these measures are published on the Czech Open Data Portal12. The measures
are:
1. Number of distributions with unspecified license per publisher
2. Number of datasets with distributions with unspecified licenses per publisher
3. Number of datasets missing required attributes per publisher
4. List of datasets missing required attributes per publisher
5. Number of distributions with a given mime type per publisher
6. Distribution licenses per publisher
7. Number of publishers per license
8. Number of datasets with a given accrual periodicity per publisher
9. Number of datasets and distributions per publisher</p>
      <p>These measures were selected based on the most frequently appearing errors
in the metadata records. These erroneous records cause a decline in the overall
metadata quality in the NODC. When the users encounter them, they tend to
blame the NODC for the inconsistent looking record, therefore, it is important
to us that the publisher correct their records. This is also why it is important
12 https://opendata.gov.cz/statistika:datova-kvalita (in Czech only)
to consistently point out errors in the records and demand their correction.
From our experience, the most effective way to achieve the correction in the
(Czech) public administration is to publicly display the errors attributed to
the originating publishers, along with clear instructions on how to correct the
mistakes. The errors in the records also usually reveal a deeper problem with
data management at the original publisher.
5.2</p>
    </sec>
    <sec id="sec-5">
      <title>Web access based quality measures</title>
      <p>The measures listed in this section check whether the resources linked from the
metadata records actually exist, and whether they are served correctly. There
are four types of resources linked from the metadata, i.e. distributions, licenses,
dataset documentation and distribution schema. For each of the four resource
types we compute a summary statistic and a list of offending resources.</p>
      <p>Here, we list the quality measures along with the description of the individual
columns in the result.
1. Statistics of unavailable dataset distributions per publisher
2. List of unavailable distributions
3. Statistics of unavailable schemas of dataset distributions per publisher
4. List of unavailable distribution schemas
5. Statistics of unavailable licenses of dataset distributions per publisher
6. List of unavailable distribution licenses
7. Statistics of unavailable documentation of datasets per publisher
8. List of unavailable dataset documentation</p>
      <p>In addition to the availability measures described above, there is one more
measure dealing with inconsistency between the distribution Media Type
registered in the NODC and the Media Type returned by the web server serving the
distribution.
6</p>
      <p>
        Additional impact of publishing NODC as Linked Open
Data using DCAT-AP v1.1
In this section of [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], we demonstrate the impact of publishing the NODC
contents as Linked Open Data according to the DCAT-AP v1.1 specification besides
us being able to compute the quality measures described in Section 5 by
describing the effects it has on the LOD environment.
6.1
      </p>
    </sec>
    <sec id="sec-6">
      <title>Promotion of Linked Open Data and usage of standardized vocabularies</title>
      <p>
        Theoretical advantages of LOD described in existing literature are not convincing
enough to the representatives of public administration institutions regarding
publishing their data as LOD. We are using the example of the NODC and others,
such as the Czech Social Security Administration [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], and the infrastructure
used to process the data and publish it as DCAT-AP v1.1 to convince other
institutions that publishing LOD is possible without excessive resources.
      </p>
    </sec>
    <sec id="sec-7">
      <title>Harvesting by the European Data Portal</title>
      <p>A clear added value of the DCAT-AP v1.1 representation of the NODC data is
the ability to be harvested by the European Data Portal (EDP), a well-known
pan-European open data catalog, using a native LOD way. In fact, this was
beneficial not only to the Czech publishers, as their metadata got published
on the European level, but also to the developers of the European Data
Portal. This is because the Czech NODC was the first European data portal to
publish the metadata using DCAT-AP v1.1 in RDF natively, i.e. as an RDF
data dump, dereferencable IRIs and a SPARQL endpoint. At the same time, the
Czech NODC is the largest catalog in EDP.
6.3</p>
    </sec>
    <sec id="sec-8">
      <title>Ability to use LinkedPipes DCAT-AP Viewer as frontend</title>
      <p>
        The original NODC viewer was quite unfriendly to the users. However, the
proprietary nature of the published metadata made it hard to convince someone
to develop an alternative frontend. Thanks to the transformation of the data to
DCAT-AP v1.1 [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] we are now able to use the LinkedPipes DCAT-AP Viewer
which is friendlier (based on System Usability Scale (SUS)13) and offers more
functionality than the original, including multilingual user interface exploiting
the multilingual EU MDR NALs where possible, full text search, keywords word
cloud, handling of large numbers of distributions, etc.
6.4
      </p>
    </sec>
    <sec id="sec-9">
      <title>Proof of need for a Linked Data Consumption Platform</title>
      <p>
        In our research group we are focusing not only on LOD publishing, but also LOD
consumption, where we identified a distinct lack of tools for actually using LOD
that is published [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. This lack of tools is proven every time we publish a new
dataset, as users are saying that they do not know how to consume LOD and
that they require data in formats they are used to, i.e. CSV, JSON and XML
files. The case with NODC was no different. After publishing the data in RDF
and in the SPARQL endpoint, some users demanded CSV exports of the data,
even though they could be obtained using a simple SPARQL SELECT query.
The users need a tool we call a Linked Data Consumption Platform (LDCP),
which would help them in consuming LOD, and ideally, it would be easier to use
than tools for consumption of CSV, JSON and XML files thanks to the benefits
LOD brings, and it may even not require any specific LOD related knowledge.
The users who demand those non-LOD representations of data then serve us as
motivation for our LDCP related efforts.
7
      </p>
      <sec id="sec-9-1">
        <title>Environment evaluation</title>
        <p>
          In this section of [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ], we evaluate the LOD publishing environment described in
Section 4 used by the Ministry of the Interior of the Czech Republic (MoI) to
13 https://www.usability.gov/how-to-and-tools/methods/
        </p>
        <p>
          system-usability-scale.html
prepare and publish the DCAT-AP v1.1 NODC RDF dataset. We evaluate the
environment using so called quality attributes as introduced in [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]. We evaluate
the following quality attributes:
– usability
– portability
– availability
– performance
8
        </p>
      </sec>
      <sec id="sec-9-2">
        <title>Conclusions</title>
        <p>The environment integrates various open-source tools. We do not evaluate
each individual tool but the environment as a whole.</p>
        <p>
          In the paper [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] we describe the current architecture of the Czech National Open
Data Catalog (NODC), starting from manual data entry, Local Open Data
Catalogs (LODCs) harvesting, data storage to data publication using its proprietary
XML API and a rather unfriendly viewer. Next we described the vocabularies
and codelists used in transformation of the NODC data to its DCAT-AP v1.1
RDF representation. We described the technical environment used for the data
transformation and data quality measures that can be computed using the RDF
data representation, both using LinkedPipes ETL. We describe the additional
impact of publishing NODC using DCAT-AP v1.1 and evaluate the data
transformation environment both from the perspective of the transformation designers
and from the perspective of the data users.
        </p>
        <p>During the time of writing the paper, the MoI changed their supplier of the
implementation of the original NODC, making it permanently unavailable, as
the new supplier was not able to take over the original implementation. This
nevertheless showed another benefit of publishing open data, as our copy of
the NODC used to demonstrate the transformation to DCAT-AP v1.1 and the
browsing of the data in LinkedPipes DCAT-AP Viewer remained the only
existing publicly available NODC instance. Currently, it is already running as the
official NODC instance at https://data.gov.cz.</p>
        <p>Finally, we conclude the paper with a summarization of the lessons learned
during our work with the MoI and publishers of open data in the Czech Republic.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Bass</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Clements</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kazman</surname>
          </string-name>
          , R.:
          <source>Software Architecture in Practice. AddisonWesley Professional</source>
          , 3rd edn. (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Clark</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>XSL transformations (XSLT) version 3.0</article-title>
          . W3C Recommendation,
          <source>W3C (Jun</source>
          <year>2017</year>
          ), https://www.w3.org/TR/1999/REC-xslt-19991116
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Erickson</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maali</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Data Catalog Vocabulary (DCAT)</article-title>
          .
          <source>W3C Recommendation</source>
          ,
          <source>W3C (Jan</source>
          <year>2014</year>
          ), https://www.w3.org/TR/2014/REC-vocab-dcat-
          <volume>20140116</volume>
          /
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Janev</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mijovic</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vranes</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Proposal for Implementing the EU PSI Directive in Serbia</article-title>
          . In: Ko,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Francesconi</surname>
          </string-name>
          , E. (eds.)
          <source>Electronic Government and the Information Systems Perspective - 5th International Conference, EGOVIS</source>
          <year>2016</year>
          , Porto, Portugal, September 5-
          <issue>8</issue>
          ,
          <year>2016</year>
          ,
          <source>Proceedings. Lecture Notes in Computer Science</source>
          , vol.
          <volume>9831</volume>
          , pp.
          <fpage>16</fpage>
          -
          <lpage>30</lpage>
          . Springer (
          <year>2016</year>
          ). https://doi.org/10.1007/978-3-
          <fpage>319</fpage>
          - 44159-
          <issue>7</issue>
          _2, https://doi.org/10.1007/978-3-
          <fpage>319</fpage>
          -44159-
          <issue>7</issue>
          _
          <fpage>2</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Klímek</surname>
          </string-name>
          , J.:
          <article-title>DCAT-AP representation of Czech National Open Data Catalog and its impact</article-title>
          .
          <source>Journal of Web Semantics</source>
          <volume>55</volume>
          ,
          <fpage>69</fpage>
          -
          <lpage>85</lpage>
          (
          <year>2019</year>
          ). https://doi.org/10.1016/j.websem.
          <year>2018</year>
          .
          <volume>11</volume>
          .001, http://www.sciencedirect.com/ science/article/pii/S1570826818300532
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Klímek</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kučera</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nečaský</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chlapek</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Publication and usage of official Czech pension statistics Linked Open Data</article-title>
          .
          <source>Journal of Web Semantics</source>
          <volume>48</volume>
          ,
          <fpage>1</fpage>
          -
          <lpage>21</lpage>
          (
          <year>2018</year>
          ). https://doi.org/10.1016/j.websem.
          <year>2017</year>
          .
          <volume>09</volume>
          .002, http://www. sciencedirect.com/science/article/pii/S1570826817300343
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Klímek</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Škoda</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>LinkedPipes ETL in use: practical publication and consumption of linked data</article-title>
          . In: Indrawan-Santiago,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Steinbauer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Salvadori</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.L.</given-names>
            ,
            <surname>Khalil</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.</given-names>
            ,
            <surname>Anderst-Kotsis</surname>
          </string-name>
          ,
          <string-name>
            <surname>G</surname>
          </string-name>
          . (eds.)
          <source>Proceedings of the 19th International Conference on Information Integration and Web-based Applications &amp; Services</source>
          , iiWAS
          <year>2017</year>
          , Salzburg, Austria, December 4-
          <issue>6</issue>
          ,
          <year>2017</year>
          . pp.
          <fpage>441</fpage>
          -
          <lpage>445</lpage>
          . ACM (
          <year>2017</year>
          ). https://doi.org/10.1145/3151759.3151809, https://doi.acm.
          <source>org/ 10</source>
          .1145/3151759.3151809
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Klímek</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Škoda</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <string-name>
            <surname>LinkedPipes DCAT-AP Viewer</surname>
          </string-name>
          :
          <article-title>A Native DCAT-AP Data Catalog</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>López</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            ,
            <surname>Srinivas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Fortuna</surname>
          </string-name>
          , C. (eds.)
          <source>Proceedings of the ISWC</source>
          <year>2018</year>
          <article-title>Posters &amp; Demonstrations, Industry and Blue Sky Ideas Tracks co-located with 17th International Semantic Web Conference (ISWC</article-title>
          <year>2018</year>
          ), Monterey, USA, October 8th - to - 12th,
          <year>2018</year>
          .
          <source>CEUR Workshop Proceedings</source>
          , vol.
          <volume>2180</volume>
          .
          <string-name>
            <surname>CEUR-WS.org</surname>
          </string-name>
          (
          <year>2018</year>
          ), http://ceur-ws.
          <source>org/</source>
          Vol-
          <volume>2180</volume>
          /paper-32.pdf
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Klímek</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Škoda</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nečaský</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>Requirements on Linked Data Consumption Platform</article-title>
          . In: Auer,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Berners-Lee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            ,
            <surname>Bizer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            ,
            <surname>Heath</surname>
          </string-name>
          , T. (eds.)
          <source>Proceedings of the Workshop on Linked Data on the Web, LDOW</source>
          <year>2016</year>
          ,
          <article-title>co-located with 25th</article-title>
          <source>International World Wide Web Conference (WWW</source>
          <year>2016</year>
          ).
          <source>CEUR Workshop Proceedings</source>
          , vol.
          <volume>1593</volume>
          .
          <string-name>
            <surname>CEUR-WS.org</surname>
          </string-name>
          (
          <year>2016</year>
          ), http://ceur-ws.
          <source>org/</source>
          Vol-
          <volume>1593</volume>
          / article-01.pdf
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Musyaffa</surname>
            ,
            <given-names>F.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Halilaj</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Li</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Orlandi</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jabeen</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Auer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vidal</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>OpenBudgets.eu: A Platform for Semantically Representing and Analyzing Open Fiscal Data</article-title>
          . In: Mikkonen,
          <string-name>
            <given-names>T.</given-names>
            ,
            <surname>Klamma</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            ,
            <surname>Hernández</surname>
          </string-name>
          ,
          <string-name>
            <surname>J</surname>
          </string-name>
          . (eds.) Web Engineering - 18th International Conference, ICWE 2018, Cáceres, Spain, June 5-8,
          <year>2018</year>
          ,
          <source>Proceedings. Lecture Notes in Computer Science</source>
          , vol.
          <volume>10845</volume>
          , pp.
          <fpage>433</fpage>
          -
          <lpage>447</lpage>
          . Springer (
          <year>2018</year>
          ). https://doi.org/10.1007/978-3-
          <fpage>319</fpage>
          -91662-0_
          <fpage>35</fpage>
          , https: //doi.org/10.1007/978-3-
          <fpage>319</fpage>
          -91662-0_
          <fpage>35</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Reynolds</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cyganiak</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          :
          <source>The RDF Data Cube Vocabulary. W3C Recommendation</source>
          ,
          <source>W3C (Jan</source>
          <year>2014</year>
          ), https://www.w3.org/TR/2014/ REC-vocab
          <article-title>-data-cube-20140116/</article-title>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>