<?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: OpenXML again</title>
	<atom:link href="http://stateless.geek.nz/2007/08/27/openxml-again/feed/" rel="self" type="application/rss+xml" />
	<link>http://stateless.geek.nz/2007/08/27/openxml-again/</link>
	<description></description>
	<lastBuildDate>Wed, 09 May 2012 07:26:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: stateless</title>
		<link>http://stateless.geek.nz/2007/08/27/openxml-again/comment-page-1/#comment-2105</link>
		<dc:creator>stateless</dc:creator>
		<pubDate>Mon, 27 Aug 2007 09:03:57 +0000</pubDate>
		<guid isPermaLink="false">http://stateless.geek.nz/2007/08/27/openxml-again/#comment-2105</guid>
		<description>That is exact the point.

Any document standard will not be defined by what exists now, regardless of how much it is embedded in to culture.  DOC will never be an ISO standard.

However, many in the pro OOXML camp are using this as a reason to claim that OOXML should be a standard.

They are confusing the market position of Microsoft with the needs of a document standard.  Thinking that just because there are a billion plus DOC files out there, that Microsoft will make a better DOC 2.0.

Of course there is probably the other aspect with some people expecting to make money of the transition from DOC to an ISO standard. Given existing partnerships with Microsoft they expect they will have an easier time holding on to their existing markets as well. 

None of this is justification for accepting OOXML as an ISO standard.</description>
		<content:encoded><![CDATA[<p>That is exact the point.</p>
<p>Any document standard will not be defined by what exists now, regardless of how much it is embedded in to culture.  DOC will never be an ISO standard.</p>
<p>However, many in the pro OOXML camp are using this as a reason to claim that OOXML should be a standard.</p>
<p>They are confusing the market position of Microsoft with the needs of a document standard.  Thinking that just because there are a billion plus DOC files out there, that Microsoft will make a better DOC 2.0.</p>
<p>Of course there is probably the other aspect with some people expecting to make money of the transition from DOC to an ISO standard. Given existing partnerships with Microsoft they expect they will have an easier time holding on to their existing markets as well. </p>
<p>None of this is justification for accepting OOXML as an ISO standard.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://stateless.geek.nz/2007/08/27/openxml-again/comment-page-1/#comment-2104</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Mon, 27 Aug 2007 08:54:41 +0000</pubDate>
		<guid isPermaLink="false">http://stateless.geek.nz/2007/08/27/openxml-again/#comment-2104</guid>
		<description>&gt; Business case - Many billion documents in the old format.

I don&#039;t understand this. Nobody is going to convert billions of documents into the &quot;new&quot; format, so the .doc binaries are here to stay for most existing documents. 

But we can *move on* and create new documents with a good quality standard. It&#039;s not like MS Office has a good backwards-compatibility record to start with!</description>
		<content:encoded><![CDATA[<p>&gt; Business case &#8211; Many billion documents in the old format.</p>
<p>I don&#8217;t understand this. Nobody is going to convert billions of documents into the &#8220;new&#8221; format, so the .doc binaries are here to stay for most existing documents. </p>
<p>But we can *move on* and create new documents with a good quality standard. It&#8217;s not like MS Office has a good backwards-compatibility record to start with!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

