<?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>Coffee on the Keyboard &#187; dom</title>
	<atom:link href="http://coffeeonthekeyboard.com/tag/dom/feed/" rel="self" type="application/rss+xml" />
	<link>http://coffeeonthekeyboard.com</link>
	<description>by James Socol</description>
	<lastBuildDate>Mon, 06 Feb 2012 23:33:42 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/>		<item>
		<title>The W3C Sucks</title>
		<link>http://coffeeonthekeyboard.com/the-w3c-sucks-92/</link>
		<comments>http://coffeeonthekeyboard.com/the-w3c-sucks-92/#comments</comments>
		<pubDate>Thu, 22 May 2008 22:54:53 +0000</pubDate>
		<dc:creator>James</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Standards]]></category>
		<category><![CDATA[Code]]></category>
		<category><![CDATA[dom]]></category>
		<category><![CDATA[html]]></category>
		<category><![CDATA[mathml]]></category>
		<category><![CDATA[things that suck]]></category>
		<category><![CDATA[w3c]]></category>
		<category><![CDATA[xhtml]]></category>
		<category><![CDATA[xml]]></category>

		<guid isPermaLink="false">http://coffeeonthekeyboard.com/the-w3c-sucks-92/</guid>
		<description><![CDATA[&#8220;If you wish to be a success in the world, promise everything, deliver nothing.&#8221; If you want to remain the standard-setting body for the web, promise new recommendations, never deliver. A decade ago, the W3C was actively working to improve the standards we designers and developers use every day. Sure there were some controversial things [...]]]></description>
			<content:encoded><![CDATA[<p>&#8220;If you wish to be a success in the world, promise everything, deliver nothing.&#8221;</p>
<p>If you want to remain the standard-setting body for the web, promise new recommendations, never deliver.<span id="more-92"></span></p>
<div class="image left"><img src="http://coffeeonthekeyboard.com/wp-content/uploads/2008/05/css.png" alt="CSS 2.1 is not even a published recommendation. Off with their (the W3C) heads." style="float: left" /></div>
<p>A decade ago, the <abbr title="World Wide Web Consortium">W3C</abbr> was actively working to improve the standards we designers and developers use every day. Sure there were some controversial things (<abbr title="HyperText Markup Language">HTML</abbr> 3.0, <abbr title="eXtensible Markup Language">XML</abbr> 1.1) that never caught on, but at least there was discussion, thought, and sometimes even action.</p>
<p>The W3C started work on the <abbr title="Cascading Style Sheets">CSS</abbr>3 specification the same year they published CSS2—1998. Ten years later, CSS2.1 is still not technically a published recommendation.</p>
<p>Between 1995, when the W3C was founded, and 1999, HTML went from version 2, an <abbr title="Request For Comments">RFC</abbr>, to version 4.01. Where is 5? In January of <em>this year</em> it became a Working Draft.</p>
<p>When was <abbr title="eXtensible HyperText Markup Language">XHTML</abbr> last updated? 2001. The <abbr title="Document Object Model">DOM</abbr>? 2004. <abbr title="Math Markup Language">MathML</abbr>? 2003.</p>
<p>What happened?</p>
<p>When did &#8220;do nothing group&#8221; replace &#8220;working group&#8221; over there? (Probably around 2004.)</p>
<p>I realize that implementing new standards is not trivial. I also realize that standards are crucial to the continued growth of the web—this site is valid XHTML and uses valid CSS.</p>
<p>However, without updates, these &#8220;standards&#8221; will get old and die. Something else, or someone else, will replace them. We&#8217;ve already used CSS2 for a decade. Will we use it for another? (I want my drop shadows! I want my opacity! I want my rounded corners!)</p>
<p>I lead with a quote from Napoleon, so I&#8217;ll finish with the French Revolution: Off with their heads. The W3C needs a change in leadership or a vigorous shakedown to get off their asses and do something.</p>
<p>If they&#8217;re not willing to put forth the effort, then let them eat cake while someone else does.</p>
]]></content:encoded>
			<wfw:commentRss>http://coffeeonthekeyboard.com/the-w3c-sucks-92/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

