<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wikidot="http://www.wikidot.com/rss-namespace">

	<channel>
		<title>OOXML as a response</title>
		<link>http://www.noooxml.org/forum/t-179085/ooxml-as-a-response</link>
		<description>Posts in the discussion thread &quot;OOXML as a response&quot; - Why did OOXML come into existence?</description>
				<copyright></copyright>
		<lastBuildDate>Wed, 08 Feb 2012 09:35:13 +0000</lastBuildDate>
		
					<item>
				<guid>http://www.noooxml.org/forum/t-179085#post-572104</guid>
				<title>OOXML as a response</title>
				<link>http://www.noooxml.org/forum/t-179085/ooxml-as-a-response#post-572104</link>
				<description></description>
				<pubDate>Sat, 29 Aug 2009 18:59:49 +0000</pubDate>
				<wikidot:authorName>arebenti</wikidot:authorName>				<wikidot:authorUserId>36024</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>James D. Mason <a href="http://blogs.computerworld.com/14532/microsoft_banned_from_selling_word#comment-153527">says</a>:</p> <blockquote> <p>I spent 22 years as the chairman of what is now ISO/IEC JTC1/SC34. SC34 is the committee that standardized SGML in the 1980s and now is responsible for both ODF, supported by many open-source products, and OOXML, <strong>the XML released by Microsoft in response to ODF</strong>. Neither ODF nor OOXML has anything to do with ODA/ODIF, which have been dormant since the turn of the current century but were still under development in the 1990s in a committee that was parallel to the one that became SC34.</p> </blockquote> <p>Our past analysis: OOXML is a response. Thank you very much for the confirmation. Stronger language from Mason found <a href="http://www.builderau.com.au/news/soa/OOXML-just-a-Microsoft-marketing-tool-/0,339028227,339288289,00.htm">in this article</a>.</p> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>
