, ; ; "Kingsley Uyi Idehen's Weblog" . ; . ; ; "Kingsley Idehen" . , ; ; ; ; "2008-02-11T19:19:13Z"^^ ; "2008-02-11T14:28:25.000-05:00"^^ ; "Contd: Why we need Linked Data" ; ; "2008-02-11T19:19:13Z" ; "2008-02-11T19:28:25Z" ; ; ; "Contd: Why we need Linked Data" ; , , , , ; "Contd: Why we need Linked Data" ; ; "<p>Increasingly, I am encountering commentary from the <a href="http://www.readwriteweb.com" id="link-id166f5440">ReadWriteWeb</a> data space that highlights critical problems solved by a <a href="http://en.wikipedia.org/wiki/Linked_Data" id="link-id1698f0e0">Linked Data</a> Web. Unfortunately, most of the time, there is a disconnect between the problem and the solution. By this I mean: technology in the Semantic Web realm isn&#39;t seen as the solution.</p>\n<p>A while back, I wrote a post titled:<a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1267" id="link-id1676b440">Why we need Linked Data</a>. The aim of the post was to bring attention to the implications of <a href="http://www.johnbreslin.com/blog/2008/01/23/an-interesting-talk-by-mike-brodie/" id="link-id16f14740">exponential growth of User Generated Content</a> (typically, semi-structured and unstructured data) on the Web. The growth in question is occurring within a fixed data &amp; information processing timeframe (i.e. there will always be 24hrs in a day), which sets the stage for Information Overload as expressed in a recent post from ReadWriteWeb titled: <a href="http://www.readwriteweb.com/archives/visualizing_social_media_fatigue.php" id="link-id164a6278">Visualizing Social Media Fatigue</a>.</p>\n<p>The emerging &quot;Web of Linked Data&quot; augments the current &quot;Web of Linked Documents&quot;, by providing a structured data corpus partitioned by containers I prefer to call: Data Spaces. These spaces enable Linked Data aware solutions to deliver immense value such as, complex data graph traversal, starting from document beachheads, that expose relevant data within a faction of the time it would take to achieve the same thing using traditional document web methods such as full text search patterns, scraping, and mashing etc.</p>\n<p>Remember, our DNA based data &amp; information system far exceeds that of any inorganic system when it comes to reasoning, but it remains immensely incapable of accurately and efficiently processing huge volumes of data &amp; information -- irrespective of data model.</p>\n<p>The Idea behind the Semantic Web has always been about an evolution of the Web into a structured data collective comprised of interlinked Data items and Data Containers (Data Spaces). Of course we can argue forever about the Semantics of the solution (ironically), but we can&#39;t shirk away from the impending challenges that &quot;Information Overload&quot; is about to unleash on our limited processing time and capabilities.</p>\n<p>For those looking for a so called &quot;killer application&quot; for the Semantic Web, I would urge you to align this quest with the &quot;Killer Problem&quot; of our times, because when you do so you will that all routes lead to: Linked Data that leverages existing Web Architecture. </p>\n<p>Once you understand the problem, you will hopefully understand that we all need some kind of &quot;Data Junction Box&quot; that provides a &quot;Data Access Focal Point&quot; for all of the data we splatter across the net as we sign up for the next greatest and latest Web X.X hosted service, or as we work on a daily basis with a variety of tools within enterprise Intranets.</p>\n<p>BTW - these &quot;Data Junction Boxes&quot; will also need to be unobtrusively bound to our individual Identities.</p>\n" ; "7f2ada6bcfc29e8994b83dbea5497fa3" ; ; . . , ; ; ; "Kingsley Uyi Idehen's Weblog" ; ; . ; ; . ; ; ; "Kingsley Idehen" .