<?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: Interactive map of U.S. nanotechnology</title>
	<atom:link href="http://www.foresight.org/nanodot/?feed=rss2&#038;p=2484" rel="self" type="application/rss+xml" />
	<link>http://www.foresight.org/nanodot/?p=2484</link>
	<description>examining transformative technology</description>
	<lastBuildDate>Wed, 03 Apr 2013 18:23:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: In The Works &#187; Blog Archive &#187; nNews: Mapping Nanotech in the US</title>
		<link>http://www.foresight.org/nanodot/?p=2484#comment-243683</link>
		<dc:creator>In The Works &#187; Blog Archive &#187; nNews: Mapping Nanotech in the US</dc:creator>
		<pubDate>Thu, 17 May 2007 18:01:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.foresight.org/nanodot/?p=2484#comment-243683</guid>
		<description>[...] The Foresight Nanotech Institute blog recently posted about a map using Google&#8217;s API that the Project on Emerging Nanotechnologies put up. The map clearly shows a concentration in the Silicon Valley and Massachusetts areas, but it also reveals that nanotech is not going to exist solely in those areas. [...]</description>
		<content:encoded><![CDATA[<p>[...] The Foresight Nanotech Institute blog recently posted about a map using Google&#8217;s API that the Project on Emerging Nanotechnologies put up. The map clearly shows a concentration in the Silicon Valley and Massachusetts areas, but it also reveals that nanotech is not going to exist solely in those areas. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phillip Huggan</title>
		<link>http://www.foresight.org/nanodot/?p=2484#comment-243655</link>
		<dc:creator>Phillip Huggan</dc:creator>
		<pubDate>Thu, 17 May 2007 16:36:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.foresight.org/nanodot/?p=2484#comment-243655</guid>
		<description>Really minor quibble, but for the purposes of cluster theory the Metro area is defined is an area of shared commuters in suburbia.  That is, a person working in SJ would have no problem taking another position in Anahiem, but the wife and kids would have a fit if the new job was in Dallas.
When I used the Nanovip database in 2005 to try to get a feel of where the &quot;nanoclusters&quot; were in the world, the Bay area came out in front by far in the US.  Followed by Boston and suburbs, then the LA region, then Chicago, and finally New York as I saw fit to include ventures and angels.

I don&#039;t know the highways of the region, but is there any difference from a commuter perspective whether you&#039;re stuck in rush-hour traffic on the way home from Oakland versus San Franscisco?
I once commuted home to Burnaby BC by vehicle from Richmond, and also by bus-monorail from elsewhere in Burnaby.  The 15 minute difference in rush hour wouldn&#039;t be enough for me to label them separate employer locations on a national map.</description>
		<content:encoded><![CDATA[<p>Really minor quibble, but for the purposes of cluster theory the Metro area is defined is an area of shared commuters in suburbia.  That is, a person working in SJ would have no problem taking another position in Anahiem, but the wife and kids would have a fit if the new job was in Dallas.<br />
When I used the Nanovip database in 2005 to try to get a feel of where the &#8220;nanoclusters&#8221; were in the world, the Bay area came out in front by far in the US.  Followed by Boston and suburbs, then the LA region, then Chicago, and finally New York as I saw fit to include ventures and angels.</p>
<p>I don&#8217;t know the highways of the region, but is there any difference from a commuter perspective whether you&#8217;re stuck in rush-hour traffic on the way home from Oakland versus San Franscisco?<br />
I once commuted home to Burnaby BC by vehicle from Richmond, and also by bus-monorail from elsewhere in Burnaby.  The 15 minute difference in rush hour wouldn&#8217;t be enough for me to label them separate employer locations on a national map.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Howard Lovy</title>
		<link>http://www.foresight.org/nanodot/?p=2484#comment-243621</link>
		<dc:creator>Howard Lovy</dc:creator>
		<pubDate>Thu, 17 May 2007 14:55:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.foresight.org/nanodot/?p=2484#comment-243621</guid>
		<description>Hello, Foresight Folks,

I&#039;m surprised that the Boston Globe would be so technologically uninformed that it would mistake a Google Maps search that anybody can do for a full-fledged survey on nanotech hotbeds.

Even if you believe the exaggeration that this is any kind of real survey, it is far from the first. A long time ago, in a galaxy far, far away, I used to be the news editor for Small Times Magazine, where we actually did the first-ever rankings of nanotechnology hotbeds.

More here:

http://nanobot.blogspot.com/2007/05/dear-boston-globe-mashup-is-not-survey.html</description>
		<content:encoded><![CDATA[<p>Hello, Foresight Folks,</p>
<p>I&#8217;m surprised that the Boston Globe would be so technologically uninformed that it would mistake a Google Maps search that anybody can do for a full-fledged survey on nanotech hotbeds.</p>
<p>Even if you believe the exaggeration that this is any kind of real survey, it is far from the first. A long time ago, in a galaxy far, far away, I used to be the news editor for Small Times Magazine, where we actually did the first-ever rankings of nanotechnology hotbeds.</p>
<p>More here:</p>
<p><a href="http://nanobot.blogspot.com/2007/05/dear-boston-globe-mashup-is-not-survey.html" rel="nofollow">http://nanobot.blogspot.com/2007/05/dear-boston-globe-mashup-is-not-survey.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>