<?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: War (on XML), what is it good for?</title>
	<atom:link href="http://philwilson.org/blog/2006/11/war-on-xml-what-is-it-good-for/feed" rel="self" type="application/rss+xml" />
	<link>http://philwilson.org/blog/2006/11/war-on-xml-what-is-it-good-for</link>
	<description>a geek commodity</description>
	<lastBuildDate>Wed, 18 Apr 2012 11:42:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Aristotle Pagaltzis</title>
		<link>http://philwilson.org/blog/2006/11/war-on-xml-what-is-it-good-for/comment-page-1#comment-958</link>
		<dc:creator>Aristotle Pagaltzis</dc:creator>
		<pubDate>Fri, 10 Nov 2006 18:10:00 +0000</pubDate>
		<guid isPermaLink="false">http://philwilson.org/blog/2006/11/war-on-xml-what-is-it-good-for#comment-958</guid>
		<description>Ah, so that is the question. Well, that’s a good guess. I think easy client-side transclusion (some sort of XInclude profile maybe) could have been a killer app. Even just dedicated markup for footnotes, sidenotes and pullquotes might have gotten entire populations of web inhabitants to switch, if coupled with some updates to CSS (consider the accessibility angle here as well as the force of the standards compliance movement among designers creating for the open web). There would quite conceivably have been scope for better SVG integration, as well.&lt;br/&gt;&lt;br/&gt;More ideally, there would have been several iterations by now, so there might have been a confluence of additions, each individually too weak to get any particular publisher to switch, but in combination enticing enough. Heck, people would switch just because of the presence of new and shiny features, even in absence of an immediate need for them.&lt;br/&gt;&lt;br/&gt;Microsoft have been able to afford their torpor because it was simply a reflection of the web’s.</description>
		<content:encoded><![CDATA[<p>Ah, so that is the question. Well, that’s a good guess. I think easy client-side transclusion (some sort of XInclude profile maybe) could have been a killer app. Even just dedicated markup for footnotes, sidenotes and pullquotes might have gotten entire populations of web inhabitants to switch, if coupled with some updates to CSS (consider the accessibility angle here as well as the force of the standards compliance movement among designers creating for the open web). There would quite conceivably have been scope for better SVG integration, as well.</p>
<p>More ideally, there would have been several iterations by now, so there might have been a confluence of additions, each individually too weak to get any particular publisher to switch, but in combination enticing enough. Heck, people would switch just because of the presence of new and shiny features, even in absence of an immediate need for them.</p>
<p>Microsoft have been able to afford their torpor because it was simply a reflection of the web’s.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://philwilson.org/blog/2006/11/war-on-xml-what-is-it-good-for/comment-page-1#comment-957</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 08 Nov 2006 02:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://philwilson.org/blog/2006/11/war-on-xml-what-is-it-good-for#comment-957</guid>
		<description>Why would any monopoly spend money to support an open standard?!</description>
		<content:encoded><![CDATA[<p>Why would any monopoly spend money to support an open standard?!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

