<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: A Foolish Inconsistency</title>
	<atom:link href="http://www.robweir.com/blog/2007/01/foolish-inconsistency.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.robweir.com/blog/2007/01/foolish-inconsistency.html</link>
	<description>Thinking the unthinkable, pondering the imponderable, effing the ineffable and scruting the inscrutable</description>
	<lastBuildDate>Tue, 16 Mar 2010 23:56:05 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Wesley Parish</title>
		<link>http://www.robweir.com/blog/2007/01/foolish-inconsistency.html#comment-343</link>
		<dc:creator>Wesley Parish</dc:creator>
		<pubDate>Tue, 23 Jan 2007 09:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2007/01/a-foolish-inconsistency.html#comment-343</guid>
		<description>Rob, have a read of &quot;Who Invented What When&quot;, by David Ellyard, New Holland, 2006, ISBN 17410488-2.  One of the points made in it is the importance of standards in establishing a technological civilization.&lt;br /&gt;&lt;br /&gt;Perhaps you could do a standards-oriented review of the book?</description>
		<content:encoded><![CDATA[<p>Rob, have a read of &#8220;Who Invented What When&#8221;, by David Ellyard, New Holland, 2006, ISBN 17410488-2.  One of the points made in it is the importance of standards in establishing a technological civilization.</p>
<p>Perhaps you could do a standards-oriented review of the book?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://www.robweir.com/blog/2007/01/foolish-inconsistency.html#comment-337</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Mon, 22 Jan 2007 14:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2007/01/a-foolish-inconsistency.html#comment-337</guid>
		<description>John,&lt;br /&gt;&lt;br /&gt;Thanks for making your opinion count.  I should note that other countries have their own national standards bodies.  A list of JTC1 NB members for other nations, as well as contact information is on GrokLaw &lt;a href=&quot;http://www.grokdoc.net/index.php/EOOXML_Contacts&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Although JTC1 has not issued a public &quot;call for comments&quot; or anything like that, it can&#039;t hurt to express your informed opinion, in a polite way to those who represent your country in the international standards arena.</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>Thanks for making your opinion count.  I should note that other countries have their own national standards bodies.  A list of JTC1 NB members for other nations, as well as contact information is on GrokLaw <a href="http://www.grokdoc.net/index.php/EOOXML_Contacts" rel="nofollow">here</a>.</p>
<p>Although JTC1 has not issued a public &#8220;call for comments&#8221; or anything like that, it can&#8217;t hurt to express your informed opinion, in a polite way to those who represent your country in the international standards arena.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.robweir.com/blog/2007/01/foolish-inconsistency.html#comment-331</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sun, 21 Jan 2007 17:15:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2007/01/a-foolish-inconsistency.html#comment-331</guid>
		<description>When the railroads were being built each company build the rails to&lt;br /&gt;their own gauge. When goods travelling on one company&#039;s railroad reached another company&#039;s, the goods had to be manhandled from one set of wagons to another.&lt;br /&gt;&lt;br /&gt;Microsoft seems to have a railroad system with many different gauges,&lt;br /&gt;different rolling stock sizes and signalling conventions — there are&lt;br /&gt;even signals which show Red for Go and Green for Stop: a mistake was&lt;br /&gt;made, the Microsoft drivers know about it and it is too much trouble to change it now.&lt;br /&gt;&lt;br /&gt;Anybody wanting to transport their goods over Microsoft&#039;s system has to transfer them to Microsoft rolling stock — and they then can&#039;t be transferred back out again undamaged.&lt;br /&gt;&lt;br /&gt;What people want is a railway system that covers the country: with one gauge, one set of height and width limits for rolling stock and a clearly defined signalling system with no secret bits that one company can use to make things more difficult or expensive for its competitors.</description>
		<content:encoded><![CDATA[<p>When the railroads were being built each company build the rails to<br />their own gauge. When goods travelling on one company&#8217;s railroad reached another company&#8217;s, the goods had to be manhandled from one set of wagons to another.</p>
<p>Microsoft seems to have a railroad system with many different gauges,<br />different rolling stock sizes and signalling conventions — there are<br />even signals which show Red for Go and Green for Stop: a mistake was<br />made, the Microsoft drivers know about it and it is too much trouble to change it now.</p>
<p>Anybody wanting to transport their goods over Microsoft&#8217;s system has to transfer them to Microsoft rolling stock — and they then can&#8217;t be transferred back out again undamaged.</p>
<p>What people want is a railway system that covers the country: with one gauge, one set of height and width limits for rolling stock and a clearly defined signalling system with no secret bits that one company can use to make things more difficult or expensive for its competitors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Hardin</title>
		<link>http://www.robweir.com/blog/2007/01/foolish-inconsistency.html#comment-324</link>
		<dc:creator>John Hardin</dc:creator>
		<pubDate>Sat, 20 Jan 2007 17:28:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2007/01/a-foolish-inconsistency.html#comment-324</guid>
		<description>The ANSI represents the American public to the ISO. Contact them with your comments!&lt;br /&gt;&lt;br /&gt;Fire up your mail clients and drop a (polite, technically meritorious) email to &lt;isot@ansi.org&gt;, or fax something to:&lt;br /&gt;&lt;br /&gt;Scully, Henrietta&lt;br /&gt;Program Manager, Standards Facilitation (ISOT)&lt;br /&gt;fax: 212.730.1346&lt;br /&gt;&lt;br /&gt;Cornish, Steven P.&lt;br /&gt;Program Director, International Policy&lt;br /&gt;fax: 212.730.1346&lt;br /&gt;&lt;br /&gt;Kushnier, Gary W.&lt;br /&gt;Vice President, International Policy&lt;br /&gt;fax: 202.293.9287&lt;br /&gt;&lt;br /&gt;Rajchel, Lisa&lt;br /&gt;Director, International Secretariats Standards Facilitation&lt;br /&gt;fax: 212.840.2298&lt;br /&gt;&lt;br /&gt;The more protests they get, the more likely our voices are to be heard at the ISO.&lt;br /&gt;&lt;br /&gt;I will post my letter on my website (click my name above as soon as it&#039;s sent.</description>
		<content:encoded><![CDATA[<p>The ANSI represents the American public to the ISO. Contact them with your comments!</p>
<p>Fire up your mail clients and drop a (polite, technically meritorious) email to &lt;isot@ansi.org&gt;, or fax something to:</p>
<p>Scully, Henrietta<br />Program Manager, Standards Facilitation (ISOT)<br />fax: 212.730.1346</p>
<p>Cornish, Steven P.<br />Program Director, International Policy<br />fax: 212.730.1346</p>
<p>Kushnier, Gary W.<br />Vice President, International Policy<br />fax: 202.293.9287</p>
<p>Rajchel, Lisa<br />Director, International Secretariats Standards Facilitation<br />fax: 212.840.2298</p>
<p>The more protests they get, the more likely our voices are to be heard at the ISO.</p>
<p>I will post my letter on my website (click my name above as soon as it&#8217;s sent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GaryEdwards</title>
		<link>http://www.robweir.com/blog/2007/01/foolish-inconsistency.html#comment-321</link>
		<dc:creator>GaryEdwards</dc:creator>
		<pubDate>Fri, 19 Jan 2007 22:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2007/01/a-foolish-inconsistency.html#comment-321</guid>
		<description>Thanks Rob.  You&#039;re absolutely precious. &lt;br /&gt;&lt;br /&gt;Isn&#039;t it strange that ISO/IEC JTC1 has it in their reach to do what no government body has been able to achieve?  &lt;br /&gt;&lt;br /&gt;ISO can restore competition to the desktop productivity environment simply by rejecting MOOX based on the massive contradictions it poses to existing ISO products.  They can break the monopolist grip, leveling the playing field in ways that the hapless and hopeless USA Anti Trust action/settlement sadly failed to do.  &lt;br /&gt;&lt;br /&gt;So here we are.  A cornerstone for the future of the Open Internet, where desktop, server and device systems globally connect and exchange information with ease, is now in the hands of ISO/IEC JTC1 representatives.  &lt;br /&gt;&lt;br /&gt;If they stand by ODF, alternatives to MSOffice and the Vista Information Processing Chain will finally have their shot. &lt;br /&gt;&lt;br /&gt;If they stand by ODF, the risk of investing in alternatives to Microsoft products will significantly decrease.  And when that happens, governments demanding ODF solutions will finally have access to the kind of alternative applications that will make sense of what is today an impossible challenge - making the real world migration from MSOffice bound business processes and information systems to ODF enabled systems.  Systems where open Internet aggregates of SaaS, SOA, Web 2.0 Hubs, and enterprise publication, content and archive management systems can easily connect and exchange info with desktop productivity systems.&lt;br /&gt;&lt;br /&gt;The ISO/IEC decision comes at a most important moment in time.  Microsoft is nearing a moment when they finally have all the pieces in place to effectively leverage their desktop monopoly into server, device and Internet systems markets.  The MS product pipeline for this push, the Vista Stack, is filled with systems, services and applications that have one undeniable advantage over all competitors - integration with the MSOffice bound desktop.  &lt;br /&gt;&lt;br /&gt;The MS server, device and Internet systems all feature advanced integration with the MSOffice productivity environment.  A level of integration that can&#039;t be touched by competitors.  Even those entrenched in enterprise services such as Oracle, Sun and IBM. &lt;br /&gt;&lt;br /&gt;At the heart of this &quot;advanced integration&quot; is control over desktop productivity file formats.  Of course Microsoft markets this monopolist exclusive integration advantage as the most helpful and harmless sounding &quot;interoperability by design&quot;.  The truth is that this monopolist expansion ploy depends in large part on MSOffice information and information processes remaining bound to Microsoft applications and systems.  Bound even as that information moves across the Internet using MOOX as the transport, from  Microsoft desktops, to the MS E/S Hub, to MSOffice Groove, to MSLive, to MS CRM, integrating with backend MS SQL Server systems.&lt;br /&gt;&lt;br /&gt;ODF was designed to be application and platform independent.  MOOX was not.  It&#039;s time for ISO/IEC to speak, and by so doing, change the world.&lt;br /&gt;&lt;br /&gt;~ge~</description>
		<content:encoded><![CDATA[<p>Thanks Rob.  You&#8217;re absolutely precious. </p>
<p>Isn&#8217;t it strange that ISO/IEC JTC1 has it in their reach to do what no government body has been able to achieve?  </p>
<p>ISO can restore competition to the desktop productivity environment simply by rejecting MOOX based on the massive contradictions it poses to existing ISO products.  They can break the monopolist grip, leveling the playing field in ways that the hapless and hopeless USA Anti Trust action/settlement sadly failed to do.  </p>
<p>So here we are.  A cornerstone for the future of the Open Internet, where desktop, server and device systems globally connect and exchange information with ease, is now in the hands of ISO/IEC JTC1 representatives.  </p>
<p>If they stand by ODF, alternatives to MSOffice and the Vista Information Processing Chain will finally have their shot. </p>
<p>If they stand by ODF, the risk of investing in alternatives to Microsoft products will significantly decrease.  And when that happens, governments demanding ODF solutions will finally have access to the kind of alternative applications that will make sense of what is today an impossible challenge &#8211; making the real world migration from MSOffice bound business processes and information systems to ODF enabled systems.  Systems where open Internet aggregates of SaaS, SOA, Web 2.0 Hubs, and enterprise publication, content and archive management systems can easily connect and exchange info with desktop productivity systems.</p>
<p>The ISO/IEC decision comes at a most important moment in time.  Microsoft is nearing a moment when they finally have all the pieces in place to effectively leverage their desktop monopoly into server, device and Internet systems markets.  The MS product pipeline for this push, the Vista Stack, is filled with systems, services and applications that have one undeniable advantage over all competitors &#8211; integration with the MSOffice bound desktop.  </p>
<p>The MS server, device and Internet systems all feature advanced integration with the MSOffice productivity environment.  A level of integration that can&#8217;t be touched by competitors.  Even those entrenched in enterprise services such as Oracle, Sun and IBM. </p>
<p>At the heart of this &#8220;advanced integration&#8221; is control over desktop productivity file formats.  Of course Microsoft markets this monopolist exclusive integration advantage as the most helpful and harmless sounding &#8220;interoperability by design&#8221;.  The truth is that this monopolist expansion ploy depends in large part on MSOffice information and information processes remaining bound to Microsoft applications and systems.  Bound even as that information moves across the Internet using MOOX as the transport, from  Microsoft desktops, to the MS E/S Hub, to MSOffice Groove, to MSLive, to MS CRM, integrating with backend MS SQL Server systems.</p>
<p>ODF was designed to be application and platform independent.  MOOX was not.  It&#8217;s time for ISO/IEC to speak, and by so doing, change the world.</p>
<p>~ge~</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: W^L+</title>
		<link>http://www.robweir.com/blog/2007/01/foolish-inconsistency.html#comment-318</link>
		<dc:creator>W^L+</dc:creator>
		<pubDate>Fri, 19 Jan 2007 04:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2007/01/a-foolish-inconsistency.html#comment-318</guid>
		<description>A comment on Bryan Smith&#039;s history http://thebs413.blogspot.com/2007/01/office-suites-opendocument-and-openxml.html led me to something pertinent Joel Spolsky said.  Joel&#039;s post, http://www.joelonsoftware.com/articles/fog0000000052.html explains a lot.</description>
		<content:encoded><![CDATA[<p>A comment on Bryan Smith&#8217;s history <a href="http://thebs413.blogspot.com/2007/01/office-suites-opendocument-and-openxml.html" rel="nofollow">http://thebs413.blogspot.com/2007/01/office-suites-opendocument-and-openxml.html</a> led me to something pertinent Joel Spolsky said.  Joel&#8217;s post, <a href="http://www.joelonsoftware.com/articles/fog0000000052.html" rel="nofollow">http://www.joelonsoftware.com/articles/fog0000000052.html</a> explains a lot.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.437 seconds -->
