<?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">Linked Data Spaces &amp; Data Portability</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Kingsley</forename><surname>Idehen</surname></persName>
							<email>kidehen@openlinksw.com</email>
							<affiliation key="aff0">
								<orgName type="institution">OpenLink Software</orgName>
								<address>
									<addrLine>10 Mall Road</addrLine>
									<postCode>01803</postCode>
									<settlement>Burlington</settlement>
									<region>MA</region>
									<country key="US">USA</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Orri</forename><surname>Erling</surname></persName>
							<email>oerling@openlinksw.com</email>
							<affiliation key="aff1">
								<orgName type="institution">OpenLink Software</orgName>
								<address>
									<addrLine>10 Mall Road</addrLine>
									<postCode>01803</postCode>
									<settlement>Burlington</settlement>
									<region>MA</region>
									<country key="US">USA</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Linked Data Spaces &amp; Data Portability</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">657101F0E445B3A0AB9B454E4D206D16</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.2 [Information Storage] H.3.3 [Information Search &amp; Retrieval] Management</term>
					<term>Performance</term>
					<term>Design</term>
					<term>Standardization</term>
					<term>Languages</term>
					<term>Theory Linked Data</term>
					<term>Semantic Web</term>
					<term>SPARQL</term>
					<term>Data Integration</term>
					<term>Data Spaces</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>In the year 2007, the size of the Linked Data injected into the Web grew to several billion RDF triples, served by a network of interlinked data sources that cover domains such as general knowledge, geographic information, people, companies, online communities, films, music, books and scientific publications. Unfortunately, the growth rate of User Generated content from a variety of Web based unstructured and semi-structured data-silos continues to exceed that of structured Linked Data. Thus, we have a pressing need for technology, capable of bridging this broadening divide via transparent generation of Linked Data from existing data-silos on the Web. Our Linked Data technology demonstration explores the use of the OpenLink Data Spaces platform as a solution to this problem.</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>User generated content is growing at an exponential rate behind corporate firewalls and across the Internet in general. The use of Web technologies has been the prime accelerator of the aforementioned growth due to the pervasiveness of Web based distributed collaborative applications. Examples include: Social Networking, Weblogs, Wikis, Shared Bookmark Managers, Photo Sharing, Polls Management, Calendars, Discussion Forums, File Sharing, and Feed Aggregation, to name a few.</p><p>The exponential growth of user-generated content has resulted in the growth of silos comprised of unstructured and/or semistructured content. Unfortunately, these silos have accelerated, rather than decelerated, the imminence of an "information overload" quagmire. We identify the items above, collectively, as critical components of Linked Data Spaces: points of presence on the Web that expose structured data via HTTP based URIs.</p><p>During this demonstration / presentation session we are going explore the creation of "Data Junction Boxes in the Clouds" via OpenLink Data Spaces that exploits in-built RDFization Middleware, plus the ability to mesh User Identity and User Data, en route to surmounting the issues and challenges associated with Data Portability attainment.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Issues &amp; Challenges 2.1 Data Portability</head><p>It's no secret that data wants to be free of the tyranny of application logic confinement. In recent times, the realization that meshing Identity and Data ownership on the Web are critical requirements of this pursuit of freedom, has resulted in the emergence of a movement for Data Portability as yet another enclave within the broader Open Data movement.</p><p>Data portability addresses to key issues: data mobility and data referencing. Today, data mobility though the use of standard data formats for moving data across silos (import and export style) have emerged as the focal point of attention with regards to addressing the proliferation of data silos on the Web. Examples include: RSS 1.0, RSS 2.0, Atom, OPML, FOAF, SIOC, and others. Unfortunately, the ability to reference and de-reference data across data-silos is yet to catch the attention of those pursuing data portability.</p><p>The traditional resistance to RDF adoption, which is critical to Linked Data comprehension and production, comes from the grounding of the RDF Data Model in Graph Theory and the unwillingness of most Web Application developers to interact with data formally. This reality has lead to a genre of middleware tools collectively known as RDFizers, that generate RDF on the fly.</p><p>With regards, to Linked Data, generating RDF on-the-fly is only part of the equation; the generated RDF must retain the core principles of linked data by providing URIs for physical web accessible resources, concrete entities, and abstract things. Of course, this process must include intelligent production of instance data associated with relevant shared schemas or ontologies.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.3">Data Junction Boxes in the Clouds</head><p>It is our belief that the Linked Data Web will be more distributed than centralized in architecture. We envisage a Linked Data Web comprised of hubs that range is size from large (e.g. DBpedia, Geonames, Zitgist etc.), medium sized group (e.g. RDFized Weblogs, Wikis, Bulletin Boards etc.), and smaller personal hubs enabled by operating system virtualization technologies like Amazon EC2. The medium and smaller hubs are best described as data junction boxes because they act as conduits between existing systems and Linked Data aware User Agents.</p><p>This demonstration will demonstrate a Data Space initialization process for end-users that covers: </p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>•</head><label></label><figDesc>Domain Name Registration (e.g. .Name acquisition) • DNS configuration • Bonding with existing Web 2.0 platforms Facebook, phpBB3, MediaWiki, Wordpress, Drupal, Del.icio.us, Flickr, and Bugzilla • Production of a dereferencable URIs that exposed the resulting Data Graph • Interaction with the resulting data graph via a number of Linked Data aware User Agents</figDesc></figure>
		</body>
		<back>
			<div type="references">

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