Slashdot Mirror

An anonymous reader writes with news that the Open Document Format 1.2 specification has finally been approved. "The most important improvement to ODF 1.2 is the newly built spreadsheet support. The old format was buggy and had a lot of legacy problems. Therefore the new spreadsheet module was written from scratch. 'A complete clean room implementation of the spreadsheet formula was built,' said [Michiel Leenaars, director of the Internet Society Netherlands]. ... Another important improvement in ODF 1.2 is the support for Resource Description Framework (RDF) metadata, a W3C standard model for data interchange on the Web. ... Instead of only being able to link to a URL, RDF allows users to link text in documents to other things like a V-Card or a calendar item. Companies can use this technology to structure their workflow."

Rob Weir got wind that a Slovakian tech site had been discussing the non-randomness of Microsoft's intended-to-be-random browser choice screen, which went into effect on European Windows 7 systems last week. He did some testing and found that indeed the order in which the five browser choices appear on the selection screen is far from random — though probably not intentionally slanted. He then proceeds to give Microsoft a lesson in random-shuffle algorithms. "This computational problem has been known since the earliest days of computing. There are 5 well-known approaches: 3 good solutions, 1 acceptable solution that is slower than necessary and 1 bad approach that doesn’t really work. Microsoft appears to have picked the bad approach. But I do not believe there is some nefarious intent to this bug. It is more in the nature of a 'naive algorithm,' like the bubble sort, that inexperienced programmers inevitably will fall upon when solving a given problem. I bet if we gave this same problem to 100 freshmen computer science majors, at least 1 of them would make the same mistake. But with education and experience, one learns about these things. And one of the things one learns early on is to reach for Knuth. ... The lesson here is that getting randomness on a computer cannot be left to chance. You cannot just throw Math.random() at a problem and stir the pot and expect good results."

David Gerard writes "Microsoft Office 2007 SP2 claims support for ODF 1.1. With hard work and careful thinking, they have successfully achieved technical compliance but zero interoperability! MSO 2007sp2 won't read ODF 1.1 from any other existing application, and its ODF is only readable by the CleverAge plugin. The post goes into detail as to how it manages this so thoroughly."

I Don't Believe in Imaginary Property writes "The rumors of a fourth OOXML complaint turned out to be true. Denmark has become the fourth nation to protest the ISO's acceptance of OOXML, and Groklaw has a translation of their complaint. They now join India, Brazil, and South Africa. There are going to be plenty of questions about deadlines, because people have been given two different deadlines for appeals, and the final DIS of OOXML was late in being distributed and not widely available. In fact, that seems to be one of Denmark's complaints, along with missing XML schemas, contradictory wording, lack of interoperability, and troubles with the maintenance of DIS29500. In other words, we should expect a lot of wrangling over untested rules from here on out, and Microsoft knows how to deal with that."

I Don't Believe in Imaginary Property writes "Brazil is now appealing the ISO's decision to standardize OOXML, following South Africa's lead. Interestingly, part of the reason this took so long was that Microsoft supporters at the meetings kept asking for delays because they 'weren't prepared' to discuss the issues raised. And the ISO as a whole is moving rather slowly, after that delay in releasing the DIS. But at least the ISO is also rewriting the directives in a special working group so this doesn't happen again. Of course, they'd have to be strict about making sure the directives are followed for it to help."

I Don't Believe in Imaginary Property writes "IBM's Rob Weir has done a study on how many flaws were addressed by the OOXML Ballot Resolution Meeting. So far, using a random sampling technique, he has yet to find a flaw that was addressed, making the upper bound a paltry 1.5%. Even so, he's found a number of new flaws, including a security vulnerability: OOXML stores passwords in database connection strings in plain text. At least there were no mistakes on five of the first twenty five random pages he reviewed."

I Don't Believe in Imaginary Property writes "With all the pieces floating around on OOXML, it's been hard to get a good sense of where it is in the standardization process. Fortunately, IBM's Rob Weir has a provided us a road map. Today Microsoft is due to submit its set of proposals for resolving the 3,522 comments to JTC1, which controls OOXML. Tomorrow or soon after, we can expect a media blitz heralding these 'changes,' as numerous reporters are, reportedly, being flown to Redmond. But all those recommendations are non-binding, because only JTC1 can change the standard and that happens during the Ballot Resolution Meeting. And even if all of the recommendations are adopted, no one has to change their vote. The BRM, where all the real work will happen, isn't until February 25-29. Within the 30 days after that, everyone will be able to reconsider their vote. That's when we can expect the real fireworks."

