<?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>Promise of OOXML Oversight By ISO Falls Through</title>
		<link>http://www.noooxml.org/forum/t-30225/promise-of-ooxml-oversight-by-iso-falls-through</link>
		<description>Posts in the discussion thread &quot;Promise of OOXML Oversight By ISO Falls Through&quot; - Rob Weir reports that MSFT is backtracking on its promise to let ISO have oversight of and possible OOXML standard.</description>
				<copyright></copyright>
		<lastBuildDate></lastBuildDate>
		
					<item>
				<guid>http://www.noooxml.org/forum/t-30225#post-76803</guid>
				<title>Promise of OOXML Oversight By ISO Falls Through</title>
				<link>http://www.noooxml.org/forum/t-30225/promise-of-ooxml-oversight-by-iso-falls-through#post-76803</link>
				<description></description>
				<pubDate>Fri, 07 Dec 2007 14:59:53 +0000</pubDate>
				<wikidot:authorName>ggiedke</wikidot:authorName>				<wikidot:authorUserId>32664</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>In his Dec 6 blog entry<br /> <a href="http://www.robweir.com/blog/">http://www.robweir.com/blog/</a><br /> reports how Microsoft first promised through many spokespeople that stewardship of OOXML would be handed over to ISO, but "Ecma's "<em>Proposal for a Joint Maintenance Plan" [pdf] outlines quite a different vision for how OOXML will be maintained. A summary of the proposed terms:<br /> * OOXML remains under Ecma (Microsoft) control under Ecma IPR policy.<br /> * Ecma TC45 will accept a liaison from JTC1/SC34 who can participate on maintenance activities and only maintenance activities.<br /> * […]</em>"</p> <p>There are discussions at Groklaw <a href="http://www.groklaw.net/article.php?story=20071206131310362">http://www.groklaw.net/article.php?story=20071206131310362</a> and Slashdot <a href="http://slashdot.org/article.pl?sid=07/12/06/2129203">http://slashdot.org/article.pl?sid=07/12/06/2129203</a> on this news.</p> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>