The recent Wikipedia imbroglio centered around
DBpedia is the fundamental driver for this
particular blog post. At time of writing this blog post,
the DBpedia project definition in Wikipedia
remains unsatisfactory due to the following shortcomings:
Here are some insights on DBpedia, from the perspective of
someone intimately involved with the other three-quarters of the
A live Web accessible RDF
model database (Quad Store) derived from Wikipedia content
snapshots, taken periodically. The RDF database underlies a
Linked Data Space comprised of: HTML (and most recently
HTML+RDFa) based data browser pages and a SPARQL endpoint.
Note: DBpedia 3.4 now exists in snapshot
(warehouse) and Live Editions (currently being hot-staged).
This post is about the snapshot (warehouse) edition, I'll drop a
different post about the DBpedia Live Edition where a new
Delta-Engine covers both extraction and database record
replacement, in realtime.
As an idea under the moniker "DBpedia" it was conceptualized in
late 2006 by researchers at University of Leipzig (lead by Soren
Auer) and Freie University, Berlin (lead by Chris Bizer). The first public instance of
DBpedia (as described above) was released in February 2007. The
official DBpedia coming out party occurred at WWW2007, Banff,
during the inaugural Linked Data gathering, where it
showcased the virtues and immense potential of TimBL's Linked Data meme.
OpenLink Software (developers of OpenLink
Virtuoso and providers of Web Hosting
infrastructure), University of Leipzig, and Freie Univerity,
Berlin. In addition, there is a burgeoning community of
collaborators and contributors responsible DBpedia based
applications, cross-linked data sets, ontologies (OpenCyc,
SUMO, UMBEL, and YAGO) and other utilities. Finally, DBpedia
wouldn't be possible without the global content contribution and
curation efforts of Wikipedians, a point typically overlooked
The steps are as follows:
In a nutshell, there are four distinct and vital components to
DBpedia. Thus, DBpedia doesn't exist if all the project offered was
a collection of RDF data dumps. Likewise, it doesn't exist without
a fully populated SPARQL compliant Quad Store. Last but not least,
it doesn't exist if you have a fully loaded SPARQL compliant Quad
Store isn't up to the cocktail of challenges (query load and
complexity) presented by live Web database accessibility.
It remains a live exemplar for any individual or organization
seeking to publishing or exploit HTTP based Linked Data on the
World Wide Web. Its existence continues to
stimulate growth in both density and quality of the burgeoning Web
of Linked Data.
In the most basic sense, simply browse the HTML based resource
decriptor pages en route to discovering erstwhile undiscovered
relationships that exist across named entities and subject
matter concepts / headings. Beyond that, simply look at DBpedia
as a master lookup table in a Web hosted distributed database setup; enabling you to
mesh your local domain specific details with DBpedia records via
structured relations (triples or 3-tuples records), comprised of
HTTP URIs from both realms e.g., via owl:sameAs relations.
Expanding on the Master-Details point above, you can use its
rich URI corpus to alleviate tedium associated
with activities such as:
About this entry:
Author: Kingsley Uyi Idehen
Published: 01/31/2010 17:43 GMT-0500
Modified: 09/15/2010 18:10 GMT-0500
Tags: rdf , linked_data , semanticweb , sparql , virtuoso , openlink , DataSpace
Categories: Virtual Database ,
Semantic Web ,
Web Services (Web 2.0)
Comment Status: 0
This document is empty and basically useless. It is generated by a web service that can make some statements in HTML Microdata format.
This time the service made zero such statements, sorry.