<?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: Why are only Microsoft’s competitors allowed to innovate?</title>
	<atom:link href="http://mustafa.arif.me.uk/node/112/feed" rel="self" type="application/rss+xml" />
	<link>http://mustafa.arif.me.uk/node/112</link>
	<description>Engineer, Londoner, Commentator</description>
	<lastBuildDate>Wed, 25 Jan 2012 03:49:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Blogs, references and hyperlinks at Mustafa Arif</title>
		<link>http://mustafa.arif.me.uk/node/112/comment-page-1#comment-1960</link>
		<dc:creator>Blogs, references and hyperlinks at Mustafa Arif</dc:creator>
		<pubDate>Sun, 03 Dec 2006 05:56:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.mustafa.arif.me.uk/node/112#comment-1960</guid>
		<description>[...] Recently I’ve been guilty of taking this “hyperlink the reference” approach too literally. You may have noticed that many of my posts have involved a long reference in square brackets. Take, as an example, the post Why are only Microsoft’s competitors allowed to innovate? The use of hyperlinks as references in there is clearly wrong. It is unsightly and detracts from the subject matter. In retrospect the real problem is failing to understand that whilst a hyperlink need not always be a reference, a reference need not always be a hyperlink (at least not to another page). When we have long things to cite, perhaps the best way to reference, without compromising writing style is to make use of good old-fashioned footnotes in web pages [SmackTheMouse.com]. [...]</description>
		<content:encoded><![CDATA[<p>[...] Recently I’ve been guilty of taking this “hyperlink the reference” approach too literally. You may have noticed that many of my posts have involved a long reference in square brackets. Take, as an example, the post Why are only Microsoft’s competitors allowed to innovate? The use of hyperlinks as references in there is clearly wrong. It is unsightly and detracts from the subject matter. In retrospect the real problem is failing to understand that whilst a hyperlink need not always be a reference, a reference need not always be a hyperlink (at least not to another page). When we have long things to cite, perhaps the best way to reference, without compromising writing style is to make use of good old-fashioned footnotes in web pages [SmackTheMouse.com]. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mustafa Arif</title>
		<link>http://mustafa.arif.me.uk/node/112/comment-page-1#comment-1923</link>
		<dc:creator>Mustafa Arif</dc:creator>
		<pubDate>Fri, 24 Nov 2006 01:31:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.mustafa.arif.me.uk/node/112#comment-1923</guid>
		<description>No, I was blaming legislators and competition authorities...</description>
		<content:encoded><![CDATA[<p>No, I was blaming legislators and competition authorities&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Saracen</title>
		<link>http://mustafa.arif.me.uk/node/112/comment-page-1#comment-1914</link>
		<dc:creator>Saracen</dc:creator>
		<pubDate>Tue, 21 Nov 2006 11:49:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.mustafa.arif.me.uk/node/112#comment-1914</guid>
		<description>No problem all. But these are the downsides of commercial business. Can&#039;t blame Adobe, or MS; it&#039;s what they&#039;re programmed to do.</description>
		<content:encoded><![CDATA[<p>No problem all. But these are the downsides of commercial business. Can&#8217;t blame Adobe, or MS; it&#8217;s what they&#8217;re programmed to do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mustafa Arif</title>
		<link>http://mustafa.arif.me.uk/node/112/comment-page-1#comment-1913</link>
		<dc:creator>Mustafa Arif</dc:creator>
		<pubDate>Tue, 21 Nov 2006 10:41:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.mustafa.arif.me.uk/node/112#comment-1913</guid>
		<description>What on earth is the problem with Microsoft creating their own open document specfication? Microsoft Office documents are already a &lt;i&gt;de facto&lt;/i&gt; standard, adopted by the market. An open specification for Office documents, enabling other software publishers to write compatible software, would be no bad thing for consumer choice. If it topples PDF, so be it. PDF is clearly not good enough given that it has failed to supercede MS Office formats for everyday work. Consumers should not have to be forced to download a plugin. If there is consumer demand MS should be able to bundle the software.</description>
		<content:encoded><![CDATA[<p>What on earth is the problem with Microsoft creating their own open document specfication? Microsoft Office documents are already a <i>de facto</i> standard, adopted by the market. An open specification for Office documents, enabling other software publishers to write compatible software, would be no bad thing for consumer choice. If it topples PDF, so be it. PDF is clearly not good enough given that it has failed to supercede MS Office formats for everyday work. Consumers should not have to be forced to download a plugin. If there is consumer demand MS should be able to bundle the software.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Saracen</title>
		<link>http://mustafa.arif.me.uk/node/112/comment-page-1#comment-1912</link>
		<dc:creator>Saracen</dc:creator>
		<pubDate>Tue, 21 Nov 2006 10:13:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.mustafa.arif.me.uk/node/112#comment-1912</guid>
		<description>Link: http://news.zdnet.com/2100-3513-6079320.html

Note where they said they&#039;ve been forced to remove both.</description>
		<content:encoded><![CDATA[<p>Link: <a href="http://news.zdnet.com/2100-3513-6079320.html" rel="nofollow">http://news.zdnet.com/2100-3513-6079320.html</a></p>
<p>Note where they said they&#8217;ve been forced to remove both.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Saracen</title>
		<link>http://mustafa.arif.me.uk/node/112/comment-page-1#comment-1911</link>
		<dc:creator>Saracen</dc:creator>
		<pubDate>Tue, 21 Nov 2006 10:11:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.mustafa.arif.me.uk/node/112#comment-1911</guid>
		<description>There is conjecture that MS wanted to add the PDF capability into Vista in order to avoid Antitrust suits in bundling its own &quot;XML Paper Specification&quot;, since that would preclude charges of taking advantage of market dominance. Adobe probably felt that this would then lead to MS pushing XPS, and eventually toppling PDF, quite likely, depending on how each was made to function.

Might be an interesting angle, and I wouldn&#039;t put it beyond MS!</description>
		<content:encoded><![CDATA[<p>There is conjecture that MS wanted to add the PDF capability into Vista in order to avoid Antitrust suits in bundling its own &#8220;XML Paper Specification&#8221;, since that would preclude charges of taking advantage of market dominance. Adobe probably felt that this would then lead to MS pushing XPS, and eventually toppling PDF, quite likely, depending on how each was made to function.</p>
<p>Might be an interesting angle, and I wouldn&#8217;t put it beyond MS!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

