<!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>refer: a Linked Data based Text Annotation and Recommender System for Wordpress</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Tabea Tietz</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jörg Waitelonis</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Joscha Jäger</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Harald Sack</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Hasso-Plattner-Intitute</institution>
          ,
          <addr-line>Prof.-Dr.-Helmert-Str. 2-3, 14482 Potsdam</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>yovisto GmbH</institution>
          ,
          <addr-line>August-Bebel-Str. 25-53, 14482 Potsdam</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>When searching for an arbitrary subject in weblogs or archives, users often don’t
get the information they are really looking for, because they are overwhelmed
with an overflow of information while sometimes the presented information is too
scarce to make any use of it. Without further knowledge about the context or
background of the intended subject users are easily frustrated because they either
cannot handle the amount of information or they might give up because they
cannot make sense of the topic at all. Furthermore, authors of online-platforms
often deal with the issue to provide useful recommendations of other articles and
to motivate the readers to explore more of the available but often hidden content
of their blog or archive.</p>
      <p>In the demo presentation, we present refer, a semantic annotation and
visualization system integrated into the Wordpress platform. refer enables content
creators to (semi-)automatically annotate their texts with DBpedia resources as
part of the original writing process and visualize them automatically. With refer
users are encouraged to take an active part in discovering a platform’s
information content interactively. They can discover background information as well as
relationships among persons, places, events, and anything related to the subject
in current focus and are inspired to navigate the previously hidden information
on a platform.</p>
      <p>
        Related systems include Pundit [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] and WYSIWYM [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. The original concept
of the presented user interface and a first prototype have already been presented
in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>
        refer Components
refer consists of the following tools and visualizations, integrated into Wordpress
(cf. Fig. 1). An Annotator is implemented as an extension of the Wordpress
text editing interface to create semantic text annotations based on DBpedia. To
create annotations, the author selects a text fraction in the Wordpress editing
environment. The author can further choose between manual and automated
annotation by means of automated Named Entity Linking (NEL). For automated
annotation, refer deploys KEA-NEL [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], which implements entity linking with
DBpedia entities [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Nevertheless, there are still errors that have to be revised
manually. The user has to be supported in selecting the correct entity from the
large knowledge-base which is a challenge especially for highly ambiguous
textual mentions. Further, utilities are applied to rank and organize the candidate
lists according to e. g. string similarity with the entity mention, or popularity of
the entity [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] to increase the users’ annotation performance. The refer Annotator
provides two configurable user interface modes: (1) The Modal Annotator is
triggered via a button in the TinyMCE control panel, whereby the suggested
entities are displayed in a modal dialog window (cf. Fig. 1.1) in a table-based
layout. Entities are divided into the four categories Person (green), Place (blue),
Event (yellow) and Thing (purple). The text abstract and entity IRI is displayed
on mouseover. The selected annotation is encoded in RDFa markup, which is
added to the according text fragment. (2) The Inline Annotator (cf. Fig. 1.2)
is triggered automatically via highlighting a text fragment and opens a
circular category menu which allows the user to instantly show suggestions from
the respective category (Person, Place, Event, Thing). By selecting a category,
the suggested entities are displayed. In order to provide more context within
the relatively small space, these entities are divided into dynamically retrieved
sub-categories. While the Inline Annotator provides fast and simple means of
semantic text annotation without losing the context of the written text, the
Modal Annotator provides a larger overview and enables a better comparison of
entities.
      </p>
      <p>Infoboxes are used to visualize annotations in the article view, and
annotated entities are indicated directly in the article text. On mouseover, an infobox
as in Fig. 1.3 is shown right below the annotated text fragment, which contains
basic information about the entity, e.g. a label, a thumbnail, and additional data
in a table-layout. The infobox allows the user to gather basic facts about an
entity and relations to other entities. While some basic information can be derived
just from the webpage‘s RDFa microdata and is displayed instantly, additional
content is asynchronously loaded from the web service. When the text fragment
or any of the infobox entities are clicked, the Relation Browser slides down from
the top of the page with the selected entity in focus.</p>
      <p>The Relation Browser and Recommender visualizes relationships
between annotations as well as suggestions for further reading. It allows users to
navigate and explore relations among entities. It can be opened by the user either
via click on the refer icon bar on top of the page or by selecting an entity of
interest in the article text, (e.g. Jules Verne). The entity Jules Verne then becomes
the focus-entity. Its DBpedia abstract and image are displayed on the bottom of
the Relation Browser and its background color depends on its category (Person,
Place, Event, Thing). Based on the focus-entity, related entities (derived from
DBpedia and all annotations available on the platform) are displayed in a four
column grid. The pagination bars on the right hand side of each column allow
the users to browse through all entities in a category. When hovering one of the
displayed entities (e.g. Jacques Cousteau in Fig. 1.4), relations to the focus-entity
and to further entities in the grid-view (e.g. Oceanography) are visualized by line
connectors. A label (property) indicates the direction and type of connection.
If there are more entity-relations than displayed in the first overview,
connections to hidden entities are indicated by dotted lines, which can be activated
via hovering a small ’plus’ icon inside the entity box. A click on an entity in
the grid-view replaces the focus-entity with the selected item and refreshes the
related entities in all categories. A ranked list of recommended blogposts for the
entity in focus is displayed on the bottom-left. The recommendations comprise
blogposts that cover the focus-entity and entities related to the focus entity. The
more entities are related with the entity in focus, the higher is the rank of the
recommended article in the list.
3</p>
    </sec>
    <sec id="sec-2">
      <title>Summary</title>
      <p>We have presented refer as a tool to help blog authors to enhance their content
with the help of Linked Open Data and to engage the readers to further explore
the available content as well as to provide background information from DBpedia
and Wikipedia. A proof-of-concept is provided as being integrated into a daily
weblog3. The Wordpress-plugin of refer is publicly available for download4, and
a screencast5 demonstrates the annotator interfaces.</p>
      <p>Acknowledgement: This work has been funded by the German Government,
Federal Ministry of Education an Research under project number 03WKCJ4D.
3 http://blog.yovisto.com
4 http://refer.cx/
5 http://s16a.org/sites/default/files/refer/refer_Screencast.mov</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>A.</given-names>
            <surname>Khalili</surname>
          </string-name>
          and
          <string-name>
            <given-names>S.</given-names>
            <surname>Auer</surname>
          </string-name>
          .
          <article-title>WYSIWYM - integrated visualization, exploration and authoring of semantically enriched unstructured content</article-title>
          .
          <source>Semantic Web Journal</source>
          ,
          <volume>1</volume>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>C.</given-names>
            <surname>Morbidoni</surname>
          </string-name>
          and
          <string-name>
            <given-names>A.</given-names>
            <surname>Piccioli</surname>
          </string-name>
          . The Semantic Web:
          <article-title>ESWC 2015 Satellite Events, chapter Curating a Document Collection via Crowdsourcing with Pundit 2.0</article-title>
          , pages
          <fpage>102</fpage>
          -
          <lpage>106</lpage>
          . Springer,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>J.</given-names>
            <surname>Osterhoff</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Waitelonis</surname>
          </string-name>
          , and
          <string-name>
            <given-names>H.</given-names>
            <surname>Sack</surname>
          </string-name>
          . Widen the Peepholes!
          <article-title>Entity-Based AutoSuggestion as a rich and yet immediate Starting Point for Exploratory Search</article-title>
          .
          <source>In Proc. of 2nd Workshop Interaction and Visualization in the Web of Data (IVDW</source>
          <year>2012</year>
          ),
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>T.</given-names>
            <surname>Tietz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Waitelonis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Jäger</surname>
          </string-name>
          , and
          <string-name>
            <given-names>H.</given-names>
            <surname>Sack</surname>
          </string-name>
          .
          <article-title>Smart media navigator: Visualizing recommendations based on linked data</article-title>
          .
          <source>In 13th Int. Semantic Web Conf.</source>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>R.</given-names>
            <surname>Usbeck</surname>
          </string-name>
          et al. Gerbil:
          <article-title>General entity annotator benchmarking framework</article-title>
          .
          <source>In Proc. of the 24th Int. Conf. on World Wide Web</source>
          , pages
          <fpage>1133</fpage>
          -
          <lpage>1143</lpage>
          . ACM,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>J.</given-names>
            <surname>Waitelonis</surname>
          </string-name>
          and
          <string-name>
            <given-names>H.</given-names>
            <surname>Sack</surname>
          </string-name>
          .
          <article-title>Named entity linking in #tweets with kea</article-title>
          .
          <source>In 6th workshop on 'Making Sense of Microposts', Named Entity Recognition and Linking (NEEL) Challenge, at the 25th Int. World Wide Web Conf.</source>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>