<!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>The GeoKnow Generator Workbench - an Integrated Tool Supporting the Linked Data Lifecycle for Enterprise Usage</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Andreas Both</string-name>
          <email>andreas.both@unister.de</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Alejandra Garcia-Rojas</string-name>
          <email>alejandra.garciarojas@ontos.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Matthias Wauer</string-name>
          <email>matthias.wauer@unister.de</email>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Daniel Hladky</string-name>
          <email>daniel.hladky@ontos.com</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jens Lehmann</string-name>
          <email>lehmann@informatik.uni-</email>
          <email>lehmann@informatik.unileipzig.de</email>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Ontos A.G.</institution>
          ,
          <addr-line>Nidau</addr-line>
          ,
          <country country="CH">Switzerland</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Ontos A.G.</institution>
          ,
          <addr-line>Nidau</addr-line>
          ,
          <country country="CH">Switzerland</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>R&amp;D, Unister GmbH</institution>
          ,
          <addr-line>Leipzig</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>R&amp;D, Unister GmbH</institution>
          ,
          <addr-line>Leipzig</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>Universität Leipzig, AKSW</institution>
          ,
          <addr-line>Leipzig</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <fpage>92</fpage>
      <lpage>95</lpage>
      <abstract>
        <p>Linked Data promises to make data integration easier for academic and industrial use. However, performing such data integration tasks currently requires high investments because of several major challenges. Available tools are not connected to each other, access restrictions on private data and certain tools have to be enforced, processes have to be managable and easy to use, and, nally, data processing needs to be comprehensible in terms of provenance and traceability. The GeoKnow Generator Workbench solves these problems by providing an integrated Web interface on top of an extensible solution for easy access to tools dedicated to certain Linked Data lifecycle phases, also addressing major industrial requirements. While it focuses on geospatial aspects, it is generally applicable to Linked Data management tasks.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;linked data management</kwd>
        <kwd>data processing</kwd>
        <kwd>data publishing</kwd>
        <kwd>data provenance</kwd>
        <kwd>integrated workbench</kwd>
        <kwd>geospatial information systems</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. INTRODUCTION</title>
      <p>
        In the last decade, many open data sources have been
