<!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>
      <journal-title-group>
        <journal-title>April</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>zLinks: Semantic Framework for Invoking Contextual Linked Data</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Michael K. Bergman Zitgist LLC Coralville</string-name>
          <email>fred@zitgist.com</email>
          <email>mike@zitgist.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>IA USA</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Frédérick Giasson Zitgist LLC Quebec City</institution>
          ,
          <addr-line>Quebec</addr-line>
          <country country="CA">Canada</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2008</year>
      </pub-date>
      <volume>22</volume>
      <issue>2008</issue>
      <abstract>
        <p>This first-ever demonstration of the new zLinks plug-in shows how any existing Web document link can be automatically transformed into a portal to relevant Linked Data. Each existing link disambiguates to its contextual and relevant subject concept (SC) or named entity (NE). The SCs are grounded in the OpenCyc knowledge base, supplemented by aliases and WordNet synsets to aid disambiguation. The NEs are drawn from Wikipedia as processed via YAGO, and other online fact-based repositories. The UMBEL ontology basis to this framework offers significant further advantages. The zLinks popup is invoked only as desired via unobtrusive user interface cues.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;demo</kwd>
        <kwd>Linked Data</kwd>
        <kwd>zLinks</kwd>
        <kwd>OpenCyc</kwd>
        <kwd>Wikipedia</kwd>
        <kwd>WordNet</kwd>
        <kwd>YAGO</kwd>
        <kwd>UMBEL</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. INTRODUCTION</title>
      <p>
        Linked Data [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] follows recommended practices for identifying,
exposing and connecting data on the semantic Web. A robust
Linked Open Data (LOD)1 community has rapidly developed
around the practice with literally billions of compliant data items
now available.
      </p>
      <p>
        A notable catalyst to the Linked Data movement has been
