<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">zLinks: Semantic Framework for Invoking Contextual Linked Data</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Michael</forename><forename type="middle">K</forename><surname>Bergman</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">Zitgist LLC Coralville</orgName>
								<address>
									<region>IA</region>
									<country key="US">USA</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Frédérick</forename><surname>Giasson</surname></persName>
							<affiliation key="aff1">
								<orgName type="institution">Zitgist LLC Quebec</orgName>
								<address>
									<settlement>City</settlement>
									<region>Quebec</region>
									<country key="CA">Canada</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">zLinks: Semantic Framework for Invoking Contextual Linked Data</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">9F4BAA6E034F7EA8C9BD2B31EBDF893E</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T23:27+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>H.3.3 [Information Search and Retrieval]: Information filtering, Query formulation</term>
					<term>H.5.4 [Hypertext/Hypermedia]: Navigation</term>
					<term>H.5.2 [User Interfaces]: Interaction styles demo, Linked Data, zLinks, OpenCyc, Wikipedia, WordNet, YAGO, UMBEL</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><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></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">INTRODUCTION</head><p>Linked Data <ref type="bibr" target="#b1">[1]</ref> 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 <ref type="bibr" target="#b2">[2]</ref>, 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 1 http://esw.w3.org/topic/SweoIG/TaskForces/Community Projects/LinkingOpenData positioned at its core <ref type="bibr" target="#b3">[3]</ref>.</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 <ref type="figure">1</ref>) 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.</p><p>This précis first describes the technical underpinnings to zLinks' semantic framework, then overviews the application and possible future directions.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">SEMANTIC FRAMEWORK</head><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 WordNet<ref type="foot" target="#foot_0">2</ref> (W), OpenCyc<ref type="foot" target="#foot_1">3</ref> (O), Wikipedia<ref type="foot" target="#foot_2">4</ref> (W) and YAGO <ref type="bibr" target="#b4">[4]</ref> (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.</p><p>All canonical SCs are embedded in a subject structure ontologythe "backbone". Use of this ontology brings inference and other relationship advantages. These various semantic frameworks are described below.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.1">Subject Concepts</head><p>Subject concepts (SCs) are the core constituents to the framework. All SCs are based on existing concepts in OpenCyc, the open</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Figure 1. zLinks toggle popup</head><p>Copyright is held by the author/owner(s). LDOW2008, April 22, 2008, Beijing, China.</p><p>source version of the Cyc <ref type="bibr" target="#b5">[5]</ref> 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).</p><p>Aliases for these concepts as maintained by Cyc were combined with matching WordNet synsets to produce the SC disambiguation lexicon.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2">Named Entities</head><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 term <ref type="foot" target="#foot_3">5</ref> . 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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.3">UMBEL Ontology</head><p>All of the SCs are expressed in the UMBEL (Upper-level Mapping and Binding Exchange Layer) <ref type="foot" target="#foot_4">6</ref> 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.</p><p>Quick relations can be determined from UMBEL for a given SC; more involved inferencing can be directed to OpenCyc.</p><p>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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">APPLICATION</head><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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1">Plug-in Design</head><p>The demo is provided as a standard WordPress<ref type="foot" target="#foot_5">7</ref> PHP plug-in, with many options parameterized.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2">Snippet Evaluation</head><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 <ref type="bibr">[6]</ref>.</p><p>This extraction process can also result in issued queries to standard Web search services.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.3">User Cues</head><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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.4">Popup</head><p>A popup presents the contextual zLinks results (see Figure <ref type="figure">1</ref>), 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.<ref type="foot" target="#foot_6">8</ref> </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">FUTURE DIRECTIONS</head><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.</p><p>The basic zLinks design also lends itself to incorporating additional sources of named entity lookups and Linked Data.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">CONCLUSIONS</head><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 Wikify<ref type="foot" target="#foot_7">9</ref> -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></div>			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_0">http://wordnet.princeton.edu/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_1">http://www.opencyc.org/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_2">http://en.wikipedia.org</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_3">See http://en.wikipedia.org/wiki/Named_entity_recognition</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="6" xml:id="foot_4">http://www.umbel.org</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="7" xml:id="foot_5">http://www.wordpress.org</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="8" xml:id="foot_6">http://dataviewer.zitgist.com</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="9" xml:id="foot_7">http://www.wikifyer.com/</note>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title/>
		<author>
			<persName><surname>References</surname></persName>
		</author>
		<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<title level="m" type="main">Design Issues-Linked Data</title>
		<author>
			<persName><forename type="first">T</forename><surname>Berners-Lee</surname></persName>
		</author>
		<ptr target="http://www.w3.org/DesignIssues/LinkedData.html" />
		<imprint>
			<date type="published" when="2007-05">May 2007</date>
		</imprint>
	</monogr>
	<note>Published online</note>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">DBpedia: A nucleus for a web of open data</title>
		<author>
			<persName><forename type="first">S</forename><surname>Auer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Bizer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Lehmann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Kobilarov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Cyganiak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Z</forename><surname>Ives</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 6th International Semantic Web Conference and 2nd Asian Semantic Web Conference (ISWC/ASWC2007)</title>
				<meeting>the 6th International Semantic Web Conference and 2nd Asian Semantic Web Conference (ISWC/ASWC2007)<address><addrLine>Busan, South Korea</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2007-11">November 2007</date>
			<biblScope unit="volume">4825</biblScope>
			<biblScope unit="page" from="715" to="728" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">The Linking Open Data dataset cloud</title>
		<author>
			<persName><forename type="first">R</forename><surname>Cyganiak</surname></persName>
		</author>
		<ptr target="http://richard.cyganiak.de/2007/10/lod/" />
	</analytic>
	<monogr>
		<title level="m">Figure published and maintained online</title>
				<imprint>
			<date type="published" when="2007-12">December 2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Yago: a core of semantic knowledge</title>
		<author>
			<persName><forename type="first">F</forename><surname>Suchanek</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Kasneci</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Weikum</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">WWW &apos;07: Proceedings of the 16th international conference on World Wide Web</title>
				<meeting><address><addrLine>New York, NY, USA</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2007">2007</date>
			<biblScope unit="page" from="697" to="706" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Cyc: A large-scale investment in knowledge infrastructure</title>
		<author>
			<persName><forename type="first">D</forename><forename type="middle">B</forename><surname>Lenat</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Communications of the ACM</title>
		<imprint>
			<biblScope unit="volume">38</biblScope>
			<biblScope unit="issue">11</biblScope>
			<date type="published" when="1995-11">November 1995</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Wikify! Linking documents to encyclopedic knowledge</title>
		<author>
			<persName><forename type="first">R</forename><surname>Mihalcea</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Csomai</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the Sixteenth ACM conference on Conference on Information and Knowledge Management (CIKM &apos;07)</title>
				<meeting>the Sixteenth ACM conference on Conference on Information and Knowledge Management (CIKM &apos;07)</meeting>
		<imprint>
			<date type="published" when="2007">November 6-8, 2007</date>
			<biblScope unit="page" from="233" to="241" />
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
