<!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>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Frederik Simon Bäumer</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Michaela Geierhos</string-name>
          <email>geierhos@hni.upb.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jangwon Gim*</string-name>
          <email>jangwon@kisti.re.kr</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Hanmin Jung</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Do-Heon Jeong</string-name>
          <email>heon@kisti.re.kr</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Heinz Nixdorf Institute, HNI, University of Paderborn</institution>
          ,
          <addr-line>Paderborn</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Korea Institute of Science and, Technology Information, KISTI</institution>
          ,
          <addr-line>Daejeon</addr-line>
          ,
          <country country="KR">South Korea</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2014</year>
      </pub-date>
      <fpage>8</fpage>
      <lpage>10</lpage>
      <abstract>
        <p>In this paper, we present a system which makes scientific data available following the linked open data principle using standards like RDF und URI as well as the popular D2R server (D2R) and the customizable D2RQ mapping language. Our scientific data sets include acronym data and expansions, as well as researcher data such as author name, affiliation, coauthors, and abstracts. The system can easily be extended to other records. Regarding this, a domain adaptation to patent mining seems possible. For this reason, obvious similarities and differences are presented here. The data set is collected from several different providers like publishing houses and digital libraries, which follow different standards in data format and structure. Most of them are not supporting semantic web technologies, but the legacy HTML standard. The integration of these large amounts of scientific data into the Semantic Web is challenging and it needs flexible data structures to access this information and interlink them. Based on these data sets, we will be able to derive a general technology trend as well as the individual research domain for each researcher. The goal of our Linked Open Data System for scientific data is to provide access to this data set for other researchers using the Web of Linked Data. Furthermore we implemented an application for visualization, which allows us to explore the relations between single data sets.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Categories and Subject Descriptors</title>
      <sec id="sec-1-1">
        <title>D.2.12 [Interoperability]: Data mapping E.2 [Data Storage Representations]: Linked representations</title>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>1. INTRODUCTION</title>
      <p>The increase in the number of datasets including scholarly
publications in the Linked Data cloud shows the importance of
Linked Data for the scientific community. There are many
different providers for scientific data available on the Web.
Publishing houses, digital libraries, and resellers have popular
data sources. The information types range from author
information (e.g. full name, affiliation, email), over publications
(e.g. title, abstract, coauthors), to specific data like acronyms and
their related expansion. Each of these types has own requirements
on the data presentation and storage, but they all are somehow
interlinked with each other.</p>
      <p>One common way to represent this interlinks are network models.
This database model is a generalized graph structure without any
hierarchical restriction, which allows storing objects with their
individual relationships. This is a common way to store data, but
does not fit our requirements for modern data publishing.
A more promising way to share data is the Web of Linked Data.
The main idea of Linked Open Data (LOD) is to publish free
accessible, structured data and to interlink it with other data. This
interlinking generates more valuable information under the
consequent implementation of standard Web technologies such as
RDF or URI. The core benefit for further data exploration is the
ability to apply complex graph queries, which allow the
interlinking, combining and modifying of data.</p>
      <p>For publishing scientific data stored in relational databases, a data
bridge is needed. For that reason we present our three-component
LOD system for scientific data sets, based on the popular D2R
server and the customizable D2RQ mapping language. For further
data exploration, we integrated RelFinder, an application that
visualizes relationships between RDF objects enables the
exploration of data interactively. We will demonstrate the
functionalities of our system on a test set.</p>
    </sec>
    <sec id="sec-3">
      <title>2. RELATED WORK</title>
      <p>
        A lot of work regarding Linked Open Data and the Semantic Web
