<?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: How long should we wait for a standard to emerge and what is the cost of doing so?</title>
	<atom:link href="http://www.opengardensblog.futuretext.com/archives/2009/05/how_long_should.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.opengardensblog.futuretext.com/archives/2009/05/how_long_should.html</link>
	<description>Wireless mobility - Innovation - Digital convergence - mobile web 2.0</description>
	<lastBuildDate>Thu, 19 Jan 2012 13:47:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Justin James</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2009/05/how_long_should.html/comment-page-1#comment-1818</link>
		<dc:creator>Justin James</dc:creator>
		<pubDate>Tue, 26 May 2009 17:36:04 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2009/05/how_long_should.html#comment-1818</guid>
		<description>You&#039;ve made the same unfortunate misunderstanding regarding HTML 5 that Jeff Croft made in his famous rant... Ian *never* said that HTML 5 would be &quot;done&quot; in 2022. In fact, the HTML 5 spec is nearly done, and it is headed to &quot;Last Call&quot; status in a few months. What Ian specifically said is that HTML 5 would not be considered a full W3C recommendation until 2022, which is dependent on *two fully compliant implementations*. Seeing as you can&#039;t even find one fully compliant implementation of HTML 4 out there, saying &quot;2022&quot; for that criteria to be met is no surprise. HTML 5 will be &quot;done&quot; in late 2009 or early 2010, if I had a guess, based on the activity I have been seeing on the HTML mailing list. In fact, it&#039;s been published as a &quot;working draft&quot; for some time.
Is the stadnard process perfect? Far from it. Probably 2/3rds of the messages on the HTML 5 list of political nonsense regarding things that most people find irrelevant, like matters of process. But at the same time, HTML 5 is not nearly as broken as many people have interpreted based on the &quot;2022&quot; number.
J.Ja
</description>
		<content:encoded><![CDATA[<p>You&#8217;ve made the same unfortunate misunderstanding regarding HTML 5 that Jeff Croft made in his famous rant&#8230; Ian *never* said that HTML 5 would be &#8220;done&#8221; in 2022. In fact, the HTML 5 spec is nearly done, and it is headed to &#8220;Last Call&#8221; status in a few months. What Ian specifically said is that HTML 5 would not be considered a full W3C recommendation until 2022, which is dependent on *two fully compliant implementations*. Seeing as you can&#8217;t even find one fully compliant implementation of HTML 4 out there, saying &#8220;2022&#8243; for that criteria to be met is no surprise. HTML 5 will be &#8220;done&#8221; in late 2009 or early 2010, if I had a guess, based on the activity I have been seeing on the HTML mailing list. In fact, it&#8217;s been published as a &#8220;working draft&#8221; for some time.<br />
Is the stadnard process perfect? Far from it. Probably 2/3rds of the messages on the HTML 5 list of political nonsense regarding things that most people find irrelevant, like matters of process. But at the same time, HTML 5 is not nearly as broken as many people have interpreted based on the &#8220;2022&#8243; number.<br />
J.Ja</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
