<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Goodbye, Corporate Data Silo; Hello Linked Data</title>
	<atom:link href="http://www.fastforwardblog.com/2008/06/19/goodbye-corporate-data-silo-hello-linked-data/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fastforwardblog.com/2008/06/19/goodbye-corporate-data-silo-hello-linked-data/</link>
	<description></description>
	<pubDate>Wed, 07 Jan 2009 08:59:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kingsley Idehen</title>
		<link>http://www.fastforwardblog.com/2008/06/19/goodbye-corporate-data-silo-hello-linked-data/comment-page-1/#comment-161776</link>
		<dc:creator>Kingsley Idehen</dc:creator>
		<pubDate>Fri, 20 Jun 2008 19:28:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.fastforwardblog.com/?p=955#comment-161776</guid>
		<description>Joe,

Really great to see that you've picked up on the linkage between "Linked Data" and Open Database Connectivity (ODBC)  :-)

Linked Data simply injects HTTP into the act of Data Source Naming, and results in the following:

1. Naming scoped to database records as opposed to Database, Table, Views, Procedures levels of ODBC (so you have additional granularity)
2. Direct Access to Named Records across Intranets, Extranets, and the Internet via the use of HTTP (since it's part of the naming scheme)
3. Network partitioning (public vs. private) due to the incorporation of hosts and domains withing HTTP

1-3 simply express the fact that documents (hard copy and electronic) are becoming less important than the things they are about. Just as computers have become less important than the HTTP accessible documents that they host.

My keynote presentation is available at:
http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/Creating_Deploying_Exploiting_Linked_Data2.html


Kingsley</description>
		<content:encoded><![CDATA[<p>Joe,</p>
<p>Really great to see that you&#8217;ve picked up on the linkage between &#8220;Linked Data&#8221; and Open Database Connectivity (ODBC)  <img src='http://www.fastforwardblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Linked Data simply injects HTTP into the act of Data Source Naming, and results in the following:</p>
<p>1. Naming scoped to database records as opposed to Database, Table, Views, Procedures levels of ODBC (so you have additional granularity)<br />
2. Direct Access to Named Records across Intranets, Extranets, and the Internet via the use of HTTP (since it&#8217;s part of the naming scheme)<br />
3. Network partitioning (public vs. private) due to the incorporation of hosts and domains withing HTTP</p>
<p>1-3 simply express the fact that documents (hard copy and electronic) are becoming less important than the things they are about. Just as computers have become less important than the HTTP accessible documents that they host.</p>
<p>My keynote presentation is available at:<br />
<a href="http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/Creating_Deploying_Exploiting_Linked_Data2.html" rel="nofollow">http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/Creating_Deploying_Exploiting_Linked_Data2.html</a></p>
<p>Kingsley</p>
]]></content:encoded>
	</item>
</channel>
</rss>
