<?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">The Linked Data Visualization Model</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Josep</forename><forename type="middle">Maria</forename><surname>Brunetti</surname></persName>
							<email>josepmbrunetti@diei.udl.cat</email>
							<affiliation key="aff0">
								<orgName type="department">GRIHO</orgName>
								<orgName type="institution">Universitat de Lleida</orgName>
								<address>
									<addrLine>Jaume II</addrLine>
									<postCode>69. 25001</postCode>
									<settlement>Lleida</settlement>
									<country key="ES">Spain</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Sören</forename><surname>Auer</surname></persName>
							<affiliation key="aff1">
								<orgName type="department" key="dep1">AKSW</orgName>
								<orgName type="department" key="dep2">Computer Science</orgName>
								<orgName type="institution">University of Leipzig</orgName>
								<address>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Roberto</forename><surname>García</surname></persName>
							<email>rgarcia@diei.udl.cat</email>
							<affiliation key="aff0">
								<orgName type="department">GRIHO</orgName>
								<orgName type="institution">Universitat de Lleida</orgName>
								<address>
									<addrLine>Jaume II</addrLine>
									<postCode>69. 25001</postCode>
									<settlement>Lleida</settlement>
									<country key="ES">Spain</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">The Linked Data Visualization Model</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">849A5EEA012AA8CA18B7827BF81226B5</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T11:45+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>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>The potential of the semantic data available in the Web is enormous but in most cases it is very difficult for users to explore and use this data. Applying information visualization techniques to the Semantic Web helps users to easily explore large amounts of data and interact with them. We devise a formal Linked Data Visualization model (LDVM), which allows to dynamically connect data with visualizations.</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>In the last years, the amount of semantic data available on the Web has increased dramatically, especially thanks to initiatives like Linked Open Data (LOD). The potential of this vast amount of data is enormous but in most cases it is very difficult and cumbersome for users to visualize, explore and use this data, especially for lay-users without experience with Semantic Web technologies.</p><p>Applying information visualization techniques to the Semantic Web helps users to explore large amounts of data and interact with them. Visualizations are useful for obtaining an overview of the datasets, their main types, properties and the relationships between them. Compared to prior information visualization strategies, we have a unique opportunity on the Data Web. The unified RDF data model being prevalent on the Data Web enables us to bind data to visualizations in an unforeseen and dynamic way. An information visualization technique requires certain data structures to be present. When we can derive and generate these data structures automatically from reused vocabularies or semantic representations, we are able to realize a largely automatic visualization workflow. This will enable users to explore datasets even if the publisher of the data does not provide any exploration or visualization means.</p><p>The Linked Data Visualization Model (LDVM) we propose allows to connect different datasets with different visualizations in a dynamic way. In order to achieve such flexibility and a high degree of automation the LDVM is based on a visualization workflow incorporating analytical extraction and visual abstraction steps. Each of the visualization workflow steps comprises a number of transformation operators, which can be defined in a declarative way. As a result, the LDVM balances between flexibility of visualization options and efficiency of implementation or configuration.</p><p>We use the Data State Reference Model (DSRM) proposed by Chi <ref type="bibr" target="#b0">[1]</ref> as conceptual framework for our Linked Data Visualization Model (LDVM). While the DSRM describes the visualization process in a generic way, we instantiate and adopt this model with LDVM for the visualization of RDF and Linked Data. The names of the stages, transformations and operators have been adapted to the context of Linked Data and RDF. Figure <ref type="figure" target="#fig_0">1</ref> shows an overview of LDVM. It can be seen as a pipeline, which originates in one end with raw data and results in the other end with the visualization. The LDVM pipeline is organized in four stages that data needs to pass through:</p><p>1. RDF Data: the raw data, which can be all kinds of information adhering to the RDF data model, e.g. instance data, taxonomies, vocabularies, ontologies, etc. 2. Analytical extraction: data extractions obtained from raw data, e.g. calculating aggregated values. 3. Visual abstraction: information that is visualizable on the screen using a visualization technique. 4. View: the result of the process presented to the user, e.g. plot, treemap, map, timeline, etc.</p><p>Data is propagated through the pipeline from one stage to another by applying three types of transformation operators:</p><p>1. Data transformation: transforms raw data values into analytical extractions declaratively (using SPARQL query templates). 2. Visualization transformation: takes analytical extractions and transforms them into a visualization abstraction. The goal of this transformation is to condense the data into a displayable size and create a suitable data structure for particular visualizations. 3. Visual mapping transformation: processes the visualization abstractions in order to obtain a visual representation.</p><p>As illustrated in Figure <ref type="figure" target="#fig_1">2</ref>, our model allows to connect different RDF datasets and different data extractions with different visualization techniques. Not all datasets are compatible with all data extractions and each data extraction is only compatible with some visual configurations. Each dataset offers different data structures to be extracted, e.g. class hierarchy, property hierarchy, geospatial data, etc. Each data extraction can be visualized with different configurations, which contain information such as the visualization technique to use, colors, etc. Then, a concrete visualization is generated depending on the data extraction and the visual configuration.</p><p>In summary, the model is divided in two main areas: data space and visual space. The RDF data stage, analytical extraction stage and data transformation belong to the data space, while visual abstraction stage, view stage and visual mapping transformation belong to the visual space. These two main blocks are connected by a visualization transformation.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Demonstration</head><p>We have implemented a prototype called LODVisualization<ref type="foot" target="#foot_0">1</ref> that supports the Linked Data Visualization Model proposed. It allows to explore and interact with the Data Web through different visualizations. This way, our prototype serves not only as a proof-of-concept of our LDVM but also provides useful visualizations of RDF. These visualizations allow users to obtain an overview of RDF datasets and realize what the data is about: their main types, properties, etc.</p><p>LODVisualization is compatible with most of SPARQL endpoints as long as they support JSON and SPARQL 1.1. We have evaluated our implementation of the Linked Data Visualization Model with different datasets, data extractions and visualizations. The goal of our evaluation was to prove that the LDVM can be applied to different datasets providing different data visualizations in real time. All the visualization examples are available on the website and it easy to create new ones.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Related Work</head><p>Some of the existing tools available to explore and visualize Linked Data have been analyzed in <ref type="bibr" target="#b1">[2]</ref>. However, only very few provide visualizations and they are focused on concrete data types or domains.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Conclusions</head><p>The Linked Data Visualization Model (LDVM) can be applied to rapidly create visualizations of RDF data. It allows to connect different datasets, different data extractions and different visualizations in a dynamic way. Applying this model, developers and designers can obtain a better understanding of the visualization process with data stages, transformations and operators. The LDVM offers user guidance on how to create visualizations for RDF data.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Fig. 1 .</head><label>1</label><figDesc>Fig. 1. High level overview of the Linked Data Visualization Model.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Fig. 2 .</head><label>2</label><figDesc>Fig. 2. Linked Data Visualization Model ecosystem, which allows to dynamically connect datasets with visualizations.</figDesc></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">http://lodvisualization.appspot.com/</note>
		</body>
		<back>

			<div type="availability">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Data n</head><p>Config 1</p></div>
			</div>

			<div type="annex">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>RDF Data Analytical Extraction Visualization Abstraction View</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Data Transformation Visualization Transformation Visual Mapping Transformation</head></div>			</div>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">A taxonomy of visualization techniques using the data state reference model</title>
		<author>
			<persName><forename type="first">Ed</forename><forename type="middle">H</forename><surname>Chi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the IEEE Symposium on Information Vizualization 2000, INFOVIS &apos;00</title>
				<meeting>the IEEE Symposium on Information Vizualization 2000, INFOVIS &apos;00<address><addrLine>Washington, DC, USA</addrLine></address></meeting>
		<imprint>
			<publisher>IEEE Computer Society</publisher>
			<date type="published" when="2000">2000</date>
			<biblScope unit="page">69</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Approaches to visualising linked data: A survey</title>
		<author>
			<persName><forename type="first">Aba-Sah</forename><surname>Dadzie</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Matthew</forename><surname>Rowe</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Semantic Web</title>
		<imprint>
			<biblScope unit="volume">2</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="89" to="124" />
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

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