<?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">DING! Dataset Ranking using Formal Descriptions</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Nickolai</forename><surname>Toupikov</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">DERI</orgName>
								<orgName type="institution">National University of Ireland</orgName>
								<address>
									<addrLine>IDA Business Park</addrLine>
									<settlement>Galway, Galway</settlement>
									<country key="IE">Ireland</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">J</forename><surname>Ürgen Umbrich</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">DERI</orgName>
								<orgName type="institution">National University of Ireland</orgName>
								<address>
									<addrLine>IDA Business Park</addrLine>
									<settlement>Galway, Galway</settlement>
									<country key="IE">Ireland</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Renaud</forename><surname>Delbru</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">DERI</orgName>
								<orgName type="institution">National University of Ireland</orgName>
								<address>
									<addrLine>IDA Business Park</addrLine>
									<settlement>Galway, Galway</settlement>
									<country key="IE">Ireland</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Michael</forename><surname>Hausenblas</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">DERI</orgName>
								<orgName type="institution">National University of Ireland</orgName>
								<address>
									<addrLine>IDA Business Park</addrLine>
									<settlement>Galway, Galway</settlement>
									<country key="IE">Ireland</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Giovanni</forename><surname>Tummarello</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">DERI</orgName>
								<orgName type="institution">National University of Ireland</orgName>
								<address>
									<addrLine>IDA Business Park</addrLine>
									<settlement>Galway, Galway</settlement>
									<country key="IE">Ireland</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">DING! Dataset Ranking using Formal Descriptions</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">1CAD363EB44A9AB51A6B6401197C0A86</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T18:53+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>Considering that thousands if not millions of linked datasets will be published soon, we motivate in this paper the need for an efficient and effective way to rank interlinked datasets based on formal descriptions of their characteristics. We propose DING (from Dataset RankING) as a new approach to rank linked datasets using information provided by the voiD vocabulary. DING is a domain-independent link analysis that measures the popularity of datasets by considering the cardinality and types of the relationships. We propose also a methodology to automatically assign weights to link types. We evaluate the proposed ranking algorithm against other well known ones, such as PageRank or HITS, using synthetic voiD descriptions. Early results show that DING performs better than the standard Web ranking algorithms.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">MOTIVATION</head><p>Following Marshall and Shipman <ref type="bibr" target="#b0">[1]</ref>, we understand linked datasets in terms of the distributed database perspective. The primary targeted consumers are expected to be machines; a fair degree of automation needs to be guaranteed in order to enable new types of Web applications. While nowadays the number of datasets-published in accordance to the linked data principles <ref type="bibr" target="#b1">[2]</ref>-is somewhat limited, this is expected to change soon. Considering thousands if not millions of linked datasets <ref type="foot" target="#foot_0">1</ref> , one can expect to get lost, soon when trying to identify appropriate datasets for a certain task.</p><p>Two issues come to mind when talking about selecting (possibly many) datasets: efficiency and effectiveness. While the former basically refers to how fast certain datasets can be identified, the latter focuses on the relevancy, that is how well the dataset fulfills the stated requirements in a certain context (the domain of the Web application). When faced with a list of potential candidates, one usually wants to rank them according to certain criteria in order to select the most relevant ones.</p><p>Our thesis at hand now is that, based on a formal (highlevel) description of a dataset's content and interlinking provided by voiD, Semantic Web clients can effectively rank datasets using well-known strategies such as PageRank <ref type="bibr" target="#b3">[4]</ref> or HITS <ref type="bibr" target="#b4">[5]</ref> in a very efficient way. Without such highlevel descriptions, the client would have to "crawl" a large number of documents in order to analyze and derive precise statistics about the content of a dataset, hereby requiring an excessive amount of time and resources.</p><p>The rest of the paper is structured as follows: the next section discusses exitsing approaches. Then, we lay out the foundations regarding the formal description of linked datasets in sec. 3 and render our proposal in detail (sec. 4). Further, in sec. 5, we report on early findings when comparing our approach to widely used ones such as PageRank or HITS. We conclude in sec. 6 by discussing the proposed ranking methodology and point out possible future steps.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">EXISTING WORKS</head><p>Link analysis has proven to be effective for query independent quality web search. PageRanks <ref type="bibr" target="#b3">[4]</ref> and HITS <ref type="bibr" target="#b4">[5]</ref> have been successfully applied to measure the importance of web pages by analysing their link structure. These two algorithms consider only one type of links, i.e. hyperlinks, but has been shown to improve the effectiveness of web search engines <ref type="bibr" target="#b5">[6,</ref><ref type="bibr" target="#b6">7]</ref>.</p><p>When working on a finer granularity level -such as entity level -with more heterogeneous links, the previous approaches are no longer applicable. In such condition, by assuming that links are equivalent, the analysis of entity relationships does not provide accurate results since links of different types can have various impact on the ranking computation.</p><p>Recent works <ref type="bibr" target="#b7">[8,</ref><ref type="bibr" target="#b8">9]</ref> have extended PageRank to consider different types of relations between entities or objects. Pop-Rank <ref type="bibr" target="#b9">[10]</ref>, a domain independent object-level link analysis, proposes a machine learning approach to automatically assigns a "popularity propagation factor" to each type of relations. ObjectRank <ref type="bibr" target="#b10">[11]</ref> goes further by applying authoritybased ranking to keyword search in databases where various objects are connected with semantic relations.</p><p>The Swoogle search engine <ref type="bibr" target="#b11">[12]</ref> was the first one to propose, OntoRank, an adaptation of PageRank for Semantic Web resources. In their work, they compute popularity of resources based on three levels of granularity: documents, terms and RDF graphs. In <ref type="bibr" target="#b12">[13]</ref>, a link analysis is applied at query time for computing the popularity of resources and contexts (which can be seen as documents or datasets).</p><p>Their approach differentiates two levels of link analysis, resources and context graphs, and the different relationships between them.</p><p>In this paper, we are studying how to improve search results by ranking datasets according to their popularity. Our approach is based on link analysis between datasets by using the information provided by the voiD descriptions. We consider the types of relationships but also the cardinality of link sets. We propose also an automatic weighting scheme to find appropriate weights for relation types.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">DESCRIBING DATASETS</head><p>In order to realise our vision of a semantic ranking, we build upon a formal description of the datasets and their interlinking. Only recently the Vocabulary of Interlinked Datasets (voiD) <ref type="bibr" target="#b13">[14]</ref> has been released; voiD is an RDFS vocabulary for describing linked datasets. A dataset in voiD is "a collection of data, published and maintained by a single provider, available as RDF, and accessible, for example, through dereferenceable HTTP URIs or a SPARQL endpoint". Interlinking in voiD is modeled utilising a so called linksets. A linkset in voiD is "a subset of a dataset, used for storing triples to express the interlinking relationship between datasets; in each interlinking triple, the subject is a resource hosted in one dataset and the object is a resource hosted in another dataset".</p><p>Given that such voiD descriptions are published alongside with the datasets, they can be collected via pings, by crawling, or simply follow-your-nose by a semantic indexer such as Sindice <ref type="bibr" target="#b14">[15]</ref> or the Yahoo! Search Monkey <ref type="bibr" target="#b15">[16]</ref>. We assume such a collection of voiD descriptions in the following. We note further that, as voiD being metadata about linked data, is RDF-grounded, we can use all current RDF tools and libraries to process, store and visualise it. Further, it is perfectly possible to go from the meta-level to the metameta-level, that is having a voiD description about voiD descriptions.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">DING-DATASET RANKING</head><p>Our proposal for a semantic ranking of RDF datasets is called DING (from Dataset RankING) and is based on voiD descriptions of the datasets.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1">Exploiting voiD's characteristics</head><p>Based on the voiD guide <ref type="bibr" target="#b16">[17]</ref> we will review the relevant features of voiD in the following and discuss their suitability with respect to dataset selection and ranking.</p><p>• The size of the dataset, that is, for example the number of triples or the number of distinct subjects can be used for ranking. In voiD this is a void:statItem property along with one of five predefined dimensions such as void:numberOfTriples or void:numberOfDocuments. We have argued in <ref type="bibr" target="#b17">[18]</ref> recently that the sheer numbers of triples is likely not a good measure for its value.</p><p>• Categorisation of datasets in voiD is done using dcterms:subject along with DBpedia <ref type="bibr" target="#b18">[19]</ref> resources. This can be used in a first step to massively decrease the search space. It acts as a sort of lexicon allowing to lookup a category and find related datasets. As a second step, DING can be used to rank the list of datasets matching a certain category.</p><p>• The interlinking of a dataset in voiD, that is, its outgoing and incoming links, is represented using the void:linkPredicate property. We identify two potential dimensions that might be exploited for ranking:</p><p>regarding the semantics of the links (such as rdfs-:seeAlso vs. foaf:knows) and on a quantitative level, that is regarding the number of interlinking triples.</p><p>• The kind of and number of used vocabularies in a dataset can be seen from the void:vocabulary property value.</p><p>• Other voiD characteristics such as void:uriRegexPattern or the technical features of a dataset (such as available serialisations) via void:TechnicalFeature) can not directly be used for ranking, though perfectly for filtering (as in case with categorisation).</p><p>The following example in Fig. <ref type="figure" target="#fig_0">1</ref> may help highlight our thinking: </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.2">DING! Implementation</head><p>In this section, we present how we adapted the weighted PageRank algorithm in order to perform the Dataset ranking based on their interconnection. We then explain how it is possible to assign automatically a weight to a certain link type.</p><p>PageRank is a ranking system that originates from Web Search Engines using a random walk algorithm. The Ranking system evaluates the probability of finding the web surfer on any given page. This algorithm is based on the assumption that when someone publishes a resource on the web, he will do his best to link the published resource -be it a web page, or in our case -a dataset -to the most relevant and trustworthy resources availiable on the web. Hence the relevancy is assumed to be related to a high degree of inlinks from other web resources. And from a probabilistic point of view -the more inlinks a dataset has, the most likely the 'random surfer' will be lead to it in his journey.</p><p>The original PageRank r(Pi) of a web page i is given by r(Pi) = X Listing 1: An exemplary voiD description.</p><formula xml:id="formula_0">P j ∈B P i r(Pj) |Pj|<label>(1</label></formula><p>Where BP i is the set of pages linking to Pi and |Pj| is the total number of pages linked by Pj . Hence, 1 |P j | is in fact the probability for the random surfer to choose to go from Pj to Pi out of all pages linked by Pj. This probability referred to as pj→i, can be modified in order to provide a weighting of the "importance" of the hyperlink.</p><p>The parallel from web documents to voiD descriptions is done in a naive way. The web pages are now datasets, and the hyperlinks correspond to linksets joining the dataset they belong to another:</p><p>• Pi corresponds to an element Di define by void:dataset.</p><p>• A hyperlink form in the page Pi pointing to the page Pj will correspond to a void:linkset element connecting Di and Dj, defined as void:subset of a dataset Di. The linkset will be referred to as Li→j. We also define n(Li→j) as the number of relations in the linkset, and s(Li→j) as the predicate declared in the linkset. For example, in Fig. <ref type="figure" target="#fig_0">1</ref> n(L1→3) = 600 and s(L1→3) = "foaf:interest". L is the set of linksets defined in the entire data collection.</p><p>• Similarly to the set BP i of pages linking to Pi, we define O(i) = {j|∃Li→j ∈ L} as the indices of datasets linked from Di.</p><p>• pi→j can be modified according to the information available about the linkest Li→j, such as s(Li→j) or n(Li→j), as well as general statistics over L.</p><p>Like in the web page link analysis, the links between datasets deserve a deeper analysis in order to obtain a finer ranking. For example in Fig. <ref type="figure" target="#fig_0">1</ref> the probability of the user going from DS1 to DS3 is likely to be different from the probability of going to DS4 -since the predicate and number of links associated to L1→3 are not the same as the ones associated to L1→4.</p><p>The goal will hence be to define a weight function w(Li→j). The weight will then be normalized in order to generate the transition probability pi→j as follows.</p><formula xml:id="formula_1">pi→j = w(Li→j) P k∈O(i) w(L i→k )<label>(2)</label></formula><p>The first approach is simply to define w(Li→j) = n(Li→j) .</p><p>In the case of Fig. <ref type="figure" target="#fig_0">1</ref>, p1→3 = 600 2000+600 0.23 and p1→4 = 2000 2000+600 0.77. However, this definition does not take into account the nature of the link, and the likelihood that the user may well chose foaf:interest above dc:author to browse into another dataset. As a result, additional weights can be assigned based on the nature of the predicate involved in the link.</p><p>The values assigned can be either statically predefined, or computed dynamically, given the accumulated voiD information. We present our approach, based on TF-IDF a well known algorithm when it comes to weight the relevance of a term(in our case -the predicate), given its frequency in a data collection. Hence, the weight, given by TF-IDF would be</p><formula xml:id="formula_2">T F (Li→j) = n(Li→j) max k∈O(i) n(L i→k )<label>(3)</label></formula><formula xml:id="formula_3">IDF (s(Li→j)) = log N 1 + f req(s(Li→j))<label>(4)</label></formula><p>Where f req(s(Li→j)) is the frequency of occurrence of linksets using the predicate of Li→j in the collection's datasets. Finally, we define w as</p><formula xml:id="formula_4">w(Li→j) = T F (Li→j) × IDF (s(Li→j))<label>(5)</label></formula></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">EXPERIMENTS AND EARLY FINDINGS</head><p>In order to verify our thesis that formal descriptions of linked datasets help yielding better results for the ranking of the datasets, we have set up an evaluation framework that executes various ranking algorithms on a synthetic voiD description<ref type="foot" target="#foot_1">2</ref> (see Fig. <ref type="figure" target="#fig_2">2</ref>). It is composed of 15 artificial dataset descriptions interlinked using 8 different predicates and partitioned into two clouds (datasets 1 to 9 and 10 to 15). The experiment used several ranking algorithms to estimate the generic relevancy of every artificial dataset within the synthetic cloud.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.1">The setup</head><p>For the evaluation we use the Java Universal Network/-Graph Framework (JUNG) <ref type="foot" target="#foot_2">3</ref> to compare the DING algorithm with other established and well known ranking algorithms. Further, we use a naive link-sum rank function (DRank ) as a baseline to discuss the results. Three out of the four ranking algorithms are also extended with the DING link weight function. In detail we evaluate and compare the following ranking algorithms: Table <ref type="table">1</ref>: Evaluation results: the top 6 datasets for each ranking algorithm with their normalized score</p><p>• DRank: A baseline ranking algorithm using a naive approach. The datasets are ranked according to the number of links they have with other datasets.</p><p>• PageRank Google's page rank algorithm <ref type="bibr" target="#b3">[4]</ref>.</p><p>• DING PageRank modification of the PageRank Algorithm as described in Sec 4.2</p><p>• HITS Another well known ranking algorithm is HITS <ref type="bibr" target="#b4">[5]</ref>. For each data set in the voiD graph a "hubs-andauthorities" importance measure is calculated.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.2">Results</head><p>Table <ref type="table">1</ref> lists the results of the evaluation. The naive ranking approach, DRank, completely leaves out the first cloud for having much less links in its linksets than the second cloud. We see that standard PageRank and HITS algorithms do not take into account the nature of the links and rank DS1 first. Although DS1 is indeed heavily linked by other datasets, it is mostly inlinked by "weak" links like owl:sameAs or rdfs:seeAlso. The information-theory view defined in tfidf suggests that these links -being the most common ones -do not hold as much information content as less common ones, and are therefore less significant. For example while looking for information about an article, the user will get more precise information following dcterms:author than a generic property such as rdfs:seeAlso, and is hence more likely to follow the former. As a result a dataset linked by uncommon links will likely be more significant than one linked by common ones -and should have a higher voiD ranking.</p><p>Another advantage of PageRank that makes it very relevant for the Linked Data approach is that it gives a low ranking to datasets that do not have inlinks. The value of a dataset within the cloud is dependent on how well it is linked by other datasets.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">CONCLUSION</head><p>We have presented DING, a new approach to rank linked datasets based on voiD descriptions. Though one might object that currently there are not many voiD descriptions available <ref type="foot" target="#foot_3">4</ref> we argued that this is very likely to change soon. Further, the infrastructure to collect voiD descriptions is in place (voiD being RDF, the requirements to do so are minimal).</p><p>We have motivated the need for a efficient and effective way to rank datasets based on their characteristics (contentwise and with respect to the interlinking). Finally we have shown how DING performs in relation to existing ranking algorithms and discussed the results. </p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: Exemplary collection of four voiD descriptions.</figDesc><graphic coords="2,328.77,284.52,215.19,151.85" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head></head><label></label><figDesc>12) DS13 (0.072) DS10 (0.056) DING PageRank DS4 (0.18) DS1 (0.14) DS11 (0.12) DS13 (0.091) DS3 (0.081) DS10 (0.074) DRank DS10 (0.35) DS13 (0.16) DS12 (0.16) DS11 (0.12) DS15 (0.11) DS14 (0.044) HITS DS1 (0.43) DS4 (0.28) DS2 (0.11) DS3 (0.094) DS11 (0.022) DS10 (0.017)</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2: Visualisation of the synthetical dataset network</figDesc><graphic coords="4,316.81,152.13,239.10,209.69" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head></head><label></label><figDesc>)</figDesc><table><row><cell cols="2">1 : DS1 a void : Dataset ;</cell></row><row><cell>2</cell><cell>foaf : homepage &lt; http :// example . org / cats / &gt; ;</cell></row><row><cell>3</cell><cell>dcterms : subject</cell></row><row><cell></cell><cell>&lt; http :// dbpedia . org / r e s o u r c e / Cats &gt; ;</cell></row><row><cell>4</cell><cell>void : subset : DS1toDS3 ;</cell></row><row><cell>5</cell><cell>void : subset : DS1toDS4 .</cell></row><row><cell>6</cell><cell></cell></row><row><cell cols="2">7 : DS2 a void : Dataset ;</cell></row><row><cell>8</cell><cell>foaf : homepage &lt; http :// petfood . example . org / &gt; ;</cell></row><row><cell>9</cell><cell>dcterms : subject</cell></row><row><cell></cell><cell>&lt; http :// dbpedia . org / r e s o u r c e / Cats &gt; ;</cell></row><row><cell>10</cell><cell>dcterms : subject</cell></row><row><cell></cell><cell>&lt; http :// dbpedia . org / r e s o u r c e / P e t _ f o o d s &gt; ;</cell></row><row><cell>11</cell><cell>void : subset : DS2toDS1 .</cell></row><row><cell>12</cell><cell></cell></row><row><cell cols="2">13 : DS1toDS3 a void : Linkset ;</cell></row><row><cell>14</cell><cell>void : sub jectsTa rget : DS1 ;</cell></row><row><cell>15</cell><cell>void : objectsTarget : DS3 ;</cell></row><row><cell>16</cell><cell>void : linkPredicate foaf : interest ;</cell></row><row><cell>17</cell><cell>void : statItem [</cell></row><row><cell>18</cell><cell>rdf : value 600;</cell></row><row><cell>19</cell><cell>scovo : dimension void : n um be rO f Tr ip l es ;</cell></row><row><cell>20</cell><cell>] .</cell></row><row><cell>21</cell><cell></cell></row><row><cell cols="2">22 : DS2toDS1 a void : Linkset ;</cell></row><row><cell>23</cell><cell>void : target : DS1 ;</cell></row><row><cell>24</cell><cell>void : target : DS2 ;</cell></row><row><cell>25</cell><cell>void : linkPredicate owl : sameAs ;</cell></row><row><cell>26</cell><cell>void : statItem [</cell></row><row><cell>27</cell><cell>rdf : value 10000;</cell></row></table><note>28 scovo : dimension void : n um be rO f Tr ip l es ; 29 ] .</note></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">A simple estimation might support this argument: take for example relational databases such as MySQL found in nearly every modern Web application, or the manifold repositories in the software development domain (for example, CVS or SVN) or registries (LDAP, OPACs, etc.)-each of them, once on the Web of Data (using out-of-the-box linked data publishing tools such as Triplify<ref type="bibr" target="#b2">[3]</ref>) represents at least one dataset.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">The full benchmark data is available at http://sw.deri. org/2009/02/DING/example-void-collection.ttl. Unfortunately no real-world voiD cloud was readily availiable for the experiment at the time of writing.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">3 http://jung.sourceforge.net/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_3">Indeed one finds voiD descriptions at time of writing, already; see for example http://void.rkbexplorer.com/.</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgements</head><p>Our work has partly been supported by the European Commission under Grant No. 217031, FP7/ICT-2007.1.2, project "Domain Driven Design and Mashup Oriented Development based on Open Source Java Metaframework for Pragmatic, Reliable and Secure Web Development" (Romulus) 5 , by the European FP7 project Okkam -Enabling a Web of Entities (contract no. ICT-215032), and by Science Foundation Ireland under Grant No. SFI/02/CE1/I131.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Which Semantic Web?</title>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">C</forename><surname>Marshall</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">M</forename><surname>Shipman</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the fourteenth ACM conference on Hypertext and hypermedia</title>
				<meeting>the fourteenth ACM conference on Hypertext and hypermedia<address><addrLine>New York, NY, USA</addrLine></address></meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2003">2003</date>
			<biblScope unit="page" from="57" to="66" />
		</imprint>
	</monogr>
	<note>HYPERTEXT &apos;03</note>
