W3C home > Mailing lists > Public > public-lod@w3.org > March 2010

Re: RelFinder - Version 1.0 released

From: Steffen Lohmann <steffen.lohmann@uni-duisburg-essen.de>
Date: Mon, 15 Mar 2010 14:16:21 +0100
Message-ID: <4B9E3325.6060202@uni-duisburg-essen.de>
To: Kingsley Idehen <kidehen@openlinksw.com>
CC: public-lod@w3.org, semantic-web@w3.org, dbpedia-discussion@lists.sourceforge.net, Timo Stegemann <timo.stegemann@uni-due.de>, Philipp Heim <philipp.heim@vis.uni-stuttgart.de>, Virtuoso Users <virtuoso-users@lists.sourceforge.net>
Thanks Kingsley,

I quickly added URIBurner as a dataset but cannot see the added value 
w.r.t. the RelFinder - your Google-Apple example produces mainly 
"seeAlso" links, which are not that helpful to discover new 
relationships. Here is the link with the parameters:
http://relfinder.semanticweb.org/RelFinder.swf?obj1=R29vZ2xlfGh0dHA6Ly9kYnBlZGlhLm9yZy9yZXNvdXJjZS9Hb29nbGU=&obj2=QXBwbGV8aHR0cDovL2RicGVkaWEub3JnL3Jlc291cmNlL0FwcGxl&name=VVJJQnVybmVy&abbreviation=YnVybmVy&description=QSBzZXJ2aWNlIHRoYXQgZGVsaXZlcnMgUkRGLWJhc2VkIHN0cnVjdHVyZWQgZGVzY3JpcHRpb25zIG9mIFdlYiBhZGRyZXNzYWJsZSByZXNvdXJjZXMgKGRvY3VtZW50cyBvciByZWFsIHdvcmxkIG9iamVjdHMpIGluIGEgdmFyaWV0eSBvZiBmb3JtYXRzIHRocm91Z2ggR2VuZXJpYyBIVFRQIFVSSXMu&endpointURI=aHR0cDovL3VyaWJ1cm5lci5jb20vc3BhcnFs&isVirtuoso=dHJ1ZQ==&useProxy=dHJ1ZQ==&autocompleteURIs=aHR0cDovL3d3dy53My5vcmcvMjAwMC8wMS9yZGYtc2NoZW1hI2xhYmVs&imageURIs=aHR0cDovL3htbG5zLmNvbS9mb2FmLzAuMS9kZXBpY3Rpb24=&linkURIs=aHR0cDovL3htbG5zLmNvbS9mb2FmLzAuMS9wYWdl&maxRelationLegth=Mg==

Once again a demonstration that variety of link types is a big challenge 
when automatically generating RDF data (link variety is indeed important 
for the RelFinder).

Anyways - thanks for the pointer. We are generally interest in 
integrating further datasets to the RelFinder's default installation (as 
long as they produce valuable relationships). Further ideas and links 
are welcome!

Steffen

--
Kingsley Idehen schrieb:
> Steffen,
>
> Very cool!
>
> Please add: http://uriburner.com/sparql to the default list of SPARQL 
> endpoints. The effect of doing this ups the implications of this tool 
> exponentially! Try it yourself e.g. Google to Apple (use the DBpedia 
> URIs).
>
> The density of the graph, the response time provide quite an 
> experience to the user (especially a Linked Data neophyte).
>
> Notes about URIBurner:
>
> 1. Quad Store is populated progressively with contributions by anyone 
> that uses the service to seek structured descriptions of an HTTP 
> accessible resource via ODE bookmarklets, browser extensions, or 
> SPARQL FROM Clause that references external Data Sources
> 2. As part of the graph construction process it not only performs RDF 
> model transformation (re. non RDF data sources); it also performs LOD 
> cloud lookups and joins, ditto across 30+ Web 2.0 APIs
> 3. Anyone with a Virtuoso installation that enables the RDF Mapper VAD 
> (which is how the Sponger Middleware is packaged) ends up with their 
> own personal or service specific variant of URIBurner.
>
> Again, great stuff, this tool is going to simplify the message, a lot 
> re., Linked Data and its penchant for serendipitous discovery of 
> relevant things.
>
>
Received on Monday, 15 March 2010 13:17:15 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:25 UTC