<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.newamerica.net" xmlns:dc="
http://purl.org/dc/elements/1.1/">
<channel>
 <title>Muniwireless.com</title>
 <link>http://www.newamerica.net/taxonomy/term/356</link>
 <description>The taxonomy view with a depth of 0.</description>
 <language>en</language>
<item>
 <title>Philadelphia Network Flop Points To Failure Of Corporate Franchise Model</title>
 <link>http://www.newamerica.net/publications/articles/2008/philadelphia_network_flop_points_failure_corporate_franchise_model_7205</link>
 <description>&lt;div class=&quot;teaser-content&quot;&gt;
&lt;p&gt;
Last year, New America Foundation released an in-depth report and analysis of the Wireless Philadelphia Project, “The Philadelphia Story: Learning from a Municipal Wireless Pioneer.” We concluded that the private franchise model was suboptimal and that Philadelphia’s solution was problematic in a number of ways. At the time, we received good press coverage and a helluvalot of blowback from certain constituencies (who continued to assert that everything was on track).
&lt;/p&gt;
&lt;p&gt;
Now that we’ve made it to May, 2008, Wireless Philadelphia is on its last legs. While many of us are still working to salvage something from this mess, reading through&amp;hellip; &lt;a href=&quot;/publications/articles/2008/philadelphia_network_flop_points_failure_corporate_franchise_model_7205&quot;&gt;more&lt;/a&gt;&lt;/div&gt;&lt;!-- /.teaser-content --&gt;
</description>
 <category domain="http://www.newamerica.net/people/sascha_meinrath/recent_work">Sascha Meinrath</category>
 <category domain="http://www.newamerica.net/taxonomy/term/356">Muniwireless.com</category>
 <category domain="http://www.newamerica.net/taxonomy/term/560">Broadband &amp;amp; Community Wireless</category>
 <category domain="http://www.newamerica.net/taxonomy/term/23">Wireless Future Program</category>
 <category domain="http://www.newamerica.net/taxonomy/term/12">Telecom &amp;amp; Technology</category>
 <pubDate>Fri, 16 May 2008 09:21:00 -0400</pubDate>
 <dc:creator>Ron Tang</dc:creator>
 <guid isPermaLink="false">7205 at http://www.newamerica.net</guid>
</item>
<item>
 <title>Which is More Important for Spectrum Policy: FCC or DOT?</title>
 <link>http://www.newamerica.net/publications/articles/2006/which_is_more_important_for_spectrum_policy_fcc_or_dot</link>
 <description>&lt;div class=&quot;teaser-content&quot;&gt;
&lt;p&gt;Which has more influence on spectrum policy: the Federal Communications Commission (FCC) or the various federal, state, and local departments of transportation? Conventional wisdom would place the FCC as the hands down winner. Surely, that continues to be the case. But if current technological trends continue, the departments of transportation, especially the United States Department of Transportation (USDOT), could end up a strong second. We&amp;#39;re all familiar with the growing importance of municipal Wi-Fi. But why not highway Wi-Fi? Why should Wi-Fi stop at city boundaries?  &lt;/p&gt;  &lt;p&gt;That&amp;#39;s where the USDOT&amp;#39;s planned Intelligent Transportation System (ITS) could come&amp;hellip; &lt;a href=&quot;/publications/articles/2006/which_is_more_important_for_spectrum_policy_fcc_or_dot&quot;&gt;more&lt;/a&gt;&lt;/div&gt;&lt;!-- /.teaser-content --&gt;
</description>
 <category domain="http://www.newamerica.net/people/jh_snider/recent_work">J.H. Snider</category>
 <category domain="http://www.newamerica.net/taxonomy/term/356">Muniwireless.com</category>
 <category domain="http://www.newamerica.net/taxonomy/term/535">Spectrum Policy Reform</category>
 <category domain="http://www.newamerica.net/taxonomy/term/23">Wireless Future Program</category>
 <category domain="http://www.newamerica.net/taxonomy/term/12">Telecom &amp;amp; Technology</category>
 <category domain="http://www.newamerica.net/issues/keywords/transportation">Transportation</category>
 <pubDate>Sun, 08 Jan 2006 04:00:00 -0500</pubDate>
 <dc:creator>Articles</dc:creator>
 <guid isPermaLink="false">2019 at http://www.newamerica.net</guid>
</item>
</channel>
</rss>