</biblStruct>

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

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Triplify -Lightweight Linked Data Publication from Relational Databases</title>
		<author>
			<persName><forename type="first">S</forename><surname>Auer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Dietzold</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Lehmann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Hellmann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Aumueller</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International World Wide Web Conference (WWW 09)</title>
				<meeting><address><addrLine>Madrid, Spain</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
	<note>page upcoming</note>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<author>
			<persName><forename type="first">Lawrence</forename><surname>Page</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Sergey</forename><surname>Brin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Rajeev</forename><surname>Motwani</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Terry</forename><surname>Winograd</surname></persName>
		</author>
		<ptr target="http://www.ict-romulus.eu/Bringingordertotheweb.TechnicalReport1999-66" />
		<title level="m">The pagerank citation ranking: 5</title>
				<imprint>
			<date type="published" when="1999-11">November 1999</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Authoritative sources in a hyperlinked environment</title>
		<author>
			<persName><forename type="first">Jon</forename><forename type="middle">M</forename><surname>Kleinberg</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">J. ACM</title>
		<imprint>
			<biblScope unit="volume">46</biblScope>
			<biblScope unit="issue">5</biblScope>
			<biblScope unit="page" from="604" to="632" />
			<date type="published" when="1999">1999</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">The anatomy of a large-scale hypertextual web search engine</title>
		<author>
			<persName><forename type="first">Sergey</forename><surname>Brin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Lawrence</forename><surname>Page</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Comput. Netw. ISDN Syst</title>
		<imprint>
			<biblScope unit="volume">30</biblScope>
			<biblScope unit="issue">1-7</biblScope>
			<biblScope unit="page" from="107" to="117" />
			<date type="published" when="1998">1998</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Mining the web&apos;s link structure</title>
		<author>
			<persName><forename type="first">Soumen</forename><surname>Chakrabarti</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Byron</forename><forename type="middle">E</forename><surname>Dom</surname></persName>
		</author>
		<author>
			<persName><forename type="first">David</forename><surname>Gibson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Jon</forename><surname>Kleinberg</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Ravi</forename><surname>Kumar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Prabhakar</forename><surname>Raghavan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Andrew</forename><surname>Sridhar Rajagopalan</surname></persName>
		</author>
		<author>
			<persName><surname>Tomkins</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Computer</title>
		<imprint>
			<biblScope unit="volume">32</biblScope>
			<biblScope unit="issue">8</biblScope>
			<biblScope unit="page" from="60" to="67" />
			<date type="published" when="1999">1999</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Weighted pagerank algorithm</title>
		<author>
			<persName><forename type="first">Wenpu</forename><surname>Xing</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Ali</forename><surname>Ghorbani</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">CNSR &apos;04: Proceedings of the Second Annual Conference on Communication Networks and Services Research</title>
				<meeting><address><addrLine>Washington, DC, USA</addrLine></address></meeting>
		<imprint>
			<publisher>IEEE Computer Society</publisher>
			<date type="published" when="2004">2004</date>
			<biblScope unit="volume">0</biblScope>
			<biblScope unit="page" from="305" to="314" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Web page ranking using link attributes</title>
		<author>
			<persName><forename type="first">Ricardo</forename><surname>Baeza</surname></persName>
		</author>
		<author>
			<persName><forename type="first">-</forename><surname>Yates</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Emilio</forename><surname>Davis</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 13th international World Wide Web conference on Alternate track papers &amp; posters</title>
				<meeting>the 13th international World Wide Web conference on Alternate track papers &amp; posters<address><addrLine>New York, NY, USA</addrLine></address></meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2004">2004</date>
			<biblScope unit="page" from="328" to="329" />
		</imprint>
	</monogr>
	<note>WWW Alt. &apos;04</note>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Object-level ranking: bringing order to Web objects</title>
		<author>
			<persName><forename type="first">Zaiqing</forename><surname>Nie</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Yuanzhi</forename><surname>Zhang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Ji-Rong</forename><surname>Wen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Wei-Ying</forename><surname>Ma</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 14th international conference on World Wide Web -WWW 05 WWW 05</title>
				<meeting>the 14th international conference on World Wide Web -WWW 05 WWW 05</meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2005">2005</date>
			<biblScope unit="page">567</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Objectrank: authority-based keyword search in databases</title>
		<author>
			<persName><forename type="first">Andrey</forename><surname>Balmin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Vagelis</forename><surname>Hristidis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Yannis</forename><surname>Papakonstantinou</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">VLDB &apos;04: Proceedings of the Thirtieth international conference on Very large data bases</title>
				<imprint>
			<publisher>VLDB Endowment</publisher>
			<date type="published" when="2004">2004</date>
			<biblScope unit="page" from="564" to="575" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Finding and ranking knowledge on the semantic web</title>
		<author>
			<persName><forename type="first">Li</forename><surname>Ding</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Rong</forename><surname>Pan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Timothy</forename><forename type="middle">W</forename><surname>Finin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Anupam</forename><surname>Joshi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Yun</forename><surname>Peng</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Pranam</forename><surname>Kolari</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International Semantic Web Conference</title>
				<imprint>
			<date type="published" when="2005">2005</date>
			<biblScope unit="page" from="156" to="170" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Reconrank: A scalable ranking method for semantic web data with context</title>
		<author>
			<persName><forename type="first">Aidan</forename><surname>Hogan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Andreas</forename><surname>Harth</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Stefan</forename><surname>Decker</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of Second International Workshop on Scalable Semantic Web Knowledge Base Systems (SSWS 2006)</title>
				<meeting>Second International Workshop on Scalable Semantic Web Knowledge Base Systems (SSWS 2006)<address><addrLine>Athens, GA, USA</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2006">2006</date>
			<biblScope unit="page">11</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Describing Linked Datasets -On the Design and Usage of voiD, the &apos;Vocabulary of Interlinked Datasets</title>
		<author>
			<persName><forename type="first">K</forename><surname>Alexander</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Cyganiak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Hausenblas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Zhao</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">WWW 2009 Workshop: Linked Data on the Web (LDOW2009)</title>
				<meeting><address><addrLine>Madrid, Spain</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Sindice.com: Weaving the Open Linked Data</title>
		<author>
			<persName><forename type="first">G</forename><surname>Tummarello</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Delbru</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Oren</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The Semantic Web, 6th International Semantic Web Conference, 2nd Asian Semantic Web Conference, ISWC 2007 + ASWC 2007</title>
				<imprint>
			<date type="published" when="2007">2007</date>
			<biblScope unit="page" from="552" to="565" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Microsearch: An Interface for Semantic Search</title>
		<author>
			<persName><forename type="first">P</forename><surname>Mika</surname></persName>
		</author>
		<ptr target="CEUR-WS.org" />
	</analytic>
	<monogr>
		<title level="m">Semantic Search, International Workshop located at the 5th European Semamntic Web Conference (ESWC 2008)</title>
		<title level="s">CEUR Workshop Proceedings</title>
		<imprint>
			<date type="published" when="2008">2008</date>
			<biblScope unit="volume">334</biblScope>
			<biblScope unit="page" from="79" to="88" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">voiD guide-Using the Vocabulary of Interlinked Datasets</title>
		<author>
			<persName><forename type="first">K</forename><surname>Alexander</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Cyganiak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Hausenblas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Zhao</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Community Draft, voiD working group</title>
				<imprint>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">What is the Size of the Semantic Web</title>
		<author>
			<persName><forename type="first">Michael</forename><surname>Hausenblas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Wolfgang</forename><surname>Halb</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Yves</forename><surname>Raimond</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Tom</forename><surname>Heath</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of I-Semantics 2008</title>
				<meeting>I-Semantics 2008<address><addrLine>Graz, Austria</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<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">G</forename><surname>Kobilarov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Lehmann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Cyganiak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Z</forename><forename type="middle">G</forename><surname>Ives</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The Semantic Web, 6th International Semantic Web Conference, 2nd Asian Semantic Web Conference, ISWC 2007 + ASWC 2007</title>
				<imprint>
			<date type="published" when="2007">2007</date>
			<biblScope unit="page" from="722" to="735" />
		</imprint>
	</monogr>
</biblStruct>

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