<?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: data standardization, microformats, not just all hype</title>
	<atom:link href="http://dangerouslyawesome.com/2006/09/data-standardization-microformats-not-just-all-hype/feed/" rel="self" type="application/rss+xml" />
	<link>http://dangerouslyawesome.com/2006/09/data-standardization-microformats-not-just-all-hype/</link>
	<description>Alex Hillman Writes Here</description>
	<lastBuildDate>Mon, 06 Feb 2012 14:50:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: shim</title>
		<link>http://dangerouslyawesome.com/2006/09/data-standardization-microformats-not-just-all-hype/comment-page-1/#comment-58</link>
		<dc:creator>shim</dc:creator>
		<pubDate>Tue, 19 Sep 2006 15:22:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.dangerouslyawesome.com/2006/09/18/data-standardization-microformats-not-just-all-hype/#comment-58</guid>
		<description>&lt;p&gt;Dude!!! are you coming this year on the ski trip?
we are planning on going to alberta canada... to ski banff, lake louise, and kicking horse... although we are hoping to focus on kicking horse primarily.
zev is already working on our accomodations, and erik is planning on coming with his girlfriend.
dates are feb. 4th to the 11th 2007
here&#039;s to hoping you can make it!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Dude!!! are you coming this year on the ski trip?
we are planning on going to alberta canada&#8230; to ski banff, lake louise, and kicking horse&#8230; although we are hoping to focus on kicking horse primarily.
zev is already working on our accomodations, and erik is planning on coming with his girlfriend.
dates are feb. 4th to the 11th 2007
here&#8217;s to hoping you can make it!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: shim</title>
		<link>http://dangerouslyawesome.com/2006/09/data-standardization-microformats-not-just-all-hype/comment-page-1/#comment-1813</link>
		<dc:creator>shim</dc:creator>
		<pubDate>Tue, 19 Sep 2006 15:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dangerouslyawesome.com/2006/09/18/data-standardization-microformats-not-just-all-hype/#comment-1813</guid>
		<description>&lt;p&gt;Dude!!! are you coming this year on the ski trip?
we are planning on going to alberta canada... to ski banff, lake louise, and kicking horse... although we are hoping to focus on kicking horse primarily.
zev is already working on our accomodations, and erik is planning on coming with his girlfriend. 
dates are feb. 4th to the 11th 2007
here&#039;s to hoping you can make it!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Dude!!! are you coming this year on the ski trip?
we are planning on going to alberta canada&#8230; to ski banff, lake louise, and kicking horse&#8230; although we are hoping to focus on kicking horse primarily.
zev is already working on our accomodations, and erik is planning on coming with his girlfriend. 
dates are feb. 4th to the 11th 2007
here&#8217;s to hoping you can make it!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: dangerouslyawesome</title>
		<link>http://dangerouslyawesome.com/2006/09/data-standardization-microformats-not-just-all-hype/comment-page-1/#comment-57</link>
		<dc:creator>dangerouslyawesome</dc:creator>
		<pubDate>Tue, 19 Sep 2006 01:53:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.dangerouslyawesome.com/2006/09/18/data-standardization-microformats-not-just-all-hype/#comment-57</guid>
		<description>&lt;p&gt;the glaring problem i see with the openid project is a lack of coherant documentation.&lt;/p&gt;

&lt;p&gt;for example, the task of installing OpenID for blog commenting on wordpress 2.0.&lt;/p&gt;

&lt;p&gt;going to the openidenabled.com website and searching for &quot;wordpress&quot; i get 7 results, only 2 of which are really relevant to wordpress at all. and one of those is simply a link to the other. So that one relevant link, which is http://www.openidenabled.com/Members/http-3A-2F-2Fedulix.videntity.org-2F/openid-plugin-for-wordpress/openid-full-tar.bz2/view
is mostly a list of comments complaining about the lack of documentation! (the zip for the plugin contains NO readme. not good)&lt;/p&gt;

&lt;p&gt;Ok, so onto google. A quick google of wordpress turns up some more useful links, which are more detailed than the directions on the openid site itself. Essentially, the &quot;beta&quot; plugin has dependencies  as documented a few comments down on http://photomatt.net/2006/04/14/openid-for-wp/&lt;/p&gt;

