<?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 for In Re:</title>
	<atom:link href="http://inre.dundeemt.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://inre.dundeemt.com</link>
	<description>(Because some things just can&#039;t go unsaid)</description>
	<lastBuildDate>Tue, 22 Nov 2005 00:19:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Open Document Format: &#8220;The&#8221; Document Interchange Format by In Re: &#187; Blog Archive &#187; Microsoft to &#8220;Standardize&#8221; file formats&#8230;</title>
		<link>http://inre.dundeemt.com/2005-10-20/open-document-format-the-document-interchange-format/#comment-4</link>
		<dc:creator>In Re: &#187; Blog Archive &#187; Microsoft to &#8220;Standardize&#8221; file formats&#8230;</dc:creator>
		<pubDate>Tue, 22 Nov 2005 00:19:02 +0000</pubDate>
		<guid isPermaLink="false">http://inre.dundeemt.com/?p=12#comment-4</guid>
		<description>[...] Microsoft, today, announced that there were going to &#8220;standardize&#8221; their Office 12 XML file formats. Looks like someone from Microsoft read my article on ODF. But there is an awful lot of word parsing coming out in these announcements. To wit, the use of the phrases, &#8220;standardize&#8221; and &#8220;openess.&#8221; Either they are playing word games to trick the public or the managment at Microsoft. If Microsoft was truly serious they would approach OASIS and participate in the ODF work going on there. [...]</description>
		<content:encoded><![CDATA[<p>[...] Microsoft, today, announced that there were going to &#8220;standardize&#8221; their Office 12 XML file formats. Looks like someone from Microsoft read my article on ODF. But there is an awful lot of word parsing coming out in these announcements. To wit, the use of the phrases, &#8220;standardize&#8221; and &#8220;openess.&#8221; Either they are playing word games to trick the public or the managment at Microsoft. If Microsoft was truly serious they would approach OASIS and participate in the ODF work going on there. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What Microsoft doesn&#8217;t get&#8230; by JeffH</title>
		<link>http://inre.dundeemt.com/2005-10-15/what-microsoft-doesnt-get/#comment-3</link>
		<dc:creator>JeffH</dc:creator>
		<pubDate>Sun, 16 Oct 2005 15:23:06 +0000</pubDate>
		<guid isPermaLink="false">http://inre.dundeemt.com/?p=7#comment-3</guid>
		<description>Have you ever encountered an environment where &quot;used in corporate environments where people collaborate on the same document and publish them directly to the web&quot; was in wide spread and/or continued use?  Word is not a Content Management System in any stretch of the imagination.  It is another example of shoe-horning functionality.  Word is presented by Microsoft as a &lt;a href=&quot;http://snltranscripts.jt.org/75/75ishimmer.phtml&quot; rel=&quot;nofollow&quot;&gt;Shimmer&lt;/a&gt;  type of product.

The argument about the internet is a specious argument, unless you are suggesting that Microsoft knows better than it&#039;s customers.

Yes, I am talking about that IBM.  You, of course, realize that IBM viewed the PC as a mistake and tried to foist &lt;a href=&quot;http://en.wikipedia.org/wiki/Micro_Channel_architecture&quot; rel=&quot;nofollow&quot;&gt;MCA&lt;/a&gt; on the world.  There is example after example of the attempts to herd the computing public back in to the IBM corral.  That same &quot;PC mistake&quot; by IBM launched Microsoft itself.  See what &quot;openess&quot; can do.  It is a very powerful argument against closed, proprietary systems.

Microsoft&#039;s file format for it&#039;s past and currently shipping applications is indeed not open.  I challenge you to submit the link to the specification for any shipping verison of Word.  I present http://www.gnu.org/philosophy/no-word-attachments.html as  defense for my position.  As to MS&#039;s announced file format, I challenge you to prove that MS is and will keep it open and not try to stymie other applications from reading/writing that same format.  Their history does not lend any weight to your argument.

My arguments are neither wrong nor untrue.  I too am a consultant but I champion the cause of my employers not my suppliers.</description>
		<content:encoded><![CDATA[<p>Have you ever encountered an environment where &#8220;used in corporate environments where people collaborate on the same document and publish them directly to the web&#8221; was in wide spread and/or continued use?  Word is not a Content Management System in any stretch of the imagination.  It is another example of shoe-horning functionality.  Word is presented by Microsoft as a <a href="http://snltranscripts.jt.org/75/75ishimmer.phtml" rel="nofollow">Shimmer</a>  type of product.</p>
<p>The argument about the internet is a specious argument, unless you are suggesting that Microsoft knows better than it&#8217;s customers.</p>
<p>Yes, I am talking about that IBM.  You, of course, realize that IBM viewed the PC as a mistake and tried to foist <a href="http://en.wikipedia.org/wiki/Micro_Channel_architecture" rel="nofollow">MCA</a> on the world.  There is example after example of the attempts to herd the computing public back in to the IBM corral.  That same &#8220;PC mistake&#8221; by IBM launched Microsoft itself.  See what &#8220;openess&#8221; can do.  It is a very powerful argument against closed, proprietary systems.</p>
<p>Microsoft&#8217;s file format for it&#8217;s past and currently shipping applications is indeed not open.  I challenge you to submit the link to the specification for any shipping verison of Word.  I present <a href="http://www.gnu.org/philosophy/no-word-attachments.html" rel="nofollow">http://www.gnu.org/philosophy/no-word-attachments.html</a> as  defense for my position.  As to MS&#8217;s announced file format, I challenge you to prove that MS is and will keep it open and not try to stymie other applications from reading/writing that same format.  Their history does not lend any weight to your argument.</p>
<p>My arguments are neither wrong nor untrue.  I too am a consultant but I champion the cause of my employers not my suppliers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What Microsoft doesn&#8217;t get&#8230; by Blake Handler</title>
		<link>http://inre.dundeemt.com/2005-10-15/what-microsoft-doesnt-get/#comment-2</link>
		<dc:creator>Blake Handler</dc:creator>
		<pubDate>Sat, 15 Oct 2005 20:55:04 +0000</pubDate>
		<guid isPermaLink="false">http://inre.dundeemt.com/?p=7#comment-2</guid>
		<description></description>
		<content:encoded><![CDATA[<p>You begin with your “fact” that Microsoft “continually updates things. . . but hardly ever by fixing the brokenness of existing functionality.” </p>
<p>I too am amazed about the amount of “features” that Microsoft continues to cram into their products. And I know that there are plenty of people that are now using the latest version of Microsoft Word – yet only still write simple letters!</p>
<p>The development of software continues at an accelerated rate – unlike the Automobile industry that can wait a year to show off new features.  While Microsoft Word began as just a “word processor” – that same exact program is now used in corporate environments where people collaborate on the same document and publish them directly to the web!</p>
<p>Now I have no problem that many people do not need this functionality. But the home user didn’t think they’d need high-speed Internet access a few years go either.</p>
<p>You mentioned that IBM had lessons to be learned the 90’s due to “their proprietary, non-interoperable tendencies” – huh? Are you talking about the same IBM that gave us the IBM PC – that spawned an entire home computer industry with their VERY OPEN system?????</p>
<p>Microsoft’s file format is NOT a “a closed proprietary file format” it’s well documented – but more importantly the next version of Microsoft Office is completely built on an OPEN file format!</p>
<p>I have no problem when some simply has a bias towards their software due to Security, Features, or simply how it “Looks”. . .but as a Microsoft consultant, it’s frustrating when people dislike their products for the “wrong reasons”</p>
]]></content:encoded>
	</item>
</channel>
</rss>