DBpedia [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], which exposes Wikipedia data in best-practices
format. It is appropriate that the flagship figure showing the
interrelationships of many Linked Data sources has DBpedia
positioned at its core [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>However, the Linked Data community readily acknowledges that
the existing semantics and basis for relating compliant datasets
are relatively poor. Moreover, there presently are no techniques
or methods for relating non-Linked Data to the rapidly growing
storehouse of LOD-compliant datasets.</p>
      <p>The newest release of the zLinks plug-in (see Figure 1) and its
supporting server-side infrastructure directly addresses the issues
of improved semantics for Linked Data matching and relating
Linked Data with standard Web content. Our demonstration
shows how normal hyperlinks in standard WordPress blogs can be
automatically related to contextually relevant Linked Data.
This précis first describes the technical underpinnings to zLinks’
semantic framework, then overviews the application and possible
future directions.</p>
    </sec>
    <sec id="sec-2">
      <title>2. SEMANTIC FRAMEWORK</title>
      <p>
        W-O-W-Y is the term we apply to the semantic framework for
relating a given hypertext link to its relevant Linked Data. The
term is derived from the constituent resources of WordNet2 (W),
OpenCyc3 (O), Wikipedia4 (W) and YAGO [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] (Y). Via the
WOWY framework, we first determine if the link refers to either
a named entity (NE) or a subject concept (SC) as well as to
disambiguate alternate senses. If an NE, the entity is also related
to its parent subject concept; every link thus has a SC basis.
All canonical SCs are embedded in a subject structure ontology –
the “backbone”. Use of this ontology brings inference and other
relationship advantages. These various semantic frameworks are
described below.
      </p>
    </sec>
    <sec id="sec-3">
      <title>2.1 Subject Concepts</title>
      <p>Subject concepts (SCs) are the core constituents to the framework.</p>
      <p>All SCs are based on existing concepts in OpenCyc, the open</p>
      <sec id="sec-3-1">
        <title>2 http://wordnet.princeton.edu/</title>
      </sec>
      <sec id="sec-3-2">
        <title>3 http://www.opencyc.org/</title>
      </sec>
      <sec id="sec-3-3">
        <title>4 http://en.wikipedia.org</title>
        <p>
          source version of the Cyc [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] knowledge base. SCs are the
concrete, non-abstract topic-related classes within Cyc. About
22,000 of them were vetted from Cyc (paper in preparation).
Aliases for these concepts as maintained by Cyc were combined
with matching WordNet synsets to produce the SC
disambiguation lexicon.
        </p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>2.2 Named Entities</title>
      <p>The named entities (NE) are drawn from Wikipedia as processed
via YAGO, and other online fact-based repositories. NEs are the
instances of the SC classes in the standard definition of the term5.
NEs also have aliases for disambiguation purposes (such as the
many ways to refer to the “United States”).</p>
      <p>Each NE is mapped to a governing SC for ontology purposes.</p>
    </sec>
    <sec id="sec-5">
      <title>2.3 UMBEL Ontology</title>
      <p>All of the SCs are expressed in the UMBEL (Upper-level
Mapping and Binding Exchange Layer)6 ontology. UMBEL is a
lightweight structure of subject concepts and their semantic
relationships. There is a direct overlap of UMBEL subject
concepts to a subset of class concepts within OpenCyc.
Quick relations can be determined from UMBEL for a given SC;
more involved inferencing can be directed to OpenCyc.
Thus, via these semantic relationships, other relations such as
parent concepts, domains, various entity types, and similar
relationships can be obtained once a given SC is identified.</p>
    </sec>
    <sec id="sec-6">
      <title>3. APPLICATION</title>
      <p>This semantic framework is applied on the server-side once a
given standard link is processed. The client-side zLinks plug-in
provides the user interface, initial link extraction and results
reporting to the user.</p>
    </sec>
    <sec id="sec-7">
      <title>3.1 Plug-in Design</title>
      <p>The demo is provided as a standard WordPress7 PHP plug-in, with
many options parameterized.</p>
    </sec>
    <sec id="sec-8">
      <title>3.2 Snippet Evaluation</title>
      <p>
        A “snippet” of text based on a word window or sentence
surrounding the target link is extracted, parsed, filtered and then
submitted to the server for sense evaluation. We use a variant of
a graph-based disambiguation algorithm suited for use with large
knowledge lexicons [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
      </p>
      <p>This extraction process can also result in issued queries to
standard Web search services.</p>
    </sec>
    <sec id="sec-9">
      <title>3.3 User Cues</title>
      <p>The semantic result of this link evaluation – the individual zLink
– is presented to the user via a subtle, small icon. The results are
only presented to the user after a mouseover with set delay, to
ensure the popup is purposefully desired and unobtrusive.</p>
    </sec>
    <sec id="sec-10">
      <title>3.4 Popup</title>
      <p>A popup presents the contextual zLinks results (see Figure 1),
with toggle views presented as substitution overlays to preserve
screen real estate. Because of the multiple relations possible,
there are multiple contextual overlays. The basic results
paradigm is taken from Zitgist’s related DataViewer for RDF
data.8</p>
    </sec>
    <sec id="sec-11">
      <title>4. FUTURE DIRECTIONS</title>
      <p>This initial zLinks design is but a mere taste of the possibilities
with Linked Data from the twin perspectives of additional
relationships and presentation templates. We expect rapid
developments in both areas.</p>
      <p>A generalization of the plug-in architecture will enable extension
to other user-content platforms. Still further extending this
generalization to the Web browser would bring zLinks
capabilities to every Internet user for all existing Web content.
The basic zLinks design also lends itself to incorporating
additional sources of named entity lookups and Linked Data.</p>
    </sec>
    <sec id="sec-12">
      <title>5. CONCLUSIONS</title>
      <p>Linked Data has been a triggering event in the nascent emergence
of the semantic Web. We expect to see similar innovations to
zLinks – such as Wikify9 – emerge to test out different paradigms
and interfaces for how best to exploit a Web of Data.</p>
      <p>An older zLinks prototype may be found at
http://zlinks.zitgist.com/; an updated demo based on the version
herein will be posted shortly after the presentation.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>T.</given-names>
            <surname>Berners-Lee</surname>
          </string-name>
          .
          <article-title>Design Issues-Linked Data</article-title>
          . Published online, May
          <year>2007</year>
          . http://www.w3.org/ DesignIssues/LinkedData.html
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>S.</given-names>
            <surname>Auer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Bizer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Lehmann</surname>
          </string-name>
          , G. Kobilarov,
          <string-name>
            <given-names>R.</given-names>
            <surname>Cyganiak</surname>
          </string-name>
          , and
          <string-name>
            <surname>Z. Ives.</surname>
          </string-name>
          <article-title>DBpedia: A nucleus for a web of open data</article-title>
          .
          <source>In Proceedings of the 6th International Semantic Web Conference and 2nd Asian Semantic Web Conference (ISWC/ASWC2007)</source>
          , Busan, South Korea, volume
          <volume>4825</volume>
          <source>of LNCS</source>
          , pages
          <fpage>715</fpage>
          -
          <lpage>728</lpage>
          ,
          <year>November 2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>R.</given-names>
            <surname>Cyganiak</surname>
          </string-name>
          .
          <article-title>The Linking Open Data dataset cloud</article-title>
          .
          <source>Figure published and maintained online; version December</source>
          <year>2007</year>
          . http://richard.cyganiak.de/2007/10/lod/
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>F.</given-names>
            <surname>Suchanek</surname>
          </string-name>
          , G. Kasneci, and
          <string-name>
            <given-names>G.</given-names>
            <surname>Weikum.</surname>
          </string-name>
          <article-title>Yago: a core of semantic knowledge</article-title>
          .
          <source>In WWW '07: Proceedings of the 16th international conference on World Wide Web</source>
          , pages
          <fpage>697</fpage>
          -
          <lpage>706</lpage>
          , New York, NY, USA,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>D. B.</given-names>
            <surname>Lenat</surname>
          </string-name>
          .
          <article-title>Cyc: A large-scale investment in knowledge infrastructure</article-title>
          .
          <source>Communications of the ACM</source>
          <volume>38</volume>
          , no.
          <issue>11</issue>
          ,
          <year>November 1995</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>R.</given-names>
            <surname>Mihalcea</surname>
          </string-name>
          and
          <string-name>
            <given-names>A.</given-names>
            <surname>Csomai</surname>
          </string-name>
          . Wikify!
          <article-title>Linking documents to encyclopedic knowledge</article-title>
          .
          <source>In Proceedings of the Sixteenth ACM conference on Conference on Information and Knowledge Management (CIKM '07)</source>
          , pp.
          <fpage>233</fpage>
          -
          <lpage>241</lpage>
          , November 6-
          <issue>8</issue>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>