published following the Linked Data (LD) principles [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Today,
even some industrial applications are driven by LD (e.g., [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]).
Many LD data sources include geospatial attributes. In
general, geospatial data has a high relevance in everyday life
and is crucial for decision making and search applications.
For instance, being able to make use of demographics and
terrain data for strategic business planning, or improving
search engines for questions like " nd a good typical
restaurant in Vienna next to the Danube river". Finding answers
to such questions depends on appropriate preprocessing of
a combination of geospatial and related information.
The Linked Data lifecycle1 (c.f., Figure 1) is a blueprint for
extracting data from di erent types of sources,
interlinking with other datasets, enrichment, quality assurance, as
well as exploring and visualising it. Thus, it describes the
processes needed to make LD useable. Based on the LD
lifecycle, the GeoKnow Generator presented in this paper
enables a seamless integrated work ow and comprehensive
processing options, based on a variety of tools in a
modular workbench Web application, meeting industrial
requirements. Most of the integrated tools include speci c
functionality for working with geospatial data.
      </p>
      <p>The paper is organized as follows. We discuss primary
requirements in Section 2. The GeoKnow Generator
Workbench is presented in Section 3. Section 4 outlines
applications based on the proposed solution. Related work is
discussed in Section 5. Finally, the paper closes with the
conclusions and future work.</p>
    </sec>
    <sec id="sec-2">
      <title>2. REQUIREMENTS</title>
      <p>In this section, we describe the use cases and the related
derived requirements which led to the creation of the GeoKnow
Generator.
2.1</p>
    </sec>
    <sec id="sec-3">
      <title>Use Cases</title>
      <p>Tourism e-Commerce. In this use case by Unister2
internal data have to be enriched with public geospatial data in
order to improve online search applications. Thus, Unister
can understand user's search motives and support queries
beyond basic hotel features.</p>
      <sec id="sec-3-1">
        <title>1See http://stack.linkeddata.org/.</title>
      </sec>
      <sec id="sec-3-2">
        <title>2http://www.unister.com/</title>
        <p>Storage/
Querying
Quality</p>
        <p>Analysis
Linked Data</p>
        <p>Lifecycle
Search/
Browsing/
Exploration</p>
        <p>Classification/
Enrichment</p>
        <p>EvRoeluptaioirn /
Supply Chain. In order to visualize key information of the
logistics in a supply chain, information from supply chain
transactions have to be connected to related LD. As a result,
the ow of material and accompanying information can be
observed in real-time, bottlenecks can be identi ed early,
media breaks in the information ows are minimised. This
use case by a large automotive company incorporates tra c,
weather, and transport information, which is linked to the
supply chain information.</p>
        <p>E-Government Services. The Linked Data Service3
(LINDAS) has the objective to provide information about
authorities. Their services and software solutions are collected
decentralised by the Swiss Confederation, the cantons or
communes. The service gathers, homogenises, and publishes
authority data using Semantic Web standard.</p>
        <p>Automotive Data Investigation. Geosocial networks for
sharing location-based messages, such as recommendations
and noti cations, bene t from providing context-related
information. For services like community-based truck
networks developed by Continental Automotive GmbH,
relevant geospatial LD has to be ltered and selected, e.g.,
motorway service areas. Of future interest are further touristic
information, such as museums and playgrounds, which are
readily available in public data sets.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>2.2 Requirements</title>
      <p>Concerning functional requirements, the primary
functionality of tools for LD lifecycle phases has to be extended
towards geospatial data, e.g., by implementating geospatial
distance metrics for interlinking and fusing datasets, and
appropriate quality metrics. In addition, non-functional
requirements include:</p>
      <p>Scalability for working with large data sets
Authentication, Authorization and Role Management
as a primary requirement in companies
Data Provenance tracking for tracability of changes
Job Monitoring and Robustness for applicability in
production
Modularity and Composability in order to provide
exibility w.r.t. integrating additional tools</p>
    </sec>
    <sec id="sec-5">
      <title>3. GEOKNOW GENERATOR</title>
      <p>The GeoKnow Generator is a stack of tools for data
preparation following the LD lifecycle. The GeoKnow Generator
Workbench is the common entry point of all those tools. The
actual architecture is presented in Figure 2. This diagram
re ects the stack of tools integrated for each stage of the LD
lifecycle. This architecture lays on following three pillars:
Software integration and deployment using the Debian
packaging system. This infrastructure facilitates the
packaging and integration as well as the maintenance of
dependencies between the various components. Using
the Debian system also enables the deployment on
individual servers or cloud infrastructures.</p>
      <p>Use of a central SPARQL endpoint and standardized
vocabularies for knowledge base access and integration
between the di erent tools. All components can
access this central knowledge base repository and write
their data back to it. In order for other tools to make
sense out of the information it is important to de ne
vocabularies for each of the stages of the LD lifecycle.
Integration of the user interfaces based on REST enabled
Web applications. Currently the user interfaces of the
various tools are technologically and methodologically
heterogeneous. Thus, a common entry point for
accessing the tools can forward a user to a speci c UI
component provided by a certain tool in order to
complete a certain task. For tools that do not provide an
interface, extra development e ort is needed.</p>
      <p>For integrating components, some JavaScript and basic RDF
editing are required. Speci cally, the AngularJS framework4
is used for straight-forward creation of GUIs and application
routing. A more detailed description of the GeoKnow
Generator Workbench and how to integrate components can be
found in the repository wiki5.</p>
      <sec id="sec-5-1">
        <title>4https://angularjs.org/</title>
      </sec>
      <sec id="sec-5-2">
        <title>5https://github.com/GeoKnow/GeoKnowGeneratorUI/</title>
        <p>wiki
Table 1 describes the actual software tools integrated in the
GeoKnow Generator Workbench. Besides these integration
work, the main bene ts of the GeoKnow Generator
Workbench are the following features: (1) Authentication and
Role Management: Access to di erent components can be
restricted via the Workbench using roles. (2) Authorisation:
A graph-based security access control allows users to
create and con gure public and user-speci c access control to
datasets. For components accessing private graphs,
Crossorigin resource sharing (CORS) and proxy-based model is
provided. (3) Job Monitoring: For some of the software
tools, which can have long runtime on large-scale input,
the user can execute batch jobs that are con gured and
observable in a dashboard (Figure 3b). (4) Data Provenance:
When working with several datasources and di erent
processing stages, it is required to keep information about the
provenance of certain triples. The Workbench adds
metadata about the tools used to process these data, timestamp,
and authors. (5) Scalability: Storage scalability is supported
thanks to Virtuoso Cluster edition. Workbench and
integrated tools can be easly scaled out to di erent nodes.
All software tools used in the GeoKnow Generator
Workbench and the GeoKnow Generator Workbench itself are
availeble in the LD Stack6 repositories. The LD Stack is an
independent project that aims to ease the distribution and
installation and integration of LD tools developed in di ernt
research projects. GeoKnow project is an active contributor
and supporter of the LD Stack.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>4. APPLICATION IN USE CASES</title>
      <p>In the Tourism e-Commerce use case, the GeoKnow
Generator Workbench has been applied to generate an interlinked
dataset used for a motive-based search infrastructure.
External datasets have been transformed to RDF using
Triple</p>
      <p>Geo and Sparqlify. The linking of external data and
internal data was performed using LIMES with immense
performance gains compared to a comparable custom approach.
Besides integration of structured data, unstructured data
such as hotel reviews can be processed using DEER. That
way, related entities can be identi ed and integrated so their
attributes (such as locations) can be used for further analysis
of places, providing useful information for a search engine.
In the Supply Chain use case, a Dashboard (see Figure 3a)
o ers a uni ed spatial view on the logistics in the supply
chain. Companies can bene t from the Supply Chain
Dashboard by gaining a better picture of the current state of the
supply chain and the spatial distribution of goods and
products in the supply chain. The required data integration and
linking were enabled by the Sparqlify and LIMES
components of the Workbench. The resulting information allows
live visualisation of orders and shipments status in the
Dashboard. Circulated messages and a supplier score card
provide live analytics of the supply chain based on user-de ned
metrics.</p>
      <p>Continental products DropYa and TruckYa use GeoKnow
technology in the Automotive Data Investigation use case.
DropYa is a geosocial network where users can send and
receive location-based messages sharing their experience and
recommendations. TruckYa is a community-based tool for
nding adequate parking spaces aimed at truck drivers. In
the investigation process of assessing LD sources, Facete
provides the functionality to browse data on a map, view
attributes of interest, export relevant parts and support the
editorial process.</p>
      <p>The Ontos AG7 Linked Data Information Workbench
(OntosLDIW) is a generic, enterprise-ready workbench on the
GeoKnow architecture supporting the LD Lifecycle.
OntosLDIW was applied to a real world e-government scenario
for the State Secretariat for Economic A airs (SECO) in
Switzerland8. The developed Linked Data Service
(LINDAS) has centralized the tasks of the data scientist into one
common workbench allowing to orchestrate, monitor and
execute processes from one standardized UI. Thus, it reduces
the e orts to learn various tools and front ends, improves
e ciency, and reduces costs.</p>
      <p>As generalized feedback from these use case applications,
an integrated workbench brings the bene t of orchestrating
the process from a single point of view. It reduces the time
required for learning and switching between tools, and it
reduces the interface and data exchange through a single
point of access and common UI.</p>
    </sec>
    <sec id="sec-7">
      <title>5. RELATED WORK</title>
      <p>
        The LOD2 Statistical Workbench [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] provides an integrated
set of tools from the LD Stack for o cial statistical
production processes of governments. The workbench supports
many di erent operations. This solution is suitable for a
speci c use case but lacks the general applicability of a more
con gurable approach. Uni edviews[
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] is a LD processing
      </p>
      <sec id="sec-7-1">
        <title>7http://ontos.com/ 8http://www.seco.admin.ch/?lang=en</title>
        <p>
          (a) The supply chain dashboard.
(b) Task monitoring dashbord.
framework created under the EU project COSMODE9
using components from the LD Stack. This platform requires
implementing Data Processing Units for each component in
order to be integrated. Moreover, Uni edviews doesn't
provide support for authentication or authorisation features.
Still, it represents a relevant reference point for the
GeoKnow Generator Workbench. [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ] presents a workbench for
publishing geospatial linked data. In contrast to our work,
the data processing is highly specialized and does not
provide solutions for all steps of the LD lifecycle.
        </p>
      </sec>
    </sec>
    <sec id="sec-8">
      <title>6. CONCLUSIONS AND FUTURE WORK</title>
      <p>The main contribution of this paper, presented in 3, is the
GeoKnow Generator Workbench, which is a web-based user
interface that integrates all components needed for
processing data following the LD lifecycle. It enables simple access
and interaction with the di erent components needed for
di erent tasks. Moreover, it provides APIs for being
integrated into other systems and to exchange the components
currently available out-of-the-box. Future tools can be
integrated easily. An online demo and video tutorials of the
Workbench are available at http://generator.geoknow.eu.
We described the GeoKnow Generator and the main
features enabling an enterprise use. All requirements, including
those w.r.t managing geospatial data, are derived from real
world use cases, which also demonstrate the usability of the
Generator components and the Workbench in enterprise
environments. In the future we will integrate additional tools
and decouple the Workbench from Virtuoso.</p>
      <p>Acknowledgments.</p>
      <p>This work is part of the European Commission FP7 Project
GeoKnow (GA No 318159).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Mappify</surname>
            <given-names>:</given-names>
          </string-name>
          <article-title>a tool to easily create interactive maps backed by semantic web technologies</article-title>
          . http://mappify.aksw.org/.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Sparqlify</surname>
            <given-names>:</given-names>
          </string-name>
          <article-title>a sparql-sql rewrite</article-title>
          . http://aksw.org/Projects/Sparqlify.html.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>C.</given-names>
            <surname>Bizer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Heath</surname>
          </string-name>
          , and
          <string-name>
            <given-names>T.</given-names>
            <surname>Berners-Lee</surname>
          </string-name>
          .
          <article-title>Linked data-the story so far</article-title>
          .
          <source>Semantic Services, Interoperability and Web Applications: Emerging Concepts</source>
          , pages
          <volume>205</volume>
          {
          <fpage>227</fpage>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>G.</given-names>
            <surname>Giannopoulos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Skoutas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Maroulis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Karagiannakis</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Athanasiou</surname>
          </string-name>
          .
          <article-title>Fagi: A framework for fusing geospatial rdf data</article-title>
          .
          <source>In On the Move to Meaningful Internet Systems: OTM 2014 Conferences</source>
          , volume
          <volume>8841</volume>
          of Lecture Notes in Computer Science, pages
          <volume>553</volume>
          {
          <fpage>561</fpage>
          . Springer,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>V.</given-names>
            <surname>Janev</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B. V.</given-names>
            <surname>Nu elen</surname>
          </string-name>
          , V. Mijovi,
          <string-name>
            <given-names>K.</given-names>
            <surname>Kremer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Martin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>U.</given-names>
            <surname>Milosevi</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Vrane</surname>
          </string-name>
          .
          <article-title>Supporting the linked data publication process with the lod2 statistical workbench</article-title>
          .
          <source>Semantic Web ^aAS Interoperability</source>
          , Usability, Applicability,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>T.</given-names>
            <surname>Knap</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Kukhar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Machac</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Skoda</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Tomes</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Vojt</surname>
          </string-name>
          .
          <article-title>Uni edviews: An ETL framework for sustainable RDF data processing</article-title>
          . In The Semantic Web:
          <article-title>ESWC 2014 Satellite Events - ESWC 2014 Satellite Events</article-title>
          , Anissaras, Crete, Greece, May
          <volume>25</volume>
          -29,
          <year>2014</year>
          , Revised Selected Papers, pages
          <volume>379</volume>
          {
          <fpage>383</fpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>G.</given-names>
            <surname>Kobilarov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Scott</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Raimond</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Oliver</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Sizemore</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Smethurst</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Bizer</surname>
          </string-name>
          , and
          <string-name>
            <given-names>R.</given-names>
            <surname>Lee</surname>
          </string-name>
          .
          <article-title>Media meets semantic web{how the bbc uses dbpedia and linked data to make connections</article-title>
          .
          <source>In The semantic web: research and applications</source>
          , pages
          <volume>723</volume>
          {
          <fpage>737</fpage>
          . Springer,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>A.-C. N.</given-names>
            <surname>Ngomo</surname>
          </string-name>
          .
          <article-title>Orchid - reduction-ratio-optimal computation of geo-spatial distances for link discovery</article-title>
          .
          <source>In International Semantic Web Conference</source>
          , pages
          <volume>395</volume>
          {
          <fpage>410</fpage>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>K.</given-names>
            <surname>Patroumpas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Alexakis</surname>
          </string-name>
          , G. Giannopoulos, and
          <string-name>
            <given-names>S.</given-names>
            <surname>Athanasiou</surname>
          </string-name>
          .
          <article-title>Triplegeo: an etl tool for transforming geospatial data into rdf triples</article-title>
          .
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>A.</given-names>
            <surname>Shaon</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Woolf</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Boczek</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Rogers</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Jackson</surname>
          </string-name>
          .
          <article-title>An Open Source Linked Data Framework for Publishing Environmental Data under the UK Location Strategy</article-title>
          , volume
          <volume>798</volume>
          .
          <source>CEUR Workshop Proceedings</source>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>M.</given-names>
            <surname>Sherif</surname>
          </string-name>
          , A.
          <string-name>
            <surname>-C. Ngonga Ngomo</surname>
            , and
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Lehmann</surname>
          </string-name>
          .
          <article-title>Automating RDF dataset transformation and enrichment</article-title>
          .
          <source>In 12th Extended Semantic Web Conference</source>
          , Portoroz, Slovenia, 31st May - 4th
          <source>June 2015</source>
          . Springer,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>C.</given-names>
            <surname>Stadler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Martin</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Auer</surname>
          </string-name>
          .
          <article-title>Exploring the web of spatial data with facete</article-title>
          .
          <source>In Proceedings of the companion publication of the 23rd international conference on World wide web companion</source>
          , pages
          <volume>175</volume>
          {
          <fpage>178</fpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>