is already done. Popular tools like the D2R server or standards
like RDF, HTTP and SPARQL are well proved and used in many
LOD systems [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
      <p>
        A major technological advantage is the backward compatibility,
for example, to relational databases (RDB) because the majority
of data on the current Web is stored in this kind of databases. The
process of mapping RDB to RDF is subject of current research
and different approaches like D2RQ, Triplify or R2RML were
created [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. R2RML currently developed by the W3C with the
main goal to define a RDB to RDF mapping standard for
readonly data access. A different approach is Triplify. It is a very
lightweight plugin for existing Web applications, which makes
database content available as RDF and other formats.
      </p>
      <p>
        RDB to RDF mapping can be done by applications such as D2R
server. It is a java-based application for publishing the content of
relational databases on the Semantic Web and for providing RDF
and HTML representations of resources. The D2RQ language is
used for the mapping, which is popular because of the possibility
to provide access via SPARQL queries very easily [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
The ability to interlink resources under the use of “typed
relationships” allows a goal-oriented navigation trough the
database content by web browsers as well as crawler applications
[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Because these LOD systems and components are very
flexible, it is possible to adapt them to different domains.
Interlinked User-generated content from social networks, a Linked
Open Drug Data (LODD) for pharmaceutical research and
development or a LOD live database of semantically enriched
sensor data, are only few successful examples, using the D2R
server [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>
        Latif, Afzal and Maurer [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] utilized the D2R server to publish
unstructured datasets of the Journal of Universal Computer
Science (J.UCS) as Linked Data in the Web. The linked Open
Data project provides a new way to publish machine readable
structured data on the Web and best practices for interlinking
these structured datasets. Moreover, the increase in the number of
datasets including scholarly publications in the Linked Data cloud
shows its importance in the scientific community. In order to take
advantage of benefits of LOD projects, the legacy HTML data in
this journal is converted into machine-readable and structured
RDF data using the D2R server. It is considered to be an
appropriate for data conversion due to its good performance,
scalability and the availability of SPARQL endpoint and explorer
features. A RDF graph converted from the legacy HTML data has
been made available in Linked Data cloud for the data reuse and
interlinking. Moreover, structured journal data was interlinked
with Linked Data resources and it successfully disambiguated and
interlinked datasets of authors and publications with DBpedia,
DBLP and Faceted DBLP as well as CiteULike.
      </p>
      <p>
        In addition, Mitrevski, Javanovik and Stonjanov [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] identified
some issues regarding the D2R server, which appear during the
process of publishing the open data of the faculty of computer
science and engineering in Ss. Cyril and Methodius University.
One problem is that these relational databases include some
confidential data about employees and students. However, the
D2R server does not provide a way to convert only specific parts
from the database into data in a semantic web format. Moreover,
it lacks of functionality enabling the user to link existing
ontologies to the tables. These issues can be solved by creating a
new database called Open Data DB including only the data with
no privacy infringement as well as building the mapping tool
utilizing functionalities of the D2R server, but linking the data
with ontologies. Although a mapping tool was created, the study
presents some improvements of this system such as automatic
proposal ontology annotations.
      </p>
      <p>
        For a structured representation of semantically annotated data and
a more intuitive exploration, RelFinder has been created by Heim
et al. The main idea is that a structured representation of RDF data
opens up new possibilieties in the way they can be accessed and
queried. For that purpose, a force-directed graph layout which
supports every RDF know-ledge base, that provides standardized
SPARQL access, is implemented [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. Relationships between
objects can be identified much easier by exploring the data step by
step. Features like highlighting, previewing, and filtering are
available for further support [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. The class filter and the link filter
allow it to hide objects which contain specific classes or links.
Primary these are objects, which are in this particular case not of
interest. In addition to these, the length filter and the connectivity
filter allow a further selection by hiding objects with a specific
amount of links and relationships [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
      <p>
        RelFinder is often used as stand-alone application but also as
integrated visualization application. It is for example part of the
DBpedia Viewer, an integrative interface for DBpedia, which
combines LodLive as one more different visualization approaches
next to RelFinder. The LodLive application is a web-based tool
that allows the exploration of Linked Data in an intuiitive and
interactive way [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. In comparison, both applications provide a
good visualization. RelFinder can convince with a higher browser
compatibility. Especially when using the Internet Explorer,
LodLive throws JavaScript errors drawing several relations
between classes.
      </p>
    </sec>
    <sec id="sec-4">
      <title>3. LOD SYSTEM FOR SCIENTIFIC DATA</title>
      <p>The scientific data sets are collected from different resources and
based on different formats. For that reasons, it is a difficult task to
combine information such as researchers, affiliations or
publications and to provide them as a clean, interlinked data set
under the requirements of quality. To make a contribution to the
existing Web of Linked Data, it is necessary to publish it in a
standardized, structured way under the use of common
vocabularies and over a common server framework. Furthermore,
it has to be identified which information can be bundled to a data
set containing relevant data and how this data can be usefully
interlinked. For this reason, we developed a LOD system for
scientific data sets, which can handle all related information like
researcher data or publications and publish them in a structured
way under the use of common semantic web technologies like
RDF and SPARQL. The interlinked data becomes more useful
and can be easily adapted to other research topics.</p>
    </sec>
    <sec id="sec-5">
      <title>3.1 System architecture</title>
      <p>The system architecture in Figure 1 can be divided in three main
components. The first component contains the datasets, which
include the specific data, as a result of different acquisition and
preprocessing steps we applied before. Because these data sets are
stored in a relational database, a Linked Data view on the existing
database is needed (data bridge). A SPARQL endpoint with the
ability for serving Linked Data views on relational databases is
D2R Server, which is part of the second step.</p>
      <p>We chose D2R, because it is one of the most important and most
mature relevant solutions.</p>
      <p>The second step, called “Linked Data System”, is responsible for
the declarative mapping between the schemata of the database and
the target RDF terms, based on mapping rules. These rules are
stored in mapping files and are formalized under the use of the
popular D2RQ mapping language. Each rule defines in detail how
resources are identified and how they have to be handled (e.g. find
property values) in the SPARQL endpoint. SPARQL is a strong
query language for databases, which allows it to access and to
modify RDF data. The Endpoint in the third step is able to
translate SPARQL based queries into SQL queries, which allows
a live database access, even for non-SQL compatible applications.
The “Application System” is the third step. It allows exploring the
data sets visually. With this application, researchers can find new
latent interconnections in the database, like for example an
exceptionally usage of rare acronyms by an individual author.
This exploring is based on the RDF query language SPARQL
from the second step.</p>
    </sec>
    <sec id="sec-6">
      <title>3.2 Data Set</title>
      <p>Digital resources like the Digital Bibliography &amp; Library Project
(DBLP) and publishing houses like Springer, IEEE or Elsevier
serve as data providers. Unfortunately, like already mentioned, the
data quality is inconsistent between the data providers. For that
reason, several refinement steps were applied to the data set,
especially for the ambiguity detection. During the work is still in
process, we plan to apply more algorithms for named entity
disambiguation under the goal of an increasing data set quality.
The researcher data set contains 8,370,074 publications like PhD
theses, articles or online resources. These publications come with
additional information, for example abstracts, author names,
coauthors, year of publication and affiliations. Furthermore, we
identified acronyms as well as the individual expansion based on
publication’s abstracts. This information is also part of the
researcher data set, because they can support a future
disambiguation of researchers. One of our research subjects
applied on these datasets is for example the detection of
technology trends and the identification of the research domain of
individual researchers. Trough the data visualization, we expect to
find more latent relationships between objects and classes, which
allow us to disambiguate single named entities.</p>
    </sec>
    <sec id="sec-7">
      <title>3.3 Common vocabularies</title>
      <p>Common vocabularies are necessary to enhance the
interoperability between concepts. For that reason we use them, as
far they already exist and exactly describe the data field.
For the interlinking of the data and the automatic processing, the
exact description of an attached common vocabulary is very
important. For person related information we use for example the
schema.org types and properties.</p>
      <p>One example for a prefix is “dc”, which is commonly used for the
Dublin Core Meta Initiative Terms (http://www.dublincore.org).
We introduced “sch” as another prefix, which describes the
schemas of schema.org (http://www.schema.org). For the data
field “Acronym”, “Element type” and “Expansion” no fitting
vocabularies are known at the moment. Because of that, we
introduced our own “InSciTe” prefix and related properties. They
may be replaced during the further working process and should be
seen as temporary.</p>
      <sec id="sec-7-1">
        <title>Acronym</title>
      </sec>
      <sec id="sec-7-2">
        <title>Affiliation</title>
      </sec>
      <sec id="sec-7-3">
        <title>Author</title>
      </sec>
      <sec id="sec-7-4">
        <title>Coauthor</title>
      </sec>
      <sec id="sec-7-5">
        <title>Editor</title>
      </sec>
      <sec id="sec-7-6">
        <title>Editor Email</title>
      </sec>
      <sec id="sec-7-7">
        <title>Authors Email</title>
      </sec>
      <sec id="sec-7-8">
        <title>Expansion</title>
      </sec>
      <sec id="sec-7-9">
        <title>Source URL</title>
      </sec>
      <sec id="sec-7-10">
        <title>Title</title>
      </sec>
      <sec id="sec-7-11">
        <title>Year of publication</title>
      </sec>
      <sec id="sec-7-12">
        <title>Element type (e.g. journal)</title>
      </sec>
      <sec id="sec-7-13">
        <title>InSciTe:ElementType</title>
      </sec>
    </sec>
    <sec id="sec-8">
      <title>3.4 Design of URIs</title>
      <p>Linked data is based on URIs which identify things and enable
users and computer-based agents to refer to these things or look
them up. In this case URIs identify entities like researchers and
show their relationships to other researchers or publications.
The D2R server is managing the URIs mostly automatically. For
the class overview pages, we applied the following structure:
“http://{ip}:{port}/directory/{classname}s”</p>
      <sec id="sec-8-1">
        <title>For individual resources like researcher we applied:</title>
        <p>“http://{ip}:{port}/page/{classname}/{id}”</p>
      </sec>
    </sec>
    <sec id="sec-9">
      <title>4. IMPLEMENTATION</title>
      <p>In this section, we explain the current state of the system’s
implementation, including the D2R server and the RelFinder
visualization.</p>
    </sec>
    <sec id="sec-10">
      <title>4.1 Test data set</title>
      <p>
        For this project, we created a test set of 60 researchers and 400
related publications as well as 454 publication-related acronyms
and expansions. Researchers were selected by their number of
publications, which has to be at least two. KISTI has diverse
scientific data sets, which are derived from papers, patents and
others. In order to find more valuable relationships from those
data sets, we extracted acronyms and expansions. The number of
test data is 491,982. Using these acronyms and expansion we can
apply these data sets to analyze technology trend and we can find
specific researchers who can be an expert about these acronyms or
expansions [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. The average number of expansion about an
acronym is 2.9. We observed that the distribution of expansions
follows Zipf’s law. We separated each acronym name based on its
semantics because an acronym name can be ambiguous. Therefore,
each expansion name can have its own acronym name and its own
URI. In order to get more valuable analysis reports by using
acronyms and their expansions, we have to create relationships
between these data sets and other resources such as Linked Open
Data, SNS data, Freebase, DBPedia and others. Finally, we get
more information from those relationships.
      </p>
    </sec>
    <sec id="sec-11">
      <title>4.2 DataHub System based on LOD</title>
      <p>The publications view is shown in Figure 2. This view contains
information concerning the publication itself, but also further
information like coauthors, which have the property
“sch:contributor” or acronyms. There are two detected acronyms,
which are interlinked with an own class. This class contains the
expansion and another related publication, which also contains
this acronym in the same meaning. This allows us to find related
publications based on acronyms as a first indication for the
following classification.</p>
      <p>Furthermore, the email address of the main author is shown. It is
part of the publication, because email addresses can change from
publication to publication. During the work is still in process, the
“sch:editor” data field is not finished yet, because it contains more
than one author divided by a pipe symbol. This will be part of the
following work. Figure 3 shows for example the person view,
which contains information about a specific researcher.
In this case the researcher has one publication which is interlinked
by the “is dc:creater of” property. Furthermore an email address
and the affiliation are given. The affiliation data field is subject of
our current work, because more standardization and comparability
is needed in order to interlink this data field. The acronyms are
interlinked within an own class, which contains the expansion and
other related publication.</p>
      <p>An example graph made by RelFinder’s visualization application
is shown in Figure 4. Instead of an additional HTTP server like
Apache, we implemented the RelFinder application in the already
existing D2R web server. That way, no difficult setup is needed in
order to start our system – all components are loaded during
program’s initiation.
Here, we added two researcher resources and one acronym. An
edge shows the relation between two RDF objects in a
unidirectional way. RelFinder looks up the relations between
these resources and draws a graph. In this example, the two
researchers have one publication in common (red relation). Or in
other words: Both researchers are creators (authors) of this
publication. Furthermore the acronym is related to the second
researcher trough another paper.</p>
      <p>To build this relations, a n:m database table is needed, which
contains one identifying ID for the publication and one for the
author, which we call ‘sequence number’. The D2R server
interlinks the affiliation data with the publication data, based on
this additional table. This table has to be extended for all
publications and researchers as part of the further research.</p>
    </sec>
    <sec id="sec-12">
      <title>5. TRANSFERABILITY</title>
      <p>
        Because of the open architecture, this system can easily be
adapted to other domains. In recent years, patent mining has
gained in popularity. Considerations for data acquisition and data
providing were investigated considering several aspects [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ][
        <xref ref-type="bibr" rid="ref15">15</xref>
        ].
The use of RDF technology is also discussed in the area of patent
mining and implemented, for instance, as information retrieval
system for biomedical patents by Mukherjea and Bamba [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ].
Furthermore, it visualizes the connections between patents, but
does not allow any user interaction.
      </p>
      <p>
        The presented LOD system can be applied very well to the patent
mining and expand existing approaches by the factor of
information integration in the semantic web (data providing). The
objects of interest, for example, are inventors, assignees, titles,
abstracts etc. This information can be interlinked by relations like
“refers”, “invented”, “assigned” etc. [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. The semantic
representation of patents as well as of academic documents is
similar. Both document types can be divided into two parts: The
document structure and the content [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. Common vocabularies
are available for both information sources.
      </p>
    </sec>
    <sec id="sec-13">
      <title>6. CONCLUSIONS</title>
      <p>The main idea of this paper is to unify scientific data such as
researcher information, publications and acronyms as well as their
expansions from several original resources and to provide them as
machine-readable and structured RDF graphs, which allow
interlinking and automatic processing. For this reason we
introduced a LOD system for scientific data sets.</p>
      <p>Based on the data visualization trough RelFinder, the system can
further help to identify latent relations between researchers based
on publications, acronyms or for example co-authors and further
to disambiguate single objects and classes.</p>
      <p>As above-mentioned, this is work in progress and we want to
apply further algorithms on the data sets to solve existing
disambiguation problems, especially in the researcher data set.
Additionally we will expand the linked properties between single
classes in order to improve the identification of relations between
these classes.</p>
      <p>It could further be shown that the system is portable due to its
flexible adaptation to other domains (e.g. patent mining) although
the prototypical implementation was designed for other sources
(academic publications).</p>
      <p>In the near future, we will publish all data sets for research
purposes. It will be made available online via our homepage
(http://inscite.kisti.re.kr/ or http://semantic.kisti.re.kr).</p>
    </sec>
    <sec id="sec-14">
      <title>7. ACKNOWLEDGMENTS</title>
      <p>This work was supported by the KISTI [K-14-L02-C03-S03,
Development of Technologies for S&amp;T Text Big Data Analytics
Application Platform] and a grant from the University of
Paderborn, Germany.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Berners-Lee</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bizer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Heath</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <year>2009</year>
          .
          <article-title>Linked datathe story so far</article-title>
          .
          <source>International Journal on Semantic Web and Information Systems</source>
          ,
          <volume>5</volume>
          (
          <issue>3</issue>
          ), pp.
          <fpage>1</fpage>
          -
          <lpage>22</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Bizer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Cyganiak</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <year>2006</year>
          .
          <article-title>D2r server - publishing relational databases on the semantic web</article-title>
          .
          <source>Poster at the 5th International Semantic Web Conference.</source>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Deng</surname>
            ,
            <given-names>D. P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mai</surname>
            ,
            <given-names>G. S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hsu</surname>
            ,
            <given-names>C. H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chang</surname>
            ,
            <given-names>C. L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chuang</surname>
            ,
            <given-names>T. R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shao</surname>
            ,
            <given-names>K. T.</given-names>
          </string-name>
          <year>2012</year>
          .
          <article-title>Linking Open Data Resources for Semantic Enhancement of User-Generated Content</article-title>
          .
          <source>In the book of Semantic Technology</source>
          . pp.
          <fpage>362</fpage>
          -
          <lpage>367</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Heim</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hellmann</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lehmann</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lohmann</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Stegemann</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <year>2009</year>
          .
          <article-title>RelFinder: Revealing relationships in RDF knowledge bases</article-title>
          .
          <source>In Semantic Multimedia</source>
          , pp.
          <fpage>182</fpage>
          -
          <lpage>187</lpage>
          , Springer Berlin Heidelberg.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Hert</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reif</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Gall</surname>
            ,
            <given-names>H. C.</given-names>
          </string-name>
          <year>2011</year>
          .
          <article-title>A comparison of RDB-to-RDF mapping languages</article-title>
          .
          <source>In Proceedings of the 7th International Conference on Semantic Systems</source>
          , pp.
          <fpage>25</fpage>
          -
          <lpage>32</lpage>
          , ACM.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Jentzsch</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhao</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hassanzadeh</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cheung</surname>
            ,
            <given-names>K. H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Samwald</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Andersson</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <year>2009</year>
          .
          <article-title>Linking open drug data. In I-SEMANTICS.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Kim</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hwang</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jeong</surname>
            ,
            <given-names>D. H.</given-names>
          </string-name>
          <article-title>and</article-title>
          <string-name>
            <surname>Jung</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          <year>2012</year>
          .
          <article-title>Technology trends analysis and forecasting application based on decision tree and statistical feature analysis</article-title>
          .
          <source>In Expert Systems with Applications</source>
          ,
          <volume>39</volume>
          (
          <issue>16</issue>
          ), pp.
          <fpage>12618</fpage>
          -
          <lpage>12625</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Le-Phuoc</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parreira</surname>
            ,
            <given-names>J. X.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hausenblas</surname>
            , M., Han,
            <given-names>Y.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Hauswirth</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <year>2010</year>
          .
          <article-title>Live linked open sensor database</article-title>
          .
          <source>In Proceedings of the 6th International Conference on Semantic Systems</source>
          , p.
          <fpage>46</fpage>
          , ACM.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Lohmann</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Heim</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stegemann</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Ziegler</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <year>2010</year>
          .
          <article-title>The RelFinder User Interface: Interactive Exploration of Relationships between Objects of Interest</article-title>
          .
          <source>In Proceedings of the 15th international conference on Intelligent user interfaces</source>
          , pp.
          <fpage>421</fpage>
          -
          <lpage>422</lpage>
          , ACM.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Lukovnikov</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stadler</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kontokostas</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hellmann</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Lehmann</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <year>2014</year>
          .
          <article-title>DBpedia Viewer-An Integrative Interface for DBpedia Leveraging the DBpedia Service Eco System</article-title>
          .
          <source>In Proceedings of the 7th Workshop on Linked Data on the Web.</source>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>Mitrevski</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jovanovik</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stojanov</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Trajanov</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <year>2012</year>
          . Open University Data.
          <source>In Proceedings of the 9th Conference for Informatics and Information Technology.</source>
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>Samwald</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jentzsch</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bouton</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kallesøe</surname>
            ,
            <given-names>C. S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Willighagen</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hajagos</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Stephens</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <year>2011</year>
          .
          <article-title>Linked open drug data for pharmaceutical research and development</article-title>
          .
          <source>In Journal of cheminformatics</source>
          ,
          <volume>3</volume>
          (
          <issue>1</issue>
          ), p.
          <fpage>19</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <surname>Latif</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Afzal</surname>
            ,
            <given-names>M. T.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Maurer</surname>
            ,
            <given-names>H. A.</given-names>
          </string-name>
          <year>2012</year>
          .
          <article-title>Weaving Scholarly Legacy Data into Web of Data</article-title>
          .
          <source>J. UCS</source>
          ,
          <volume>18</volume>
          (
          <issue>16</issue>
          ), pp.
          <fpage>2301</fpage>
          -
          <lpage>2318</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>Mukherjea</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Bamba</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <year>2004</year>
          .
          <article-title>BioPatentMiner: an information retrieval system for biomedical patents</article-title>
          .
          <source>In Proceedings of the Thirtieth international conference on Very large data bases.</source>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <surname>Ghoula</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Khelif</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Dieng-Kuntz</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <year>2007</year>
          .
          <article-title>Supporting patent mining by using ontology-based semantic annotations</article-title>
          .
          <source>In Proceedings of the Web intelligence</source>
          , IEEE/WIC/ACM international conference, pp.
          <fpage>435</fpage>
          -
          <lpage>438</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>