http://www.openlinksw.com/GData/127/?q=linked+data+planet
Kingsley Idehen's Blog Data Space
2026-06-14T04:46:25Z
Kingsley Uyi Idehen
kidehen@openlinksw.com
About linked data planet
12
1
10
http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1385
<p>The build up to <a href="http://www.linkeddataplanet.com" id="link-id110a2350">Linked Data Planet</a> continues... Here is <a href="http://www.semanticweb.com" id="link-id11083a68">semanticweb.com</a>'s interview with <a href="http://www.cs.rpi.edu/~hendler/" id="link-id10c4e560">Jim Hendler</a> and *<a href="http://community.linkeddata.org/dataspace/person/kidehen2#this" id="link-id10e71dc8">I</a>* titled: <a href="http://www.semanticweb.com//article.php/3751731" id="link-id1071c688">Linked Data Leaders - The Semantic Web is Here</a>.</p>
Internet.com Interviews Jim Hendler & I
2008-06-12T00:55:15Z
2008-06-11T20:55:15-04:00
Kingsley Uyi Idehen
kidehen@openlinksw.com
http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1384
<p>As I start my countdown to the upcoming <a href="http://www.linkeddataplanet.com" id="link-id106a81b8">Linked Data Planet conference</a>, here is the first of a series of posts geared towards showcasing practical use of the burgeoning <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id109470d0">Linked Data Web</a>.</p> <p>First up, the Library of Congress, take a look at the following pages which are "Human" and machine based "User Agent" friendly:</p> <ul> <li> <a href="http://lcsh.info/sh85118553#concept" id="link-id102927f8">Science</a> </li> <li> <a href="http://lcsh.info/sh85062913#concept" id="link-id10f13820">Humanities</a> </li> <li> <a href="http://lcsh.info/sh85082139#concept" id="link-id10ca5c58">Mathematics</a> </li> <li> <a href="http://lcsh.info/sh85020816#concept" id="link-id1230aef8">Cataloging</a> </li> <li> <a href="http://lcsh.info/sh95000541#concept" id="link-id1110e140">World Wide Web</a> </li> </ul> <p>Key point: The pages above are served up in line with <a href="http://dbpedia.org/resource/Linked_Data" id="link-id102f96a8">Linked Data</a> deployment and publishing tenets espoused by the <a href="http://community.linkeddata.org/dataspace/organization/lod#this" id="link-id10685ed8">Linking Open Data Community</a> (<a href="http://community.linkeddata.org/dataspace/organization/lod#this" id="link-id103915b0">LOD</a>) which include (in my preferred terminology):</p> <ul> <li>Giving "Names" to things you observe (aka <a href="http://dbpedia.org/resource/Data">Data</a> Source Names or "DSNs" for short)</li> <li>Use HTTP URLs in your data source naming scheme so that "access by reference" to your data sources exploits the expanse of the HTTP driven <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> i.e make your DSNs "<a href="http://dbpedia.org/resource/Linked_Data" id="link-id1071cb88">Linked Data Source Names</a>" (LDNS)</li> <li>Remember that Documents / Pages are compound in nature, and they aren't the only data sources we would want to name; a document's LDSN must be distinct from the LDSNs used for the <a href="http://dbpedia.org/resource/Topic" id="link-id10c020d0">subject matter concepts</a> and/or <a href="http://dbpedia.org/resource/Named_entity_recognition" id="link-ide7a0a58">named entities</a> associated with a document </li> <li> Use the RDF Data Model to express structure within your data source(s)</li> <li>Use LDSNs when constructing statements/claims/assertions/records (triples) inside your structured data sources</li> <li> When publishing Web Pages related to your data sources; use at least one of the following to methods to guide user agents to data sources associated with your published page; the HTML <a href="http://blogs.usnet.private:8893/RPC2" id="link-id12326c48">LINK tag</a>, <a href="http://dbpedia.org/resource/RDFa" id="link-id10751788">RDFa</a>, <a href="http://dbpedia.org/resource/GRDDL" id="link-id1050e290">GRDDL</a>, or <a href="http://dbpedia.org/resource/Content_negotiation" id="link-id12e930b0">Content Negotiation</a>. </li> </ul> <p>The items above are features that users and decision makers should start to hone into when seeking, and evaluating, platforms that facilitate cost-effective exploitation of the <a href="http://dbpedia.org/resource/Linked_Data" id="link-id0x9dde928">Linked Data</a> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id0x18c3b1c0">Web</a>.</p>
Linked Data in Action: Library of Congress
2008-06-11T17:16:31Z
2008-06-11T13:16:31.000010-04:00
Kingsley Uyi Idehen
kidehen@openlinksw.com
http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1389
<p> <a href="http://community.linkeddata.org/dataspace/person/mkbergman#this" id="link-id12dd9d88">Mike Bergman</a> has just published a nice <a href="http://feeds.feedburner.com/~r/AI3_AdaptiveInformation/~3/318146056/" id="link-id10b96a98">Linked Data FAQ</a> aimed at Enterprise audiences. His post draws on a collection of questions collated from a plethora of interactions with Enterprise oriented folks during last week's <a href="http://www.linkeddataplanet.com" id="link-id12276c00">Linked Data Planet conference</a>.</p> <p>Enjoy!</p>
A Simple Linked Data Guide for the Enterprise
2008-06-23T20:54:29Z
2008-06-23T16:54:29-04:00
Kingsley Uyi Idehen
kidehen@openlinksw.com
http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1343
<p>Typo cleansed edition :-)</p> <h2>Objectives</h2> <ul> <li>Meet <a href="http://community.linkeddata.org/dataspace/organization/lod#this" id="link-id12c52e40">LOD</a> Community Members</li> <li>Participate in Workshop </li> </ul> <h3>Meeting <a href="http://community.linkeddata.org/dataspace/organization/lod#this" id="link-id10456058">LOD</a> Community Members</h3> <p>Although the <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> continues to shrink the planet by removing the restrictions of geopgrahic location, meeting people face-to-face remains invaluable (*priceless in Mastercard AD speak*). Naturally, meeting and chatting with as many <a href="http://community.linkeddata.org/dataspace/organization/lod#this" id="link-id1382d4f8">LOD</a> community members as possible was high up on my agenda.</p> <h3>Participate in Workshop </h3> <p>As one of the co-chairs of the Linking Open <a href="http://dbpedia.org/resource/Data" id="link-id143a8c30">Data</a> Workshop (<a href="http://events.linkeddata.org/ldow2008/" id="link-id10621d70">LODW</a>), I had a 5 minute workshop opening slot during which I spoke about the following:</p> <h4>Where we are today: </h4> <p>We have <a href="http://dbpedia.org/resource/DBpedia" id="link-id109b40a0">DBpedia</a> as a major hub on the burgeoning <a href="http://dbpedia.org/resource/Linked_Data" id="link-id1074f248">Linked Data</a> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id101ed948">Web</a>. When OpenLink offered to host <a href="http://dbpedia.org/resource/DBpedia" id="link-id10cd1b20">DBpedia</a> (a combination of <a href="http://virtuoso.openlinksw.com" id="link-id13d19880">Virtuoso</a> DBMS Software and sizable backend Hardware infrastructure), it did so knowing that such an effort would emphatically address the "chicken and egg" conundrum that, prior to this undertaking, stifled the ability to demonstrate practical utility of <a href="http://dbpedia.org/resource/Hypertext_Transfer_Protocol" id="link-id13835980">HTTP</a> based <a href="http://dbpedia.org/resource/Linked_Data" id="link-id14a89c28">Linked Data</a>.<br /> <br /> Today, the <a href="http://dbpedia.org/resource/Linked_Data" id="link-id10aa9fe0">Linked Data</a> bootstrap mission has been accomplished.</p> <h4>Where we go next:</h4> <p>Although <a href="http://dbpedia.org/resource/DBpedia" id="link-id12fe5d98">DBpedia</a> is a hub (ground zero of <a href="http://dbpedia.org/resource/Linked_Data" id="link-id14aca9b8">Linked Data</a>), we have to put it into perspective in relation to a new set of needs and expectations moving forward. Today, <a href="http://dbpedia.org/resource/DBpedia" id="link-id1027f098">DBpedia</a> is a Sun at the heart of a Solar System within the <a href="http://dbpedia.org/resource/Linked_Data" id="link-id14a6adf8">Linked Data</a> Galaxy. But unlike Space as we know it, in <a href="http://dbpedia.org/resource/Cyberspace" id="link-id14a80398">Cyberspace</a> we can have connectivity and collaboration across Solar Systems -- life exists elsewhere and we are part of a collaborative collective unimpeded by constraints of space travel etc. Thus, expect to see the emergence of other Solar Systems accessible to <a href="http://dbpedia.org/resource/DBpedia" id="link-id14904998">DBpedia</a> and its collections of planets (see. <a href="http://community.linkeddata.org/dataspace/organization/lod#this" id="link-id1097d200">LOD</a> <a href="http://richard.cyganiak.de/2007/10/lod/" id="link-id14acecf0">diagram</a>). Examples underway include <a href="http://umbel.org/about/" id="link-idfe92c08">UMBEL</a> which will serve the <a href="http://dbpedia.org/resource/Linked_Data" id="link-id107fac40">Linked Data</a> planets from <a href="http://dbpedia.org/resource/Cyc" id="link-id12fb9e88">OpenCyc</a> (Subject Matter Concepts), <a href="http://www.mpi-inf.mpg.de/~suchanek/downloads/yago/" id="link-id147ea790">Yago</a> (<a href="http://dbpedia.org/resource/Named_entity_recognition" id="link-id14ae83a8">Named Entities</a>), and <a href="http://www.bio2rdf.org/" id="link-id10890640">Bio2RDF</a> (which provides powerful Bio Informatics based <a href="http://dbpedia.org/resource/Linked_Data" id="link-id1439a858">Linked Data</a> planet).</p> <p>I urged the community to veer more aggressively towards developing and demonstrating practical <a href="http://dbpedia.org/resource/Linked_Data" id="link-id11f8e188">Linked Data</a> driven solutions that are aligned to well known problems. Of course, I encouraged all presenters to make this an integral part of their presentations :-) </p> <h4>Workshop Summary: </h4> <p>The workshop was well attended and I found all the presentations engaging and full of enthusiasm. </p> <p>As the sessions progressed, it became clear during a number of accompanying Q&A sessions that a new <a href="http://dbpedia.org/resource/Linked_Data" id="link-idff249b0">Linked Data</a> exploitation frontier is emerging. The frontier in question takes the form of a <a href="http://dbpedia.org/resource/Linked_Data" id="link-id10f73b50">Linked Data</a> substrate capable of addressing the taxonomic needs of solutions aimed at automated <a href="http://dbpedia.org/resource/Named_entity_recognition" id="link-id10d16e00">Named Entity Extraction</a>, Disambiguation, Subject matter Concept alignment, transparently integrated with existing Web Content. Thus, we are moving beyond the minting and deployment of of dereferencable URIs and <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id10419210">RDF</a> <a href="http://dbpedia.org/resource/Data" id="link-id151520d0">data</a> sets to automagically associating existing Web Content with <a href="http://dbpedia.org/resource/Named_entity_recognition" id="link-id105573b0">Named Entities</a> (People, Organizations, Places, Events etc..) and Subject matter Concepts (Politics, Music, Sports, and others) while remaining true to the <a href="http://community.linkeddata.org/dataspace/organization/lod#this" id="link-id14579108">Linking Open Data Community</a> creed i.e. ensuring the Named <a href="http://dbpedia.org/resource/Entity" id="link-id147d31e8">Entity</a> and Subject matter Concept URIs are available to user agents or users seeking to produce alternative <a href="http://dbpedia.org/resource/Data" id="link-id14ae41f0">data</a> views (i.e. Mesh-ups).</p> <p>I will get to part 2 of this report once the actual workshop sessions slides go live (*these are different from the <a href="http://events.linkeddata.org/ldow2008/" id="link-id1034eee8">pre-event PDFs links</a>*).</p>
Linked Data Trip Report - Part 1 (Update 2)
2008-04-29T15:07:43Z
2008-04-29T11:07:43.000002-04:00
Kingsley Uyi Idehen
kidehen@openlinksw.com
http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1447
<p> In response to the "<a href="http://dbpedia.org/resource/Semantic_Web" id="link-id15971040">Semantic Web</a> Technology" application classification scheme espoused by <a href="http://www.readwriteweb.com" id="link-id16391540">ReadWriteWeb</a> (RWW), emphasized in the post titled: <a href="http://www.readwriteweb.com/archives/rdf_semantic_web_apps.php" id="link-id1157eaa0">Where are all the RDF-based Semantic Web Apps?</a>, here is my attempt to clarify and reintroduce what <a href="http://www.openlinksw.com/dataspace/organization/openlink#this" id="link-id15a43758">OpenLink Software</a> offers (today) in relation to Semantic Web technology. </p> <p> From the RWW Top-Down category, which I interpret as: technologies that produce RDF from non RDF <a href="http://dbpedia.org/resource/Data">data</a> sources. Our product portfolio is comprised of the following; <a href="http://virtuoso.openlinksw.com" id="link-id14f05818">Virtuoso Universal Server</a>, <a href="http://dbpedia.org/resource/OpenLink_Data_Spaces" id="link-id162c8630">OpenLink Data Spaces</a>, <a href="http://oat.openlinksw.com" id="link-id134e1a00">OpenLink Ajax Toolkit</a>, and <a href="http://ode.openlinksw.com" id="link-id160b3bf8">OpenLink Data Explorer</a> (which includes ubiquity commands).</p> <h3>Virtuoso Universal Server functionality summary:</h3> <ol> <li>Generation of RDF <a href="http://dbpedia.org/resource/Linked_Data" id="link-id161d5f50">Linked Data</a> Views of <a href="http://dbpedia.org/resource/SQL" id="link-id161d5978">SQL</a>, XML, and <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> Services in general </li> <li>Deployment of RDF Linked Data </li> <li>"On the Fly" generation of RDF Linked Data from Document Web <a href="http://www.w3.org/TR/webarch/" id="link-id178bbc08">information resources</a> (i.e. distillation of entities from their containers e.g. Web pages) via Cartridges / Drivers</li> <li> <a href="http://dbpedia.org/resource/SPARQL" id="link-id162c2118">SPARQL</a> query language support </li> <li>SPARQL extensions that bring SPARQL closer to SQL e.g Aggregates, Update, Insert, Delete Named Graph support (i.e. use of logical names to partition RDF data within Virtuoso's multi-model dbms engine) </li> <li>Inference Engine (currently in use re. <a href="http://dbpedia.org/resource/DBpedia" id="link-id14f563c0">DBpedia</a> via Yago and <a href="http://umbel.org/about/" id="link-id113273b8">UMBEL</a>)</li> <li>Host and exposes data from <a href="http://dbpedia.org/resource/Drupal" id="link-id123d3bd8">Drupal</a>, <a href="http://dbpedia.org/resource/WordPress" id="link-id141adf40">Wordpress</a>, <a href="http://dbpedia.org/resource/MediaWiki" id="link-id1604b450">MediaWiki</a>, <a href="http://dbpedia.org/resource/PhpBB" id="link-id141013a8">phpBB3</a> as RDF Linked Data via in-built support for <a href="http://dbpedia.org/resource/PHP" id="link-id14661e58">PHP</a> runtime</li> <li> <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/ODSInstallationEC2" id="link-id146c84d0">Available as an EC2 AMI</a> </li> <li>etc..</li> </ol> <h3>OpenLink Data Spaces functionality summary:</h3> <ol> <li>Simple mechanism for Linked Data <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id15473770">Web</a> enabling yourself by giving you an <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/GetAPersonalURIIn5MinutesOrLess" id="link-id15f6d278">HTTP based User ID</a> (a de-referencable <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id15aaeb68">URI</a>) that is linked to a <a href="http://myopenlink.net/dataspace/person/kidehen" id="link-id15a7a840">FOAF based Profile page</a> and OpenID</li> <li>Binds all your data sources (blogs, wikis, bookmarks, photos, calendar items etc. ) to your URI so can "Find" things by only remembering your URI</li> <li>Makes your profile page and personal URI the focal point of Linked Data Web presence</li> <li>Delivers Data Portability (using data access by value or <a href="http://dbpedia.org/resource/Reference_(computer_science)" id="link-id16212838">data access by reference</a>) across data silos (e.g. Web 2.0 style social networks)</li> <li>Allows you make annotations about anything in your own <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id14668010">Data Space</a>(s) on the Web without exposure to RDF markup</li> <li>A Briefcase feature that provides a WebDAV driven RDF Linked Data variant of functionality seen in Mac OS X Spotlight and WinFS with the addition of SPARQL compliance</li> <li>Automatically generates <a href="http://dbpedia.org/resource/RDFa" id="link-id14691440">RDFa</a> in its (X)HTML pages</li> <li> <a href="http://dbpedia.org/resource/Blog" id="link-id14fae7b8">Blog</a>, Wiki, WebDAV File Server, Shared Bookmarks, Calendar, and other applications that look and feel like Web 2.0 counterparts but emitt RDF Linked Data amongst a plethora of data exchange formats</li> <li>Available as an EC2 AMI</li> <li>etc..</li> </ol> <h3>OpenLink Ajax Toolkit functionality summary:</h3> <ol> <li>Provides binding to SQL, RDF, XML, and Web Services via Ajax Database Connectivity Layer (you only need an <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id11550548">ODBC</a>, <a href="http://dbpedia.org/resource/Java_Database_Connectivity" id="link-id13ae5f68">JDBC</a>, OLE-DB, <a href="http://dbpedia.org/resource/ADO.NET" id="link-id162803e8">ADO</a>.NET, XMLA Driver, or Web Service on the backend for dynamic data access from Javascript)</li> <li>All controls are Ajax Database Connectivity bound (widgets get their data from Ajax Database Connectivity data sources)</li> <li>Bundled with Virtuoso and <a href="http://dbpedia.org/resource/OpenLink_Data_Spaces" id="link-id161dfe90">ODS</a> installations.</li> <li>etc.</li> </ol> <h3>OpenLink Data Explorer functionality summary</h3> <ol> <li>Distills entities associated with information resource style containers (e.g. Web Pages or files) as RDF Linked Data</li> <li>Exposes the RDF based <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id12a42ed8">Linked Data graph</a> associated with information resources (see the Linked Data behind Web pages)</li> <li>Ubiquity commands for invoking the above</li> <li>Available as a <a href="http://linkeddata.uriburner.com/ode" id="link-id15a0d2b0">Hosted Service</a> or <a href="http://ode.openlinksw.com" id="link-id138b9fa8">Firefox Extension</a> </li> <li>Bundled with Virtuoso and ODS installations</li> <li>etc.</li> </ol> <h3>Note:</h3> <p>Of course you could have simply looked up <a href="http://www.openlinksw.com/dataspace/organization/openlink" id="link-id14ef2c10">OpenLink Software's FOAF based Profile page</a> (*note the Linked Data Explorer tab*), or simply passed the <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id14cbf5c8">FOAF</a> profile page <a href="http://dbpedia.org/resource/Uniform_Resource_Locator" id="link-id16453e28">URL</a> to a Linked Data aware client application such as: <a href="http://linkeddata.uriburner.com/ode" id="link-id15a80500">OpenLink Data Explorer</a>, <a href="http://zitgist.com/about/" id="link-id1586a360">Zitgist</a> <a href="http://dataviewer.zitgist.com" id="link-id16249f60">Data Viewer</a>, <a href="http://beckr.org/marbles" id="link-id15993fb0">Marbles</a>, and <a href="http://dig.csail.mit.edu/2005/ajar/release/tabulator/0.8/tab.html" id="link-id14d63048">Tabulator</a>, and obtained information. Remember, <a href="http://www.openlinksw.com/dataspace/organization/openlink#this" id="link-id138ba838">OpenLink Software</a> is an <a href="http://dbpedia.org/resource/Entity" id="link-id1173e120">Entity</a> of Type: <a href="http://xmlns.com/foaf/0.1/Organization" id="link-id138b87b8">foaf:Organization</a>, on the burgeoning Linked Data Web :-)</p> <h3>Related</h3> <ul> <li> <a href="http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/Creating_Deploying_Exploiting_Linked_Data2_TimBL_v3.html" id="link-id163a0c88">Linked Data Planet Keynote</a> (RDFa based remix edition)</li> <li> <a href="http://semanticbusiness.blogspot.com/2008/09/report-on-cusp-global-review-of.html" id="link-id11471a40">On The Cusp: A Global Review of the Semantic Web Industry.</a> </li> </ul>
Where Are All the RDF-based Semantic Web Applications?
2008-10-02T19:27:41Z
2008-10-02T15:27:41-04:00
Kingsley Uyi Idehen
kidehen@openlinksw.com
http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1427
<p>Here are some demonstrations of (X)HTML based representations of resource descriptions from <a href="http://www.freebase.com" id="link-id12275470">Freebase</a>, <a href="http://dbpedia.org/resource/DBpedia" id="link-id168abcc0">DBpedia</a>, <a href="http://www.bbc.co.uk/music/artists" id="link-id107c75c8">BBC Music Beta</a>, <a href="http://crunchbase.com" id="link-id1322e9a0">CrunchBase</a>, <a href="http://sw.opencyc.org" id="link-id16e09ea8">OpenCyc</a>, and <a href="http://umbel.org/about/" id="link-id188687c0">UMBEL</a> etc. What is really being demonstrated here is the use of Proxy / Wrapper URIs to expose powerful links across entities distilled from their container documents (or <a href="http://dbpedia.org/resource/Information" id="link-id13e117b0">information</a> resources). Of course, you see exactly the same technique in action whenever you visit <a href="http://dbpedia.org/resource/DBpedia" id="link-id10afe178">DBpedia</a> pages. Again, we are moving the concept of Linking from the document to document level, down to the document-<a href="http://dbpedia.org/resource/Entity" id="link-id16032730">entity</a> to document-<a href="http://dbpedia.org/resource/Entity" id="link-id13eef3d8">entity</a> level. The evolution of network link focal points is illustrated in slides <a href="http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/Creating_Deploying_Exploiting_Linked_Data2_TimBL_v3.html#(15)" id="link-id183523a8">15</a> to <a href="http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/Creating_Deploying_Exploiting_Linked_Data2_TimBL_v3.html#(22)" id="link-id18270200">22</a> of my <a href="http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/Creating_Deploying_Exploiting_Linked_Data2_TimBL_v3.html" id="link-id16f0a7c8">Linked Data Planet presentation</a> remix.</p> <h3>Live Examples</h3> <ol> <li> <a href="http://demo.openlinksw.com/proxy/html/http://www.freebase.com/view/en/abraham_lincoln" id="link-id11cf00b8">Abraham Lincoln</a> - Freebase (note: link from Freebase to <a href="http://dbpedia.org/resource/DBpedia" id="link-id17db1620">DBpedia</a> via Wikipedia)</li> <li> <a href="http://demo.openlinksw.com/proxy/html/http://www.crunchbase.com/company/amazon" id="link-id171d9930">Amazon</a> - CrunchBase (note: links from CruncBase to <a href="http://dbpedia.org/resource/DBpedia" id="link-id0x1ed41510">DBpedia</a>)</li> <li> <a href="http://demo.openlinksw.com/proxy/html/http://www.bbc.co.uk/music/artists/cc197bad-dc9c-440d-a5b5-d52ba2e14234" id="link-id10a01dc0">Cold Play</a> - <a href="http://dbpedia.org/resource/BBC" id="link-id12fa5648">BBC</a> Music Beta (note: links to <a href="http://musicbrainz.org/" id="link-id126f71c8">Musicbrainz</a>)</li> <li> <a href="http://demo.openlinksw.com/proxy/html/http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/Creating_Deploying_Exploiting_Linked_Data2_TimBL_v3.html" id="link-id1732e820">Linked Data Planet Presentation</a> - Also a Slidy, Bibo Ontology, and <a href="http://dbpedia.org/resource/RDFa" id="link-id104869a8">RDFa</a> usage example</li> <li> <a href="http://demo.openlinksw.com/proxy/html/http://sw.opencyc.org/2008/06/10/concept/en/Music" id="link-id1699d628">Music</a> - <a href="http://dbpedia.org/resource/Cyc" id="link-id126c74f0">OpenCyc</a> Concept which exposes a <a href="http://dbpedia.org/resource/Linked_Data" id="link-id15687380">Hyperdata</a> link to its equivalent <a href="http://demo.openlinksw.com/proxy/html/http://umbel.org/ns/sc/Music" id="link-id13ebbac0">UMBEL Subject Concept</a> and back</li> </ol> <h4> <a href="http://virtuoso.openlinksw.com" id="link-id10537a28">Virtuoso</a>'s RDFization Middleware & <a href="http://dbpedia.org/resource/Linked_Data" id="link-id10869440">Linked Data</a> Deployment Architecture Diagram</h4> <div> <table border="1"> <tr> <td><br /> <br /> <img src="http://virtuoso.openlinksw.com/ldp_presentation/images/linked_data_gen_opts3.png" /> <br /> <br /> </td> </tr> </table> </div> <p>Note: You can substitute my examples using any <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> resource <a href="http://dbpedia.org/resource/Uniform_Resource_Locator" id="link-id105a3e20">URL</a>. The underlying RDFization and <a href="http://dbpedia.org/resource/Linked_Data" id="link-id18155cd0">Linked Data</a> deployment functionality of the <a href="http://virtuoso.openlinksw.com" id="link-id13f56ed0">Virtuoso</a> demo instance takes care of everything else. Also note that the HTML based resource description page capability is now deployed as part of the <a href="http://virtuoso.openlinksw.com" id="link-id17db1128">Virtuoso</a> <a href="http://virtuoso.openlinksw.com/Whitepapers/html/VirtSpongerWhitePaper.html" id="link-id100a7630">Sponger</a> component of every <a href="http://virtuoso.openlinksw.com" id="link-id109eed20">Virtuoso</a> installation starting with from version <a href="http://sourceforge.net/project/shownotes.php?group_id=161622&release_id=622380" id="link-id1441f530">5.0.8.</a> </p>
Connecting Freebase, Wikipedia, DBpedia, and other Linked Data Spaces (Update 1)
2008-08-29T18:57:02Z
2008-08-29T14:57:02.000001-04:00
Kingsley Uyi Idehen
kidehen@openlinksw.com
http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1415
<p> <a href="http://www.jasonkolb.com/" id="link-id13ba6d90">Jason Kolb</a> (who <a href="http://www.jasonkolb.com/weblog/2008/08/the-future-of-t.html" id="link-id1524e210">initially</a> nudged me to chime in), and then <a href="http://www.readwriteweb.com/archives/future_of_the_desktop.php" id="link-id13a182c0">ReadWriteWeb</a>, and of course <a href="http://www.twine.com/item/11bshgkbr-1k5/the-future-of-the-desktop" id="link-id13f1e1f0">Nova's Twine about the topic</a>, have collectively started an interesting discussion about <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a>.vNext (3.0 and beyond) under the heading: The Future of the Desktop.</p> <p>My contribution to the developing discourse takes the form of a Q&A session. I've taken the questions posed and provided answers that express my particular points of view: </p> <blockquote> <cite>Q: Is the desktop of the future going to just be a web-hosted version of the same old-fashioned desktop metaphors we have today?</cite> </blockquote> <blockquote>A: No, it's going to be a more <a href="http://www.w3.org/TR/webarch/" id="link-id1524d4a0">Web Architecture</a> aware and compliant variant exposed by appropriate metaphors.</blockquote> <br /> <blockquote> <cite>Q: The desktop of the future is going to be a hosted web service</cite> </blockquote> <blockquote>A: A vessel for exploiting the virtues of the <a href="http://dbpedia.org/resource/Linked_Data" id="link-id10827ad0">Linked Data</a> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id155bc698">Web</a>.</blockquote> <br /> <blockquote> <cite>Q: The Browser is Going to Swallow Up the Desktop</cite> </blockquote> <blockquote>A: Literally, of course not! Metaphorically, of course! And then the Browser metaphor will decomposes into function specific bits of Web interaction amenable to orchestration by its users.</blockquote> <br /> <blockquote> <cite>Q: The focus of the desktop will shift from <a href="http://dbpedia.org/resource/Information" id="link-id1667e2e0">information</a> to attention</cite> </blockquote> <blockquote>A: No! <a href="http://dbpedia.org/resource/Knowledge" id="link-id104bb9c8">Knowledge</a>, <a href="http://dbpedia.org/resource/Information" id="link-id1524dd48">Information</a>, and <a href="http://dbpedia.org/resource/Data">Data</a> sharing courtesy of <a href="http://dbpedia.org/resource/Linked_Data" id="link-id10723640">Hyperdata</a> & Hypertext Linking.</blockquote> <br /> <blockquote> <cite>Q: Users are going to shift from acting as librarians to acting as daytraders</cite> </blockquote> <blockquote>A: They were Librarians at Web 1.0, Journalist at Web 2.0, and Analysts in Web 3.0 (i.e, analyze structured and interlinked data), and CEOs in Web 4.0 (i.e. get Agents to do stuff intelligently en route to making decisions).</blockquote> <blockquote> <br /> <cite>Q: The Webtop will be more social and will leverage and integrate collective intelligence</cite> </blockquote> <blockquote>A: The <a href="http://dbpedia.org/resource/Linked_Data" id="link-id13a01ed0">Linked Data</a> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id106343a8">Web</a> vessel will only require you to fill in your profile (once) and then serendipitous discovery and meshing of relevant data will simply happen (the serendipity quotient will grow in line with <a href="http://dbpedia.org/resource/Linked_Data" id="link-id10560050">Linked Data</a> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id100f4940">Web</a> density).</blockquote> <br /> <blockquote> <cite>Q: The desktop of the future is going to have powerful semantic search and social search capabilities built-in</cite> </blockquote> <blockquote>A: It is going to be able to "Find" rather than "Search" for stuff courtesy of the <a href="http://dbpedia.org/resource/Linked_Data" id="link-id10a18a70">Linked Data</a> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id10a976f0">Web</a>.</blockquote> <br /> <blockquote> <cite> Q: Interactive shared spaces will replace folders</cite> </blockquote> <blockquote>A: Data Spaces and their URIs (Data Source Names) replace everything. You simply choose the exploration metaphor that best suits you space interaction needs.</blockquote> <br /> <blockquote> <cite>Q: The Portable Desktop</cite> </blockquote> <blockquote>A: Ubiquitous Desktop i.e. do the same thing (all answers above) on any device connected to the Web.</blockquote> <br /> <blockquote> <cite>Q: The Smart Desktop</cite> </blockquote> <blockquote>A: Vessels with access to Smart Data (<a href="http://dbpedia.org/resource/Linked_Data" id="link-id1666e4e8">Linked Data</a> + Action driven <a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id171d1ff0">Context</a> sprinklings).</blockquote> <br /> <blockquote> <cite>Q: Federated, open policies and permissions</cite> </blockquote> <blockquote>A: More federation for sure, XMPP will become a lot more important, and OAuth will enable resurgence of the federated aspects of the Web and <a href="http://dbpedia.org/resource/Internet" id="link-id100a66a8">Internet</a>.</blockquote> <br /> <blockquote> <cite>Q: The personal cloud</cite> </blockquote> <blockquote>A: <a href="http://dbpedia.org/resource/OpenLink_Data_Spaces" id="link-id104ba580">Personal Data Spaces</a> plugged into Clouds (<a href="http://dbpedia.org/resource/Intranet" id="link-id15bbb970">Intranet</a>, <a href="http://dbpedia.org/resource/Extranet" id="link-id1026d6b0">Extranet</a>, <a href="http://dbpedia.org/resource/Internet" id="link-id140508c8">Internet</a>).</blockquote> <br /> <blockquote> <cite>Q: The WebOS</cite> </blockquote> <blockquote>A: An operating system endowed with traditional Database and Host Operating system functionality such as: RDF Data Model, <a href="http://dbpedia.org/resource/SPARQL" id="link-idd86f48">SPARQL</a> Query Language, <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id13f47268">URI</a> based <a href="http://en.wikipedia.org/wiki/Pointer" id="link-id1055bc78">Pointer mechanism</a>, and HTTP based message Bus.</blockquote> <br /> <blockquote> <cite>Q: Who is most likely to own the future desktop?</cite> </blockquote> <blockquote>A: You! And all you need is a <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id106b79e8">URI</a> (an ID or Data Source Name for "<a href="http://dbpedia.org/resource/Entity" id="link-id133c88a0">Entity</a> You") and a Profile Page (a place where "<a href="http://dbpedia.org/resource/Entity" id="link-id15fa8060">Entity</a> You" is Describe by You).</blockquote> <h3>One Last Thing</h3> <p>You can get a feel for the future desktop by <a href="http://ode.openlinksw.com/#Download" id="link-id165ec048">downloading</a> and then installing the <a href="http://ode.openlinksw.com/" id="link-id13baba38">OpenLink Data Explorer</a> plugin for Firefox, which allows you to switch viewing modes between Web Page and <a href="http://dbpedia.org/resource/Linked_Data" id="link-id13f12410">Linked Data</a> behind the page. :-)</p> <h3>Related</h3> <ul> <li> <a href="http://en.wikipedia.org/wiki/OpenLink_Data_Spaces" id="link-id12496e48">OpenLink Data Spaces</a> </li> <li> <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/GetAPersonalURIIn5MinutesOrLess" id="link-id1027f060">Get Yourself a URI in 5 Minutes or Less</a> </li> <li> <a href="http://virtuoso.openlinksw.com/presentations/DataPortability_and_DataSpaces/DataPortability_and_DataSpaces.html" id="link-id10890f70">Linked Data Spaces & Data Portability</a> </li> <li> <a href="http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/Creating_Deploying_Exploiting_Linked_Data2_TimBL_v3.html" id="link-id137efdf8">Linked Data Conference Keynote</a> (<a href="http://dbpedia.org/resource/RDFa" id="link-id1239d300">RDFa</a> based remix edition that includes vital bits from <a href="http://www.w3.org/People/Berners-Lee/card#i" id="link-id1317a048">TimBL</a>'s <a href="http://www.linkeddataplanet.com/" id="link-id165f57c8">Linked Data Planet presentation</a>).</li> </ul>
The Future of the Desktop
2008-08-21T19:59:25Z
2008-08-21T15:59:25.000001-04:00
Kingsley Uyi Idehen
kidehen@openlinksw.com
http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1413
<p>This post is in response to <a href="http://www.furia.com" id="link-id107907b8">Glenn McDonald</a>'s post titled: <a href="http://www.furia.com/page.cgi?type=log&id=308" id="link-id13dcf2d0">Whole Data</a>, where he highlights a number of issues relating to "<a href="http://dbpedia.org/resource/Semantic_Web" id="link-id1016c1f0">Semantic Web</a>" marketing communications and overall messaging, from his perspective.</p> <p> By coincidence, Glenn and I presented at this month's Cambridge <a href="http://dbpedia.org/resource/Semantic_Web" id="link-idd526f48">Semantic Web</a> Gathering.</p> <p>I've provided a dump of Glenn's issues and my responses below:</p> <h3>Issue - RDF</h3> <ul> <li>Ingenious <a href="http://dbpedia.org/resource/Data">data</a> decomposition idea, but: </li> <li>too low-level; the assembly language of data, where we need Java or <a href="http://dbpedia.org/resource/Ruby_programming_language" id="link-id103f3dd0">Ruby</a> </li> <li>"resource" is not the issue; there's no such thing as "metadata", it's all data; "meta" is a perspective </li> <li>lists need to be effortless, not painful and obscure </li> <li>nodes need to be represented, not just implied; they need types and literals in a more pervasive, integrated way. </li> </ul> <h4>Response:</h4> <p>RDF is a Graph based Data Model it stands for Resource Description Framework. The Metadata data angle comes from it's <a href="http://dbpedia.org/resource/Meta_Content_Framework" id="link-id1690df60">Meta Content Framework (MCF)</a> origins. You can express and serialize data based on the RDF Data Model using: Turtle, N3, TriX, N-Triples, and RDF/XML.</p> <h3>Issue - <a href="http://dbpedia.org/resource/SPARQL" id="link-id10234b38">SPARQL</a> (and Freebase's MQL)</h3> <p>These are just appeasement: <br />- old query paradigm: fishing in dark water with superstitiously tied lures; only works well in carefully stocked lakes <br />- we don't ask questions by defining answer shapes and then hoping they're dredged up whole.</p> <h4>Response:</h4> <p> <a href="http://dbpedia.org/resource/SPARQL" id="link-id16e45e50">SPARQL</a>, <a href="http://www.freebase.com/view/freebase/api" id="link-id13e7d468">MQL</a>, and <a href="http://msdn.microsoft.com/en-us/library/bb387145.aspx" id="link-id1516fbd8">Entity-SQL</a> are Graph Model oriented Query Languages. Query Languages always accompany Database Engines. <a href="http://dbpedia.org/resource/SQL" id="link-id13f8c100">SQL</a> is the Relational Model equivalent. </p> <h3>Issue - <a href="http://dbpedia.org/resource/Linked_Data" id="link-id171dee68">Linked Data</a> </h3> <p>Noble attempt to ground the abstract, but: <br />- <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id1576d5f8">URI</a> dereferencing/namespace/<a href="http://dbpedia.org/resource/Open_world_assumption" id="link-id15f50180">open-world</a> issues focus too much technical attention on cross-source cases where the human issues dwarf the technical ones anyway <br />- <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id105df458">FOAF</a> query over the people in this room? forget it. <br />- link asymmetry doesn't scale <br />- identity doesn't scale <br />- generating RDF from non-graph sources: more appeasement, right where the win from actually converting could be biggest! </p> <h4>Response:</h4> <p>Innovative use of HTTP to deliver "<a href="http://dbpedia.org/resource/Reference_%28computer_science%29" id="link-id13eeab20">Data Access by Reference</a>" to the <a href="http://dbpedia.org/resource/Linked_Data" id="link-id13492610">Linked Data</a> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id105dfc10">Web</a>.</p> <p>When you have a Data Model, Database Engine, and Query Language, the next thing you need is a Data Access mechanism that provides "<a href="http://dbpedia.org/resource/Reference_(computer_science)" id="link-id100ef2c0">Data Access by Reference</a>". <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id16692e88">ODBC</a> and <a href="http://dbpedia.org/resource/Java_Database_Connectivity" id="link-id1699b970">JDBC</a> (amongst others) provide "<a href="http://dbpedia.org/resource/Reference_(computer_science)" id="link-id16034b48">Data Access by Reference</a>" via Data Source Names. <a href="http://dbpedia.org/resource/Linked_Data" id="link-id16690118">Linked Data</a> is about the same thing (URIs are Data Source Names) with the following differences:</p> <ul> <li>Naming is scoped to the <a href="http://dbpedia.org/resource/Entity" id="link-id1195dc48">entity</a> level rather than container level</li> <li>HTTP's use within the data source naming scheme expands the referencability of the Named <a href="http://dbpedia.org/resource/Entity" id="link-id10485760">Entity</a> Descriptions beyond traditional confines such as applications, operating systems, and database engines. </li> </ul> <h3> Issue - <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id104684d0">Giant Global Graph</a> </h3> <p>Hugely motivating and powerful idea, worthy of a superhero (Graphius!), but: <br />- giant and global parts are too hard, and starting global makes every problem harder <br />- local projects become unmanageable in global <a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id12497088">context</a> (Cyc, Freebase data-modeling lists...). And my thus my plea, again. Forget "semantic" and "<a href="http://dbpedia.org/resource/World_Wide_Web">web</a>", let's fix the database tech first: <br />- node/arc data-model, path-based exploratory query-model <br />- data-graph applications built easily on top of this common model; building them has to be easy, because if it's hard, they'll be bad <br />- given good database tech, good web data-publishing tech will be trivial! <br />- given good tools for graphs, the problems of uniting them will be only as hard as they have to be.</p> <h4>Response:</h4> <p> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id144466d8">Giant Global Graph</a> is just another moniker for a "Web of <a href="http://dbpedia.org/resource/Linked_Data" id="link-id15c2c738">Linked Data</a>" or "<a href="http://dbpedia.org/resource/Linked_Data" id="link-id14e73520">Linked Data</a> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id10aef200">Web</a>".</p> <p>Multi-Model Database technology that meshes the best of the Graph & Relational Models exist. In a nutshell, this is what <a href="http://virtuoso.openlinksw.com" id="link-id13492e10">Virtuoso</a> is all about and it's existed for a very long time :-)</p> <p> <a href="http://virtuoso.openlinksw.com" id="link-id105a4f58">Virtuoso</a> is also a Virtual DBMS engine (so you can see Heterogeneous Relational Data via Graph Model <a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id15845110">Context</a> Lenses). Naturally, it is also a <a href="http://dbpedia.org/resource/Linked_Data" id="link-id109e2c78">Linked Data</a> Deployment platform (or <a href="http://dbpedia.org/resource/Linked_Data" id="link-id1086d650">Linked Data</a> Sever). </p> <p>The issue isn't the "<a href="http://dbpedia.org/resource/Semantic_Web" id="link-id107f1ba8">Semantic Web</a>" moniker per se., it's about how <a href="http://dbpedia.org/resource/Linked_Data" id="link-id0xba72818">Linked Data</a> (foundation layer of <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id101dbf50">Semantic Web</a>) gets introduced to users. As I said during the MIT Gathering: "The Web is experienced via Web Browsers primarily, so any enhancement to the Web must be exposed via traditional Web Browsers", which is why we've opted to simply add "View <a href="http://dbpedia.org/resource/Linked_Data">Linked Data</a> Sources" to the existing set of common Browser options that includes:</p> <ol> <li>View page in rendered form (default)</li> <li>View page source (i.e., how you see the markup behind the page)</li> </ol> <p>By exposing the Linked Data <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id15a04b70">Web</a> option as described above, you enable the Web user to knowingly transition from the traditional Rendered (X)HTML page view to the Linked Data View (i.e., structured data behind the page). This simple "User Interaction" tweak makes the notion of exploiting a Structured Web becomes somewhat clearer.</p> <p>The Linked Data <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id10a187d0">Web</a> isn't a panacea. It's just an addition to the existing Web that enrichens the things you can do with the Web. It's predominance, like any application feature, will be subject to the degrees to which it delivers tangible value or matrializes internal and external opportunity costs.</p> <p>Note: The Web isn't ubiquitous today becuase all it's users groked HTML Markup. It's ubquitity is a function of opportunity costs: there simply came a point in the Web boostrap when nobody could afford the opportunity costs associated with being off the Web. The same thing will play out with Linked Data and the broader <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id10a97330">Semantic Web</a> vision.</p> <b>Links:</b> <ol> <li> <a href="http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/Creating_Deploying_Exploiting_Linked_Data2_TimBL_v3.html(15)" id="link-id137fc560">Linked Data Journey part of my Linked Data Planet Presentation Remix</a>(from slides 15 to 22 - which include bits from <a href="http://www.w3.org/People/Berners-Lee/card#i" id="link-id1048a968">TimBL</a>'s presentation)</li> <li> <a href="http://ode.openlinksw.com" id="link-id1667df98">OpenLink Data Explorer</a> </li> <li> <a href="http://ode.openlinksw.com/example.html" id="link-id137ee860">OpenLink Data Explorer Screenshots and examples</a>.</li> </ol>
Response to: Whole Data Post (Update 3)
2008-08-15T22:31:48Z
2008-08-15T18:31:48-04:00
Kingsley Uyi Idehen
kidehen@openlinksw.com
http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1388
<p>Stumbled across a nice post titled: <a href="http://derivadow.com/2008/06/22/what-do-people-have-against-urls" id="link-id10c035c8">What do people have against URLs</a>?. My answer: Everything, if they don't understand the inherent power of URLs when incorporated into the "<a href="http://dbpedia.org/resource/Data">Data</a> Source Naming" mechanism of the <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> called: URIs :-)</p> <p>URIs are simple to use i.e you simply click on them via a user agents UI. However, URLs when incorporated into Data Source Naming en route to constructing HTTP based Identifiers, that deliver HTTP based pointers to the location / address of a Resource Descriptions, another matter.</p> <p>I touched on this issue in my <a href="http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/Creating_Deploying_Exploiting_Linked_Data2.html" id="link-id1076e998">Linked Data Planet keynote</a> last week, and I must say, it did set off a light.</p> <p>I believe, we can only get the broader Web community to comprehend the utility of URIs (Web Data Source Names) by exposing said utility via the Web's Universal Client (Web Browser). For instance, how do URN based Identity / Naming schemes help in a world dominated by Web Browsers that only grok "http://"? From my vantage point, the practical solution is for data providers who already have "doi", "lsid" and other Handle based Identifiers in place, to embark upon http-to-native-naming-scheme-proxying.</p> <p>In my usual "dog-fooding" and "practice what you preach" fashion, this is exactly what we do in the new <a href="http://myopenlink.net:8890/~kidehen/Public/rdfb.xpi" id="link-id13038bb0">Linked Data Web extension</a> that we've decided to reveal to the public (albeit late beta). Thus, when you use an existing browser to view pages with "lsid" or "doi" URNs, you still enjoy the utility of getting at the "Raw <a href="http://dbpedia.org/resource/Linked_Data" id="link-id1090f2a0">Linked Data</a> Sources" that these names expose.</p>
What do people have against URLs or URIs? (Updated)
2008-06-23T13:37:57Z
2008-06-23T09:37:57.000003-04:00
Kingsley Uyi Idehen
kidehen@openlinksw.com
http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1387
<p>I've finally found a second to drop a note about my keynote.</p> <p>The keynote: <a href="http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/Creating_Deploying_Exploiting_Linked_Data2.html" id="link-id103acfb8">Creating, Deploying, and Exploiting Linked Data</a>, sought to achieve the fundamental goal of: Demystify the concept of "<a href="http://dbpedia.org/resource/Linked_Data" id="link-id107134e8">Linked Data</a>" using anecdotal material that resonates with enterprise decision makers.</p> <p>To my pleasure, 90% of the audience members confirmed familiarization with the "<a href="http://dbpedia.org/resource/Data">Data</a> Source Name" concept of <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id106d97a8">Open Database Connectivity</a> (<a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id10956268">ODBC</a>). Thus, all I had to do was map "<a href="http://dbpedia.org/resource/Linked_Data" id="link-id10a55728">Linked Data</a>" to <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id10e77210">ODBC</a>, and then unveil the fundamental add-ons that "<a href="http://dbpedia.org/resource/Linked_Data" id="link-id10d1d290">Linked Data</a>" delivers:</p> <ul> <li>The ability to give database records names (Identifiers)</li> <li>The use of HTTP in the database record naming mechanism - which expands a named database record's reference scope via the expanse of the <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> (i.e HTTP based Identifiers called URIs).</li> </ul> <p>I believe a majority of attendees came to realize that the combination above injects a new Web interaction dynamic: access to "<a href="http://dbpedia.org/resource/Topic" id="link-id110978d0">Subject matter Concepts</a>" and <a href="http://dbpedia.org/resource/Named_entity_recognition" id="link-id10ea5160">Named Entities</a> contained within a page via HTTP base Data Source Names (URIs).</p> <p>BTW - My presentation is a <a href="http://dbpedia.org/resource/Linked_Data" id="link-id109e5e30">Linked Data Space</a> in it's own right courtesy of the <a href="http://bibliontology.com/" id="link-id10e76d90">Bibliographic Ontology</a> (which provides slide show modeling) and <a href="http://dbpedia.org/resource/RDFa" id="link-id10d48e40">RDFa</a> that allows me to embed annotations into my <a href="http://www.w3.org/Talks/Tools/Slidy/" id="link-id104be488">Slidy</a> based presentation :-)</p> <h3>Related</h3> <ul> <li> <a href="http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/Linked_Data_2008_keynote.ppt" id="link-id10a63640">PowerPoint</a> version of Presentation</li> <li> <a href="http://www.slideshare.net/rumito/linked-data-planet-key-note/" id="link-id103aaff8">Slideshare hosted </a>version</li> <li> <a href="http://www.authorstream.com/Presentation/rumito-72460-linked-data-planet-key-note-2008-keynote-science-technology-ppt-powerpoint/" id="link-id10b97c68">Authorstream hosted </a>version</li> <li> <a href="http://docs.google.com/Presentation?id=dc7jvc6m_1061gz888hdb" id="link-id10e01640">Google Docs hosted </a>version</li> </ul>
My Linked Data Planet Keynote (Updated with missing link)
2008-06-19T13:48:14Z
2008-06-19T09:48:14-04:00
Kingsley Uyi Idehen
kidehen@openlinksw.com
http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1366
<p>Courtesy of <a href="http://novaspivack.typepad.com/about.html" id="link-id101d8750">Nova Spivack</a>'s post titled: <a href="http://feeds.feedburner.com/~r/typepad/MindingThePlanet/~3/295624567/tagging-and-the.html" id="link-id11067248">Tagging and the Semantic Web: Tags as Objects</a>, I stumbled across a related post by <a href="http://www.designmills.com/" id="link-idffb9a38">John Clarke</a> titled: <a href="http://feeds.feedburner.com/~r/DesignMills/~3/294554634/" id="link-id101d6138">Tagging and the Semantic Web</a>. Both of these posts use the common practice of tagging to shed light on the increasing realization that "<a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id11011f98"><a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1356" id="link-id1003f248">The Pursuit of Context</a></a>" is the fusion point between the current <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> and its evolution into a structured Web of <a href="http://dbpedia.org/resource/Linked_Data" id="link-id101d6788">Linked Data</a>.</p> <h3>How Semantic Tagging Works (from a 1000 feet)</h3> <p>When tagging a document, the semantic tagging service passes the content of a target document through a processing pipeline (a distillation process of sorts) that results in automagic extraction of the following:</p> <ul> -- <a href="http://dbpedia.org/resource/Named_entity_recognition" id="link-id1015fdd0">Named Entities</a> </ul> <ul>-- <a href="http://dbpedia.org/resource/Topic" id="link-id100ccff8">Subject matter Entities</a> (<a href="http://dbpedia.org/resource/Topic" id="link-idfe9a898">Subject matter Concepts</a> reflecting topics covered by the document</ul> <p>Once the extraction phase is completed, a user is presented with a list of "suggested tags" using a variety of user interaction techniques. The literal values of elected Tags are then associated with one or more <a href="http://dbpedia.org/resource/Tag" id="link-idfed5eb0">Tag</a> and <a href="http://dbpedia.org/resource/Tag" id="link-id101ae0c8">Tag</a> Meaning <a href="http://dbpedia.org/resource/Data">Data</a> Objects, with each Object type endowed with a unique Identifier.</p> <h3>Issues to Note</h3> <p>Broad acceptance that: "<a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id100b9010">Context</a> is king", is gradually taking shape. That said, "<a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id101d2670">Context</a>" landlocked within Literal values offers little over what we have right now (e.g. at <a href="http://del.icio.us" id="link-id1004be08">Del.icio.us</a> or <a href="http://www.technorati.com" id="link-id100421c8">Technorati</a>), long term. By this I mean: if the end product of semantically enhanced tagging leaves us with: Literal <a href="http://dbpedia.org/resource/Tag" id="link-id101e5730">Tag</a> values only, Tags associated with <a href="http://dbpedia.org/resource/Tag" id="link-id1004a890">Tag</a> Data Objects endowed with platform specific Identifiers, or <a href="http://dbpedia.org/resource/Tag" id="link-id100364f8">Tag</a> Data Objects with any other Identity scheme that excludes <a href="http://dbpedia.org/resource/Hypertext_Transfer_Protocol" id="link-id101e6630">HTTP</a>, the ability of Web users to discern or derive multiple perspectives from the base <a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id10180868">Context</a> (exposed by semantically enhanced Tags) will be lost, or severely impeded at best.</p> <p>The shape, form, and quality of the lookup substrate that underlies semantic tagging services, ultimately affects "<a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id10160f28">context</a> fidelity" matters such as <a href="http://dbpedia.org/resource/Entity" id="link-id100f2618">Entity</a> Disambiguation. The importance of quality lookup infrastructure on the burgeoning <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id10044b10">Linked Data Web</a> is the reason why <a href="http://www.openlinksw.com/dataspace/organization/openlink#this" id="link-id10102360">OpenLink Software</a> is intimately involved with the <a href="http://dbpedia.org/resource/DBpedia" id="link-id110760f8">DBpedia</a> and <a href="http://umbel.org/about/" id="link-id1015fc68">UMBEL</a> projects. </p> <h3>Conclusions</h3> <p>I am immensely happy to see that the Web 2.0 and <a href="http://dbpedia.org/resource/Semantic_Web" id="link-idffb8ca8">Semantic Web</a> communities are beginning to coalesce around the issue of "<a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id101656b0">Context</a>". This was the case at the <a href="http://events.linkeddata.org/ldow2008/" id="link-id1017b878">WWW2008 Linked Data Workshop</a>, I am feeling a similar vibe emerging from the <a href="http://www.semantic-conference.com/" id="link-idffb9978">Semantic Web Technologies</a> conference currently nearing completion in San Jose. Of course, I will be talking about, and demonstrating practical utility of all of this, at the upcoming <a href="http://www.linkeddataplanet.com" id="link-id10042168">Linked Data Planet</a> conference.</p> <h3>Related</h3> <ul> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/tagcloud" id="link-id147a1848">My Data Space Tag Cloud</a> (*a <a href="http://dbpedia.org/resource/Linked_Data" id="link-id0x24756e98">Linked Data</a> <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id0x24c2bd20">Space</a>*) </ul> <ul> <a href="http://www.faviki.com/" id="link-id101ac668">Faviki</a> (note: this service needs to expose <a href="http://dbpedia.org/resource/Linked_Data" id="link-id1042cdc0">Linked Data</a> compliant <a href="http://dbpedia.org/resource/Tag" id="link-id1038c2e0">Tag</a> URIs) </ul> <ul> <a href="http://moat-project.org/ontology" id="link-id10199770">MOAT Ontology</a> </ul>
Context, Tagging, Semantic Web, and Linked Data (Updated)
2008-05-27T22:36:37Z
2008-05-27T18:36:37-04:00
Kingsley Uyi Idehen
kidehen@openlinksw.com
http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1361
<p> <a href="http://blogs.talis.com/nodalities/2008/05/kingsley-idehen-talks-about-openlink-software-linked-data-and-the-semantic-web.php" id="link-id1036b118">My podcast interview</a> with <a href="http://www.linkedin.com/in/pau1mi11er" id="link-id1026ed10">Paul Miller</a> of <a href="http://www.talis.com" id="link-id12d210d8">Talis</a> is out. As I listened to the podcast (naturally awkward affair) I got a first hand sense of Paul's mastery of the art of interviewing, even when dealing with a fast talking <a href="http://dbpedia.org/resource/Data" id="link-id180e1208">data</a> blitzers like me. Personally, I think I still talk a little too fast (the Nigerian in me), especially when the subject matter hones right into the epicenter of my professional passions: Open <a href="http://dbpedia.org/resource/Data" id="link-id1737a258">Data</a> Access and Heterogeneous <a href="http://dbpedia.org/resource/Data" id="link-id180f0668">Data</a> Integration (aka. <a href="http://dbpedia.org/resource/Virtual_Database" id="link-id10c62348">Virtual Database</a> Technology) -- so you may need to rewind every now and then during the interview :-)</p> <p>During this particular podcast interview, I deliberately wanted to have an conversation about the practical value of <a href="http://dbpedia.org/resource/Linked_Data" id="link-id180c9f88">Linked Data</a>, rather than the technical innards. The fundamental utility of <a href="http://dbpedia.org/resource/Linked_Data" id="link-id17387618">Linked Data</a> remains somewhat mercurial, and I am certainly hoping to do my bit at the upcoming <a href="http://dbpedia.org/resource/Linked_Data" id="link-id183ec288">Linked Data</a> Planet conference re. demonstrating and articulating <a href="http://dbpedia.org/resource/Linked_Data" id="link-id1401f250">linked data</a> value across the blurring realms of "the individual" and "the enterprise".</p> <p> <strong>Note to my old schoolmates on Facebook</strong>: when you listen to this podcast you will at least reconcile "Uyi Idehen" with "<a href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-id180a7060">Kingsley Idehen</a>". Unfortunately, Facebook refuses to let me Identify myself in the manner I choose. Ideally, I would like to have the name: "Kingsley (Uyi) Idehen" associated with my Facebook ID since this is the Identifier known to my personal network of friends, family, and old schoolmates. This Identity predicament is a long running Identity case study in the making.</p>
My Talis Podcast re. Semantic Web, Linked Data, and OpenLink Software
2008-05-16T16:53:49Z
2008-05-16T12:53:49.000002-04:00
Kingsley Uyi Idehen
kidehen@openlinksw.com