&lt;p&gt;overall, a pretty tedious process compared to how easy most other WP plugins are.&lt;/p&gt;

&lt;p&gt;the openid site is effectively expansive, but difficult to navigate. this is a huge hinderance to the effectiveness of the mission of the project. how is it that something dedicated to make one process easy exists in a site that is possibly one of the most confusing i&#039;ve ever experienced?&lt;/p&gt;

&lt;p&gt;OpenID libraries exist for half a dozen major development platforms, including php , java, and .net. But with all of the other authentication schemes that are practically turn key, what incentive is there for a developer to impliment something that requires tons of digging just to get a mediocre set of documentation? The concept is gold. unfortunately, it&#039;s a the bottom of a pretty rapid riverbed right now. I&#039;m not sure how to even start panning for the value.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>the glaring problem i see with the openid project is a lack of coherant documentation.</p>

<p>for example, the task of installing OpenID for blog commenting on wordpress 2.0.</p>

<p>going to the openidenabled.com website and searching for &#8220;wordpress&#8221; i get 7 results, only 2 of which are really relevant to wordpress at all. and one of those is simply a link to the other. So that one relevant link, which is <a href="http://www.openidenabled.com/Members/http-3A-2F-2Fedulix.videntity.org-2F/openid-plugin-for-wordpress/openid-full-tar.bz2/view" rel="nofollow">http://www.openidenabled.com/Members/http-3A-2F-2Fedulix.videntity.org-2F/openid-plugin-for-wordpress/openid-full-tar.bz2/view</a>
is mostly a list of comments complaining about the lack of documentation! (the zip for the plugin contains NO readme. not good)</p>

<p>Ok, so onto google. A quick google of wordpress turns up some more useful links, which are more detailed than the directions on the openid site itself. Essentially, the &#8220;beta&#8221; plugin has dependencies  as documented a few comments down on <a href="http://photomatt.net/2006/04/14/openid-for-wp/" rel="nofollow">http://photomatt.net/2006/04/14/openid-for-wp/</a></p>

<p>overall, a pretty tedious process compared to how easy most other WP plugins are.</p>

<p>the openid site is effectively expansive, but difficult to navigate. this is a huge hinderance to the effectiveness of the mission of the project. how is it that something dedicated to make one process easy exists in a site that is possibly one of the most confusing i&#8217;ve ever experienced?</p>

<p>OpenID libraries exist for half a dozen major development platforms, including php , java, and .net. But with all of the other authentication schemes that are practically turn key, what incentive is there for a developer to impliment something that requires tons of digging just to get a mediocre set of documentation? The concept is gold. unfortunately, it&#8217;s a the bottom of a pretty rapid riverbed right now. I&#8217;m not sure how to even start panning for the value.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: dangerouslyawesome</title>
		<link>http://dangerouslyawesome.com/2006/09/data-standardization-microformats-not-just-all-hype/comment-page-1/#comment-1812</link>
		<dc:creator>dangerouslyawesome</dc:creator>
		<pubDate>Tue, 19 Sep 2006 01:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dangerouslyawesome.com/2006/09/18/data-standardization-microformats-not-just-all-hype/#comment-1812</guid>
		<description>&lt;p&gt;the glaring problem i see with the openid project is a lack of coherant documentation.&lt;/p&gt;

&lt;p&gt;for example, the task of installing OpenID for blog commenting on wordpress 2.0.&lt;/p&gt;

&lt;p&gt;going to the openidenabled.com website and searching for &quot;wordpress&quot; i get 7 results, only 2 of which are really relevant to wordpress at all. and one of those is simply a link to the other. So that one relevant link, which is http://www.openidenabled.com/Members/http-3A-2F-2Fedulix.videntity.org-2F/openid-plugin-for-wordpress/openid-full-tar.bz2/view
is mostly a list of comments complaining about the lack of documentation! (the zip for the plugin contains NO readme. not good)&lt;/p&gt;

&lt;p&gt;Ok, so onto google. A quick google of wordpress turns up some more useful links, which are more detailed than the directions on the openid site itself. Essentially, the &quot;beta&quot; plugin has dependencies  as documented a few comments down on http://photomatt.net/2006/04/14/openid-for-wp/&lt;/p&gt;

