<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: N for structure</title>
	<atom:link href="http://blogs.law.harvard.edu/doc/2008/09/23/n-for-structure/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/doc/2008/09/23/n-for-structure/</link>
	<description>Same old blog, brand new place</description>
	<lastBuildDate>Sun, 29 Nov 2009 09:02:06 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Russell Nelson</title>
		<link>http://blogs.law.harvard.edu/doc/2008/09/23/n-for-structure/comment-page-1/#comment-87278</link>
		<dc:creator>Russell Nelson</dc:creator>
		<pubDate>Fri, 26 Sep 2008 18:09:10 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/2008/09/23/n-for-structure/#comment-87278</guid>
		<description>I&#039;ll see your fiber optic cable, and raise you two:
http://blog.russnelson.com/economics/got-fiber.html</description>
		<content:encoded><![CDATA[<p>I&#8217;ll see your fiber optic cable, and raise you two:<br />
<a href="http://blog.russnelson.com/economics/got-fiber.html" rel="nofollow">http://blog.russnelson.com/economics/got-fiber.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Lewis</title>
		<link>http://blogs.law.harvard.edu/doc/2008/09/23/n-for-structure/comment-page-1/#comment-86247</link>
		<dc:creator>Stephen Lewis</dc:creator>
		<pubDate>Wed, 24 Sep 2008 14:06:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/2008/09/23/n-for-structure/#comment-86247</guid>
		<description>Doc,

Re: Infrastructure and the Net ... Infrastructure need not be physical.  An idea that I&#039;ve been playing with (see the text I sent you yesterday) is that while the Net serves as infrastructure it also rests on infrastructure, much of it banally corporeal.  A quote from what I wrote:

&quot;... the internet has emerged as the primary infrastructure of the aggregation, dispersal, and utilization of knowledge; of scientific, commercial and social interaction; and of the management of technology, processes, and systems essential to the resources and security on which our futures depend...  The speed and ease with which the internet rose and achieved ubiquity was very much a function of the ad hoc nature of the infrastructure that carries it.  In part, the infrastructure of the internet is immaterial, a set of mutually accepted protocols and agreements.  For the rest, however, the infrastructure of the internet is purely physical and tangential -- a decentralized aggregation of an infinite number of computers interconnected through cables and fibers originally emplaced for other purposes and accessible through the marketing interfaces and billing systems of companies and institutions with their prime interests and focuses in other areas.&quot;

Looking forward to discussing this further,

SL</description>
		<content:encoded><![CDATA[<p>Doc,</p>
<p>Re: Infrastructure and the Net &#8230; Infrastructure need not be physical.  An idea that I&#8217;ve been playing with (see the text I sent you yesterday) is that while the Net serves as infrastructure it also rests on infrastructure, much of it banally corporeal.  A quote from what I wrote:</p>
<p>&#8220;&#8230; the internet has emerged as the primary infrastructure of the aggregation, dispersal, and utilization of knowledge; of scientific, commercial and social interaction; and of the management of technology, processes, and systems essential to the resources and security on which our futures depend&#8230;  The speed and ease with which the internet rose and achieved ubiquity was very much a function of the ad hoc nature of the infrastructure that carries it.  In part, the infrastructure of the internet is immaterial, a set of mutually accepted protocols and agreements.  For the rest, however, the infrastructure of the internet is purely physical and tangential &#8212; a decentralized aggregation of an infinite number of computers interconnected through cables and fibers originally emplaced for other purposes and accessible through the marketing interfaces and billing systems of companies and institutions with their prime interests and focuses in other areas.&#8221;</p>
<p>Looking forward to discussing this further,</p>
<p>SL</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Pass</title>
		<link>http://blogs.law.harvard.edu/doc/2008/09/23/n-for-structure/comment-page-1/#comment-85944</link>
		<dc:creator>Andrew Pass</dc:creator>
		<pubDate>Tue, 23 Sep 2008 23:35:19 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/2008/09/23/n-for-structure/#comment-85944</guid>
		<description>Great post!!

Unfortunately, I think that too many people have difficulty understanding abstract concepts.  This includes policymakers.  This makes it very difficult to understand the difference between the World Wide Web and the Internet.   If you don&#039;t understand something it becomes quite difficult to regulate it. 

Wait a second, we live in the United States.  This type of thing happens all the time. 

http://pass-ed.blogspot.com/</description>
		<content:encoded><![CDATA[<p>Great post!!</p>
<p>Unfortunately, I think that too many people have difficulty understanding abstract concepts.  This includes policymakers.  This makes it very difficult to understand the difference between the World Wide Web and the Internet.   If you don&#8217;t understand something it becomes quite difficult to regulate it. </p>
<p>Wait a second, we live in the United States.  This type of thing happens all the time. </p>
<p><a href="http://pass-ed.blogspot.com/" rel="nofollow">http://pass-ed.blogspot.com/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
