<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Web 2.0</title>
	<link>http://www.eministrynotes.com/2005/09/08/web-20/</link>
	<description>A place to record notes on effective web ministry</description>
	<pubDate>Wed, 20 Aug 2008 13:35:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Jeff</title>
		<link>http://www.eministrynotes.com/2005/09/08/web-20/#comment-113</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid>http://www.eministrynotes.com/2005/09/08/web-20/#comment-113</guid>
		<description>Check out this article on &lt;A HREF="http://www.digital-web.com/articles/web_2_for_designers/" REL="nofollow"&gt;Digital Web Magazine&lt;/A&gt;. It might help.</description>
		<content:encoded><![CDATA[<p>Check out this article on <a HREF="http://www.digital-web.com/articles/web_2_for_designers/" REL="nofollow">Digital Web Magazine</a>. It might help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://www.eministrynotes.com/2005/09/08/web-20/#comment-114</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid>http://www.eministrynotes.com/2005/09/08/web-20/#comment-114</guid>
		<description>Here is another explanation from &lt;A HREF="http://bokardo.com/archives/not-a-technology-but-sharing/" REL="nofollow"&gt;Bokardo, Writings on Interface Design&lt;/A&gt;.</description>
		<content:encoded><![CDATA[<p>Here is another explanation from <a HREF="http://bokardo.com/archives/not-a-technology-but-sharing/" REL="nofollow">Bokardo, Writings on Interface Design</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rob</title>
		<link>http://www.eministrynotes.com/2005/09/08/web-20/#comment-115</link>
		<dc:creator>rob</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid>http://www.eministrynotes.com/2005/09/08/web-20/#comment-115</guid>
		<description>Okay, so it seems it's mostly a phrase to descibe a set of social websites.  I know there's more to it (RSS, CSS, XML), but for most people (like myself), it seems to be a way to describe and classify social websites.&lt;BR/&gt;&lt;BR/&gt;That about it?&lt;BR/&gt;&lt;BR/&gt;Someone in their own words tell me.  I appreciate the links, Jeff, but tell me in your words.  The links were good.  Give me the "elevator speech".</description>
		<content:encoded><![CDATA[<p>Okay, so it seems it&#8217;s mostly a phrase to descibe a set of social websites.  I know there&#8217;s more to it (RSS, CSS, XML), but for most people (like myself), it seems to be a way to describe and classify social websites.</p>
<p>That about it?</p>
<p>Someone in their own words tell me.  I appreciate the links, Jeff, but tell me in your words.  The links were good.  Give me the &#8220;elevator speech&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nathan colgate</title>
		<link>http://www.eministrynotes.com/2005/09/08/web-20/#comment-116</link>
		<dc:creator>nathan colgate</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid>http://www.eministrynotes.com/2005/09/08/web-20/#comment-116</guid>
		<description>I ran across this the other day and thought it was a great real life example of one of the possibilities of Web 2.0:&lt;BR/&gt;&lt;BR/&gt;John Gruber wrote a BBEdit CSS Syntax Checker.  Unfortunately, to keep the CSS model up-to-date, he has to &lt;A HREF="http://www.catb.org/~esr/jargon/html/S/screen-scraping.html" REL="nofollow"&gt;screen-scrap&lt;/A&gt; the information off the W3C pages.&lt;BR/&gt;&lt;BR/&gt;This is unfortunate because "screen-scraping is an ugly, ad-hoc, last-resort technique that is very likely to break on even minor changes to the format of the data being snooped" - &lt;A HREF="http://www.catb.org/~esr/jargon/html/index.html" REL="nofollow"&gt;The Jargon File&lt;/A&gt;&lt;BR/&gt;&lt;BR/&gt;What would be ideal is if the W3C offered a consistant API to access their standards.  For instance some possible requests: &lt;BR/&gt;&lt;BR/&gt;http://www.w3c.org/css.xml might return a simple xml list of all the versions of CSS.  This would serve as a starting point for other requests like:&lt;BR/&gt;&lt;BR/&gt;http://www.w3c.org/css?level=2&#038;revision=1&#038;section=4.1.1 would return an xml file of the Tokenization specs for CSS 2.1.&lt;BR/&gt;&lt;BR/&gt;And suddenly, because of the adherance to a standard, &lt;I&gt;other&lt;/I&gt; people can start using that information... for what? Who knows!  The sky is the limit! It opens up the possibility to use the information elegantly, for unexpected reasons, and not with a bunch of hacking.</description>
		<content:encoded><![CDATA[<p>I ran across this the other day and thought it was a great real life example of one of the possibilities of Web 2.0:</p>
<p>John Gruber wrote a BBEdit CSS Syntax Checker.  Unfortunately, to keep the CSS model up-to-date, he has to <a HREF="http://www.catb.org/~esr/jargon/html/S/screen-scraping.html" REL="nofollow">screen-scrap</a> the information off the W3C pages.</p>
<p>This is unfortunate because &#8220;screen-scraping is an ugly, ad-hoc, last-resort technique that is very likely to break on even minor changes to the format of the data being snooped&#8221; - <a HREF="http://www.catb.org/~esr/jargon/html/index.html" REL="nofollow">The Jargon File</a></p>
<p>What would be ideal is if the W3C offered a consistant API to access their standards.  For instance some possible requests: </p>
<p><a href="http://www.w3c.org/css.xml" rel="nofollow">http://www.w3c.org/css.xml</a> might return a simple xml list of all the versions of CSS.  This would serve as a starting point for other requests like:</p>
<p><a href="http://www.w3c.org/css?level=2&#038;revision=1&#038;section=4.1.1" rel="nofollow">http://www.w3c.org/css?level=2&#038;revision=1&#038;section=4.1.1</a> would return an xml file of the Tokenization specs for CSS 2.1.</p>
<p>And suddenly, because of the adherance to a standard, <i>other</i> people can start using that information&#8230; for what? Who knows!  The sky is the limit! It opens up the possibility to use the information elegantly, for unexpected reasons, and not with a bunch of hacking.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://www.eministrynotes.com/2005/09/08/web-20/#comment-117</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid>http://www.eministrynotes.com/2005/09/08/web-20/#comment-117</guid>
		<description>From what I understand, a big part of Web 2.0 is about making information accessible.  I have heard the term "content silo" kicked around with the GCX project.  A content silo means that only I can access a database or resource documents because they are only contained in my "web."&lt;BR/&gt;&lt;BR/&gt;Google and Flikr are using new trends to make the information in their databases accessible to others so that others can take what they have created and use it for another application.  An example would be Google Maps.  Others have used the information for the "maps" and built another interface application that helps people find apartments or map the movement of hurricanes.&lt;BR/&gt;&lt;BR/&gt;RSS is making information accessible in that I do not have to browse to find information that I want but I can "subscribe" and that info comes to me.  RSS is what makes podcasting different from just posting an mp3 on a website.&lt;BR/&gt;&lt;BR/&gt;So in a nutshell, I understand Web 2.0 to be about making information more accessible, both for users and developers.</description>
		<content:encoded><![CDATA[<p>From what I understand, a big part of Web 2.0 is about making information accessible.  I have heard the term &#8220;content silo&#8221; kicked around with the GCX project.  A content silo means that only I can access a database or resource documents because they are only contained in my &#8220;web.&#8221;</p>
<p>Google and Flikr are using new trends to make the information in their databases accessible to others so that others can take what they have created and use it for another application.  An example would be Google Maps.  Others have used the information for the &#8220;maps&#8221; and built another interface application that helps people find apartments or map the movement of hurricanes.</p>
<p>RSS is making information accessible in that I do not have to browse to find information that I want but I can &#8220;subscribe&#8221; and that info comes to me.  RSS is what makes podcasting different from just posting an mp3 on a website.</p>
<p>So in a nutshell, I understand Web 2.0 to be about making information more accessible, both for users and developers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rob</title>
		<link>http://www.eministrynotes.com/2005/09/08/web-20/#comment-118</link>
		<dc:creator>rob</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid>http://www.eministrynotes.com/2005/09/08/web-20/#comment-118</guid>
		<description>This is good.  So it's like a label for open, social websites (like Google, Flickr, and del.icio.us).  It's also a lable for sites that users or programmers can craft (like bloglines or google maps).  Using tools like RSS, XML, CSS, and open APIs, a new class of website is here (trend --&gt; future) because it's about being open and sharing content.  Web 2.0 is as much a technology, label, and philosophy.&lt;BR/&gt;&lt;BR/&gt;At least that's what I'm understanding it to be.</description>
		<content:encoded><![CDATA[<p>This is good.  So it&#8217;s like a label for open, social websites (like Google, Flickr, and del.icio.us).  It&#8217;s also a lable for sites that users or programmers can craft (like bloglines or google maps).  Using tools like RSS, XML, CSS, and open APIs, a new class of website is here (trend &#8211;> future) because it&#8217;s about being open and sharing content.  Web 2.0 is as much a technology, label, and philosophy.</p>
<p>At least that&#8217;s what I&#8217;m understanding it to be.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nathan colgate</title>
		<link>http://www.eministrynotes.com/2005/09/08/web-20/#comment-119</link>
		<dc:creator>nathan colgate</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid>http://www.eministrynotes.com/2005/09/08/web-20/#comment-119</guid>
		<description>Yeah.  Web 2.0 isn't really a tangible, understandable object.  I would say Web 2.0 is a hope that the web will continue to get better.  Any 'definitions' are just suggestions for how to get there.</description>
		<content:encoded><![CDATA[<p>Yeah.  Web 2.0 isn&#8217;t really a tangible, understandable object.  I would say Web 2.0 is a hope that the web will continue to get better.  Any &#8216;definitions&#8217; are just suggestions for how to get there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lisa Boyd</title>
		<link>http://www.eministrynotes.com/2005/09/08/web-20/#comment-120</link>
		<dc:creator>Lisa Boyd</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid>http://www.eministrynotes.com/2005/09/08/web-20/#comment-120</guid>
		<description>Look at this from a programmer's point of view. When programmers enhance a program (add groovy new features) they generally give it a version number different from the original. A whole number jump from the original and you know there were some major adjustments/improvements to the program.&lt;BR/&gt;&lt;BR/&gt;Let's say a programmer writes a program called "Web" where static pages are posted and accessed by people going to those pages to see what's new. This would be the old web or Web 1.0. The way the web used to be back in the beginning.&lt;BR/&gt;&lt;BR/&gt;Now there is so much different from the old web, people are calling it Web 2.0. In the "new" web, you have podcasting, blogging, rss feeds, and thousands upon thousands of people sharing information and working off each other. Not to mention the information people are sharing is not only text, but pictures, films, music and spoken audio.&lt;BR/&gt;&lt;BR/&gt;So if someone is boasting Web 2.0 they are probably talking about some new technology; a new way of thinking; or a new way of collaborating. If your web site uses fairly new features vs just throwing up static pages and hoping someone comes by to read them, then you'd probably be considered part of the society of Web 2.0. It describes a huge puzzle where the pieces are changing all the time.&lt;BR/&gt;&lt;BR/&gt;In the future when things we do now are considered old, people will probably start talking about Web 3.0 :)&lt;BR/&gt;&lt;BR/&gt;Lisa &lt;- a wanna be effective web minister</description>
		<content:encoded><![CDATA[<p>Look at this from a programmer&#8217;s point of view. When programmers enhance a program (add groovy new features) they generally give it a version number different from the original. A whole number jump from the original and you know there were some major adjustments/improvements to the program.</p>
<p>Let&#8217;s say a programmer writes a program called &#8220;Web&#8221; where static pages are posted and accessed by people going to those pages to see what&#8217;s new. This would be the old web or Web 1.0. The way the web used to be back in the beginning.</p>
<p>Now there is so much different from the old web, people are calling it Web 2.0. In the &#8220;new&#8221; web, you have podcasting, blogging, rss feeds, and thousands upon thousands of people sharing information and working off each other. Not to mention the information people are sharing is not only text, but pictures, films, music and spoken audio.</p>
<p>So if someone is boasting Web 2.0 they are probably talking about some new technology; a new way of thinking; or a new way of collaborating. If your web site uses fairly new features vs just throwing up static pages and hoping someone comes by to read them, then you&#8217;d probably be considered part of the society of Web 2.0. It describes a huge puzzle where the pieces are changing all the time.</p>
<p>In the future when things we do now are considered old, people will probably start talking about Web 3.0 <img src='http://www.eministrynotes.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Lisa <- a wanna be effective web minister</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rob</title>
		<link>http://www.eministrynotes.com/2005/09/08/web-20/#comment-121</link>
		<dc:creator>rob</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid>http://www.eministrynotes.com/2005/09/08/web-20/#comment-121</guid>
		<description>Lisa, great comment.  I stopped by your blog and it looks good.  But I couldn't leave a comment.&lt;BR/&gt;&lt;BR/&gt;Come back here anytime!</description>
		<content:encoded><![CDATA[<p>Lisa, great comment.  I stopped by your blog and it looks good.  But I couldn&#8217;t leave a comment.</p>
<p>Come back here anytime!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lisa Boyd</title>
		<link>http://www.eministrynotes.com/2005/09/08/web-20/#comment-122</link>
		<dc:creator>Lisa Boyd</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid>http://www.eministrynotes.com/2005/09/08/web-20/#comment-122</guid>
		<description>Thanks Rob for the invite back. I'm researching a lot of things (mostly podcasting right now) and in the planning stages of getting my church on the web. How have you setup such a neat comment form with the word verification stuff? I had to turn comments off for too much spam :(&lt;BR/&gt;&lt;BR/&gt;Lisa &lt;- ever in the learning stages</description>
		<content:encoded><![CDATA[<p>Thanks Rob for the invite back. I&#8217;m researching a lot of things (mostly podcasting right now) and in the planning stages of getting my church on the web. How have you setup such a neat comment form with the word verification stuff? I had to turn comments off for too much spam <img src='http://www.eministrynotes.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
<p>Lisa <- ever in the learning stages</p>
]]></content:encoded>
	</item>
</channel>
</rss>