&lt;p&gt;overall, a pretty tedious process compared to how easy most other WP plugins are.&lt;/p&gt;

&lt;p&gt;the openid site is effectively expansive, but difficult to navigate. this is a huge hinderance to the effectiveness of the mission of the project. how is it that something dedicated to make one process easy exists in a site that is possibly one of the most confusing i&#039;ve ever experienced?&lt;/p&gt;

&lt;p&gt;OpenID libraries exist for half a dozen major development platforms, including php , java, and .net. But with all of the other authentication schemes that are practically turn key, what incentive is there for a developer to impliment something that requires tons of digging just to get a mediocre set of documentation? The concept is gold. unfortunately, it&#039;s a the bottom of a pretty rapid riverbed right now. I&#039;m not sure how to even start panning for the value.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>the glaring problem i see with the openid project is a lack of coherant documentation.</p>

<p>for example, the task of installing OpenID for blog commenting on wordpress 2.0.</p>

<p>going to the openidenabled.com website and searching for &#8220;wordpress&#8221; i get 7 results, only 2 of which are really relevant to wordpress at all. and one of those is simply a link to the other. So that one relevant link, which is <a href="http://www.openidenabled.com/Members/http-3A-2F-2Fedulix.videntity.org-2F/openid-plugin-for-wordpress/openid-full-tar.bz2/view" rel="nofollow">http://www.openidenabled.com/Members/http-3A-2F-2Fedulix.videntity.org-2F/openid-plugin-for-wordpress/openid-full-tar.bz2/view</a>
is mostly a list of comments complaining about the lack of documentation! (the zip for the plugin contains NO readme. not good)</p>

<p>Ok, so onto google. A quick google of wordpress turns up some more useful links, which are more detailed than the directions on the openid site itself. Essentially, the &#8220;beta&#8221; plugin has dependencies  as documented a few comments down on <a href="http://photomatt.net/2006/04/14/openid-for-wp/" rel="nofollow">http://photomatt.net/2006/04/14/openid-for-wp/</a></p>

<p>overall, a pretty tedious process compared to how easy most other WP plugins are.</p>

<p>the openid site is effectively expansive, but difficult to navigate. this is a huge hinderance to the effectiveness of the mission of the project. how is it that something dedicated to make one process easy exists in a site that is possibly one of the most confusing i&#8217;ve ever experienced?</p>

<p>OpenID libraries exist for half a dozen major development platforms, including php , java, and .net. But with all of the other authentication schemes that are practically turn key, what incentive is there for a developer to impliment something that requires tons of digging just to get a mediocre set of documentation? The concept is gold. unfortunately, it&#8217;s a the bottom of a pretty rapid riverbed right now. I&#8217;m not sure how to even start panning for the value.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Messina</title>
		<link>http://dangerouslyawesome.com/2006/09/data-standardization-microformats-not-just-all-hype/comment-page-1/#comment-56</link>
		<dc:creator>Chris Messina</dc:creator>
		<pubDate>Mon, 18 Sep 2006 23:44:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.dangerouslyawesome.com/2006/09/18/data-standardization-microformats-not-just-all-hype/#comment-56</guid>
		<description>&lt;p&gt;You could even start by &lt;a href=&quot;http://openidenabled.com&quot; rel=&quot;nofollow&quot;&gt;OpenID enabling&lt;/a&gt; your blog...! ;)&lt;/p&gt;

&lt;p&gt;So the real power is in hcard + openid + XFN.&lt;/p&gt;

&lt;p&gt;Think on that for a spell.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>You could even start by <a href="http://openidenabled.com" rel="nofollow">OpenID enabling</a> your blog&#8230;! <img src='http://dangerouslyawesome.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>

<p>So the real power is in hcard + openid + XFN.</p>

<p>Think on that for a spell.</p>]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  dangerouslyawesome.com/2006/09/data-standardization-microformats-not-just-all-hype/feed/ ) in 0.36771 seconds, on Feb 13th, 2012 at 2:46 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 13th, 2012 at 3:46 am UTC -->
