<?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: Standards and standarisation</title>
	<atom:link href="http://blogs.gnome.org/uraeus/2006/04/05/standards-and-standarisation/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/uraeus/2006/04/05/standards-and-standarisation/</link>
	<description>GStreamer and Collabora news and more</description>
	<lastBuildDate>Sun, 29 Jan 2012 18:31:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Chris Hubick</title>
		<link>http://blogs.gnome.org/uraeus/2006/04/05/standards-and-standarisation/comment-page-1/#comment-326</link>
		<dc:creator>Chris Hubick</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/uraeus/2006/04/05/standards-and-standarisation/#comment-326</guid>
		<description>I think it depends on what you want standards for.  I value standards which ensure my freedom of choice.  If I rely on a piece of software for something critical, and it malfunctions, I either want the ability to fix it myself, or the ability to swap it out for an alternative implementation.  In the proprietary software world, having standards is what allows for such interchangeability of implementations.  In the Free Software world however, we are generally free to fix problems ourself, so standards may not be of quite such critical importance.&lt;p/&gt;Standards for things such as Binary compatibility are just to save people work having to track a changing ABI.  Saving some work isn&#039;t a major concern to me, as worst case you just have to upgrade your code yet again.&lt;p/&gt;The scariest scenario to me is some global standard like HTML being coopted so that it would only work in Internet Explorer, and becoming a defacto standard, eventually resulting in a single company like Microsoft being able to control the direction of the entire basis behind our information society (the web), leaving things like Linux (and my freedom of choice) out in the cold.&lt;br/&gt;</description>
		<content:encoded><![CDATA[<p>I think it depends on what you want standards for.  I value standards which ensure my freedom of choice.  If I rely on a piece of software for something critical, and it malfunctions, I either want the ability to fix it myself, or the ability to swap it out for an alternative implementation.  In the proprietary software world, having standards is what allows for such interchangeability of implementations.  In the Free Software world however, we are generally free to fix problems ourself, so standards may not be of quite such critical importance.
<p />Standards for things such as Binary compatibility are just to save people work having to track a changing ABI.  Saving some work isn&#8217;t a major concern to me, as worst case you just have to upgrade your code yet again.
<p />The scariest scenario to me is some global standard like HTML being coopted so that it would only work in Internet Explorer, and becoming a defacto standard, eventually resulting in a single company like Microsoft being able to control the direction of the entire basis behind our information society (the web), leaving things like Linux (and my freedom of choice) out in the cold.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leandro GFC DUTRA</title>
		<link>http://blogs.gnome.org/uraeus/2006/04/05/standards-and-standarisation/comment-page-1/#comment-327</link>
		<dc:creator>Leandro GFC DUTRA</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/uraeus/2006/04/05/standards-and-standarisation/#comment-327</guid>
		<description>You can only standardise sanely when you have a pretty good idea about the field.&lt;p/&gt;For example, SQL was standardised before people understood the relational model for database management.  Therefore, it is an unfixable mess which has to be replaced at enormous cost.&lt;br/&gt;</description>
		<content:encoded><![CDATA[<p>You can only standardise sanely when you have a pretty good idea about the field.
<p />For example, SQL was standardised before people understood the relational model for database management.  Therefore, it is an unfixable mess which has to be replaced at enormous cost.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  blogs.gnome.org/uraeus/2006/04/05/standards-and-standarisation/feed/ ) in 0.13741 seconds, on Feb 11th, 2012 at 2:20 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 11th, 2012 at 3:20 am UTC -->
