<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://rose.geog.mcgill.ca/geoide"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>The Participatory Geoweb - Web 2.0</title>
 <link>http://rose.geog.mcgill.ca/geoide/taxonomy/term/162/0</link>
 <description>A phrase coined by the book publisher, O&#039;Reilly, to describe the next generation of the web.
</description>
 <language>en</language>
<item>
 <title>Web 2.0</title>
 <link>http://rose.geog.mcgill.ca/geoide/node/240</link>
 <description> &lt;p&gt;Here are O&#039;Reilly&#039;s recommended &lt;a href=&quot;http://www.oreillynet.com/lpt/a/6228&quot;&gt;design principles&lt;/a&gt; for Web 2 .0 applications.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The Long Tail&lt;/li&gt;
&lt;blockquote&gt;&lt;p&gt;Small sites make up the bulk of the internet&#039;s content; narrow niches make up the bulk of internet&#039;s the possible applications. Therefore: Leverage customer-self service and algorithmic data management to reach out to the entire web, to the edges and not just the center, to the long tail and not just the head.&lt;/p&gt;&lt;/blockquote&gt;
&lt;li&gt;Data is the Next Intel Inside &lt;/li&gt;
&lt;blockquote&gt;&lt;p&gt;Applications are increasingly data-driven. Therefore: For competitive advantage, seek to own a unique, hard-to-recreate source of data.&lt;/p&gt;&lt;/blockquote&gt;
&lt;li&gt;Users Add Value [in the &lt;a class=&quot;glossary-term&quot; href=&quot;/geoide/taxonomy/term/157&quot;&gt;&lt;acronym title=&quot;“Integrative, discoverable collection of geographically related web services and data that spans multiple jurisdictions and geographic regions” (Lake et al. 2007)

&quot;The Geoweb provides the means for interconnecting individual GIS databases. Desktop GIS can access and ingest data that’s found on the Geoweb as well as publish data to it. We can consume services that reside on the web, and can integrate different perspectives through the common network that is the web.

The Geoweb framework provides the means of integrating our collective knowledge. While there are means of consuming and representing our data in globes and maps, the entirety of the Geoweb is not yet a GIS. The barrier at present is largely data access and discovery, particularly when looking at the popular geographic exploration systems. There’s no access to data at the database level to unlock metadata and the multiple attributes that have been collected about our world. There’s also a lack of analysis functionality.&quot; (Ball 2008)&quot;&gt;Geoweb&lt;/acronym&gt;&lt;/a&gt;, it&#039;s called user generated content, user created content, or &lt;a class=&quot;glossary-term&quot; href=&quot;/geoide/taxonomy/term/167&quot;&gt;&lt;acronym title=&quot;“Widespread engagement of large #s of private citizens, often with little formal qualifications in the creation of geographic information” (Goodchild 2007). A traditional example is the Audubon Society&#039;s Christmas Bird Count; more recent example is Open Street Maps.&quot;&gt;volunteered geographic information&lt;/acronym&gt;&lt;/a&gt;]&lt;/li&gt;
&lt;blockquote&gt;&lt;p&gt;The key to competitive advantage in internet applications is the extent to which users add their own data to that which you provide. Therefore: Don&#039;t restrict your &quot;architecture of participation&quot; to software development. Involve your users both implicitly and explicitly in adding value to your application.&lt;/p&gt;&lt;/blockquote&gt;
&lt;li&gt;Network Effects by Default &lt;/li&gt;
&lt;blockquote&gt;&lt;p&gt;Only a small percentage of users will go to the trouble of adding value to your application. Therefore: Set inclusive defaults for aggregating user data as a side-effect of their use of the application.&lt;/p&gt;&lt;/blockquote&gt;
&lt;li&gt;Some Rights Reserved &lt;/li&gt;
&lt;blockquote&gt;&lt;p&gt;Intellectual property protection limits re-use and prevents experimentation. Therefore: When benefits come from collective adoption, not private restriction, make sure that barriers to adoption are low. Follow existing standards, and use licenses with as few restrictions as possible. Design for &quot;hackability&quot; and &quot;remixability.&quot;&lt;/p&gt;&lt;/blockquote&gt;
&lt;li&gt;The Perpetual Beta &lt;/li&gt;
&lt;blockquote&gt;&lt;p&gt;When devices and programs are connected to the internet, applications are no longer software artifacts, they are ongoing services. Therefore: Don&#039;t package up new features into monolithic releases, but instead add them on a regular basis as part of the normal user experience. Engage your users as real-time testers, and instrument the service so that you know how people use the new features.&lt;/p&gt;&lt;/blockquote&gt;
&lt;li&gt;Cooperate, Don&#039;t Control &lt;/li&gt;
&lt;blockquote&gt;&lt;p&gt;Web 2 .0 applications are built of a network of cooperating data services. Therefore: Offer web services interfaces and content syndication, and re-use the data services of others. Support lightweight programming models that allow for loosely-coupled systems.&lt;/p&gt;&lt;/blockquote&gt;
&lt;li&gt;Software Above the Level of a Single Device &lt;/li&gt;
&lt;blockquote&gt;&lt;p&gt;The PC is no longer the only access device for internet applications, and applications that are limited to a single device are less valuable than those that are connected. Therefore: Design your application from the get-go to integrate services across handheld devices, PCs, and internet servers.&lt;/p&gt;&lt;/blockquote&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;An awesome &lt;a href=&quot;http://www.youtube.com/watch?v=rDqGQ59jw_Y&amp;amp;amp;feature=related&quot;&gt;illustration&lt;/a&gt; of Web 2 .0&lt;/p&gt;
&lt;p&gt;&lt;object width=&quot;425&quot; height=&quot;344&quot;&gt;&lt;param name=&quot;movie&quot; value=&quot;http://www.youtube.com/v/rDqGQ59jw_Y&amp;amp;hl=en&quot; /&gt;&lt;/object&gt;&lt;/p&gt;
 </description>
 <comments>http://rose.geog.mcgill.ca/geoide/node/240#comments</comments>
 <category domain="http://rose.geog.mcgill.ca/geoide/taxonomy/term/162">Web 2.0</category>
 <pubDate>Sun, 22 Nov 2009 22:52:04 +0000</pubDate>
 <dc:creator>admin</dc:creator>
 <guid isPermaLink="false">240 at http://rose.geog.mcgill.ca/geoide</guid>
</item>
</channel>
</rss>