Rob Weir has an interesting essay comparing the viciousness of RTF and OOXML: "The [document format standard] concerns of 2004 (or 1995 even) are very similar to the concerns of 2007... 'RTF is defined as whatever Word saves when you ask it to save as RTF.' This should sound familiar. OOXML is nothing more than the preferences of Microsoft Office. Whenever Word changes, OOXML will change. And if you are a user or competitor of Word, you will be the last one to hear about these changes. The coding of Office 14 a.k.a. Office 2009 is well underway. Beta releases are expected in early 2008. But are file format changes needed to accommodate the new features being discussed in Ecma? No. Are they being discussed in ISO? No. Are they being discussed anywhere publicly? No. By owning the 'standard' and developing it in secret, in an Ecma rubber-stamp process, Microsoft rigs the system so they can author an ISO standard with which they are effortlessly compatible, while at the same time ensuring that their products maintain an insurmountable head start in implementing these same standards. Is this how an open standard is developed?"

Rob Isn't Weird writes "Microsoft has finally responded to the resolutions concerning OOXML (or 662 of them at any rate). The only problem? The JTC1 NBs who are deciding OOXML's fate have to download 662 individual PDFs from a slow, password-protected server; and many have had trouble getting the password. Don't misunderstand the ECMA's intent, though: there would have been 662 OOXML files if they had wanted to make it hard for people to read and criticize the responses. Thanks to the Internet, other interested parties have put all 662 resolutions online in a searchable, taggable format and are requesting that everyone interested help examine them. That means you, Slashdot."

Rob Isn't Weird writes "Microsoft has finally responded to the resolutions concerning OOXML (or 662 of them at any rate). The only problem? The JTC1 NBs who are deciding OOXML's fate have to download 662 individual PDFs from a slow, password-protected server; and many have had trouble getting the password. Don't misunderstand the ECMA's intent, though: there would have been 662 OOXML files if they had wanted to make it hard for people to read and criticize the responses. Thanks to the Internet, other interested parties have put all 662 resolutions online in a searchable, taggable format and are requesting that everyone interested help examine them. That means you, Slashdot."

Rob Isn't Weird writes "In the wake of the exposure of Microsoft's attempt to buy Sweden's vote on OOXML and Sweden's annulment of that vote due to irregularities, IBM's Rob Weir points out that the fiasco could cause anti-trust worries for Microsoft. He quotes ALLIED TUBE & CONDUIT CORP. v. INDIAN HEAD, INC., 486 U.S. 492 (1988), which says 'What petitioner may not do (without exposing itself to possible antitrust liability for direct injuries) is bias the process by, as in this case, stacking the private standard-setting body with decision makers sharing their economic interest in restraining competition.'"

Rob Isn't Weird writes "In the wake of the exposure of Microsoft's attempt to buy Sweden's vote on OOXML and Sweden's annulment of that vote due to irregularities, IBM's Rob Weir points out that the fiasco could cause anti-trust worries for Microsoft. He quotes ALLIED TUBE & CONDUIT CORP. v. INDIAN HEAD, INC., 486 U.S. 492 (1988), which says 'What petitioner may not do (without exposing itself to possible antitrust liability for direct injuries) is bias the process by, as in this case, stacking the private standard-setting body with decision makers sharing their economic interest in restraining competition.'"

Xenographic writes "INCITS V1, the US group responsible for the US vote over whether or not ANSI will grant fast-track approval to Microsoft's OOXML format, failed to reach the 2/3 consensus required to recommend OOXML to ANSI. What makes this vote interesting is the graph in the article, showing all the new Microsoft business partners who joined INCITS just this year to vote for OOXML. The INCITS Executive Board will now deliberate further, until they can come to some agreement on what to recommend to ANSI, but it's pretty clear that Microsoft is pushing OOXML as hard as it can."

hill101 writes "According to Rob Weir's blog, Microsoft's 325-page OOXML specification for spreadsheet formulas is deeply flawed. From basic trigonometric functions that forget to specify units, to statistical functions, to critical financial functions — the specification does not contain correct formulas that could possibly be implemented in an interoperable way. Quoting Mr. Weir: 'It has incorrect formulas that, if implemented according to the standard, may cause loss of life, property, and capital... Shame on all those who praised and continue to praise the OOXML formula specification without actually reading it.'"

hormiga writes "Some scholarly journals are rejecting submissions made using new Office 2007 formats. Science and Nature are among publishers unwilling to deal with incompatibilities in the new formats, and recommend using older versions of Office or converting to older formats before submission. The new equation editor is cited as a specific problem. Rob Wier recommends that those publishers consider using ODF instead."

hormiga writes "Some scholarly journals are rejecting submissions made using new Office 2007 formats. Science and Nature are among publishers unwilling to deal with incompatibilities in the new formats, and recommend using older versions of Office or converting to older formats before submission. The new equation editor is cited as a specific problem. Rob Wier recommends that those publishers consider using ODF instead."

Standard Disclaimer writes "Most here on Slashdot know that Microsoft released its OpenXML specification to counter ODF and to help preserve its market position, but most people probably aren't aware of all the interesting legacy code the OpenXML specification has brought to light. This article by Rob Weir details many of the crazy legacy features in the dark corners of OpenXML. As it concludes after analyzing specification requirements like suppressTopSpacingWP, 'so not only must an interoperable OOXML implementation first acquire and reverse-engineer a 14-year old version of Microsoft Word, it must also do the same thing with a 16-year old version of WordPerfect.'"