http://www.openlinksw.com/GData/127/?q=rdfization
Kingsley Idehen's Blog Data Space
2026-06-10T22:35:57Z
Kingsley Uyi Idehen
kidehen@openlinksw.com
About rdfization
11
1
10
http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1395
<p>It's getting really hot in <a href="http://dbpedia.org/resource/Linked_Data" id="link-id15eea8f8">Linked Data</a> land! Two days ago <a href="http://bnode.org/about" id="link-id107e2f70">Benjamin Nowack</a> pinged the <a href="http://community.linkeddata.org/dataspace/organization/lod#this" id="link-id11b93670">LOD</a> community about his <a href="http://lists.w3.org/Archives/Public/public-lod/2008Jul/0110.html" id="link-id1022a270">RDFization of Crunchbase</a> (sample (X)HTML view: http://cb.semsol.org/company/opera-software) courtesy of Crounchbase releasing an API. As you know, I've always equated <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> Service API to Database CLIs (<a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id16327528">ODBC</a>, <a href="http://dbpedia.org/resource/Java_Database_Connectivity" id="link-id1027f410">JDBC</a>, <a href="http://dbpedia.org/resource/ADO.NET" id="link-id10683850">ADO</a>.<a href="http://dbpedia.org/resource/ADO.NET" id="link-id13beb9b8">NET</a> etc.) as both offer code level hooks into <a href="http://dbpedia.org/resource/Data">Data</a> Spaces.</p> <p></p> <p></p> <p>Naturally, we've decided to join the Crunchbase RDFization party, and have just completed a <a href="http://virtuoso.openlinksw.com" id="link-id10282208">Virtuoso</a> <a href="http://virtuoso.openlinksw.com/Whitepapers/html/VirtSpongerWhitePaper.html" id="link-id10acf0f8">Sponger</a> Cartridge (an RDFizer) for Crouncbase. What we add in our particular cartridge is additional meshing with <a href="http://dbpedia.org/resource/DBpedia" id="link-id115e2a98">DBpedia</a> and Wikicompany <a href="http://dbpedia.org/resource/Linked_Data" id="link-id132f0568">Linked Data</a> Spaces, plus RDFizaton of the Crunchbase (X)HTML pages :-)</p> <p></p> <p></p> <p>As I've postulated for a while, <a href="http://dbpedia.org/resource/Linked_Data" id="link-id13304010">Linked Data</a> is about data "Meshing" and "Meshups". This isn't a buzzword play. I am pointing out an important distinction between "Mashups" and "Meshpus". Which goes as follows: "Mashups" are about code level joining devoid of structured modelling, hence the revelation of code as opposed to data when you look behind a "Mashup". "Meshups" on the other hand, are about joining disparate structured data sources across the Web. And when you look behind a "Meshup" you see structured data (preferably <a href="http://dbpedia.org/resource/Linked_Data" id="link-id143bdb68">Linked Data</a>) that enables further "Meshing".</p> <p></p> <p></p> <p>I truly believe that we are now inches away from critical mass re. <a href="http://dbpedia.org/resource/Linked_Data" id="link-id14829640">Linked Data</a>, and because we are dealing with data, the network-effect will be sky-high! I shudder to think about the state of the <a href="http://dbpedia.org/resource/Linked_Data" id="link-id0x1c41d150">Linked Data</a> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id133364e8">Web</a> in 12 months time. Yes, I am giving the explosion 12 months (or less). These are very exciting times.</p> <p></p> <p></p> <p>Demo Links:</p> <p></p> <p></p> <ul> <li> <a href="http://demo.openlinksw.com/ode/?uri%5B%5D=http%3A%2F%2Fcb.semsol.org%2Fcompany%2Fopera-software&" id="link-id12fe1dc8">Opera Software via Benjee's Linked Data Space for Cunchbase</a> </li> <li> <a href="http://demo.openlinksw.com/ode/?uri=http%3A%2F%2Fwww.crunchbase.com%2Fcompany%2Fopera-software" id="link-id10739a18">Opera Software via our Linked Data Space for Crunchbas</a> </li> </ul> <p></p> <p></p> <p>For best experience I encourage you to look at the <a href="https://addons.mozilla.org/en-US/firefox/addon/8062" id="link-id1499a0f8">OpenLink Data Explorer extension</a> for Firefox (2.x - 3.x). This enables you to go to Crunchbase (X)HTML pages (and other sites on the Web of course), and then simply use the "View | <a href="http://dbpedia.org/resource/Linked_Data">Linked Data</a> Sources" main or <a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id10051b50">context</a> menu sequence to unveil the Linked Data Sources associated with any Web Page.</p> <p></p> <p>Of course there is much more to come!</p>
CrunchBase gets hooked up with the Linked Data Web!
2008-07-30T01:43:27Z
2008-07-29T21:43:27-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/1289
<p>As 2007 came to a close I repeatedly mulled over the idea of putting together a usual "year in review" and a set of predictions for the coming year etc. Anyway, the more I pondered, the smaller the list became. While pondering (as 2008 rolled around), the <a href="http://www.techmeme.com/080103/p154#a080103p154" id="link-id113db9a0">Blogosphere was set ablaze with the <a href="http://dbpedia.org/resource/Robert_Scoble" id="link-idfe12a58">Robert Scoble</a>'s announcement of his account suspension by Facebook</a>. Of course, many chimed in expressing views either side of the ensuing debate: <a href="http://www.scripting.com/stories/2008/01/03/scobleAndHisFacebookData.html" id="link-id161e7c48">Who is right -- Scoble or Facebook</a>. The more I assimilated the views expressed about this event, the more ironic I found the general discourse, for the following reasons:</p> <ol> <li> <a href="http://dbpedia.org/resource/Web_2.0" id="link-id16f6f3e0">Web 2.0</a> is fundamentally about <a href="http://dbpedia.org/resource/Web_service" id="link-id1770f3c0">Web Services</a> as the prime vehicle for interactions across "points of Web presence"</li> <li> <a href="http://dbpedia.org/resource/Facebook" id="link-id162f3f60">Facebook</a> is a Web 2.0 hosted service for <a href="http://dbpedia.org/resource/Social_Networking" id="link-id16e1dfc8">social networking</a> that provides Web Services APIs for accessing data in the Facebook data space. You have to do so "on the fly" within clearly defined constraints i.e you can interact with data across your social network via Facebook APIs, but you cannot cache the data (perform an export style dump of the data)</li> <li> Facebook is a main driver of the term: "social graph", but their underlying data model is relational and the Web Services response (data you get back) doesn't return a data graph, instead it returns an tree (i.e XML)</li> <li> <a href="http://blogsearch.google.com/blogsearch?hl=en&q=scoble+semantic+web&btnG=Search+Blogs" id="link-id16680d08">Scoble's had a number of close encounters with Linked Data Web | Semantic Data Web | Web 3.0 aficionados</a> in various forms throughout 2007, but still doesn't quite make the connection between Web Services APIs as part of a processing pipeline that includes structured data extraction from XML data en route to producing Data Graphs comprised of Data Objects (Entities) endowed with: <a href="http://dbpedia.org/resource/Identity_%28object-oriented_programming%29" id="link-id16af1f98">Unique Identifiers</a>, Classification or Categorization schemes, Attributes, and Relationships prescribed by one or more shared Data Dictionaries/Schemas/Ontologies</li> <li> A global information bus that exposes a <a href="http://dbpedia.org/resource/Linked_Data" id="link-id16ce7c68">Linked Data</a> mesh comprised of Data Objects, Object Attributes, and Object Relationships across "points of Web presence" is what <a href="http://www.w3.org/People/Berners-Lee/card#i" id="link-id1aa304e0">TimBL</a> described in 1998 (<a href="http://www.w3.org/DesignIssues/Semantic.html" id="link-id1a822db0">Semantic Web Roadmap</a>) and more recently in 2007 (<a href="http://dig.csail.mit.edu/breadcrumbs/node/215" id="link-id181e5998">Giant Global Graph</a>)</li> <li> The Linked Data mesh (i.e Linked Data Web or GGG) is anchored by the use of HTTP to mint Location, Structure, and Value independent Object Identifiers called <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id16eae370">URI</a>s or <a href="http://dbpedia.org/resource/IRI" id="link-idffe16b8">IRI</a>s. In addition, the Linked Data Web is also equipped with a query language, protocol, and results serialization format for XML and JSON called: SPARQL. </li> </ol> <p>So, unlike Scoble, I am able to make my Facebook Data portable without violating Facebook rules (no data caching outside Facebook realm) by doing the following:</p> <ol> <li> Use an RDFizer for Facebook to convert XML response data from Facebook Web Services into RDF "on the fly" Ensure that my RDF is comprised of Object Identifiers that are HTTP based and thereby dereferencable (i.e. I can use SPARQL to unravel the Linked Data Graph in my Facebook data space)</li> <li> The act of data dereferencing enables me to expose my Facebook Data as Linked Data associated with my <a href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-id16b3e9d0">Personal URI</a> </li> <li> This interaction only occurs via my data space and in all cases the interactions with data work via my <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1172" id="link-id16c628b8">RDFizer middleware</a> (e.g the <a href="http://virtuoso.openlinksw.com/presentations/Virtuoso_Sponger_1/Virtuoso_Sponger_1.html" id="link-id1572fb28">Virtuoso Sponger</a>) that talks directly to Facebook Web Services. </li> </ol> <p>In a nutshell, my Linked Data Space enables you to reference data in my data space via Object Identifiers (URIs), and some cases the Object IDs and Graphs are constructed on the fly via RDFization middleware.</p> <p>Here are my URIs that provide different paths to my Facebook Data Space:</p> <ul> <a href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-id16f817a8"> Personal URI</a> </ul> <ul> <a href="http://myopenlink.net/proxy?url=http%3A//www.facebook.com/people/Kingsley_Idehen/605980750&force=rdf&login=kidehen" id="link-id1a8e5950">My Facebook Data Space</a> (best viewed via a <a href="http://demo.openlinksw.com/rdfbrowser/?uri=http%3A%2F%2Fmyopenlink.net%2Fproxy%3Furl%3Dhttp%253A%2F%2Fwww.facebook.com%2Fpeople%2FKingsley_Idehen%2F605980750%26force%3Drdf%26login%3Dkidehen" id="link-id15476588">Linked Data Browser/Viewer</a> session) </ul> <ul> <a href="http://myopenlink.net/proxy?url=http%3A//www.facebook.com/album.php%3Faid%3D14768%26id%3D605980750&force=rdf&login=kidehen" id="link-id16e3bcf0">My Facebook Photo Gallery -- WWW2007 Photo Collection</a> (also best viewed via a <a href="http://demo.openlinksw.com/rdfbrowser/?uri=http%3A%2F%2Fmyopenlink.net%2Fproxy%3Furl%3Dhttp%253A%2F%2Fwww.facebook.com%2Falbum.php%253Faid%253D14768%2526id%253D605980750%26force%3Drdf%26login%3Dkidehen" id="link-id16e10270">Linked Data Browser/Viewer</a> session) </ul> <p>To conclude, 2008 is clearly the inflection year during which we will final unshackle Data and Identity from the confines of "Web Data Silos" by leveraging the HTTP, SPARQL, and RDF induced virtues of Linked Data. </p> <p>Related Posts:</p> <ol> <li> <a href="http://blogs.sun.com/bblfish/entry/2008_the_rise_of_linked" id="link-id156baac0">2008 and the Rise of Linked Data</a> </li> <li> <a href="http://blogs.sun.com/bblfish/entry/data_portability_scoble_explains" id="link-id16291310">Scoble Right, Wrong, and Beyond</a> </li> <li> <a href="http://scobleizer.com/2007/11/30/talking-with-tim-berners-lee-inventor-of-the-web/" id="link-id163c9c38">Scoble interviewing TimBL</a> (note to Scoble: re-watch your interview since he made some specific points about Linked Data and URIs that you need to grasp)</li> <li>Prior Blog posts my this Blog Data Space that include the literal patterns: <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=scoble%20semantic%20web&type=text&output=html" id="link-id163e6cd0">Scoble Semantic Web</a> </li> </ol>
2008, Facebook Data Portability, and the Giant Global Graph of Linked Data
2008-01-07T16:44:42Z
2008-01-07T11:44:42.000007-05:00
Kingsley Uyi Idehen
kidehen@openlinksw.com
http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1556
<p> While exploring the <a href="http://id.loc.gov/authorities/" id="link-id1488cca8">Subject Headings Linked Data Space</a> (LCSH) recently unveiled by the <a href="http://id.loc.gov/" id="link-id1672ad10">Library of Congress</a>, I noticed that the <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id158fef78">URI</a> for the subject heading: <a href="http://id.loc.gov/authorities/sh95000541#concept" id="link-id14c8d3e8">World Wide Web</a>, exposes an "owl:sameAs" link to resource URI: "info:lc/authorities/sh95000541" -- in fact, a URI.URN that isn't HTTP protocol scheme based.</p> <p> The observations above triggered a <a href="http://search.twitter.com/search?q=&ands=&phrase=&ors=&nots=&tag=linkeddata&lang=all&from=kidehen&to=edsu&ref=&near=&within=15&units=mi&since=2009-05-01&until=2009-05-05&rpp=10" id="link-id14e21ba0">discussion thread on Twitter</a> that involved: <a href="http://twitter.com/edsu" id="link-ide411808">@edsu</a>, <a href="http://twitter.com/iand" id="link-id11915ed0">@iand</a>, and <a href="http://twitter.com/kidehen" id="link-id1519c028">moi</a>. Naturally, it morphed into a live demonstration of: human vs machine, interpretation of claims expressed in the RDF graph.</p> <h3>What makes this whole thing interesting?</h3> <p>It showcases (in Man vs Machine style) the issue of unambiguously discerning the meaning of the owl:sameAs claim expressed in the LCSH <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id17004728">Linked Data Space</a>.</p> <h4>Perspectives & Potential Confusion</h4> <p> From the Linked Data perspective, it may spook a few people to see owl:sameAs values such as: "info:lc/authorities/sh95000541", that cannot be de-referenced using HTTP. </p> <p> It may confuse a few people or user agents that see URI de-referencing as not necessarily HTTP specific, thereby attempting to de-reference the URI.URN on the assumption that it's associated with a "<a href="http://www.handle.net/overviews/overview.html" id="link-id155517a8">handle system</a>", for instance.</p> <p> It may even confuse RDFizer / RDFization middleware that use owl:sameAs as a <a href="http://dbpedia.org/resource/Data">data</a> provider attribution mechanism via hint/nudge URI values derived from original content / data URI.URLs that de-reference to nothing e.g., an original resource URI.<a href="http://dbpedia.org/resource/Uniform_Resource_Locator" id="link-id119e0d80">URL</a> plus "#this" which produces URI.URN-URL -- think of this pattern as "owl:shameAs" in a sense :-)</p> <h3> Unambiguously Discerning Meaning</h3> <p> Simply bring OWL reasoning (inference rules and reasoners) into the mix, thereby negating human dialogue about interpretation which ultimately unveils a mesh of orthogonal view points. Remember, OWL is all about infrastructure that ultimately enables you to express yourself clearly i.e., say what you mean, and mean what you say. </p> <h3>Path to Clarity (using <a href="http://virtuoso.openlinksw.com" id="link-id1537aa68">Virtuoso</a>, its in-built Sponger Middleware, and Inference Engine):</h3> <ol> <li>GET the data into the Virtuoso Quad store -- what the sponger does via its <a href="http://linkeddata.uriburner.com/about/html/http://id.loc.gov/authorities/sh95000541#concept" id="link-id1669fa40">URIBurner Service</a> (while following designated predicates such as owl:sameAs in case they point to other mesh-able data sources)</li> <li>Query the data in Quad Store with "owl:sameAs" inference rules enabled</li> <li>Repeat the last step with the inference rules excluded.</li> </ol> <h4>Actual <a href="http://dbpedia.org/resource/SPARQL" id="link-id17374110">SPARQL</a> Queries:</h4> <ul> <li> <a href="http://demo.openlinksw.com/DAV/home/demo/Public/Queries/DataWeb/lcsh_www_subject_heading.isparql" id="link-id16c986d0">SPARQL Query against the HTTP based Subject Heading URI for WWW</a> </li> <li> <a href="http://demo.openlinksw.com/DAV/home/demo/Public/Queries/DataWeb/lcsh_www_subject_heading_sameAs_inference_on.isparql" id="link-id16d4fea0">SPARQL Query (with reasoning via inference rule for owl:sameAs)</a> against the URN based Subject Heading URI for WWW</li> <li> <a href="http://demo.openlinksw.com/DAV/home/demo/Public/Queries/DataWeb/lcsh_www_subject_heading_no_sameAs_inference_on.isparql" id="link-id11bad768">SPARQL Query (*without* reasoning via inference rule for owl:sameAs)</a> against the URN based Subject Heading URI for WWW</li> </ul> <h4>Observations:</h4> <p> The <a href="http://dbpedia.org/resource/SPARQL" id="link-ide6acf68">SPARQL</a> queries against the Graph generated and automatically populated by the Sponger reveal -- without human intervention-- that: "info:lc/authorities/sh95000541", is just an alternative name for < xmlns="http" id.loc.gov="id.loc.gov" authorities="authorities" sh95000541="sh95000541" concept="concept">, and that the graph produced by LCSH is self-describing enough for an OWL reasoner to figure this all out courtesy of the <a href="http://linkeddata.uriburner.com/about/html/http://www.w3.org/2002/07/owl%23sameAs" id="link-id13e364b0">owl:sameAs</a> property :-).</p> <p>Hopefully, this post also provides a simple example of how <a href="http://dbpedia.org/resource/Web_Ontology_Language" id="link-id158a3fe8">OWL</a> facilitates "Reasonable Linked Data". </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/1455" id="link-id164e19f8">State of the Linked Data Web</a> </li> <li> <a href="http://www.mkbergman.com/?p=474" id="link-id11973d10">Making Linked Data Reasonable Using Description Logics Series</a> - post by <a href="http://community.linkeddata.org/dataspace/person/mkbergman#this" id="link-id1184bfb8">Mike Bergman</a> </li> </ul>
Library of Congress & Reasonable Linked Data
2009-05-06T18:26:15Z
2009-05-06T14:26:15.000034-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/1429
<p>Here are a few descriptions of pages covering Google's Chrome browser:</p> <ul> <li> <a href="http://demo.openlinksw.com/proxy/html/http://vanirsystems.com/danielsblog/2008/09/03/google-chrome-my-verdict/" id="link-id14b2ad20">Daniel Lewis</a> - Comparative Analysis</li> <li> <a href="http://demo.openlinksw.com/proxy/html/http://demo.openlinksw.com/proxy/rdf/http://www.crunchbase.com/product/chrome%23this" id="link-id120f35d0">CrunchBase</a> - Product Page</li> <li> <a href="http://demo.openlinksw.com/proxy/html/http://feeds.feedburner.com/~r/OmMalik/~3/381659273/" id="link-id13e28090">GigaOM</a> - Industry Analysis</li> <li> <a href="http://demo.openlinksw.com/proxy/html/http://en.wikipedia.org/wiki/Google_Chrome" id="link-id10db3e48">Wikipedia</a> </li> <li> <a href="http://demo.openlinksw.com/proxy/html/http://news.cnet.com/8301-13860_3-10031661-56.html?part=rss&subj=news&tag=2547-1_3-0-20" id="link-id14a17f78">CNET</a> - Privacy Issues Analysis</li> <li> <a href="http://demo.openlinksw.com/proxy/html/http://feedproxy.google.com/~r/readwriteweb/~3/vF9P80B90XI/security_flaw_in_google_chrome.php" id="link-id14bdf6a8">ReadWriteWeb</a> - Security Issues Analysis</li> <li> <a href="http://demo.openlinksw.com/proxy/html/http://oakleafblog.blogspot.com/2008/09/chromes-evil-terms-of-service.html" id="link-id140af0a8">OakLeaf</a> - SaaS Terms Analysis</li> </ul> <p>As per usual, this is part post and part <a href="http://dbpedia.org/resource/Linked_Data" id="link-id140af0a8">Linked Data</a> demo. This time around, I am showcasing Proxy/Wrapper based dereferencable URIs and a new "Page Description" feature that showcases the capabilities of <a href="http://virtuoso.openlinksw.com" id="link-id11291898">Virtuoso</a>'s in-built RDFization Middleware. Also note, the resource descriptions (RDF) are presented using an HTML page.</p>
What's Up with Chrome?
2008-09-04T12:39:02Z
2008-09-04T08:39:02.000014-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/1424
<p>After reading <a href="http://blog.crunchbase.com/2008/08/26/building-a-semantic-web-interview-with-benjamin-nowack/" id="link-id16b8e0e0">Bengee's interview with CrunchBase</a>, I decided to knock up a quick interview remix as part of my usual attempt to add to the developing discourse.</p> <blockquote> <cite><a href="http://www.crunchbase.com/" id="link-id17c8e7b8">CrunchBase</a>: When we released the <a href="http://www.crunchbase.com/help/api" id="link-id16681f68">CrunchBase API</a>, you were one of the first developers to step up and quickly released a <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com's%20BLOG%20%5B127%5D/1395" id="link-id1016d5f0">CrunchBase Sponger Cartridge</a>. Can you explain what a CrunchBase Sponger Cartridge is?</cite> </blockquote> <blockquote> <a href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-id13243300">Me</a>: A Sponger Cartridge is a <a href="http://dbpedia.org/resource/Data">data</a> access driver for <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> Resources that plugs into our <a href="http://virtuoso.openlinksw.com" id="link-id17042f08">Virtuoso</a> <a href="http://dbpedia.org/resource/Virtuoso_Universal_Server" id="link-id1399b588">Universal Server</a> (DBMS and <a href="http://dbpedia.org/resource/Linked_Data" id="link-id137fd188">Linked Data</a> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id100b23d8">Web</a> Server combo amongst other things). It uses the internal structure of a resource and/or a web service associated with a resource, to materialize an RDF based <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id10418750">Linked Data graph</a> that essentially describes the resource via its properties (Attributes & Relationships). </blockquote> <br /> <img src="http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/images/ldp4.png" /> <br /> <br /> <br /> <blockquote> <cite>CrunchBase: And what inspired you to create it?</cite> </blockquote> <blockquote> <a href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-id12fa60c0">Me</a>: Bengee built a new space with your data, and we've built a space on the fly from your data which still resides in your domain. Either solution extols the virtues of <a href="http://dbpedia.org/resource/Linked_Data" id="link-id101a8d28">Linked Data</a> i.e. the ability to explore relationships across data items with high degrees of serendipity (also colloquially known as: following-your-nose pattern in <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id14a3ff30">Semantic Web</a> circles).</blockquote> <blockquote> <a href="http://cb.semsol.org/" id="link-id182a0170">Bengee</a> posted a notice to the <a href="http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/LinkingOpenData" id="link-id131e8d10">Linking Open Data Community</a>'s public <a href="http://lists.w3.org/Archives/Public/public-lod/2008Jul/0110.html" id="link-id11dd0720">mailing list announcing his effort</a>. Bearing in mind the fact that we've been using <a href="http://www.openlinksw.com/blog/~kidehen/?id=1144" id="link-id117cf6e8">middleware to mesh the realms of Web 2.0 and the Linked Data Web</a> for a while, it was a no-brainer to knock something up based on the conceptual similarities between <a href="http://wikicompany.org/wiki/Main_Page" id="link-id13b87a68">Wikicompany</a> and CrunchBase. In a sense, a quadrant of orthogonality is what immediately came to mind re. Wikicompany, CrunchBase, Bengee's RDFization efforts, and ours.</blockquote> <blockquote>Bengee created an RDF based <a href="http://dbpedia.org/resource/Linked_Data" id="link-id133c8fc8">Linked Data</a> warehouse based on the data exposed by your API, which is exposed via the <a href="http://cb.semsol.org/" id="link-id1826f928">Semantic CrunchBase</a> <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id102d8890">data space</a>. In our case we've taken the "RDFization on the fly" approach which produces a transient <a href="http://dbpedia.org/resource/Linked_Data" id="link-id16a0b8d0">Linked Data</a> View of the CrunchBase data exposed by your APIs. Our approach is in line with our world view: all resources on the Web are data sources, and the <a href="http://dbpedia.org/resource/Linked_Data" id="link-id1668e6c8">Linked Data</a> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id188e7da0">Web</a> is about incorporating HTTP into the naming scheme of these data sources so that the conventional <a href="http://dbpedia.org/resource/Uniform_Resource_Locator" id="link-id13490710">URL</a> based hyperlinking mechanism can be used to access a structured description of a resource, which is then transmitted using a range negotiable representation formats. In addition, based on the fact that we house and publish a lot of <a href="http://dbpedia.org/resource/Linked_Data" id="link-id169aa568">Linked Data</a> on the Web (e.g. <a href="http://dbpedia.org/resource/DBpedia" id="link-id10af10e8">DBpedia</a>, <a href="http://www.pingthesemanticweb.com/about/" id="link-id10a2b710">PingTheSemanticWeb</a>, and others), we've also automatically meshed Crunchbase data with related data in <a href="http://dbpedia.org/resource/DBpedia" id="link-id1403cd40">DBpedia</a> and Wikicompany data.</blockquote> <br /> <blockquote> <cite>CrunchBase: Do you know of any apps that are using CrunchBase Cartridge to enhance their functionality?</cite> </blockquote> <blockquote> <a href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-id177d24c8">Me</a>: Yes, the <a href="http://ode.openlinksw.com" id="link-id10725ca0">OpenLink Data Explorer</a> which provides CrunchBase site visitors with the option to explore the <a href="http://dbpedia.org/resource/Linked_Data" id="link-id17dedea8">Linked Data</a> in the CrunchBase <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id13f02a00">data space</a>. It also allows them to "Mesh" (rather than "Mash") CrunchBase data with other <a href="http://dbpedia.org/resource/Linked_Data" id="link-id11fb3ba0">Linked Data</a> sources on the Web without writing a single line of code. </blockquote> <br /> <blockquote> <cite>CrunchBase: You have been immersed in the <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id12e18a00">Semantic Web</a> movement for a while now. How did you first get interested in the <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id15132110">Semantic Web</a>?</cite> </blockquote> <blockquote> <a href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-id0xddaa9c8">Me</a>: We saw the <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id188b3330">Semantic Web</a> as a vehicle for standardizing conceptual views of heterogeneous data sources via <a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id10350978">context</a> lenses (URIs). In 1998 as part of our strategy to expand our business beyond the development and deployment of <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id171d6798">ODBC</a>, <a href="http://dbpedia.org/resource/Java_Database_Connectivity" id="link-id138120a0">JDBC</a>, and OLE-DB data providers, we decided to build a <a href="http://dbpedia.org/resource/Virtual_Database" id="link-id13ea6618">Virtual Database</a> Engine (see: <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VOSHistory" id="link-id11a4fa30">Virtuoso History</a>), and in doing so we sought a standards based mechanism for the conceptual output of the <a href="http://dbpedia.org/resource/Federated_database_system" id="link-id101a1248">data virtualization</a> effort. As of the time of the <a href="http://www.w3.org/DesignIssues/Semantic.html" id="link-id18882cf8">seminal unveiling of the Semantic Web in 1998</a> we were clear about two things, in relation to the effects of the Web and <a href="http://dbpedia.org/resource/Internet" id="link-id12fa2c58">Internet</a> data management infrastructure inflections: 1) Existing DBMS technology had reached it limits 2) Web Servers would ultimately hit their functional limits. These fundamental realities compelled us to develop <a href="http://virtuoso.openlinksw.com" id="link-id102b09a0">Virtuoso</a> with an eye to leveraging the <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id11984d98">Semantic Web</a> as a vehicle from completing its technical roadmap.</blockquote> <br /> <blockquote> <cite>CrunchBase: Can you put into layman’s terms exactly what RDF and <a href="http://dbpedia.org/resource/SPARQL" id="link-id1066dcf0">SPARQL</a> are and why they are important? Do they only matter for developers or will they extend past developers at some point and be used by website visitors as well?</cite> </blockquote> <blockquote>Me: RDF (Resource Description Framework) is a Graph based Data Model that facilitates resource description using the <a href="http://www.eslincanada.com/englishlesson2.html" id="link-id178b94a8">Subject, Predicate, and Object principle</a>. Associated with the core data model, as part of the overall framework, are a number of markup languages for expressing your descriptions (just as you express presentation markup semantics in HTML or document structure semantics in XML) that include: <a href="http://dbpedia.org/resource/RDFa" id="link-id188db0a8">RDFa</a> (simple extension of HTML markup for embedding descriptions of things in a page), N3 (a human friendly markup for describing resources), RDF/XML (a machine friendly markup for describing resources).</blockquote> <blockquote> <a href="http://dbpedia.org/resource/SPARQL" id="link-id188c2030">SPARQL</a> is the query language associated with the RDF Data Model, just as <a href="http://dbpedia.org/resource/SQL" id="link-id13f0ffe0">SQL</a> is a query language associated with the Relational Database Model. Thus, when you have RDF based structured and <a href="http://dbpedia.org/resource/Linked_Data" id="link-id166874d0">linked data</a> on the Web, you can query against Web using <a href="http://dbpedia.org/resource/SPARQL" id="link-id1016cc98">SPARQL</a> just as you would against an <a href="http://dbpedia.org/resource/Oracle_Database" id="link-id101c9708">Oracle</a>/<a href="http://dbpedia.org/resource/SQL" id="link-id11cb0b18">SQL</a> Server/<a href="http://dbpedia.org/resource/IBM_DB2" id="link-id10760ec0">DB2</a>/<a href="http://dbpedia.org/resource/IBM_Informix" id="link-id1066c8c0">Informix</a>/<a href="http://dbpedia.org/resource/Ingres" id="link-id18894f40">Ingres</a>/<a href="http://dbpedia.org/resource/MySQL" id="link-iddc9ebb0">MySQL</a>/etc.. DBMS using <a href="http://dbpedia.org/resource/SQL" id="link-id1030d120">SQL</a>. That's it in a nutshell.</blockquote> <br /> <blockquote> <cite>CrunchBase: On your website you wrote that “RDF and <a href="http://dbpedia.org/resource/SPARQL" id="link-id168e9ad0">SPARQL</a> as productivity boosters in everyday web development”. Can you elaborate on why you believe that to be true?</cite> </blockquote> <blockquote>Me: I think the ability to discern a formal description of anything via its discrete properties is of immense value re. productivity, especially when the capability in question results in a graph of <a href="http://dbpedia.org/resource/Linked_Data" id="link-id0x179f6328">Linked Data</a> that isn't confined to a specific host operating system, database engine, application or service, programming language, or development framework. RDF <a href="http://dbpedia.org/resource/Linked_Data">Linked Data</a> is about infrastructure for the true materialization of the "<a href="http://dbpedia.org/resource/Information" id="link-id13e475b8">Information</a> at Your Fingertips" vision of yore. Even though it's taken the emergence of RDF Linked Data to make the aforementioned vision tractable, the comprehension of the vision's intrinsic value have been clear for a very long time. Most organizations and/or individuals are quite familiar with the adage: <a href="http://dbpedia.org/resource/Knowledge" id="link-id13e38a30">Knowledge</a> is Power, well there isn't any <a href="http://dbpedia.org/resource/Knowledge" id="link-id188b7348">knowledge</a> without accessible <a href="http://dbpedia.org/resource/Information" id="link-id140415d0">Information</a>, and there isn't any accessible <a href="http://dbpedia.org/resource/Information" id="link-id11a976e8">Information</a> without accessible Data. The Web has always be grounded in accessibility to data (albeit via compound container documents called Web Pages).</blockquote> <blockquote>Bottom line, RDF based Linked Data is about Open <a href="http://dbpedia.org/resource/Reference_(computer_science)" id="link-id1206bfb8">Data access by reference</a> using URIs (HTTP based <a href="http://dbpedia.org/resource/Entity" id="link-idfaa6ce0">Entity</a> IDs / Data Object IDs / Data Source Names), and as I said earlier, the intrinsic value is pretty obvious bearing in mind the costs associated with integrating disparate and heterogeneous data sources -- across intranets, extranets, and the <a href="http://dbpedia.org/resource/Internet" id="link-id188ecc68">Internet</a>.</blockquote> <br /> <blockquote> <cite>CrunchBase: In his definition of Web 3.0, Nova Spivack proposes that the <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id12e2d968">Semantic Web</a>, or Semanti<a href="http://dbpedia.org/resource/C_(programming_language)" id="link-id105744c0">c</a> Web technologies, will be force behind much of the innovation that will occur during Web 3.0. Do you agree with Nova Spivack? What role, if any, do you feel the <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id13fa4218">Semantic Web</a> will play in Web 3.0?</cite> </blockquote> <blockquote>Me: I agree with Nova. But I see Web 3.0 as a phase within the <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id188c9000">Semantic Web</a> innovation continuum. Web 3.0 exists because Web 2.0 exists. Both of these Web versions express usage and technology focus patterns. Web 2.0 is about the use of Open Source technologies to fashion Web Services that are ultimately used to drive proprietary Software as Service (SaaS) style solutions. Web 3.0 is about the use of "Smart Data Access" to fashion a new generation of Linked Data aware Web Services and solutions that exploit the federated nature of the Web to maximum effect; proprietary branding will simply be conveyed via quality of data (cleanliness, <a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id188d2ef8">context</a> fidelity, and comprehension of privacy) exposed by URIs.</blockquote> <p>Here are some examples of the CrunchBase Linked Data <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id122756f8">Space</a>, as projected via our CruncBase Sponger Cartridge:</p> <ol> <li> <a href="http://demo.openlinksw.com/rdfbrowser2/?uri=http%3A%2F%2Fwww.crunchbase.com%2Fcompany%2Famazon" id="link-id13e0fd18">Amazon.com</a> </li> <li> <a href="http://demo.openlinksw.com/rdfbrowser2/?uri=http%3A%2F%2Fwww.crunchbase.com%2Fcompany%2Fmicrosoft" id="link-id13eef9e0">Microsoft</a> </li> <li> <a href="http://demo.openlinksw.com/rdfbrowser2/?uri=http%3A%2F%2Fwww.crunchbase.com%2Fcompany%2Fgoogle" id="link-id13fe47a0">Google</a> </li> <li> <a href="http://demo.openlinksw.com/rdfbrowser2/?uri=http%3A%2F%2Fwww.crunchbase.com%2Fcompany%2Fapple" id="link-id170c73b8">Apple</a> </li> </ol>
Crunchbase & Semantic Web Interview (Remix - Update 1)
2008-08-28T00:35:15Z
2008-08-27T20:35: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/1408
<p>At OpenLink, we've been investigating <a href="http://code.google.com/p/linqtordf/" id="link-id1296eb18">LinqToRdf</a>, an exciting project from <a href="http://aabs.wordpress.com/" id="link-id13e860a8">Andrew Matthews</a> that seeks to expose the <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id105d84f8">Semantic Web</a> technology space to the large community of .NET developers. </p> <p>The LinqToRdf project is about binding LINQ to RDF. It sits atop <a href="http://razor.occams.info/" id="link-id102e3b10">Joshua Tauberer</a>'s <a href="http://dbpedia.org/resource/C_(programming_language)" id="link-id1471b0d0">C</a># based <a href="http://razor.occams.info/code/semweb/" id="link-id14cb9030">Semantic Web/RDF library</a> which has been out there for a while and works across Microsoft .NET and it's open source variant "Mono".</p> <p>Historically, the <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id13ee9f40">Semantic Web</a> realm has been dominated by RDF frameworks such as <a href="http://www.openrdf.org/" id="link-id109f8a68">Sesame</a>, <a href="http://jena.sourceforge.net/" id="link-id144c3210">Jena</a> and <a href="http://librdf.org/" id="link-id10600228">Redland</a>; which by their Open Source orientation, predominantly favor non-Windows platforms (Java and Linux). Conversely, Microsoft's .NET frameworks have sought to offer Conceptualization technology for heterogeneous Logical <a href="http://dbpedia.org/resource/Data">Data</a> Sources via .NET's <a href="http://en.wikipedia.org/wiki/ADO.NET_Entity_Framework" id="link-id10726628">Entity Frameworks</a> and <a href="http://dbpedia.org/resource/ADO.NET" id="link-id13e7edd8">ADO.NET</a>, but without any actual bindings to RDF. </p> <p>Interestingly, believe it or not, .NET already has a data query language that shares a number of similarities with <a href="http://dbpedia.org/resource/SPARQL" id="link-id1042f480">SPARQL</a>, called <a href="http://dbpedia.org/resource/Entity" id="link-id105a46b0">Entity</a>-<a href="http://dbpedia.org/resource/SQL" id="link-id1041d2e8">SQL</a>, and a very innovative programming language called LINQ; that offers a blend of constructs for natural data access and manipulation across relational (<a href="http://dbpedia.org/resource/SQL" id="link-id139f5848">SQL</a>), hierarchical (XML), and graph (Object) models without the traditional object language->database impedance tensions of the past.</p> <p>With regards to all of the above, we've just released a mini white paper that covers the exploitation of <a href="http://virtuoso.openlinksw.com/Whitepapers/html/linqtordf/linqtordf1.htm" id="link-id14b2f138">RDF-based Linked Data using .NET via LINQ</a>. The paper offers a an overview of LinqToRdf, plus enhancements we've contributed to the project (available in <a href="http://aabs.wordpress.com/2008/08/01/announcing-linqtordf-v08/" id="link-id101defa8">LinqToRdf v0.8</a>.). The paper includes real-world examples that tap into a MusicBrainz powered <a href="http://dbpedia.org/resource/Linked_Data" id="link-id101ffd18">Linked Data</a> <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id105cb858">Space</a>, the Music Ontology, the <a href="http://virtuoso.openlinksw.com" id="link-id13f55860">Virtuoso</a> RDF Quad Store, <a href="http://virtuoso.openlinksw.com" id="link-id12826718">Virtuoso</a> <a href="http://virtuoso.openlinksw.com/Whitepapers/html/VirtSpongerWhitePaper.html" id="link-id1030cb60">Sponger</a> Middleware, and our RDfization Cartridges for Musicbrainz. </p> Enjoy!
.NET, LINQ, and RDF based Linked Data (Update 2)
2008-08-08T12:54:01Z
2008-08-08T08:54:01.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/1363
<p>Unfortunately, I could only spend 4 days at the recent <a href="http://www2008.org/" id="link-id196acf60">WWW2008</a> event in <a href="http://dbpedia.org/resource/Beijing" id="link-id1974fe28">Beijing</a> (I departed the morning following the <a href="http://events.linkeddata.org/ldow2008/" id="link-id1863f858">Linked Data Workshop</a>), so I couldn't take my slot on the "Commercializing the <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id18990f90">Semantic Web</a> panel" etc.. Anyway, thanks to the <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id0x18f29310">Web</a> I can still inject my points of view in the broad <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> based discourse. Well so I hoped, when I attempted to post a comment to Paul Miller's ZDNet domain hosted <a href="http://dbpedia.org/resource/Blog" id="link-id180d6750">blog</a> thread titled: <a href="http://blogs.zdnet.com/semantic-web/?p=132" id="link-id12d206c0">Commercialising the Semantic Web</a>.</p> <p>Unfortunately, the cost of completing ZDNet's unwieldy signup process simply exceeded the benefits of dropping my comments in their particular space :-( Thus, I'll settle for a trackback ping instead.</p> <p>What follows is the cut and paste of my intended comment contributions to Paul's post.</p> <p>Paul,</p> <p> As discussed earlier this week during <a href="http://blogs.talis.com/nodalities/2008/05/kingsley-idehen-talks-about-openlink-software-linked-data-and-the-semantic-web.php" id="link-id1332fb48">our podcast session</a>, commercialization of <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id17382338">Semantic Web</a> technology shouldn't be a mercurial matter at this stage in the game :-) It's all about looking at how it provides value :-)</p> <p>From the <a href="http://dbpedia.org/resource/Linked_Data" id="link-id10d4f4a8">Linked Data</a> angle, the ability to produce, dispatch, and exploit "<a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id13bed160">Context</a>" across an array of "Perspectives" from a plethora of disparate <a href="http://dbpedia.org/resource/Data" id="link-id1731e5f0">data</a> sources on the Web and/or behind corporate firewalls, offers immense commercial value.</p> <p> <a href="http://developer.yahoo.com/searchmonkey/" id="link-id1975d248">Yahoo's Searchmonkey</a> effort will certainly bring clarity to some of the points I made during the podcast re. the role of URIs as "value consumption tickets" (<a href="http://dbpedia.org/resource/Data" id="link-id173eb7b0">Data</a> Services are exposed via URIs). There has to be a trigger (in user space) that compels Web users to seek broader, or simply varied, perspectives as a response to <a href="http://dbpedia.org/resource/Data" id="link-id0x1c7e7f60">data</a> encountered on the Web. Yahoo! is about to put this light on in a big way (imho).</p> <p>The "self annotating" nature of the Web is what ultimately drives the manifestation of the long awaited <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id0xa18a83e8">Semantic Web</a>. I believe I postulated about <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=self%20annotation&type=text&output=html" id="link-id173d7458">"Self Annotation & the Semantic Web" in a number of prior posts</a> which, by the way, should be <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&type=text&kwds=self%20annotation&OpenSearch" id="link-id10b12208">DataRSS compatible right now</a> due to Yahoo's support of OpenSearch <a href="http://dbpedia.org/resource/Data" id="link-id0x1b8412e8">Data</a> Providers (which this <a href="http://dbpedia.org/resource/Blog" id="link-id170b8df8">Blog</a> Space has been for eons).</p> <p>Today, have many communities adding strucuture to the Web (via their respective tools of preference) without explicitly realizing what they are contributing. Every RSS/Atom feed, <a href="http://dbpedia.org/resource/Tag" id="link-id183d5178">Tag</a>, Weblog, Shared Bookmark, <a href="http://dbpedia.org/resource/WikiWord" id="link-id10c5e758">Wikiword</a>, Microformat, Microformat++ (<a href="http://dbpedia.org/resource/Embedded_RDF" id="link-id16d8ee40">eRDF</a> or <a href="http://dbpedia.org/resource/RDFa" id="link-id1059a688">RDFa</a>), <a href="http://dbpedia.org/resource/GRDDL" id="link-id1090ae10">GRDDL</a> stylesheet, and RDFizer etc.. is a piece of structured <a href="http://dbpedia.org/resource/Data">data</a>.</p> <p>Finally, the different communities are all finding ways to work together (thank heavens!) and the results are going to be cataclysmic when it all plays out :-)</p> <p>Data, Structure, and Extraction are the keys to the Semantic Life! First you get the Data in a container (<a href="http://dbpedia.org/resource/Information" id="link-id180e5648">information</a> resource), and then you add Structure to the <a href="http://dbpedia.org/resource/Information" id="link-id103801e0">information</a> resource (RSS, Atom, <a href="http://dbpedia.org/resource/Microformats" id="link-id17825e40">microformats</a>, <a href="http://dbpedia.org/resource/RDFa" id="link-id189a8738">RDFa</a>, <a href="http://dbpedia.org/resource/Embedded_RDF" id="link-id1933d5c0">eRDF</a>, SIOC, FOAF, etc.), once you have Structure RDFization (i.e. transformation to <a href="http://dbpedia.org/resource/Linked_Data" id="link-id19744878">Linked Data</a>) is a synch thanks to <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id180dde30">RDF</a> Middleware (as per <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&type=text&kwds=self%20annotation&OpenSearch" id="link-id16dc3130">earlier RDF middleware posts</a>).</p>
Commercializing the Semantic Web
2008-05-18T14:58:26Z
2008-05-18T10:58:26.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/1362
<p>Unfortunately, I could only spend 4 days at the recent <a href="http://www2008.org/" id="link-id196acf60">WWW2008</a> event in <a href="http://dbpedia.org/resource/Beijing" id="link-id1974fe28">Beijing</a> (I departed the morning following the <a href="http://events.linkeddata.org/ldow2008/" id="link-id1863f858">Linked Data Workshop</a>), so I couldn't take my slot on the "Commercializing the <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id18990f90">Semantic Web</a> panel" etc.. Anyway, thanks to the <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> I can still inject my points of view in the broad Web based discourse. Well so I hoped, when I attempted to post a comment to Paul Miller's ZDNet domain hosted <a href="http://dbpedia.org/resource/Blog" id="link-id180d6750">blog</a> thread titled: <a href="http://blogs.zdnet.com/semantic-web/?p=132" id="link-id12d206c0">Commercialising the Semantic Web</a>.</p> <p>Unfortunately, the cost of completing ZDNet's unwieldy signup process simply exceeded the benefits of dropping my comments in their particular space :-( Thus, I'll settle for a trackback ping instead.</p> <p>What follows is the cut and paste of my intended comment contributions to Paul's post.</p> <p>Paul,</p> <p> As discussed earlier this week during <a href="http://blogs.talis.com/nodalities/2008/05/kingsley-idehen-talks-about-openlink-software-linked-data-and-the-semantic-web.php" id="link-id1332fb48">our podcast session</a>, commercialization of <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id17382338">Semantic Web</a> technology shouldn't be a mercurial matter at this stage in the game :-) It's all about looking at how it provides value :-)</p> <p>From the <a href="http://dbpedia.org/resource/Linked_Data" id="link-id10d4f4a8">Linked Data</a> angle, the ability to produce, dispatch, and exploit "<a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id13bed160">Context</a>" across an array of "Perspectives" from a plethora of disparate <a href="http://dbpedia.org/resource/Data" id="link-id1731e5f0">data</a> sources on the Web and/or behind corporate firewalls, offers immense commercial value.</p> <p> <a href="http://developer.yahoo.com/searchmonkey/" id="link-id1975d248">Yahoo's Searchmonkey</a> effort will certainly bring clarity to some of the points I made during the podcast re. the role of URIs as "value consumption tickets" (<a href="http://dbpedia.org/resource/Data" id="link-id173eb7b0">Data</a> Services are exposed via URIs). There has to be a trigger (in user space) that compels Web users to seek broader, or simply varied, perspectives as a response to <a href="http://dbpedia.org/resource/Data" id="link-id0x1c7e7f60">data</a> encountered on the Web. Yahoo! is about to put this light on in a big way (imho).</p> <p>The "self annotating" nature of the Web is what ultimately drives the manifestation of the long awaited <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id0xa18a83e8">Semantic Web</a>. I believe I postulated about <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=self%20annotation&type=text&output=html" id="link-id173d7458">"Self Annotation & the Semantic Web" in a number of prior posts</a> which, by the way, should be <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&type=text&kwds=self%20annotation&OpenSearch" id="link-id10b12208">DataRSS compatible right now</a> due to Yahoo's support of OpenSearch <a href="http://dbpedia.org/resource/Data">Data</a> Providers (which this <a href="http://dbpedia.org/resource/Blog" id="link-id170b8df8">Blog</a> Space has been for eons).</p> <p>Today, have many communities adding strucuture to the Web (via their respective tools of preference) without explicitly realizing what they are contributing. Every RSS/Atom feed, <a href="http://dbpedia.org/resource/Tag" id="link-id183d5178">Tag</a>, Weblog, Shared Bookmark, <a href="http://dbpedia.org/resource/WikiWord" id="link-id10c5e758">Wikiword</a>, Microformat, Microformat++ (<a href="http://dbpedia.org/resource/Embedded_RDF" id="link-id16d8ee40">eRDF</a> or <a href="http://dbpedia.org/resource/RDFa" id="link-id1059a688">RDFa</a>), <a href="http://dbpedia.org/resource/GRDDL" id="link-id1090ae10">GRDDL</a> stylesheet, and RDFizer etc.. is a piece of structured data.</p> <p>Finally, the different communities are all finding ways to work together (thank heavens!) and the results are going to be cataclysmic when it all plays out :-)</p> <p>Data, Structure, and Extraction are the keys to the Semantic Life! First you get the Data in a container (<a href="http://dbpedia.org/resource/Information" id="link-id180e5648">information</a> resource), and then you add Structure to the <a href="http://dbpedia.org/resource/Information" id="link-id103801e0">information</a> resource (RSS, Atom, <a href="http://dbpedia.org/resource/Microformats" id="link-id17825e40">microformats</a>, <a href="http://dbpedia.org/resource/RDFa" id="link-id189a8738">RDFa</a>, <a href="http://dbpedia.org/resource/Embedded_RDF" id="link-id1933d5c0">eRDF</a>, SIOC, FOAF, etc.), once you have Structure RDFization (i.e. transformation to <a href="http://dbpedia.org/resource/Linked_Data" id="link-id19744878">Linked Data</a>) is a synch thanks to <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id180dde30">RDF</a> Middleware (as per <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&type=text&kwds=self%20annotation&OpenSearch" id="link-id16dc3130">earlier RDF middleware posts</a>).</p>
Commercializing the Semantic Web
2008-05-16T20:15:29Z
2008-05-16T16:15:29.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/1333
<p> <a href="http://dbpedia.org/resource/WordPress" id="link-id101103b0">Wordpress</a> is a Weblog platform comprised of the following: </p> <ol> <li>User Interface - <a href="http://dbpedia.org/resource/PHP" id="link-id107ba368">PHP</a> </li> <li>Application Logic - <a href="http://dbpedia.org/resource/PHP" id="link-id107066b8">PHP</a> </li> <li> <a href="http://dbpedia.org/resource/Data" id="link-id13968340">Data</a> Storage (<a href="http://dbpedia.org/resource/SQL" id="link-id104c5350">SQL</a> <a href="http://dbpedia.org/resource/Relational_database_management_system" id="link-id1076d790">RDBMS</a>) - <a href="http://dbpedia.org/resource/MySQL" id="link-id109c4ea0">MySQL</a> via <a href="http://dbpedia.org/resource/PHP" id="link-id133af570">PHP</a>-<a href="http://dbpedia.org/resource/MySQL" id="link-idf0b03b0">MySQL</a> </li> <li> <a href="http://dbpedia.org/resource/Application_server" id="link-id13217630">Application Server</a> - <a href="http://dbpedia.org/resource/Apache" id="link-id108219d8">Apache</a> </li> </ol> <p>In the form above (the norm), <a href="http://dbpedia.org/resource/WordPress" id="link-id105c6d88">Wordpress</a> <a href="http://dbpedia.org/resource/Data" id="link-id104938f8">data</a> can be injected into the <a href="http://dbpedia.org/resource/Linked_Data" id="link-id107a5f18">Linked Data</a> <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id177329c0">Web</a> via RDFization middleware such as the<a href="http://virtuoso.openlinksw.com/Whitepapers/html/VirtSpongerWhitePaper.html" id="link-id10531b50">Virtuoso Sponger</a> (built into all <a href="http://virtuoso.openlinksw.com" id="link-id10d7e710">Virtuoso</a> instances) and <a href="http://triplr.org/" id="link-id107dcab8">Triplr</a>. The downside of this approach is that the <a href="http://dbpedia.org/resource/Blog" id="link-id1055ab68">blog</a> owner doesn't necessary possess full control over their contributions to the emerging <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-idfed0358">Giant Global Graph</a> or <a href="http://dbpedia.org/resource/Linked_Data" id="link-id10d70668">Linked Data</a>.</p> <p>Another route to <a href="http://dbpedia.org/resource/Linked_Data" id="link-id104c7f68">Linked Data</a> exposure is via <a href="http://virtuoso.openlinksw.com" id="link-id0xa255fb50">Virtuoso</a>'s Metaschema Language for producing <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id10968388">RDF</a> Views over <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id13f594c8">ODBC</a>/<a href="http://dbpedia.org/resource/Java_Database_Connectivity" id="link-id138f69a8">JDBC</a> accessible <a href="http://dbpedia.org/resource/Data" id="link-id1393c068">Data</a> Sources, that enables the following setup:</p> <ol> <li>User Interface - <a href="http://dbpedia.org/resource/PHP" id="link-id0x9fb9c478">PHP</a> </li> <li>Application Logic - PHP </li> <li> <a href="http://dbpedia.org/resource/Data" id="link-id0xc605960">Data</a> Storage (<a href="http://dbpedia.org/resource/SQL" id="link-id0xc2be608">SQL</a> <a href="http://dbpedia.org/resource/Relational_database_management_system" id="link-id0xc7a28a8">RDBMS</a>) - <a href="http://dbpedia.org/resource/MySQL" id="link-id0xc7228f0">MySQL</a> via the PHP-MySQL <a href="http://dbpedia.org/resource/Data">data</a> access interface </li> <li> <a href="http://dbpedia.org/resource/Virtual_Database" id="link-id134b1ee8">Virtual Database</a> linkage of MySQL Tables into Virtuoso </li> <li> <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-idfe31548">RDF</a> View generated over the Virtual SQL Tables </li> <li> <a href="http://dbpedia.org/resource/Application_server" id="link-id0xb8dfa68">Application Server</a> - Virtuoso which provides <a href="http://dbpedia.org/resource/Linked_Data" id="link-id0xc149518">Linked Data</a> Deployment such that <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id10ad9ca0">RDF</a> <a href="http://dbpedia.org/resource/Linked_Data">Linked Data</a> is exposed when requested by <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-idfd352e0">Web</a> User Agents.</li> </ol> <p>Alternatively, you can also exploit Virtuoso as the SQL DBMS, <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id0x9ec4f440">RDF</a> DBMS, Application Server, and Linked Data Deployment platform:</p> <ol> <li>User Interface - PHP </li> <li> Application Logic - PHP </li> <li>Data Storage (SQL RDBMS) - Virtuoso via PHP-<a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id14197218">ODBC</a> data access interface (* <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id103d1a80">ODBC</a> is Virtuoso's native SQL CLI/API *) </li> <li><a href="http://dbpedia.org/resource/Resource_Description_Framework">RDF</a> View generated over the Native SQL Tables </li> <li>Application Server - Virtuoso which provides Linked Data Deployment such that RDF Linked Data is exposed when requested by <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id13918d68">Web</a> User Agents (e.g. <a href="http://demo.openlinksw.com/rdfbrowser" id="link-idff835f0">OpenLink RDF Browser</a>, <a href="http://zitgist.com/about/" id="link-id1372e510">Zitgist</a> <a href="http://dataviewer.zitgist.com" id="link-id109c3048">Data Viewer</a>, <a href="http://www4.wiwiss.fu-berlin.de/rdf_browser" id="link-id105d97f0">DISCO Hyperdata Browser</a>, and <a href="http://dig.csail.mit.edu/2005/ajar/release/tabulator/0.8/tab.html" id="link-id10cc20d8">Tabulator</a>). </li> </ol> <h2 align="left">Benefits?</h2> <ul> <li>Each user account gets a proper Linked Data <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id108c92b0">URI</a> (ID) that can me meshed/smushed with other IDs (so you add data from this new <a href="http://dbpedia.org/resource/Blog" id="link-idfd39648">blog</a> space to other linked data sources associated with you other URIs/IDs) </li> <li>Each post gets a proper <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id10add540">URI</a> All data is now query-able via <a href="http://dbpedia.org/resource/SPARQL" id="link-id101b98f0">SPARQL</a> Discoverability increases exponentially (without drop in relevance in either direction i.e. discovering or being discovered)</li> </ul> <p>How Do I map the <a href="http://dbpedia.org/resource/WordPress" id="link-id12e448c0">WordPress</a> SQL Schema to RDF using Virtuoso? </p> <ul> <li>Determine the RDF Schema or Ontologies that define the Classes for which you will be producing instance data (e.g. SIOC and FOAF) </li> <li>Declare <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-idfaf5c80">URI</a>/IRI generator functions (*special Virtuoso functions*) </li> <li>Use <a href="http://dbpedia.org/resource/SPARQL" id="link-id100436b8">SPARQL</a> Graph patterns to apply <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id0x9de74950">URI</a>/IRI generator functions to Tables, Views, Table Values mode Stored Procedures, Query Resultsets as part of RDBMS to RDF mapping </li> </ul> <p> Read the <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VOSSQL2RDF" id="link-idfaf5d58">Meta Schema Language guide</a> or simply apply our "<a href="http://dbpedia.org/resource/WordPress" id="link-id0x9ef73c78">WordPress</a> SQL Schema to RDF" script to your Virtuoso hosted instance. Of course, there are other mappings that cover other PHP applications deployed via Virtuoso:</p> <ul> <li> <a href="http://dbpedia.org/resource/PhpBB" id="link-id179f4870">phpBB3</a> SQL Schema to RDF </li> <li> <a href="http://dbpedia.org/resource/Drupal" id="link-id10b263d8">Drupal</a> SQL Schema to RDF </li> <li> <a href="http://dbpedia.org/resource/MediaWiki" id="link-id10263a40">MediaWiki</a> SQL Schema to RDF </li> </ul> <h2>Live Demos?</h2> <ul> <li> <a href="http://demo.openlinksw.com/phpBB3" id="link-id17761e88">Virtuoso Hosting phpBB3</a> (<a href="http://demo.openlinksw.com/phpBB3/user/demo#this" id="link-id10087e68">example User URI</a>)</li> <li> <a href="http://demo.openlinksw.com/drupal" id="link-id1091f1d8">Virtuoso Hosting Drupal</a> (<a href="http://demo.openlinksw.com/drupal/user/demo#this" id="link-id13e3d468">example User URI</a>)</li> <li> <a href="http://demo.openlinksw.com/mediawiki" id="link-id10531be0">Virtuoso Hosting MediaWiki</a> (<a href="http://demo.openlinksw.com/mediawiki/user/KingsleyIdehen#this" id="link-id109c5d40">example User URI</a>)</li> </ul>
Adding Wordpress Blogs into the Linked Data Web using Virtuoso
2008-04-10T16:33:05Z
2008-04-10T12:33:05.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/1293
<p>In response to the <a href="http://www.readwriteweb.com" id="link-id0x1f562c28">ReadWriteWeb</a> piece titled: <a href="http://www.readwriteweb.com/archives/semantic_web_what_is_the_killer_app.php" id="link-id0x16961368">Semantic Web: What is the Killer App.</a> by <a href="http://www.readwriteweb.com/about_alex.php" id="link-id0x16909678">Alex Iskold</a>:</p> <p>Information overload and Data Portability are two of the most pressing and imminent challenges affecting every individual connected to the global village exposed by the Internet and World Wide Web. I wrote an earlier post titled: <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1267" id="link-idfeb7718">Why We Need Linked Data</a> that shed light on frequently overlooked realities about the Document Web.</p> <p>The real Killer application of the Semantic Web (imho) is <a href="http://dbpedia.org/resource/Linked_Data" id="link-id10571ef0">Linked Data</a> (or Hyperdata), just as the killer application of the <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id102be888">Document Web</a> was Linked Documents (Hyperlinks). Linked Data enables human users (indirectly) and software agents (directly in response to human instruction) to traverse Web Data Spaces (Linked Data enclaves within the <a href="http://en.wikipedia.org/wiki/Giant_Global_Graph" id="link-id10b6ba08">Giant Global Graph</a>).</p> <p>Semantic Web applications (conduits between humans and agents) that take advantage of Linked Data include:</p> <p> <a href="http://dbpedia.org/resource/DBpedia" id="link-id10fcc8f8">DBpedia</a> - General Knowledge sourced from <a href="http://dbpedia.org/resource/Wikipedia" id="link-id10570808">Wikipedia</a> and a host of other Linked Data Spaces.</p> <p>Various Linked Data Browsers: <a href="http://dataviewer.zitgist.com" id="link-id139a2300">Zitgist Data Viewer</a>, <a href="http://demo.openlinksw.com/rdfbrowser" id="link-id12fb46f0">OpenLink RDF Browser</a>, <a href="http://www4.wiwiss.fu-berlin.de/rdf_browser" id="link-idff652c0">DISCO Browser</a>, and TimBL's <a href="http://dig.csail.mit.edu/2005/ajar/ajaw/tab.html" id="link-idff63998">Tabulator</a>.</p> <p> <a href="http://zlinks.zitgist.com/" id="link-idff62b90">zLknks </a>- Linked Data Lookup technology for Web Content Publishing systems (note: more to come on this in a future post).</p> <p> <a href="http://en.wikipedia.org/wiki/OpenLink_Data_Spaces" id="link-id1054a708">OpenLink Data Spaces</a> - a solution for Data Portability via a Linked Data Junction Box for Web 1.0 ((X)HTML Document Webs), 2.0 (XML Web Services based Content Publishing, Content Syndication, and Aggregation), and 3.0 (Linked Data) Data Spaces. Thus, via my URI (when viewed through a Linked Data Browser/Viewer) you can traverse my Data Space (i.e my Linked Data Graph) generated by the following activities:</p> <ul>Blog Posts publishing</ul> <ul>My RSS & Atom Content Subscriptions (what used to be called a "Blogroll")</ul> <ul>My Bookmarks (from my Desktop and Del.icio.us)</ul> <ul>and other things I choose to share with the public via the Web</ul> <p> <a href="http://dbpedia.org/resource/Virtuoso_Universal_Server" id="link-idff89b08">Virtuoso</a> - a Universal Server Platform that includes <a href="http://virtuoso.openlinksw.com/wiki/main/Main/VOSRDF" id="link-id12ff8810">RDF Data Management</a>, <a href="http://virtuoso.openlinksw.com/presentations/Virtuoso_Sponger_1/Virtuoso_Sponger_1.html" id="link-idf7739b8">RDFization Middleware</a>, <a href="http://virtuoso.openlinksw.com/presentations/RDF_Mapping_Presentation_W3C_workshop3/RDF_Mapping_Presentation_W3C_workshop3.html" id="link-id1025ca28">SQL-RDF Mapping</a>, <a href="http://virtuoso.openlinksw.com/presentations/Virtuoso_Deploying_Linked_Data/Virtuoso_Deploying_Linked_Data.html" id="link-id1324db10">RDF Linked Data Deployment</a>, alongside a hybrid/multi-model, virtual/federated data service in a single product offering.</p> <p></p>BTW - There is a <a href="http://events.linkeddata.org/ldow2008/" id="link-id117a0190">Linked Data Workshop</a> at this years <a href="http://www2008.org/" id="link-id102abe28">World Wide Web conference</a>. Also note the <a href="http://esw.w3.org/topic/HCLS/WWW2008" id="link-id100c3a88">Healthcare & Life Science Workshop</a> which is a related Linked Data technology and Semantic Web best practices realm.
Semantic Web Killer Application?
2008-02-05T01:32:42Z
2008-02-04T20:32:42.000003-05:00
Kingsley Uyi Idehen
kidehen@openlinksw.com