<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>HTML5 Doctor &#187; Ian Hickson</title>
	<atom:link href="http://html5doctor.com/tag/ian-hickson/feed/" rel="self" type="application/rss+xml" />
	<link>http://html5doctor.com</link>
	<description>helping you implement HTML5 today</description>
	<lastBuildDate>Wed, 16 May 2012 11:31:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>2022, or when will HTML 5 be ready?</title>
		<link>http://html5doctor.com/2022-or-when-will-html-5-be-ready/</link>
		<comments>http://html5doctor.com/2022-or-when-will-html-5-be-ready/#comments</comments>
		<pubDate>Tue, 21 Jul 2009 14:19:00 +0000</pubDate>
		<dc:creator>Remy Sharp</dc:creator>
				<category><![CDATA[Browser Compatibility]]></category>
		<category><![CDATA[Quick Tips]]></category>
		<category><![CDATA[HTML 5]]></category>
		<category><![CDATA[Ian Hickson]]></category>
		<category><![CDATA[W3C]]></category>
		<category><![CDATA[WHATWG]]></category>

		<guid isPermaLink="false">http://html5doctor.com/?p=548</guid>
		<description><![CDATA[Aside from being the year Queen Elizabeth II will celebrate her Platinum Jubilee, assuming she's still kicking around, 2022 is the year that's been inappropriately linked with HTML 5 in the minds of a lot of our community.  I understand why someone might think that, but it's wrong.  *2022* was misinterpreted as the year <abbr>HTML</abbr> 5 would be ready.  That's wrong.  <abbr>HTML</abbr> 5 is ready  <strong>today</strong>.]]></description>
			<content:encoded><![CDATA[<p>Aside from being the year Queen Elizabeth II will celebrate her Platinum Jubilee, assuming she&#8217;s still kicking around, 2022 is the year that&#8217;s been inappropriately linked with HTML 5 in the minds of a lot of our community.  </p>

<p>I understand why someone might think that, but it&#8217;s wrong.  <em>2022</em> was misinterpreted as the year <abbr>HTML</abbr> 5 would be ready.  That&#8217;s wrong.  <abbr>HTML</abbr> 5 is ready  <strong>today</strong>.</p>

<p>In an <a href="http://blogs.techrepublic.com.com/programming-and-development/?p=718">interview by Tech Republic</a>, for a techie audience, <a href="http://ln.hixie.ch/" title="Hixie's Natural Log">Ian Hickson</a>, the editor of the HTML 5 working draft, was asked to give a timeline of the HTML 5 recommendation.</p>

<p>One date <em>should</em> have come out of that interview, but another, much further away did instead: 2022 &#8211; the date of the final proposed recommendation, which actually translates to: </p>

<blockquote>
  <p>require at least two browsers to completely pass [<abbr>HTML</abbr> 5 test suites]</p>
</blockquote>

<p>Let&#8217;s put this in context of another spec that has taken a very long time: <abbr>CSS</abbr> 2.1.</p>

<p><abbr>CSS</abbr> 2.1 is <abbr>CSS</abbr> that I&#8217;m <em>certain</em> you&#8217;re familiar with.  I&#8217;m <em>certain</em> you use it day to day without any thought as to whether it&#8217;s a completed spec.  </p>

<p>It&#8217;s been in development for over 10 years, and it&#8217;s <em>only just</em> become a candidate recommendation (23rd April 2009).  </p>

<p>That said, it <strong>doesn&#8217;t</strong> have two browsers completely supporting it.  Only Internet Explorer 8 supports the full <abbr>CSS</abbr> 2.1 spec.  </p>

<p>Did that stop you from using <abbr>CSS</abbr> 2.1?  I suspect not.  Will that stop us from using <abbr>HTML</abbr> 5?  It certainly shouldn&#8217;t. <abbr>HTML</abbr> 5 is available and ready to be used today.</p>

<h2>What <em>is</em> the important <abbr>HTML</abbr> 5 date?</h2>

<p><strong>October 2009</strong>.  </p>

<p>This October is the <em>last call</em> for the <abbr>HTML</abbr> 5 working draft.</p>

<p>That means, that issues with the spec, enhancements, bugs, anything, it all needs to be in and submitted and written in to the spec for October <em>this year</em> (it can go through reiterations, the this is the main deadline).</p>

<p>The <abbr>WHATWG</abbr> is completely open for <em>anyone</em> to contribute their ideas and suggestions.</p>

<p>You can sign up to the <a href="http://www.whatwg.org/mailing-list">mailing lists</a>, look through the backlog of mailing list. You can communicate directly <a href="irc://irc.freenode.net/whatwg">using <abbr>IRC</abbr></a> and there&#8217;s even a complete log of all the <a href="http://krijnhoetmer.nl/irc-logs/"><abbr>IRC</abbr> history</a>.  All available from <a href="http://whatwg.org">http://whatwg.org</a>.
<div id="crp_related"><h3>Related Posts:</h3><ul class="related"><li><a href="http://html5doctor.com/dd-details-wrong-again/" rel="bookmark" class="crp_title">dd-details wrong again</a></li><li><a href="http://html5doctor.com/its-bug-report-time/" rel="bookmark" class="crp_title">It&#8217;s bug report time!</a></li><li><a href="http://html5doctor.com/html-5-boilerplates/" rel="bookmark" class="crp_title">HTML5 Boilerplates</a></li><li><a href="http://html5doctor.com/html5-doctor-drop-in-clinic/" rel="bookmark" class="crp_title">HTML5 Doctor Drop-In Clinic</a></li><li><a href="http://html5doctor.com/your-questions-18/" rel="bookmark" class="crp_title">Your Questions 18</a></li></ul></div></p>
<p><a href="http://html5doctor.com/2022-or-when-will-html-5-be-ready/" rel="bookmark">2022, or when will HTML 5 be ready?</a> originally appeared on <a href="http://html5doctor.com">HTML5 Doctor</a> on July 21, 2009.</p>
]]></content:encoded>
			<wfw:commentRss>http://html5doctor.com/2022-or-when-will-html-5-be-ready/feed/</wfw:commentRss>
		<slash:comments>38</slash:comments>
		</item>
	</channel>
</rss>

