http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/
Kingsley Idehen's Blog Data Space
I have seen the future and it's full of Linked Data! :-)
Kingsley Uyi Idehen
kidehen@openlinksw.com
2010-02-09T22:29:56Z
Virtuoso Universal Server 05.12.3041
http://www.openlinksw.com/weblog/public/images/vbloglogo.gif
The Business Of Linked Data (BOLD) Discussion Space
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?id=1596
2010-01-31T22:48:36Z
<p>I've created a new discussion space that's squarely focused on the business development and marketing aspects of "HTTP based <a href="http://dbpedia.org/resource/Linked_Data" id="link-id129e32d8">Linked Data" (Linked Data</a>). As its name indicates, It's a BOLD attempt to fill a VoiD. :-)</p> <h3>Background</h3> <p>A few months ago, <a href="http://blog.aldobucchi.com/#this" id="link-id1110eb30">Aldo Bucchi</a> posted a message to the <a href="http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/LinkingOpenData" id="link-id111d08a0">LOD</a> <a href="http://lists.w3.org/Archives/Public/public-lod/" id="link-id118b3778">mailing list</a> seeking a discussion space for more business and marketing oriented topic, in relation to Linked Data. At the time, my assumption was that the existing LOD mailing list served that purpose absolutely fine, but in due course I came to realize that Aldo's request had a much lager foundation than I initially suspected.</p> <h3>Historic Oversight</h3> <p>Linked Data, like its umbrella <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id16ceb618">Semantic Web</a> Project, has suffered from an inadvertent oversight on the parts of many of its enthusiasts (myself included): 100% of the discussion spaces are created by, geared towards, or dominated by researchers (from Academia primarily) and/or developers. Thus, at the very least, we've been operating in an echo chamber that only feed the existing void between the core community and those who are more interested in discussing business and marketing related topics.</p> <p>The new discussion space seeks to cover the following:</p> <ol> <li> Brainstorming Value Proposition Articulation</li> <li>War Story Exchanges</li> <li>Case Studies and Use-cases</li> <li>Market Research & Positioning (for instance Linked Data is killer technology that redefines <a href="http://dbpedia.org/resource/Data" id="link-id0x1d491e90">Data</a> Integration, but none of the major research firms currently make that connection)</li>. </ol> <p>How Do I Join The Conversation? Simply sign up on the Google hosted <a href="http://groups.google.com/group/business-of-linked-data-bold" id="link-id129e4d08">BOLD mailing list</a>, introduce yourself (ideally), and then start conversing! :-)</p>
Kingsley Uyi Idehen
kidehen@openlinksw.com
2010-01-31T17:48:48-05:00
Getting The Linked Data Value Pyramid Layers Right (Update #2)
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?id=1595
2010-01-31T22:46:47Z
<p> One of the real problems that pervades all routes to <a href="http://dbpedia.org/resource/Linked_Data" id="link-id13539328">Linked Data</a> value prop. incomprehension stems from the layering of its value pyramid; especially when communicating with -initially detached- end-users. </p> <p> <strong>Note to <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id0x1c85f498">Web</a> Programmers:</strong> Linked Data is about <a href="http://dbpedia.org/resource/Data" id="link-id0x1c85f650">Data</a> (Wine) and not about Code (Fish). Thus, it isn't a "programmer only zone", far from it. More than anything else, its inherently inclusive and spreads its participation net widely across: Data Architects, Data Integrators, Power Users, <a href="http://dbpedia.org/resource/Knowledge" id="link-id13600d98">Knowledge</a> Workers, <a href="http://dbpedia.org/resource/Information" id="link-id149f8230">Information</a> Workers, Data Analysts, etc.. Basically, everyone that can "click on a link" is invited to this particular party; remember, it is about "Linked Data" not "Linked Code", after all. :-) </p> <h3>Problematic Value Pyramid Layering</h3> <p> Here is an example of a Linked Data value pyramid that I am stumbling across --with some frequency-- these days (note: 1 being the pyramid apex):</p> <ol> <li> <a href="http://dbpedia.org/resource/SPARQL" id="link-id10e85538">SPARQL</a> Queries</li> <li> <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id1495b578">RDF</a> Data Stores</li> <li> RDF Data Sets </li> <li> <a href="http://dbpedia.org/resource/Hypertext_Transfer_Protocol" id="link-id158e4be0">HTTP</a> scheme URIs</li> </ol> <p> Basically, Linked Data deployment (assigning de-referencable HTTP URIs to DBMS records, their attributes, and attribute values [optionally] ) is occurring last. Even worse, this happens in the <a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id626d988">context</a> of Linked Open Data oriented endeavors, resulting in nothing but confusion or inadvertent perpetuation of the overarching pragmatically challenged "<a href="http://dbpedia.org/resource/Semantic_Web" id="link-id111774b8">Semantic Web</a>" stereotype. </p> <p> As you can imagine, hitting SPARQL as your introduction to Linked Data is akin to hitting <a href="http://dbpedia.org/resource/SQL" id="link-id151f9938">SQL</a> as your introduction to Relational Database Technology, neither is an elevator-style value prop. relay mechanism. </p> <p> In the relational realm, killer demos always started with desktop productivity tools (spreadsheets, report-writers, SQL QBE tools etc.) accessing, relational data sources en route to unveiling the "Productivity" and "Agility" value prop. that such binding delivered i.e., the desktop application (clients) and the databases (servers) are distinct, but operating in a mutually beneficial manner to all, courtesy of a data access standards such as <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id1519aac0">ODBC</a> (Open Database Connectivity). </p> <p> In the Linked Data realm, learning to embrace and extend best practices from the relational dbms realm remains a challenge, a lot of this has to do with hangovers from a misguided perception that RDF databases will somehow completely replace <a href="http://dbpedia.org/resource/Relational_database_management_system" id="link-id110dec88">RDBMS</a> engines, rather than compliment them. Thus, you have a counter productive variant of NIH (Not Invented Here) in play, taking us to the dreaded realm of: Break the Pot and You Own It (exemplified by the 11+ year Semantic Web Project comprehension and appreciation odyssey). </p> <p> From my vantage point, here is how I believe the <a href="http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/images/URI_Data_Source_SemWeb.png" id="link-id1592f528">Linked Data value pyramid should be layered</a>, especially when communicating the essential value prop.: </p> <ol> <li> HTTP URLs -- LINKs to documents (Reports) that users already appreciate, across the public Web and/or Intranets </li> <li> HTTP URIs -- typically not visually distinguishable from the URLs, so use the Data exposed by de-referencing a <a href="http://dbpedia.org/resource/Uniform_Resource_Locator" id="link-id11209ce8">URL</a> to show how each Data Item (<a href="http://dbpedia.org/resource/Entity" id="link-id1449b558">Entity</a> or Object) is uniquely identified by a Generic HTTP <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id112065f8">URI</a>, and how clicking on the said URIs leads to more structured metadata bearing documents available in a variety of data representation formats, thereby enabling flexible data presentation (e.g., smarter HTML pages) </li> <li> SPARQL -- when a user appreciates the data representation and presentation dexterity of a Generic HTTP URI, they will be more inclined to drill down an additional layer to unravel how HTTP URIs mechanically deliver such flexibility </li> <li> RDF Data Stores -- at this stage the user is now interested data sources behind the Generic HTTP URIs, courtesy of natural desire to tweak the data presented in the report; thus, you now have an engaged user ready to absorb the "How Generic HTTP URIs Pull This Off" message </li> <li>RDF Data Sets -- while attempting to make or tweak HTTP URIs, users become curious about the actual data loaded into the RDF Data Store, which is where data sets used to create powerful Lookup Data Spaces (e.g., <a href="http://dbpedia.org/resource/DBpedia" id="link-id110675c0">DBpedia</a>) come into play such as those from the <a href="http://www4.wiwiss.fu-berlin.de/bizer/pub/lod-datasets_2009-07-14.html" id="link-id11127ff8">LOD</a> constellation as exemplified by <a href="http://wiki.dbpedia.org/Datasets" id="link-id14a2fad8">DBpedia (extractions from Wikipedia)</a>.</li> </ol> <h3>Related</h3> <ul> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1565" id="link-id149c7048">Exploring the Linked Data Value Proposition</a> </li> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1543" id="link-id14998f98">Simple Explanation of Linked Data & RDF Dynamics</a> </li> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1546" id="link-id114fbd58">What is the Linked Data Meme About?</a> </li> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1547" id="link-id1447ada0">Linked Data & Data Item Identifiers (Identity)</a> </li> </ul>
Kingsley Uyi Idehen
kidehen@openlinksw.com
2010-01-31T17:47:04-05:00
What is the DBpedia Project? (Updated)
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?id=1594
2010-01-31T22:45:55Z
<p>The recent <a href="http://en.wikipedia.org/wiki/Talk:DBpedia" id="link-id1120a260">Wikipedia imbroglio</a> centered around <a href="http://dbpedia.org/resource/DBpedia" id="link-id14a5e588">DBpedia</a> is the fundamental driver for this particular <a href="http://dbpedia.org/resource/Blog" id="link-id113ddc10">blog</a> post. At time of writing this blog post, the <a href="http://en.wikipedia.org/wiki/DBpedia" id="link-id158edec0">DBpedia project definition in Wikipedia</a> remains unsatisfactory due to the following shortcomings:</p> <ol> <li>inaccurate and incomplete definition of the Project's What, Why, Who, Where, When, and How</li> <li>inaccurate reflection of project essence, by skewing focus towards <a href="http://dbpedia.org/resource/Data" id="link-id0x1bc892d0">data</a> extraction and data set dump production, which is at best a quarter of the project.</li> </ol> <p>Here are some insights on DBpedia, from the perspective of someone intimately involved with the other three-quarters of the project.</p> <h3>What is DBpedia?</h3> <p>A live <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id0x1c0c0cc0">Web</a> accessible RDF model database (Quad Store) derived from Wikipedia content snapshots, taken periodically. The RDF database underlies a <a href="http://dbpedia.org/resource/Linked_Data" id="link-id11ba0ad0">Linked Data</a> <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id1183c978">Space</a> comprised of: HTML (and most recently HTML+<a href="http://dbpedia.org/resource/RDFa" id="link-id602eab8">RDFa</a>) based data browser pages and a <a href="http://dbpedia.org/resource/SPARQL" id="link-id11af5400">SPARQL</a> endpoint.</p> <p>Note: <a href="http://blog.dbpedia.org/2009/11/11/dbpedia-34-released/" id="link-id110b8248">DBpedia 3.4</a> now exists in snapshot (warehouse) and <a href="http://dbpedia-live.openlinksw.com/stats/" id="link-id6473258">Live Editions</a> (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.</p> <h3>When was it Created?</h3> <p>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 <a href="http://www.wiwiss.fu-berlin.de/en/institute/pwo/bizer/" id="link-id14982c78">Chris Bizer</a>). The first public instance of DBpedia (as described above) was released in February 2007. The official DBpedia coming out party occurred at <a href="http://www2007.org/" id="link-id1497c788">WWW2007</a>, Banff, during the <a href="http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/LinkingOpenData/BanffGathering" id="link-id1448b9e8">inaugural Linked Data gathering</a>, where it showcased the virtues and immense potential of <a href="http://www.w3.org/People/Berners-Lee/card#i" id="link-id152257e0">TimBL</a>'s <a href="http://www.w3.org/DesignIssues/LinkedData.html" id="link-id111759a8">Linked Data meme</a>.</p> <h3>Who's Behind It?</h3> <p> <a href="http://www.openlinksw.com/dataspace/organization/openlink#this" id="link-id110e70f8">OpenLink Software</a> (developers of OpenLink <a href="http://virtuoso.openlinksw.com" id="link-id14462f60">Virtuoso</a> 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 (<a href="http://dbpedia.org/resource/Cyc" id="link-id11244aa0">OpenCyc</a>, <a href="http://www.ontologyportal.org/" id="link-id110e4a40">SUMO</a>, <a href="http://umbel.org/about/" id="link-id11109e48">UMBEL</a>, and <a href="http://www.mpi-inf.mpg.de/yago-naga/yago/" id="link-id10fb4218">YAGO</a>) and other utilities. Finally, DBpedia wouldn't be possible without the global content contribution and curation efforts of Wikipedians, a point typically overlooked (albeit inadvertently).</p> <h3>How is it Constructed?</h3> <p>The steps are as follows:</p> <ol> <li> RDF data set dump preparation via Wikipedia content extraction and transformation to RDF model data, using the N3 data representation format - Java and <a href="http://dbpedia.org/resource/PHP" id="link-id111c93b8">PHP</a> extraction code produced and maintained by the teams at Leipzig and Berlin </li> <li> Deployment of Linked Data that enables Data browsing and exploration using any HTTP aware user agent (e.g. basic Web Browsers) - handled by OpenLink Virtuoso (handled by Berlin via the Pubby Linked Data Server during the early months of the DBpedia project) </li> <li> SPARQL compliant Quad Store, enabling direct access to database records via SPARQL (Query language, REST or SOAP Web Service, plus a variety of query results serialization formats) - OpenLink Virtuoso since first public release of DBpedia </li> </ol> <p> 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 if you have a SPARQL compliant Quad Store without loaded data sets, and of course it doesn't exist if you have a fully loaded SPARQL compliant Quad Store is up to the cocktail of challenges presented by live Web accessibility.</p> <h3>Why is it Important?</h3> <p> It remains a live exemplar for any individual or organization seeking to publishing or exploit HTTP based Linked Data on the <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id118e6388">World Wide Web</a>. Its existence continues to stimulate growth in both density and quality of the burgeoning Web of Linked Data.</p> <h3>How Do I Use it?</h3> <p> In the most basic sense, simply browse the HTML pages en route to discovery erstwhile relationships that exist across <a href="http://dbpedia.org/resource/Named_entity_recognition" id="link-id112def88">named entities</a> and <a href="http://dbpedia.org/resource/Topic" id="link-id1591c5f8">subject matter concepts</a> / headings. Beyond that, simply look at DBpedia as a master lookup table in a Web hosted <a href="http://dbpedia.org/resource/federated_database_system" id="link-id11762618">distributed database</a> 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., owl:sameAs relations.</p> <h3>What Can I Use it For?</h3> <p> Expanding on the Master-Details point above, you can use its rich <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id1170c000">URI</a> corpus to alleviate tedium associated with activities such as: </p> <ol> <li>List maintenance - e.g., Countries, States, Companies, Units of Measurement, Subject Headings etc.</li> <li>Tagging - as a compliment to existing practices</li> <li>Analytical Research - you're only a LINK (URI) away from erstwhile difficult to attain research data spread across a broad range of topics</li> <li>Closed Vocabulary Construction - rather than commence the futile quest of building your own closed vocabulary, simply leverage Wikipedia's human curated vocabulary as our common base. </li> </ol> <h3>Related</h3> <ul> <li> <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtAWSDBpedia34S" id="link-id14a2e698">Pre-loaded and Pre-configured instances of DBpedia 3.4</a> - via publicly shared <a href="http://aws.amazon.com/ebs/" id="link-id1147fcf0">Amazon Elastic Block Storage</a> Snapshots</li> <li> <a href="http://docs.openlinksw.com/virtuoso/rdfperformancetuning.html#rdfperfgeneraldbpedia" id="link-id149ab528">Virtuoso & DBpedia Tunning Guide</a> </li> <li> <a href="http://dowhatimean.net/2009/11/whats-in-a-name-and-the-linked-data-police" id="link-id110cba10">What's In a Name & The Linked Data Police</a>. </li> </ul>
Kingsley Uyi Idehen
kidehen@openlinksw.com
2010-01-31T17:46:10.000002-05:00
Getting The Linked Data Value Pyramid Layers Right (Update #2)
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?id=1593
2010-01-31T22:44:04Z
<p> One of the real problems that pervades all routes to <a href="http://dbpedia.org/resource/Linked_Data" id="link-id13539328">Linked Data</a> value prop. incomprehension stems from the layering of its value pyramid; especially when communicating with -initially detached- end-users. </p> <p> <strong>Note to <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> Programmers:</strong> Linked Data is about <a href="http://dbpedia.org/resource/Data">Data</a> (Wine) and not about Code (Fish). Thus, it isn't a "programmer only zone", far from it. More than anything else, its inherently inclusive and spreads its participation net widely across: Data Architects, Data Integrators, Power Users, <a href="http://dbpedia.org/resource/Knowledge" id="link-id13600d98">Knowledge</a> Workers, <a href="http://dbpedia.org/resource/Information" id="link-id149f8230">Information</a> Workers, Data Analysts, etc.. Basically, everyone that can "click on a link" is invited to this particular party; remember, it is about "Linked Data" not "Linked Code", after all. :-) </p> <h3>Problematic Value Pyramid Layering</h3> <p> Here is an example of a Linked Data value pyramid that I am stumbling across --with some frequency-- these days (note: 1 being the pyramid apex):</p> <ol> <li> <a href="http://dbpedia.org/resource/SPARQL" id="link-id10e85538">SPARQL</a> Queries</li> <li> <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id1495b578">RDF</a> Data Stores</li> <li> RDF Data Sets </li> <li> <a href="http://dbpedia.org/resource/Hypertext_Transfer_Protocol" id="link-id158e4be0">HTTP</a> scheme URIs</li> </ol> <p> Basically, Linked Data deployment (assigning de-referencable HTTP URIs to DBMS records, their attributes, and attribute values [optionally] ) is occurring last. Even worse, this happens in the <a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id626d988">context</a> of Linked Open Data oriented endeavors, resulting in nothing but confusion or inadvertent perpetuation of the overarching pragmatically challenged "<a href="http://dbpedia.org/resource/Semantic_Web" id="link-id111774b8">Semantic Web</a>" stereotype. </p> <p> As you can imagine, hitting SPARQL as your introduction to Linked Data is akin to hitting <a href="http://dbpedia.org/resource/SQL" id="link-id151f9938">SQL</a> as your introduction to Relational Database Technology, neither is an elevator-style value prop. relay mechanism. </p> <p> In the relational realm, killer demos always started with desktop productivity tools (spreadsheets, report-writers, SQL QBE tools etc.) accessing, relational data sources en route to unveiling the "Productivity" and "Agility" value prop. that such binding delivered i.e., the desktop application (clients) and the databases (servers) are distinct, but operating in a mutually beneficial manner to all, courtesy of a data access standards such as <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id1519aac0">ODBC</a> (Open Database Connectivity). </p> <p> In the Linked Data realm, learning to embrace and extend best practices from the relational dbms realm remains a challenge, a lot of this has to do with hangovers from a misguided perception that RDF databases will somehow completely replace <a href="http://dbpedia.org/resource/Relational_database_management_system" id="link-id110dec88">RDBMS</a> engines, rather than compliment them. Thus, you have a counter productive variant of NIH (Not Invented Here) in play, taking us to the dreaded realm of: Break the Pot and You Own It (exemplified by the 11+ year Semantic Web Project comprehension and appreciation odyssey). </p> <p> From my vantage point, here is how I believe the <a href="http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/images/URI_Data_Source_SemWeb.png" id="link-id1592f528">Linked Data value pyramid should be layered</a>, especially when communicating the essential value prop.: </p> <ol> <li> HTTP URLs -- LINKs to documents (Reports) that users already appreciate, across the public Web and/or Intranets </li> <li> HTTP URIs -- typically not visually distinguishable from the URLs, so use the Data exposed by de-referencing a <a href="http://dbpedia.org/resource/Uniform_Resource_Locator" id="link-id11209ce8">URL</a> to show how each Data Item (<a href="http://dbpedia.org/resource/Entity" id="link-id1449b558">Entity</a> or Object) is uniquely identified by a Generic HTTP <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id112065f8">URI</a>, and how clicking on the said URIs leads to more structured metadata bearing documents available in a variety of data representation formats, thereby enabling flexible data presentation (e.g., smarter HTML pages) </li> <li> SPARQL -- when a user appreciates the data representation and presentation dexterity of a Generic HTTP URI, they will be more inclined to drill down an additional layer to unravel how HTTP URIs mechanically deliver such flexibility </li> <li> RDF Data Stores -- at this stage the user is now interested data sources behind the Generic HTTP URIs, courtesy of natural desire to tweak the data presented in the report; thus, you now have an engaged user ready to absorb the "How Generic HTTP URIs Pull This Off" message </li> <li>RDF Data Sets -- while attempting to make or tweak HTTP URIs, users become curious about the actual data loaded into the RDF Data Store, which is where data sets used to create powerful Lookup Data Spaces (e.g., <a href="http://dbpedia.org/resource/DBpedia" id="link-id110675c0">DBpedia</a>) come into play such as those from the <a href="http://www4.wiwiss.fu-berlin.de/bizer/pub/lod-datasets_2009-07-14.html" id="link-id11127ff8">LOD</a> constellation as exemplified by <a href="http://wiki.dbpedia.org/Datasets" id="link-id14a2fad8">DBpedia (extractions from Wikipedia)</a>.</li> </ol> <h3>Related</h3> <ul> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1565" id="link-id149c7048">Exploring the Linked Data Value Proposition</a> </li> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1543" id="link-id14998f98">Simple Explanation of Linked Data & RDF Dynamics</a> </li> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1546" id="link-id114fbd58">What is the Linked Data Meme About?</a> </li> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1547" id="link-id1447ada0">Linked Data & Data Item Identifiers (Identity)</a> </li> </ul>
Kingsley Uyi Idehen
kidehen@openlinksw.com
2010-02-01T09:02:14.000004-05:00
What is the DBpedia Project? (Updated)
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?id=1592
2010-01-31T22:43:08Z
<p>The recent <a href="http://en.wikipedia.org/wiki/Talk:DBpedia" id="link-id1120a260">Wikipedia imbroglio</a> centered around <a href="http://dbpedia.org/resource/DBpedia" id="link-id14a5e588">DBpedia</a> is the fundamental driver for this particular <a href="http://dbpedia.org/resource/Blog" id="link-id113ddc10">blog</a> post. At time of writing this blog post, the <a href="http://en.wikipedia.org/wiki/DBpedia" id="link-id158edec0">DBpedia project definition in Wikipedia</a> remains unsatisfactory due to the following shortcomings: <br /> </p> <ol> <li>inaccurate and incomplete definition of the Project's What, Why, Who, Where, When, and How</li> <li>inaccurate reflection of project essence, by skewing focus towards <a href="http://dbpedia.org/resource/Data">data</a> extraction and data set dump production, which is at best a quarter of the project.</li> </ol> <p>Here are some insights on DBpedia, from the perspective of someone intimately involved with the other three-quarters of the project.</p> <h3>What is DBpedia?</h3> <p>A live <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> accessible RDF model database (Quad Store) derived from Wikipedia content snapshots, taken periodically. The RDF database underlies a <a href="http://dbpedia.org/resource/Linked_Data" id="link-id11ba0ad0">Linked Data</a> <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id1183c978">Space</a> comprised of: HTML (and most recently HTML+<a href="http://dbpedia.org/resource/RDFa" id="link-id602eab8">RDFa</a>) based data browser pages and a <a href="http://dbpedia.org/resource/SPARQL" id="link-id11af5400">SPARQL</a> endpoint.</p> <p>Note: <a href="http://blog.dbpedia.org/2009/11/11/dbpedia-34-released/" id="link-id110b8248">DBpedia 3.4</a> now exists in snapshot (warehouse) and <a href="http://dbpedia-live.openlinksw.com/stats/" id="link-id6473258">Live Editions</a> (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.</p> <h3>When was it Created?</h3> <p>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 <a href="http://www.wiwiss.fu-berlin.de/en/institute/pwo/bizer/" id="link-id14982c78">Chris Bizer</a>). The first public instance of DBpedia (as described above) was released in February 2007. The official DBpedia coming out party occurred at <a href="http://www2007.org/" id="link-id1497c788">WWW2007</a>, Banff, during the <a href="http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/LinkingOpenData/BanffGathering" id="link-id1448b9e8">inaugural Linked Data gathering</a>, where it showcased the virtues and immense potential of <a href="http://www.w3.org/People/Berners-Lee/card#i" id="link-id152257e0">TimBL</a>'s <a href="http://www.w3.org/DesignIssues/LinkedData.html" id="link-id111759a8">Linked Data meme</a>.</p> <h3>Who's Behind It?</h3> <p> <a href="http://www.openlinksw.com/dataspace/organization/openlink#this" id="link-id110e70f8">OpenLink Software</a> (developers of OpenLink <a href="http://virtuoso.openlinksw.com" id="link-id14462f60">Virtuoso</a> 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 (<a href="http://dbpedia.org/resource/Cyc" id="link-id11244aa0">OpenCyc</a>, <a href="http://www.ontologyportal.org/" id="link-id110e4a40">SUMO</a>, <a href="http://umbel.org/about/" id="link-id11109e48">UMBEL</a>, and <a href="http://www.mpi-inf.mpg.de/yago-naga/yago/" id="link-id10fb4218">YAGO</a>) and other utilities. Finally, DBpedia wouldn't be possible without the global content contribution and curation efforts of Wikipedians, a point typically overlooked (albeit inadvertently).</p> <h3>How is it Constructed?</h3> <p>The steps are as follows:</p> <ol> <li> RDF data set dump preparation via Wikipedia content extraction and transformation to RDF model data, using the N3 data representation format - Java and <a href="http://dbpedia.org/resource/PHP" id="link-id111c93b8">PHP</a> extraction code produced and maintained by the teams at Leipzig and Berlin </li> <li> Deployment of Linked Data that enables Data browsing and exploration using any HTTP aware user agent (e.g. basic Web Browsers) - handled by OpenLink Virtuoso (handled by Berlin via the Pubby Linked Data Server during the early months of the DBpedia project) </li> <li> SPARQL compliant Quad Store, enabling direct access to database records via SPARQL (Query language, REST or SOAP Web Service, plus a variety of query results serialization formats) - OpenLink Virtuoso since first public release of DBpedia </li> </ol> <p> 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 if you have a SPARQL compliant Quad Store without loaded data sets, and of course it doesn't exist if you have a fully loaded SPARQL compliant Quad Store is up to the cocktail of challenges presented by live Web accessibility.</p> <h3>Why is it Important?</h3> <p> It remains a live exemplar for any individual or organization seeking to publishing or exploit HTTP based Linked Data on the <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id118e6388">World Wide Web</a>. Its existence continues to stimulate growth in both density and quality of the burgeoning Web of Linked Data.</p> <h3>How Do I Use it?</h3> <p> In the most basic sense, simply browse the HTML pages en route to discovery erstwhile relationships that exist across <a href="http://dbpedia.org/resource/Named_entity_recognition" id="link-id112def88">named entities</a> and <a href="http://dbpedia.org/resource/Topic" id="link-id1591c5f8">subject matter concepts</a> / headings. Beyond that, simply look at DBpedia as a master lookup table in a Web hosted <a href="http://dbpedia.org/resource/federated_database_system" id="link-id11762618">distributed database</a> 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., owl:sameAs relations.</p> <h3>What Can I Use it For?</h3> <p> Expanding on the Master-Details point above, you can use its rich <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id1170c000">URI</a> corpus to alleviate tedium associated with activities such as: </p> <ol> <li>List maintenance - e.g., Countries, States, Companies, Units of Measurement, Subject Headings etc.</li> <li>Tagging - as a compliment to existing practices</li> <li>Analytical Research - you're only a LINK (URI) away from erstwhile difficult to attain research data spread across a broad range of topics</li> <li>Closed Vocabulary Construction - rather than commence the futile quest of building your own closed vocabulary, simply leverage Wikipedia's human curated vocabulary as our common base. </li> </ol> <h3>Related</h3> <ul> <li> <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtAWSDBpedia34S" id="link-id14a2e698">Pre-loaded and Pre-configured instances of DBpedia 3.4</a> - via publicly shared <a href="http://aws.amazon.com/ebs/" id="link-id1147fcf0">Amazon Elastic Block Storage</a> Snapshots</li> <li> <a href="http://docs.openlinksw.com/virtuoso/rdfperformancetuning.html#rdfperfgeneraldbpedia" id="link-id149ab528">Virtuoso & DBpedia Tunning Guide</a> </li> <li> <a href="http://dowhatimean.net/2009/11/whats-in-a-name-and-the-linked-data-police" id="link-id110cba10">What's In a Name & The Linked Data Police</a>. </li> </ul>
Kingsley Uyi Idehen
kidehen@openlinksw.com
2010-02-01T09:01:57.000002-05:00
5 Very Important Things to Note about HTTP based Linked Data
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?id=1591
2010-01-31T22:31:35Z
<ol> <li> It isn't <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id115dfd68">World Wide Web</a> Specific (HTTP != World Wide Web)</li> <li> It isn't Open <a href="http://dbpedia.org/resource/Data">Data</a> Specific </li> <li> It isn't about "Free" (Beer or Speech) </li> <li> It isn't about Markup (so don't expect to grok it via "markup first" approach) </li> <li>It's about <a href="http://dbpedia.org/resource/Linked_Data" id="link-id13a6aa98">Hyperdata</a> - the use of HTTP and REST to deliver a powerful platform agnostic mechanism for Data Reference, Access, and Integration.</li> </ol> <p> When trying to understand HTTP based <a href="http://dbpedia.org/resource/Linked_Data" id="link-id18aa1490">Linked Data</a>, especially if you're well versed in DBMS technology use (User, Power User, Architect, Analyst, DBA, or Programmer) think: <br /> </p> <ul> <li> Open Database Connectivity (<a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id1428fba0">ODBC</a>) without operating system, data model, or wire-protocol specificity or lock-in potential </li> <li> Java Database Connectivity (<a href="http://dbpedia.org/resource/Java_Database_Connectivity" id="link-id18d3c2a8">JDBC</a>) without programming language specificity </li> <li> <a href="http://dbpedia.org/resource/ADO.NET" id="link-id125725b8">ADO</a>.NET without .NET runtime specificity and .NET bound language specificity </li> <li> OLE-DB without Windows operating system & programming language specificity </li> <li> XMLA without XML format specificity - with Tabular and Multidimensional results formats expressible in a variety of data representation formats. </li> <li>All of the above scoped to the Record rather than Container level, with Generic HTTP scheme URIs associated with each Record, Field, and Field value (optionally) </li> </ul> <p>Remember the need for Data Access & Integration technology is the by product of the following realities:</p> <ol> <li> Human curated data is ultimately dirty, because: <ul> <li>our thick thumbs, inattention, distractions, and general discomfort with typing, make typos prevalent</li> <li>database engines exist for a variety of data models - Graph, Relational, Hierarchical;</li> <li>within databases you have different record container/partition names e.g. Table Names;</li> <li>within a database record container you have records that are really aspects of the same thing (different keys exist in a plethora of operational / line of business systems that expose aspects of the same <a href="http://dbpedia.org/resource/Entity" id="link-id13378338">entity</a> e.g., customer data that spans Accounts, CRM, ERP application databases);</li> <li>different field names (one database has "EMP" while another has "Employee") for the same record</li>.</ul> </li> <li>Units of measurement is driven by locale, the UK office wants to see sales in Pounds Sterling while the French office prefers Euros etc.</li> <li>All of the above is subject to <a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id17e46398">context</a> halos which can be quite granular re. sensitivity e.g. staff travel between locations that alter locales and their roles; basically, profiles matters a lot.</li> </ol> <h3>Related</h3> <ul> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1364" id="link-id128f0fe8">ODBC and WODBC (Web Open Database Connectivity) Comparison</a> </li> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1364" id="link-id1367cd18">Creating, Deploying, and Exploiting Linked Data Presentation</a> </li> <li> <a href="http://www.odata.org/" id="link-id122ab708">Open Data Protocol Project</a> </li> </ul>
Kingsley Uyi Idehen
kidehen@openlinksw.com
2010-02-01T09:00:56-05:00
5 Game Changing Things about the OpenLink Virtuoso + AWS Cloud Combo
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?id=1590
2010-01-31T22:29:34Z
<p> Here are 5 powerful benefits you can immediately derive from the combination of <a href="http://virtuoso.openlinksw.com" id="link-id17eb8988">Virtuoso</a> and Amazon's AWS services (specifically the EC2 and EBS components): <br /> </p> <ol> <li> Acquire your own personal or service specific <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id1423e520">data space</a> in the Cloud. Think DBase, Paradox, FoxPRO, Access of yore, but with the power of <a href="http://dbpedia.org/resource/Oracle_Database" id="link-id136c6290">Oracle</a>, <a href="http://dbpedia.org/resource/IBM_Informix" id="link-id11b269b8">Informix</a>, <a href="http://dbpedia.org/resource/Microsoft_SQL_Server" id="link-id138084b8">Microsoft SQL Server</a> etc.. using a Conceptual, as opposed to solely Logical, model based DBMS (i.e., a Hybrid DBMS Engine for: <a href="http://dbpedia.org/resource/SQL" id="link-id132a7938">SQL</a>, RDF, XML, and Full Text) </li> <li> Ability to share and control access to your resources using innovations like <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id17ee9d28">FOAF</a>+SSL, OpenID, and OAuth, all from one place </li> <li> Construction of personal or organization based FOAF profiles in a matter of minutes; by simply creating a basic DBMS (or <a href="http://dbpedia.org/resource/OpenLink_Data_Spaces" id="link-id14784ae0">ODS</a> application layer) account; and then using this profile to create strong links (references) to all your Data silos (esp. those from the <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> 2.0 realm) </li> <li> Load data sets from the <a href="http://community.linkeddata.org/dataspace/organization/lod#this" id="link-id17e6ac98">LOD</a> cloud or Sponge existing Web resources (i.e., on the fly data transformation to RDF model based <a href="http://dbpedia.org/resource/Linked_Data" id="link-id17e65d38">Linked Data</a>) and then use the combination to build powerful lookup services that enrich the value of URLs (think: Web addressable reports holding query results) that you publish </li> <li> Bind all of the above to a domain that you own (e.g. a .Name domain) so that you have an attribution-friendly "authority" component for resource URLs and <a href="http://dbpedia.org/resource/Entity" id="link-id118a08d8">Entity</a> URIs published from your Personal Linked Data Space on the Web (or private HTTP network). </li> </ol> <p> In a nutshell, the AWS Cloud infrastructure simplifies the process of generating Federated presence on the <a href="http://dbpedia.org/resource/Internet" id="link-id1380af38">Internet</a> and/or <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id11633b10">World Wide Web</a>. Remember, centralized networking models always end up creating data silos, in some <a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id142006f0">context</a>, ultimately! :-) </p>
Kingsley Uyi Idehen
kidehen@openlinksw.com
2010-02-01T08:59:36-05:00
Virtuoso Chronicles from the Field: Nepomuk, KDE, and the quest for a sophisticated RDF DBMS.
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?id=1602
2010-01-28T16:14:04Z
<p>For this particular user experience chronicle, I've simply inserted the content of <a href="http://trueg.wordpress.com" id="link-id1368b4d8">Sebastian Trueg</a>'s post titled: <a href="http://trueg.wordpress.com/2010/01/26/what-we-did-last-summer-and-the-rest-of-2009-a-look-back-onto-the-nepomuk-development-year-with-an-obscenely-long-title/#comments" id="link-id139dddb0">What We Did Last Summer (And the Rest of 2009) – A Look Back Onto the Nepomuk Development Year ...</a>, directly into this post, without any additional commentary or modification.</p> <div class="snap_preview"> <p>2009 is over. <em>Yeah, sure, trueg, we know that, it has been over for a while now!</em> Ok, ok, I am a bit late, but still I would like to get this one out - if only for my archive. So here goes.</p> <h2> <a href="http://virtuoso.openlinksw.com" id="link-id64672f0">Virtuoso</a> </h2> <p>Let’s start with the major topic of 2009 (and also the beginning of 2010): The new Nepomuk database backend: <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/" id="link-id13cc47e0">Virtuoso</a>. Everybody who used Nepomuk had the same problems: you either used the <a href="http://openrdf.org/" id="link-id13a4ac88">sesame2</a> backend which depends on Java and steals all of your memory or you were stuck with <a href="http://librdf.org/" id="link-id11b6a550">Redland</a> which had the worst performance and missed some <a href="http://dbpedia.org/resource/SPARQL" id="link-id139d82b8">SPARQL</a> features making important parts of Nepomuk like queries unusable. So more than a year ago I had the idea to use the one GPL’ed database server out there that supported RDF in a professional manner: <a href="http://www.openlinksw.com/" id="link-id139fd948">OpenLin</a>k’s <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/" id="link-id12329590">Virtuoso</a>. It has all the features we need, has a very good performance, and scales up to dimensions we will probably never reach on the desktop (<em>yeah, right, and 64k main memory will be enough forever!</em>). So very early I started coding the necessary Soprano plugin which would talk to a locally running Virtuoso server through <a href="http://en.wikipedia.org/wiki/Open_Database_Connectivity" id="link-id14930d90">ODBC</a>. But since I ran into tons of small problems (as always) and got sidetracked by other tasks I did not finish it right away. OpenLink, however, was very interested in the idea of their server being part of every KDE installation (why wouldn’t they ;)). So they not only introduced a <a href="http://docs.openlinksw.com/virtuoso/databaseadmsrv.html#ini_Parameters" id="link-id136763c0">lite-mode</a> which makes Virtuoso suitable for the desktop but also helped in debugging all the problems that I had left. Many test runs, patches, and a Virtuoso 5.0.12 release later <a href="http://trueg.wordpress.com/2009/10/22/virtuoso-once-more-with-feeling/" id="link-id13c5a5a0">I could finally announce the Virtuoso integration</a> as usable.</p> <p>Then end of last year I dropped the support for sesame2 and redland. Virtuoso is now the only supported database backend. The reason is simple: Virtuoso is way more powerful than the rest - not only in terms of performance - and it is fully implemented in <a href="http://dbpedia.org/resource/C%2B%2B" id="link-id13a17cd8">C</a>(++) without any traces of Java. Maybe even more important is the integration of the full text index which makes the previously used CLucene index unnecessary. Thus, we can finally combine full text and graph queries in one SPARQL query. This results in a cleaner API and way faster return of search results since there is no need to combine the results from several queries anymore. A direct result of that is the new <a href="http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk/html/namespaceNepomuk_1_1Query.html" id="link-id149a9fd8">Nepomuk Query API</a> which I will discuss later.</p> <p>So now the only thing I am waiting for is the first bugfix release of Virtuoso 6, i.e. 6.0.1 which will fix the bugs that make 6.0.0 fail with Nepomuk. Should be out any day now. :)</p> <h2>The Nepomuk Query API</h2> <p>Querying <a href="http://dbpedia.org/resource/Data">data</a> in Nepomuk pre-KDE-4.4 could be done in one of two ways: 1. Use the very limited capabilities of the <a href="http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk/html/classNepomuk_1_1ResourceManager.html" id="link-id139ad3d0">ResourceManager</a> to list resources with certain properties or of a certain type; or 2. Write your own <a href="http://techbase.kde.org/Development/Tutorials/Metadata/Nepomuk/AdvancedQueries" id="link-id13c74608">SPARQL query using ugly QString::arg replacements</a>.</p> <p>With the introduction of Virtuoso and its awesome power we can now do pretty much everything in one query. This allowed <a href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-id13c4cf18">me</a> to finally create a query API for KDE: <a href="http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk/html/classNepomuk_1_1Query_1_1Query.html" id="link-id602e818">Nepomuk::Query::Query</a> and friends. I won’t go into much detail here since I did that <a href="http://trueg.wordpress.com/2009/12/07/convenient-querying-in-libnepomuk/" id="link-id11282ff8">before</a>.</p> <p>All in all you should remember one thing: whenever you think about writing your own SPARQL query in a KDE application - have a look at libnepomukquery. It is very likely that you can avoid the hassle of debugging a query by using the query API.</p> <p>The first nice effect of the new API (apart from me using it all over the place obviously) is the new query interface in Dolphin. Internally it simply combines a bunch of <a href="http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk/html/classNepomuk_1_1Query_1_1Term.html" id="link-id11952270">Nepomuk::Query::Term</a> objects into a <a href="http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk/html/classNepomuk_1_1Query_1_1AndTerm.html" id="link-id13aa85b8">Nepomuk::Query::AndTerm</a>. All very readable and no ugly query strings.</p> <div id="attachment_234" class="wp-caption aligncenter" style="width: 610px"> <a href="http://trueg.files.wordpress.com/2010/01/dolphin-kde-4-4-search-panel.png" id="link-id11454028"><img class="size-full wp-image-234" title="Dolphin Search Panel in KDE SC 4.4" src="http://trueg.files.wordpress.com/2010/01/dolphin-kde-4-4-search-panel.png?w=600&h=208" alt="" width="600" height="208" /> </a> <p class="wp-caption-text">Dolphin Search Panel in KDE SC 4.4</p> </div> <h2>Shared Desktop Ontologies</h2> <p>An important part of the <a href="http://nepomuk.semanticdesktop.org/" id="link-id13a35a90">Nepomuk research project</a> was the creation of a set of <a href="http://www.semanticdesktop.org/ontologies/" id="link-id123a6700">ontologies</a> for describing desktop resources and their metadata. After the <a href="http://xesam.org/main/XesamAbout" id="link-id13c70ab8">Xesam</a> project under the umbrella of <a href="http://www.freedesktop.org/" id="link-id139e2108">freedesktop.org</a> had been convinced to use RDF for describing file metadata they developed their own ontology. Thanks to Evgeny (phreedom) Egorochkin and Antonie Mylka both the Xesam ontology and the Nepomuk <a href="http://dbpedia.org/resource/Information" id="link-id119be318">Information</a> Elements Ontology were already very close in design. Thus, it was relatively easy to merge the two and be left with only one ontology to support. Since then not only KDE but also <a href="http://strigi.sourceforge.net/" id="link-id123b63f0">Strigi</a> and <a href="http://projects.gnome.org/tracker/" id="link-id13d02a30">Tracker</a> are using the Nepomuk ontologies.</p> <p>At the Gran Canaria Desktop Summit I met some of the guys from Tracker and we tried to come up with a plan to create a joint project to maintain the ontologies. This got off to a rough start as nobody really felt responsible. So I simply took the initiative and released the <a href="http://sourceforge.net/projects/oscaf/files/" id="link-id148d7078">shared-desktop-ontologies</a> version 0.1 in November 2009. The result was a s***-load of hate-mails and bug reports due to me breaking KDE build. But in the end it was worth it. Now the package is established and other projects can start to pick it up to create data compatible to the Nepomuk system and Tracker.</p> <p>Today the ontologies (and the shared-desktop-ontologies package) are maintained in the <a href="http://sourceforge.net/apps/trac/oscaf/" id="link-id10ce1038">Oscaf project at Sourceforge</a>. The situation is far from perfect but it is a good start. If you need specific properties in the ontologies or are thinking about creating one for your own application - come and join us in the <a href="http://sourceforge.net/apps/trac/oscaf/report/1" id="link-id11413910">bug tracker</a>…</p> <h2>Timeline KIO Slave</h2> <p>It was at the Akonadi meeting that Will Stephenson and myself got into talking about mimicking some <a href="http://live.gnome.org/Zeitgeist" id="link-id116888b0">Zeitgeist</a> functionality through Nepomuk. Basically it meant gathering some data when opening and when saving files. We quickly came up with a hacky patch for KIO and <a href="http://api.kde.org/4.x-api/kdelibs-apidocs/kio/html/classKFileDialog.html" id="link-id13637348">KFileDialog</a> which covered most cases and allowed us to track when a file was modified and by which application. This little experiment did not leave that state though (it will, however, this year) but another one did: Zeitgeist also provides a fuse filesystem which allows to browse the files by modification dates. Well, whatever fuse can do, KIO can do as well. <a href="http://trueg.wordpress.com/2009/10/26/just-another-way-of-browsing-your-files/" id="link-id13cf58c0">Introducing the timeline:/ KIO slave</a> which gives a calendar view onto your files.</p> <p> <a href="http://trueg.wordpress.com/2009/10/26/just-another-way-of-browsing-your-files/" id="link-id113d4988"><img class="aligncenter size-medium wp-image-208" title="timeline-october" src="http://trueg.files.wordpress.com/2009/10/timeline-october.png?w=300&h=235" alt="" width="300" height="235" /> </a> </p> <h2>Tips And Tricks</h2> <p>Well, I thought I would mention the <a href="http://techbase.kde.org/Development/Tutorials/Metadata/Nepomuk/TipsAndTricks" id="link-id116357d0">Tips And Tricks</a> section I wrote for the <a href="http://techbase.kde.org/Development/Tutorials/Metadata/Nepomuk" id="link-id14473520">techbase</a>. It might not be a big deal but I think it contains some valuable information in case you are using Nepomuk as a developer.</p> <h2>Google Summer Of Code 2009</h2> <p>This time around I had the privilege to <a href="http://trueg.wordpress.com/2009/04/22/nepomuk-in-the-summer-x2/" id="link-id116b0cf8">mentor two students</a> in the Google Summer of Code. Alessandro Sivieri and Adam Kidder did outstanding work on <a href="http://trueg.wordpress.com/2009/08/25/gsoc-wrap-up-part-1/" id="link-id13c9f2f8">Improved Virtual Folders</a> and the <a href="http://trueg.wordpress.com/2009/08/28/gsoc-wrap-up-part-2/" id="link-id123bac00">Smart File Dialog</a>.</p> <p>Adam’s work lead me to some heavy improvements in the Nepomuk KIO slaves myself which I only finished this week (more details on that coming up). Alessandro continued his work on faceted file browsing in KDE and created:</p> <h3>Sembrowser</h3> <p>Alessandro is following up on his work to make faceted file browsing a reality in 2010 (and KDE SC 4.5). Since it was too late to get faceted browsing into KDE SC 4.4 he is working on <a href="http://www.kde-apps.org/content/show.php/Sembrowser?content=117692" id="link-id117c67d0">Sembrowser</a>, a stand-alone faceted file browser which will be the grounds for experiments until the code is merged into Dolphin.</p> <div id="attachment_238" class="wp-caption aligncenter" style="width: 310px"> <a href="http://trueg.files.wordpress.com/2010/01/sembrowser.png" id="link-id13aa8e80"><img class="size-medium wp-image-238" title="sembrowser" src="http://trueg.files.wordpress.com/2010/01/sembrowser.png?w=300&h=189" alt="" width="300" height="189" /> </a> <p class="wp-caption-text">Faceted Browsing in KDE with Sembrowser</p> </div> <h2>Nepomuk Workshops</h2> <p>In 2009 I organized the first Nepomuk workshop in Freiburg, Germany. And also the second one. While <a href="http://trueg.wordpress.com/2009/06/23/the-first-nepomuk-workshop-its-a-wrap/" id="link-id13b553e0">I reported properly on the first one</a> I still owe a summary for the second one. I will get around to that - sooner or later. ;)</p> <h2>CMake Magic</h2> <p> <a href="http://soprano.sourceforge.net/" id="link-id148bfad8">Soprano</a> gives us a nice command line tool to create a C++ namespace from an ontology file: <a href="http://soprano.sourceforge.net/apidox/trunk/soprano_devel_tools.html" id="link-iddac3b58">onto2vocabularyclass</a>. It produces nice convenience namespaces like <a href="http://soprano.sourceforge.net/apidox/trunk/namespaceSoprano_1_1Vocabulary_1_1NAO.html" id="link-idfd4b970">Soprano::Vocabulary::NAO</a>. Nepomuk adds another tool named <a href="http://techbase.kde.org/Development/Tutorials/Metadata/Nepomuk/ResourceGenerator" id="link-id11b60200">nepomuk-rcgen</a>. Both were a bit clumsy to use before. Now we have nice cmake macros which make it very simple to use both.</p> <p>See the <a href="http://techbase.kde.org/Development/Tutorials/Metadata/Nepomuk/ResourceGenerator" id="link-id11963490">techbase article</a> on how to use the new macros.</p> <h2>Bangarang</h2> <p>Without my <a href="http://dbpedia.org/resource/Knowledge" id="link-iddcbd7c8">knowledge</a> (imagine that!) Andrew Lake created an amazing new media player named <a href="http://bangarangkde.wordpress.com/" id="link-id113d9500">Bangarang</a> - <em>a Jamaican word for noise, chaos or disorder.</em> This player is Nepomuk-enabled in the sense that it has a media library which lets you browse your media files based on the Nepomuk data. It remembers the number of times a song or a video has been played and when it was played last. It allows to add detail such as the TV series name, season, episode number, or actors that are in the video - all through Nepomuk (I hope we will soon get <a href="http://thetvdb.com/" id="link-id1154d7a0">tvdb</a> integration).</p> <div id="attachment_242" class="wp-caption aligncenter" style="width: 310px"> <a href="http://trueg.files.wordpress.com/2010/01/bangarang2.png" id="link-id148bcdb8"><img class="size-medium wp-image-242" title="bangarang2" src="http://trueg.files.wordpress.com/2010/01/bangarang2.png?w=300&h=208" alt="" width="300" height="208" /> </a> <p class="wp-caption-text">Edit metadata directly in Bangarang</p> </div> <div id="attachment_243" class="wp-caption aligncenter" style="width: 303px"> <a href="http://trueg.files.wordpress.com/2010/01/bangarang-dolphin-fileinfo.png" id="link-id11c70a48"><img class="size-full wp-image-243" title="bangarang-dolphin-fileinfo" src="http://trueg.files.wordpress.com/2010/01/bangarang-dolphin-fileinfo.png?w=293&h=242" alt="" width="293" height="242" /> </a> <p class="wp-caption-text">Dolphin showing TV episode metadata created by Bangarang</p> </div> <div id="attachment_245" class="wp-caption aligncenter" style="width: 310px"> <a href="http://trueg.files.wordpress.com/2010/01/bangarang-dolphin-search.png" id="link-id149200f8"><img class="size-medium wp-image-245" title="bangarang-dolphin-search" src="http://trueg.files.wordpress.com/2010/01/bangarang-dolphin-search.png?w=300&h=212" alt="" width="300" height="212" /> </a> <p class="wp-caption-text">And of course searching for it works, too...</p> </div> <div id="attachment_244" class="wp-caption aligncenter" style="width: 310px"> <a href="http://trueg.files.wordpress.com/2010/01/bangarang1.png" id="link-id114f7c80"><img class="size-medium wp-image-244" title="bangarang1" src="http://trueg.files.wordpress.com/2010/01/bangarang1.png?w=300&h=225" alt="" width="300" height="225" /> </a> <p class="wp-caption-text">And it is pretty, too...</p> </div> <p>I am especially excited about this since finally applications not written or mentored by me start contributing Nepomuk data.</p> <h2>Gran Canaria Desktop Summit</h2> <p>2009 was also the year of the first Gnome-KDE joint-conference. Let me make a bulletin for completeness and refer to <a href="http://trueg.wordpress.com/2009/07/13/gran-canaria-desktop-summit-2009-the-nepomuk-perspective/" id="link-id143ff668">my previous blog post reporting on my experiences on the island</a>.</p> <p>Well, that was by far not all I did in 2009 but I think I covered most of the important topics. And after all it is ‘just a blog entry’ - there is no need for completeness. Thanks for reading.</p> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/trueg.wordpress.com/232/" id="link-id118a1950"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/trueg.wordpress.com/232/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/trueg.wordpress.com/232/" id="link-id148ffb08"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/trueg.wordpress.com/232/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/trueg.wordpress.com/232/" id="link-id13c65a88"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/trueg.wordpress.com/232/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/trueg.wordpress.com/232/" id="link-id119b85a0"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/trueg.wordpress.com/232/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/trueg.wordpress.com/232/" id="link-id13f5d6b8"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/trueg.wordpress.com/232/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=trueg.wordpress.com&blog=6648236&post=232&subd=trueg&ref=&feed=1" /> </div>"
Kingsley Uyi Idehen
kidehen@openlinksw.com
2010-02-01T09:02:55-05:00
One Technology That Will Rock 2010 (Update 1)
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?id=1601
2010-01-02T17:30:38Z
<p>Thanks to the <a href="http://www.techcrunch.com/" id="link-id114eb070">TechCrunch</a> post titled: <a href="http://www.techcrunch.com/2010/01/01/ten-technologies-2010/" id="link-id1146e550">Ten Technologies That Will Rock 2010</a>, I've been able to quickly construct a derivative post that condenses the ten item list down to a Single Technology That Will Rock 2010 :-)</p> <p>Sticking with the TechCrunch layout, here is why all roads simply lead to <a href="http://dbpedia.org/resource/Linked_Data" id="link-id11141d50">Linked Data</a> come 2010 and beyond: </p> <ol> <li> <strong>The Tablet: </strong>a new form factor addition re. <a href="http://dbpedia.org/resource/Internet" id="link-id13f09418">Internet</a> and <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> application hosts which is just another way of saying: Linked Data will be accessible from Tablet applications.</li> <li> <strong>Geo:</strong> GPS chips are now standard features of mobile phones, so <a href="http://www.techcrunch.com/2009/12/23/location-2010/" id="link-id112cfdd0">geolocation</a> is increasingly becoming a necessary feature for any killer app. Thus, GeoSpatial Linked Data and GeopSpatial Queries are going to be a critical success factor for any endeavor that seeks to engage mobile applications developers and ultimately their end-users. Basiacally, you want to be able to perform Esoteric Search from these devices of the form: Find Vendors of a Camcorder (e.g., with a Zoom Factor: Weight Ratio of X) within a 2km Radius of my current location. Or how many items from my WishList are available from a Vendor within a 2km radius of my current location. Conversely, provide Vendors with the ability to spot potential Customers within a 2km of a given "clicks & mortar" location (e.g. BestBuy store).</li> <li> <strong>Realtime Search: </strong>Rich Structured Profiles that leverage standards such as <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id140ece38">FOAF</a> and <a href="http://blogs.sun.com/bblfish/entry/foaf_ssl_creating_a_global" id="link-id11856318">FOAF+SSL</a> will enable Highly Personalized Realtime Search (HPRS) without compromisng privacy. Tecnically, this is about <a href="http://esw.w3.org/topic/WebID" id="link-id13ec6260">WebID</a>s securely bound to X.509 Certificates, providing access to verifiable and highly navigable Personal Profile <a href="http://dbpedia.org/resource/Data">Data</a> Spaces that also double as personal search index entry points.</li> <li> <strong>Chrome OS: </strong>Just another operating system for exploiting the burgeoning Web of Linked Data</li> <li> <strong>HTML5: </strong>Courtesy of <a href="http://dbpedia.org/resource/RDFa" id="link-id115b08f0">RDFa</a>, just another mechanism for exposing Linked Data by making HTML+RDFa a bona fide markup for <a href="http://dbpedia.org/resource/Metadata" id="link-id1195b070">metadata</a> (i.e., format for describing real world objects via their attribute-value graphs)</li> <li> <strong>Mobile Video:</strong> Simplifies the production and sharing of Video annotations (comments, reviews etc.) en route to creating rich Linked Discourse Data Spaces.</li> <li> <strong>Augmented Reality:</strong> Ditto</li> <li> <strong>Mobile Transactions:</strong> As per points 1&2 above, Vendor Discovery and Transaction Conusmation will increasingly be driven by high SDQ applications. The "Funnel Effect" (more choices based on individual preferences) will be a critical success factor for any one operating in the Mobile Transaction realm. Note, without Linked Data you cannot deliver scalable solutions that handle the combined requirements of: SDQ, "Funnel Effect", and Mobile Device form factor, will simply maginify the importance of Web accessible Linked Data.</li> <li> <strong>Android:</strong> An additional platform for items 1-8; basically, 2010 isn't going to be an iPhone only zone. Personally, this reminds <a href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-id111ab5e8">me</a> of a battle from the past i.e., Microsoft vs Apple, re. desktop computing dominance. Google has studied history very well :-)</li> <li> <strong>Social CRM:</strong> this is simply about applying points 1-9 alongide the construction of Linked Data from eCRM Data Spaces.</li> </ol> <p>As I've stated in the past (across a variety of mediums), you cannot build applications that have long term value without addressing the following issues:</p> <ol> <li>Data Item or Object Identity</li> <li>Data Structure -- Data Models</li> <li>Data Representation -- Data Model <a href="http://dbpedia.org/resource/Entity" id="link-id1148eaf8">Entity</a> & Relationships Representation mechanism (as delivered by metadata oriented markup)</li> <li>Data Storage -- Database Management Systems</li> <li>Data Access -- Data Access Protocols </li> <li>Data Presentation -- How you present Views and Reports from Structured Data Sources</li> <li>Data Security -- Data Access Policies</li> </ol> <p>The items above basically showcase the very essence of the HTTP <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id1239af68">URI</a> abstraction that drives HTTP based Linked Data; which is also the basic payload unit that underlies <a href="http://dbpedia.org/resource/Representational_State_Transfer" id="link-id11489a98">REST</a>.</p> <h3>Conclusion</h3> <p>I simply hope that the next decade marks a period of broad appreciation and comprehension of Data Access, Integration, and Management issues on the parts of: application developers, integrators, analysts, end-users, and decision makers. Remember, without structured Data we cannot produce or share <a href="http://dbpedia.org/resource/Information" id="link-id13cb5040">Information</a>, and without Information, we cannot produce of share <a href="http://dbpedia.org/resource/Knowledge" id="link-id647abb0">Knowledge</a>.</p> <h3>Related</h3> <ul> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1567" id="link-id13fa3a20">HTTP URI Abstraction and Linked Data</a> </li> <li> <a href="http://www.dataflux.com/dfblog/?p=1458," id="link-id138f3ea8">First Law of Data Quality</a> </li> <li> <a href="http://walkingoncoals.blogspot.com/2009/12/whos-data-is-it-part-1.html" id="link-id13efccb8">Who's Data Is It?</a> </li> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1442" id="link-id1355df68">Serendipitous Discovery Quotient</a> (SDQ)</li> <li> <a href="http://www.seangolliher.com/2009/linked-data/serendipitous-discovery-quotient-sdq-the-future-of-seo-or-an-abstract-concept/" id="link-id11217cb8">SDQ: The Future of SEO or an Abstract Concept?</a> </li> <li> <a href="http://www.openlinksw.com/dataspace/oerling/weblog/Orri%20Erling%27s%20Blog/1587" id="link-id139cfbe0">SPARQL & GeoSpatial Indexing</a> (implications of <a href="http://dbpedia.org/resource/SPARQL" id="link-id13f51b78">SPARQL</a>-GEO)</li> <li> <a href="http://blog.jonudell.net/2009/09/09/talking-with-kingsley-idehen-about-mastering-your-own-search-index/" id="link-id13c5c248">Mastering Your Own Search Index</a> </li> <li> <a href="http://blog.jonudell.net/2009/11/23/talking-with-martin-hepp-about-solving-the-paradox-of-choice/" id="link-id135ba4d0">Solving the Paradox of Choice</a>.</li> </ul>
Kingsley Uyi Idehen
kidehen@openlinksw.com
2010-02-01T09:02:41-05:00
The Business Of Linked Data (BOLD) Discussion Space
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?id=1600
2009-12-04T19:40:08Z
<p>I've created a new discussion space that's squarely focused on the business development and marketing aspects of "HTTP based <a href="http://dbpedia.org/resource/Linked_Data" id="link-id129e32d8">Linked Data" (Linked Data</a>). As its name indicates, It's a BOLD attempt to fill a VoiD. :-)</p> <h3>Background</h3> <p>A few months ago, <a href="http://blog.aldobucchi.com/#this" id="link-id1110eb30">Aldo Bucchi</a> posted a message to the <a href="http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/LinkingOpenData" id="link-id111d08a0">LOD</a> <a href="http://lists.w3.org/Archives/Public/public-lod/" id="link-id118b3778">mailing list</a> seeking a discussion space for more business and marketing oriented topic, in relation to Linked Data. At the time, my assumption was that the existing LOD mailing list served that purpose absolutely fine, but in due course I came to realize that Aldo's request had a much lager foundation than I initially suspected.</p> <h3>Historic Oversight</h3> <p>Linked Data, like its umbrella <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id16ceb618">Semantic Web</a> Project, has suffered from an inadvertent oversight on the parts of many of its enthusiasts (myself included): 100% of the discussion spaces are created by, geared towards, or dominated by researchers (from Academia primarily) and/or developers. Thus, at the very least, we've been operating in an echo chamber that only feed the existing void between the core community and those who are more interested in discussing business and marketing related topics.</p> <p>The new discussion space seeks to cover the following:</p> <ol> <li> Brainstorming Value Proposition Articulation</li> <li>War Story Exchanges</li> <li>Case Studies and Use-cases</li> <li>Market Research & Positioning (for instance Linked Data is killer technology that redefines <a href="http://dbpedia.org/resource/Data">Data</a> Integration, but none of the major research firms currently make that connection)</li>. </ol> <p>How Do I Join The Conversation? Simply sign up on the Google hosted <a href="http://groups.google.com/group/business-of-linked-data-bold" id="link-id129e4d08">BOLD mailing list</a>, introduce yourself (ideally), and then start conversing! :-)</p>
Kingsley Uyi Idehen
kidehen@openlinksw.com
2010-02-01T09:02:27.000001-05:00
Personal and/or Service Specific Linked Data Spaces in the Cloud: DBpedia 3.4
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?id=1589
2009-11-16T18:17:46Z
<p> We have just released an Amazon EC2 based public Snapshot of <a href="http://dbpedia.org/resource/DBpedia" id="link-id18e899b8">DBpedia</a> 3.4. Thus, you can now instantiate a personal and/or service specific variant of the DBpedia 3.4 <a href="http://dbpedia.org/resource/Linked_Data" id="link-id168dec90">Linked Data</a> <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id18911268">Space</a>. Basically, you can replicate what we host, within minutes (as opposed to days). In addition, you no longer need to squabble --on an unpredictable basis with others-- for the infrastructure resources behind DBpedia's public instance, when using the <a href="http://dbpedia.org/resource/SPARQL" id="link-id18d5bd78">SPARQL</a> Endpoint, Faceted Search & Find Services, or HTML Browser Pages etc.</p> <h3>How Does It work?</h3> <ol> <li> <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtInstallationEC2" id="link-id115932b8">Instantiate a Virtuoso EC2 AMI</a> (paid variety, which is aggressively priced at $49.99 for setup and $19.99 per month thereafter)</li> <li> <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtAWSDBpedia34S" id="link-id182dc800"> Mount the shared DBpedia 3.4 public snapshot</a> </li> <li> Start Virtuoso Server</li> <li> Start exploiting the DBpedia Linked Data Space.</li> </ol> <h3>What Interfaces are exposed?</h3> <ol> <li> SPARQL Endpoint</li> <li> Linked Data Viewer Pages (as you see in the public DBpedia instance)</li> <li> <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtFacetBrowserInstallConfig" id="link-id117f6e80">Faceted Search & Find UI and Web Services</a> (REST or SOAP)</li> <li> All the inference rules for <a href="http://umbel.org/about/" id="link-id144b84a8">UMBEL</a>, SUMO, YAGO, <a href="http://dbpedia.org/resource/Cyc" id="link-id16b69da8">OpenCYC</a>, and DBpedia-OWL <a href="http://dbpedia.org/resource/Data">data</a> dictionaries</li> <li>Type Correlations Between DBpedia and Freebase</li> </ol> <p>Enjoy!</p>
Kingsley Uyi Idehen
kidehen@openlinksw.com
2009-11-16T13:30:20-05:00
Personal and/or Service Specific Linked Data Spaces in the Cloud: DBpedia 3.4
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?id=1599
2009-11-16T18:17:46Z
<p> We have just released an Amazon EC2 based public Snapshot of <a href="http://dbpedia.org/resource/DBpedia" id="link-id18e899b8">DBpedia</a> 3.4. Thus, you can now instantiate a personal and/or service specific variant of the DBpedia 3.4 <a href="http://dbpedia.org/resource/Linked_Data" id="link-id168dec90">Linked Data</a> <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id18911268">Space</a>. Basically, you can replicate what we host, within minutes (as opposed to days). In addition, you no longer need to squabble --on an unpredictable basis with others-- for the infrastructure resources behind DBpedia's public instance, when using the <a href="http://dbpedia.org/resource/SPARQL" id="link-id18d5bd78">SPARQL</a> Endpoint, Faceted Search & Find Services, or HTML Browser Pages etc.</p> <h3>How Does It work?</h3> <ol> <li> <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtInstallationEC2" id="link-id115932b8">Instantiate a Virtuoso EC2 AMI</a> (paid variety, which is aggressively priced at $49.99 for setup and $19.99 per month thereafter)</li> <li> <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtAWSDBpedia34S" id="link-id182dc800"> Mount the shared DBpedia 3.4 public snapshot</a> </li> <li> Start Virtuoso Server</li> <li> Start exploiting the DBpedia Linked Data Space.</li> </ol> <h3>What Interfaces are exposed?</h3> <ol> <li> SPARQL Endpoint</li> <li> Linked Data Viewer Pages (as you see in the public DBpedia instance)</li> <li> <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtFacetBrowserInstallConfig" id="link-id117f6e80">Faceted Search & Find UI and Web Services</a> (REST or SOAP)</li> <li> All the inference rules for <a href="http://umbel.org/about/" id="link-id144b84a8">UMBEL</a>, SUMO, YAGO, <a href="http://dbpedia.org/resource/Cyc" id="link-id16b69da8">OpenCYC</a>, and DBpedia-OWL <a href="http://dbpedia.org/resource/Data">data</a> dictionaries</li> <li>Type Correlations Between DBpedia and Freebase</li> </ol> <p>Enjoy!</p>
Kingsley Uyi Idehen
kidehen@openlinksw.com
2010-02-01T08:58:14-05:00
Conversation with Jon Udell: Are We There Yet Re. Web++ ?
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?id=1584
2009-09-10T15:03:01Z
<p> Personally, I believe that we've actually reached a watershed moment re. the evolution of the <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> from a mesh of <a href="http://dbpedia.org/resource/Linked_Data" id="link-id123169a8">Linked Data</a> Containers (Web of Linked Documents) to a mesh of Linked Data Items (entities or real world objects).</p> <p> The journey towards this watershed moment started with the <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id14f69f48">Semantic Web</a> Project, gained focus and pragmatism via the <a href="http://www.w3.org/DesignIssues/LinkedData.html" id="link-id11155f78">Linked Data meme</a>, attained substance & credibility via efforts such as <a href="http://dbpedia.org/resource/DBpedia" id="link-id15857c78">DBpedia</a> and the resulting cloud of <a href="http://www4.wiwiss.fu-berlin.de/bizer/pub/lod-datasets_2009-07-14.html" id="link-id16adf918">Open Linked Data Spaces</a>, and finally arrived at the most important destination of all: broad comprehension and coherence, via <a href="http://dbpedia.org/resource/RDFa" id="link-id1229b960">RDFa</a>. </p> <p> Over the years, I've chronicled the journey above via entries in this particular <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id14f76338">data space</a> (my <a href="http://dbpedia.org/resource/Blog" id="link-idfd32c88">blog</a>) and most recently, via my rapid-fire comments and debates on <a href="http://twitter.com" id="link-id11339e80">Twitter</a> (basically hastag #linkeddata account: <a href="http://twitter.com/kidehen#this" id="link-id115e9af8">kidehen</a>). </p> <p> On a parallel front re. my chronicles, I've periodically had conversations with <a href="http://blog.jonudell.net/about/" id="link-id11829170">Jon Udell</a>, who has always provided a coherent sounding board and reconciliation framework for my world views and open data access vision; naturally, this has a lot to do with his holistic grasp of the big picture issues, associated technical details, and special communication prowess :-) </p> <p> Against this backdrop, I refer you to my <a href="http://itc.conversationsnetwork.org/shows/detail4233.html" id="link-id14ac9c08">most recent podcast conversation with Jon</a>, which is about how the tandem of HTML+RDFa and the <a href="http://www.heppnetz.de/projects/goodrelations/" id="link-id14279be8">GoodRelations vocabulary</a> deliver the critical missing links re. broad comprehension of the Semantic Web vision en route to mass exploitation. </p> <h3>Related</h3> <ul> <li> <a href="http://webbackplane.com/node/57" id="link-id113b5b00">Mark Birbeck Introduces RDFa</a> </li> <li> <a href="http://webbackplane.com/rdfa-handbook" id="link-id11b36ac0">RDFa Handbook</a> </li> <li> <a href="http://www.ebusiness-unibw.org/wiki/GoodRelations#CookBook:_GoodRelations_Recipes_and_Examples" id="link-id1519f458">GoodRelations Usage Examples & Templates</a> </li> <li> <a href="http://blog.jonudell.net/2009/09/09/talking-with-kingsley-idehen-about-mastering-your-own-search-index/" id="link-id11a62ce0">Be the master of your own search index</a> </li> <li> <a href="http://itc.conversationsnetwork.org/shows/detail4312.html" id="link-id115d54f0">Jon Udell Interviews Martin Hepp about GoodRelations, RDFa, and Esoteric Web Search</a> <br /> </li> </ul>
Kingsley Uyi Idehen
kidehen@openlinksw.com
2010-02-01T08:58:04.000002-05:00
The URI, URL, and Linked Data Meme's Generic HTTP URI (Updated)
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?id=1567
2009-08-07T18:34:50Z
<h3>Situation Analysis</h3> <p>As the "<a href="http://www.w3.org/DesignIssues/LinkedData.html" id="link-id12f96a00">Linked Data" meme</a> has gained momentum you've more than likely been on the receiving end of dialog with Linked Open <a href="http://dbpedia.org/resource/Data">Data</a> community members (myself included) that goes something like this:</p> <blockquote> <cite>"Do you have a <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id139252a0">URI</a>", "Get yourself a URI", "Give <a href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-id140eab68">me</a> a de-referencable URI" etc..</cite> </blockquote> <p>And each time, you respond with a <a href="http://dbpedia.org/resource/Uniform_Resource_Locator" id="link-id112c1860">URL</a> -- which to the best of your <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> <a href="http://dbpedia.org/resource/Knowledge" id="link-id140b51c0">knowledge</a> is a bona fide URI. But to your utter confusion you are told: Nah! You gave me a Document URI instead of the URI of a real-world thing or object etc..</p> <h3>What's up with that?</h3> <p>Well our everyday use of the Web is an unfortunate conflation of two distinct things, which have Identity: Real World Objects (RWOs) & Address/Location of Documents (<a href="http://dbpedia.org/resource/Information" id="link-id144838b0">Information</a> bearing Resources).</p> <p>The "Linked Data" meme is about enhancing the Web by unobtrusively reintroducing its core essence: the generic HTTP URI, a vital piece of Web Architecture DNA. Basically, its about so realizing the full capabilities of the Web as a platform for Open Data Identification, Definition, Access, Storage, Representation, Presentation, and Integration.</p> <h3>What is a Real World Object?</h3> <p>People, Places, Music, Books, Cars, Ideas, Emotions etc..</p> <h3>What is a URI?</h3> <p>A Uniform Resource Identifier. A global identifier mechanism for network addressable data items. Its sole function is Name oriented Identification.</p> <h4>URI Generic Syntax</h4> <p>The constituent parts of a URI (from <a href="http://www.ietf.org/rfc/rfc2396.txt" id="link-id1180c700">URI Generic Syntax RFC</a>) are depicted below: <img alt="Image" src="http://virtuoso.openlinksw.com/images/generic_uri_syntax_image.png" /> </p> <h3>What is a URL?</h3> <p>A location oriented HTTP scheme based URI. The HTTP scheme introduces a powerful and inherent duality that delivers:</p> <ol> <li> Resource Address/Location Identifier</li> <li> Data Access mechanism for an Information bearing Resource (Document, File etc..) </li> </ol> <p>So far so good!</p> <h3>What is an HTTP based URI?</h3> <p>The kind of URI <a href="http://dbpedia.org/resource/Linked_Data" id="link-id11100a28">Linked Data</a> aficionados mean when they use the term: URI.</p> <p>An HTTP URI is an HTTP scheme based URI. Unlike a URL, this kind of HTTP scheme URI is devoid of any Web Location orientation or specificity. Thus, Its inherent duality provides a more powerful level of abstraction. Hence, you can use this form of URI to assign Names/Identifiers to Real World Objects (RWO). Even better, courtesy of the Identity/Address duality of the HTTP scheme, a single URI can deliver the following:</p> <ol> <li> RWO Identfier/Name</li> <li> RWO Metadata document Locator (courtesy of URL aspect) </li> <li> Negotiable Representation of the Located Document (courtesy of HTTP's content negotiation feature).</li> </ol> <h3>What is Metadata?</h3> <p> Data about Data. Put differently, data that describes other data in a structured manner.</p> <h3>How Do we Model Metadata?</h3> <p>The predominant model for metadata is the <a href="http://dbpedia.org/resource/Entity-attribute-value_model" id="link-id11193d30">Entity</a>-Attribute-Value + Classes & Relationships model (<a href="http://dbpedia.org/resource/Entity-attribute-value_model" id="link-id11725710">EAV</a>/CR). A model that's been with us since the inception of modern computing (long before the Web). </p> <h3>What about RDF?</h3> <p>The Resource Description Framework (RDF) is a framework for describing Web addressable resources. In a nutshell, its a framework for adding Metadata bearing Information Resources to the current Web. Its comprised of:</p> <ol> <li> Entity-Attribute-Value (aka. Subject-Predictate-Object) plus Classes & Relationships (<a href="http://dbpedia.org/resource/Data_dictionary" id="link-id138df0f8">Data Dictionaries</a> e.g., <a href="http://dbpedia.org/resource/Web_Ontology_Language" id="link-id116bf590">OWL</a>) metadata model</li> <li> A plethora of instance data representation formats that include: <a href="http://dbpedia.org/resource/RDFa" id="link-id13360b90">RDFa</a> (when doing so within (X)HTML docs), Turtle, N3, TriX, RDF/XML etc. </li> </ol> <h3>What's the Problem Today?</h3> <p>The ubiquitous use of the Web is primarily focused on a Linked Mesh of Information bearing Documents. URLs rather than generic HTTP URIs are the prime mechanism for Web tapestry; basically, we use URLs to conduct Information -- which is inherently subjective -- instead of using HTTP URIs to conduct "Raw Data" -- which is inherently objective. </p> <blockquote> <strong>Note:</strong> Information is "data in <a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id1395ca50">context</a>", it isn't the same thing as "Raw Data". Thus, if we can link to Information via the Web, why shouldn't we be able to do the same for "Raw Data"?</blockquote> <h3>How Does the Link Data <a href="http://dbpedia.org/resource/Meme" id="link-id1160ab70">meme</a> solve the problem?</h3> <p>The meme simply provides a set of guidelines (best practices) for producing Web architecture friendly metadata. Meaning: when producing EAV/CR model based metadata, endow Subjects, their Attributes, and Attribute Values (optionally) with HTTP URIs. By doing so, a new level of Link Abstraction on the Web is possible i.e., "Data Item to Data Item" level links (aka <a href="http://dbpedia.org/resource/Linked_Data" id="link-id137a78a0">hyperdata</a> links). Even better, when you de-reference a RWO hyperdata link you end up with a negotiated representations of its metadata.</p> <h3>Conclusion</h3> <p>Linked Data is ultimately about an HTTP URI for each item in the <a href="http://dbpedia.org/resource/Data_hierarchy" id="link-id1393c3e0">Data Organization Hierarchy</a> :-)</p> <h3>Related</h3> <ol> <li> <a href="http://lists.w3.org/Archives/Public/www-tag/2009Aug/0000.html" id="link-id140c1e78">History of how "Resource" became part of URI</a> - historic account by <a href="http://www.w3.org/People/Berners-Lee/card#i" id="link-id1172b128">TimBL</a> </li> <li> <a href="http://www.w3.org/DesignIssues/LinkedData.html" id="link-id1338cbd0">Linked Data Design Issues Document</a> - <a href="http://www.w3.org/People/Berners-Lee/card#i" id="link-id13536ad8">TimBL</a>'s initial Linked Data Guide</li> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1561" id="link-id116c1af8">Linked Data Rules Simplified</a> - My attempt at simplifying the Linked Data Meme without <a href="http://dbpedia.org/resource/SPARQL" id="link-id116c3b40">SPARQL</a> & RDF distraction</li> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1547" id="link-id135dd1b8">Linked Data & Identity</a> - another related post</li> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1565" id="link-id134afc50">The Linked Data Meme's Value Proposition</a> </li> <li> <a href="http://delicious.com/kidehen/identifier_scheme" id="link-id14cc7e18">My Del.icio.us hosted Bookmark Data Space for Identity Schemes</a> </li> <li> <a href="http://www.ted.com/talks/tim_berners_lee_on_the_next_web.html" id="link-id115a3748">TimBL's Ted Talk re. "Raw Linked Data"</a> </li> <li> <a href="http://www.infoq.com/articles/roa-rest-of-rest" id="link-id11b25558">Resource Oriented Architecture</a> </li> <li> <a href="http://www.blipfoto.com/view.php?id=465380&month=2&year=2010" id="link-id139824c8">More Famous Than Simon Cowell</a> .<br /> </li> </ol>
Kingsley Uyi Idehen
kidehen@openlinksw.com
2010-02-03T15:26:53.000005-05:00
Why Do We Put Stuff On The Web, Really?
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?id=1566
2009-07-24T15:54:26Z
<p>As espoused by the Ubuntu philosophy, no Human is an Island. Thus, although the objects of our sociality are vast and varied; that said, the basic foundation still centers on the pursuit and/or delivery of products and services.</p> <p>Today, the we put stuff on the <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> because we want it do be discovered as part of a "sharing act". Likewise, we make regular use of Search Engine Services because we want to "Find" stuff in a productive manner.</p> <p>Putting, the above in <a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id1340d970">context</a>, you don't need to be Einstein to figure out that to date the Web hasn't enabled vendors to describe their products and services clearly. Likewise, it hasn't enabled us to describe what we want, when we want it, and how much we are willing to pay etc. Basically, the SDQ of Web Content is excruciatingly low!</p> <p> The <a href="http://www.w3.org/DesignIssues/LinkedData.html" id="link-id1357e068">Linked Data meme</a> is about using the essence of the Web -- HTTP URIs -- as the mechanism for conducting <a href="http://dbpedia.org/resource/Data">data</a> across the Web that unambiguously unveils basic things like:</p> <ol> <li> Using a personal profile to describe exactly who I am, my interests, favorite things, what I want (wishlist), what I have to offer (offerlist) etc.</li> <li> Using an company profile to describe my entire product catalog, inventory levels, store locations, distributor and reseller networks, feature specs, price specs, deal terms and duration, and even opening and closing hours.</li> </ol> <h3>Conclusions</h3> <p>A Web of <a href="http://dbpedia.org/resource/Linked_Data" id="link-id124f7778">Linked Data</a> enables a complete redefinition of eCommerce, and that's just for starters :-)</p> <h3>Related</h3> <ul> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1442" id="link-id112b62c0">Post Introducing SDQ</a> </li> <li> <a href="http://www.seangolliher.com/2009/linked-data/serendipitous-discovery-quotient-sdq-the-future-of-seo-or-an-abstract-concept/" id="link-id110cf500">Serendipitous Discovery Quotient (SDQ): The Future of SEO? Or an Abstract Concept?</a> </li> </ul>
Kingsley Uyi Idehen
kidehen@openlinksw.com
2009-07-24T21:00:21-04:00