<?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: Killing Open Standards Bodies to Tout &#8216;Interoperability&#8217; Meme</title>
	<atom:link href="http://techrights.org/2008/04/25/interoperability-versus-open/feed/" rel="self" type="application/rss+xml" />
	<link>http://techrights.org/2008/04/25/interoperability-versus-open/</link>
	<description>Free Software Sentry – watching and reporting maneuvers of those threatened by software freedom</description>
	<lastBuildDate>Tue, 07 Feb 2012 14:00:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: DarkPhoenix</title>
		<link>http://techrights.org/2008/04/25/interoperability-versus-open/comment-page-1/#comment-8575</link>
		<dc:creator>DarkPhoenix</dc:creator>
		<pubDate>Sun, 27 Apr 2008 22:13:53 +0000</pubDate>
		<guid isPermaLink="false">http://boycottnovell.com/2008/04/25/interoperability-versus-open/#comment-8575</guid>
		<description>Well, it&#039;s hard to say whether splitting up HTML5 would be good or bad.  There are good reasons to do so; it is a rather large specification, and doing it in pieces allows for certain sections to be updated separate from the others.  It works rather well for CSS3, which is coming along nicely (too bad it&#039;s not well implemented outside of Selectors yet).

However, my bet is that Microsoft wants HTML5 split up so they can selectively implement it, like they did with CSS...</description>
		<content:encoded><![CDATA[<p>Well, it&#8217;s hard to say whether splitting up HTML5 would be good or bad.  There are good reasons to do so; it is a rather large specification, and doing it in pieces allows for certain sections to be updated separate from the others.  It works rather well for CSS3, which is coming along nicely (too bad it&#8217;s not well implemented outside of Selectors yet).</p>
<p>However, my bet is that Microsoft wants HTML5 split up so they can selectively implement it, like they did with CSS&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

