<?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"
	>
<channel>
	<title>Comments on: Question: what makes standards succeed?</title>
	<atom:link href="http://www.rnib.org.uk/wacblog/standards/question-what-makes-standards-succeed/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rnib.org.uk/wacblog/standards/question-what-makes-standards-succeed/</link>
	<description></description>
	<pubDate>Mon, 13 Oct 2008 05:08:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Ozbon</title>
		<link>http://www.rnib.org.uk/wacblog/standards/question-what-makes-standards-succeed/#comment-50822</link>
		<dc:creator>Ozbon</dc:creator>
		<pubDate>Mon, 14 Jan 2008 11:17:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/policy/question-what-makes-standards-succeed/#comment-50822</guid>
		<description>Much as I hate myself for saying it, one of the big steps - with internet standards at least - is to get Microsoft to be behind the standard (rather than using one of their own).

MS is still the biggest OS (by a significant margin) and IE is the biggest browser (which makes me despair, but there we go) - if IE were actually standards compliant, most websites would be written to be IE compatible and thus standards compatible.

Making IE into an MS-Standard is the primary reason so many other standards (accessibility in particular) fall by the wayside. With the biggest market share, most companies still  don't give a stuff if their site is standards compliant, so long as it works in IE. I always work to make sure my sites do both, but commercially it'll always be "IE" that takes precedence instead of "standards" until/unless MS adopt the same standards as everyone else.

Sad (and possibly heretical) but still true.</description>
		<content:encoded><![CDATA[<p>Much as I hate myself for saying it, one of the big steps - with internet standards at least - is to get Microsoft to be behind the standard (rather than using one of their own).</p>
<p>MS is still the biggest OS (by a significant margin) and IE is the biggest browser (which makes me despair, but there we go) - if IE were actually standards compliant, most websites would be written to be IE compatible and thus standards compatible.</p>
<p>Making IE into an MS-Standard is the primary reason so many other standards (accessibility in particular) fall by the wayside. With the biggest market share, most companies still  don&#8217;t give a stuff if their site is standards compliant, so long as it works in IE. I always work to make sure my sites do both, but commercially it&#8217;ll always be &#8220;IE&#8221; that takes precedence instead of &#8220;standards&#8221; until/unless MS adopt the same standards as everyone else.</p>
<p>Sad (and possibly heretical) but still true.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henny</title>
		<link>http://www.rnib.org.uk/wacblog/standards/question-what-makes-standards-succeed/#comment-45755</link>
		<dc:creator>Henny</dc:creator>
		<pubDate>Mon, 26 Nov 2007 13:42:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/policy/question-what-makes-standards-succeed/#comment-45755</guid>
		<description>Thanks Jack and Jean for your thoughts, couldn't agree with you more. Looks like standards are on a lot of people's minds today as it is &lt;a href="http://www.webstandards.org/2007/11/23/wear-the-blue-beanie-with-pride/" rel="nofollow"&gt;Blue Beanie Day&lt;/a&gt;  - a day for promoting web standards by wearing a blue beanie.

I also stumbled acorss this artical &lt;a href="http://lawver.net/archive/2007/11/12/h17_web_standards_three_buckets_of_pain.php" rel="nofollow"&gt;Web Standards - Three Buckets of Pain&lt;/a&gt; also inspired by the talks help at the November W3C Technical Plenary. Worth a read.</description>
		<content:encoded><![CDATA[<p>Thanks Jack and Jean for your thoughts, couldn&#8217;t agree with you more. Looks like standards are on a lot of people&#8217;s minds today as it is <a href="http://www.webstandards.org/2007/11/23/wear-the-blue-beanie-with-pride/" rel="nofollow">Blue Beanie Day</a>  - a day for promoting web standards by wearing a blue beanie.</p>
<p>I also stumbled acorss this artical <a href="http://lawver.net/archive/2007/11/12/h17_web_standards_three_buckets_of_pain.php" rel="nofollow">Web Standards - Three Buckets of Pain</a> also inspired by the talks help at the November W3C Technical Plenary. Worth a read.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean S</title>
		<link>http://www.rnib.org.uk/wacblog/standards/question-what-makes-standards-succeed/#comment-45267</link>
		<dc:creator>Jean S</dc:creator>
		<pubDate>Thu, 22 Nov 2007 13:39:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/policy/question-what-makes-standards-succeed/#comment-45267</guid>
		<description>The standards have to be from a reputable source so that they can be trusted to have been thought out and tested. If I'm to sell them to my peers and advise they be adopted I need to know they're worth adopting.</description>
		<content:encoded><![CDATA[<p>The standards have to be from a reputable source so that they can be trusted to have been thought out and tested. If I&#8217;m to sell them to my peers and advise they be adopted I need to know they&#8217;re worth adopting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JackP</title>
		<link>http://www.rnib.org.uk/wacblog/standards/question-what-makes-standards-succeed/#comment-44112</link>
		<dc:creator>JackP</dc:creator>
		<pubDate>Tue, 13 Nov 2007 14:11:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/policy/question-what-makes-standards-succeed/#comment-44112</guid>
		<description>The standards have to be clear, at least &lt;em&gt;relatively&lt;/em&gt; concise (e.g. WCAG 2 isn't, but the quick reference document serves as a concise version), but above all they have to be &lt;strong&gt;useful&lt;/strong&gt;.

It also helps if there is either a carrot (my site will be better if I adopt these standards) or a stick (nasty thing &lt;em&gt;X&lt;/em&gt; will happen if I don't adopt these standards).</description>
		<content:encoded><![CDATA[<p>The standards have to be clear, at least <em>relatively</em> concise (e.g. WCAG 2 isn&#8217;t, but the quick reference document serves as a concise version), but above all they have to be <strong>useful</strong>.</p>
<p>It also helps if there is either a carrot (my site will be better if I adopt these standards) or a stick (nasty thing <em>X</em> will happen if I don&#8217;t adopt these standards).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
