<?xml version="1.0" encoding="UTF-8" ?>
<!--ATOM based XML document generated By OpenLink Virtuoso-->
<atom:feed xmlns:atom="http://www.w3.org/2005/Atom" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:vi="http://www.openlinksw.com/weblog/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:itunes="http://www.itunes.com/DTDs/Podcast-1.0.dtd" xmlns:dc="http://purl.org/dc/elements/1.1/">
<atom:id>http://www.openlinksw.com/GData/127/1546/6</atom:id>
<atom:title>Kingsley Idehen&#39;s Blog Data Space</atom:title>
<atom:link href="http://www.openlinksw.com/GData/127/1546/6" type="text/html" rel="alternate" />
<atom:link href="http://www.openlinksw.com/GData/127" type="application/atom+xml" rel="self" />
<atom:updated>2009-11-23T12:32:49Z</atom:updated>
 <atom:author>
  <atom:name>Kingsley Uyi Idehen</atom:name>
  <atom:email>kidehen@openlinksw.com</atom:email>
  </atom:author>
<atom:subtitle>About</atom:subtitle>
<openSearch:totalResults>1</openSearch:totalResults>
<openSearch:startIndex>1</openSearch:startIndex>
<openSearch:itemsPerPage>10</openSearch:itemsPerPage>
 <atom:entry>
  <atom:id>http://www.openlinksw.comhttp://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1546</atom:id>
  <atom:content type="html">&lt;p&gt;The act of using URIs to &amp;quot;refer to&amp;quot; (reference) &lt;a href=&quot;http://dbpedia.org/resource/World_Wide_Web&quot;&gt;Web&lt;/a&gt; addressable &lt;a href=&quot;http://dbpedia.org/resource/Data&quot;&gt;data&lt;/a&gt; objects. It&amp;#39;s also the act of using the same &lt;a href=&quot;http://dbpedia.org/resource/Uniform_Resource_Identifier&quot; id=&quot;link-id12b41fc0&quot;&gt;URI&lt;/a&gt; to de-reference the description of a referenced data object; in this case, the representation of the description is negotiated by a Web client and/or Web server. Thus, you can access the description of a data object via data representation formats such as: JSON, XML, (X)HTML, RDF/XML, N3, Turtle, TriX etc. &lt;/p&gt; &lt;p&gt; &lt;strong&gt;Note:&lt;/strong&gt; In proper Web parlance, a data object is referred to as a resource.&lt;/p&gt; &lt;h3&gt;Simple example (using &lt;a href=&quot;http://dbpedia.org/resource/DBpedia&quot; id=&quot;link-id0x131005a0&quot;&gt;DBpedia&lt;/a&gt;)&lt;/h3&gt; &lt;p&gt;In the &lt;a href=&quot;http://dbpedia.org/resource/Linked_Data&quot; id=&quot;link-id0x13299d20&quot;&gt;Linked Data&lt;/a&gt; realm, If you want to make a reference to the &lt;a href=&quot;http://www.w3.org/DesignIssues/LinkedData.html&quot; id=&quot;link-id0x188210a8&quot;&gt;Linked Data meme&lt;/a&gt; in a &lt;a href=&quot;http://dbpedia.org/resource/Blog&quot; id=&quot;link-id0x158a3fc0&quot;&gt;blog&lt;/a&gt; post, you are better off using the resource &lt;strong&gt;URI&lt;/strong&gt;: http://dbpedia.org/resource/Linked_Data, instead of the Web page &lt;strong&gt;&lt;a href=&quot;http://dbpedia.org/resource/Uniform_Resource_Locator&quot; id=&quot;link-id0x142865b0&quot;&gt;URL&lt;/a&gt;&lt;/strong&gt;: http://dbpedia.org/page/Linked_Data, which is the address of a physical document (an &lt;a href=&quot;http://dbpedia.org/resource/Information&quot; id=&quot;link-id0x15884030&quot;&gt;information&lt;/a&gt; conveying artifact) that at best visually presents the negotiated representation of a resource description.&lt;/p&gt; &lt;h3&gt;Why is this valuable?&lt;/h3&gt; &lt;p&gt;In the simplest sense, you only have one focal point for referencing (referring to) and de-referencing (retrieving data about) a given Web resource. It protects you from the impact of Web document location changes (amongst many other things).&lt;/p&gt; &lt;p&gt;Remember, a single URI is a conduit into a realm where the identity, access, representation, presentation, and storage of a resource (data object) are completely distinct. It&amp;#39;s the mechanism for conducting data across network, machine, operating system, dbms engine, application, and service (API) boundaries. Thus, without &amp;quot;linked data meme&amp;quot; prescribed URI referencing and de-referencing, we are simply back to &amp;quot;business as usual&amp;quot; re. the industry at large, where networks, operating systems, dbms engines, applications, and services (APIs) become the basis for &amp;quot;data lock-in&amp;quot; and silo construction.&lt;/p&gt; &lt;h3&gt;Going forward&lt;/h3&gt; &lt;p&gt;Take a second to think about the profound virtues of the ubiquitous Web of Linked Document URLs that we have today, and then apply that thinking to the burgeoning Web of Linked Data URIs, that has just turned corner and heading in everyone&amp;#39;s direction at full blast.&lt;/p&gt; &lt;p&gt; &lt;strong&gt;Note to &amp;quot;Social Media&amp;quot; players:&lt;/strong&gt; Who you know isn&amp;#39;t the canonical object of sociality. What you are i.e., your description and the data objects it exposes, are real objects of your sociality :-)&lt;/p&gt; &lt;h3&gt;Related&lt;/h3&gt; &lt;ul&gt; &lt;li&gt; &lt;a href=&quot;http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&amp;amp;q=%22Linked%20Data%22&amp;amp;type=text&amp;amp;output=html&quot; id=&quot;link-id14d44430&quot;&gt;Other post in this Blog Data Space associated with &amp;quot;Linked Data&amp;quot;&lt;/a&gt;. &lt;/li&gt; &lt;/ul&gt;</atom:content>
  <atom:title>What is the Linked Data Meme about?</atom:title>
  <atom:link href="http://www.openlinksw.comhttp://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1546" type="text/html" rel="alternate" />
  <atom:link href="http://www.openlinksw.com/GData/127//6" rel="edit" />
  <atom:published>2009-04-29T20:31:10Z</atom:published>
  <atom:updated>2009-04-29T16:31:10-04:00</atom:updated>
  <atom:author>
    <atom:name>Kingsley Uyi Idehen</atom:name>
    <atom:email>kidehen@openlinksw.com</atom:email>
   </atom:author>
 </atom:entry>
</atom:feed>