<?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>Open XML, the standard that was not</title>
		<link>http://www.noooxml.org/forum/t-148110/open-xml-the-standard-that-was-not</link>
		<description>Posts in the discussion thread &quot;Open XML, the standard that was not&quot; - Many neutral BRM observers felt screwed up and they get more and more evidence that their feelings were right. Open XML proponents become twitter jerks.</description>
				<copyright></copyright>
		<lastBuildDate>Wed, 08 Feb 2012 09:32:11 +0000</lastBuildDate>
		
					<item>
				<guid>http://www.noooxml.org/forum/t-148110#post-452110</guid>
				<title>Re: Open XML, the standard that was not</title>
				<link>http://www.noooxml.org/forum/t-148110/open-xml-the-standard-that-was-not#post-452110</link>
				<description></description>
				<pubDate>Fri, 17 Apr 2009 14:41:38 +0000</pubDate>
				<wikidot:authorName>zoobab</wikidot:authorName>				<wikidot:authorUserId>2946</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Look at this one:</p> <p><a href="http://www.itscj.ipsj.or.jp/sc34/wg4/archive/sc34-wg4-2009-0036.pdf">http://www.itscj.ipsj.or.jp/sc34/wg4/archive/sc34-wg4-2009-0036.pdf</a></p> <p>29500 Defects: Explanation of whether to resolve defects by Corrigendum or by Amendment</p> <blockquote> <p>Defects in ISO/IEC 29500:2008<br /> Explanation of whether to resolve defects<br /> by Corrigendum or by Amendment<br /> ISO/IEC JTC 1/SC 34/WG4<br /> 2009-03-26<br /> […]</p> <p>However, ISO/IEC 29500 is a very large and complex multi-part standard, and <strong>it is not surprising that the text contains many unintentional technical defects</strong>, which nevertheless don't make it impossible to implement the standard.</p> <p>In the course of drafting, some existing office document features were unintentionally overlooked, which result in it being impossible to fully represent some of the <strong>corpus of existing documents</strong> in ISO/IEC 29500.</p> </blockquote> <p>The corpus of existing documents means Office 2007 documents, which is an undocumented file format.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://www.noooxml.org/forum/t-148110#post-452102</guid>
				<title>Open XML, the standard that was not</title>
				<link>http://www.noooxml.org/forum/t-148110/open-xml-the-standard-that-was-not#post-452102</link>
				<description></description>
				<pubDate>Fri, 17 Apr 2009 14:30:08 +0000</pubDate>
				<wikidot:authorName>podmokle</wikidot:authorName>				<wikidot:authorUserId>3547</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Homembit presents <a href="http://homembit.com/2009/04/for-the-skeptical-the-final-proof-the-openxml-wasnt-and-isnt-ready.html">the final proof</a> as he calls it that ISO Open XML wasn't ready to get adopted:</p> <blockquote> <p>The document N1101/N1168 contains for example, several items in which they recognize that there are <strong>decisions made in the BRM (BRM resolutions) which were not incorporated into the final published text of the standard</strong>. In other words, even taking almost a year after the aproval of the standard to publish the text (yes, approved without reading), there wasn’t time/attention or anything else necessary to assure that the changes were published in the text (most of those changes, “conditioned” the approval). What makes me much more angry about this is that during the BRM I asked about who would be responsible for verifying that all these changes would be part of the final text and the answer was ITTF (kind of joint ISO/IEC secretariat).</p> </blockquote> <p>He may be wrong that this is the <strong>final proof</strong> of misconduct at the BRM under the lead of Alex Brown and its mission impossible to fix the standard. Following the shocking uncoverings <a href="http://twitter.com/jlundstocholm/status/1540130556">Jesper Lund Stocholm</a>, <a href="http://twitter.com/al3xbrown/status/1490946571">Alex Brown</a> and <a href="http://twitter.com/dmahugh/status/1491135201">Doug Mahugh</a> are acting like little school <a href="http://twitpic.com/31r6x">girls</a> with their <a href="http://twitpic.com/2i7bb">gossip</a> and <a href="http://twitter.com/dmahugh/status/1529978568">giggles</a> on Twitter. But there may be method to the madness. OOXML is already approved by ISO JTC1. Microsoft no longer needs to persuade the national bodies or influence the press or call out their <a href="http://www.youtube.com/watch?v=H3ZLtOcuRm8">business partners</a>. It is enough for them to rely on social engineering in SC34, shmoozing, sponsorships, free <a href="http://www.garshol.priv.no/tmphoto/photo.jsp?id=t143695">dinners</a>, free beer, etc.</p> <p>The reporting of Groklaw about the Microsoft outbursts of unfiltered truth and sillyness made Alex Brown <a href="http://www.groklaw.net/comment.php?mode=display&amp;sid=20090412131523897&amp;title=Alex%20Brown%27s%20Big%20Lie&amp;type=article&amp;order=&amp;hideanonymous=0&amp;pid=751103#c751109">hit back to BRM allegations and he claims the British BSI did not do its job, didn't review ODF properly</a>:</p> <blockquote> <p>Fact is though, we (the team) <strong>did NOT read ODF</strong> - we merely made a rapid pass through parts of the text over half a day, looking for obvious problems. Even so, the UK generated by far the greatest number of NB comments. This fact tells you all you need to know about the degree of scrutiny ODF got in its JTC 1 ballot. If you believe it was studied in detail in the UK, you are very wrong. … We learned from our ODF mistake, and <strong>rectified our errors</strong> [with open xml].</p> </blockquote> <p>Pamela Jones of Groklaw answers to his flamebait:</p> <blockquote> <p>Now, as it happens, I have formed the impression that you and the the MS elves <strong>want to "interoperate" with ODF</strong> so Microsoft forces can take it over, since <strong>even you must now realize that OOXML will never work and will never be adopted.</strong></p> </blockquote> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>
