Slashdot Mirror

what about sends in a Groklaw alert warning that, by PJ's reading, Microsoft may be trying to take over ODF via a stacked SC 34 committee. The article lists the attendees at an SC 34 meeting in July and gives their affiliations, which the official meeting materials do not. (The attendees of the October 1 meeting, which generated a takeover proposal to OASIS, are not known in full.) "Why do I say Microsoft, when this is SC 34? Look at this ... list of participants in the July meeting in Japan of the SC 34 committee. The committee membership is so tilted by Microsoft employees and such, if it were a boat, it would capsize ... Of the 19 attendees, 8 are outright Microsoft employees or consultants, and 2 of them are Ecma TC45 members. So 10 out of 19 are directly controlled by Microsoft/Ecma ... [I]f the takeover were to succeed, SC 34 would get to maintain ODF as well as Microsoft's competing parody 'standard,' OOXML. How totally smooth and shark-like. Under the guise of 'synchronized maintenance,' without which they claim SC 34 can't fulfill its responsibilities, they get control of everything." A related submission from David Gerard points out that BoycottNovell has leaked the ISO OOXML documents, which ISO has kept behind passwords.

mikkl666 writes "Alex Brown, head of the ISO work group responsible for OOXML, has posted a summary of their latest meeting, and he also comments on the resolutions discussed there. The basic message is that ISO now has 'full responsibility for the standard,' and that several workgroups will be established to work on OOXML. An interesting point here is that 'setting up a maintance[sic] procedure for ODF, and then working on cross-standard initiatives' is one of the explicit goals. On a side note, they also reacted to the very emotional discussion on OOXML by posting an open letter: 'We the undersigned participants ... wish to make it clear that we deplore the personal attacks that have been made ... in recent months. We believe standards debate should always be carried out with respect for all parties, even when they strongly disagree.' As Brown correctly points out, 'This content speaks for itself.' We discussed the approval of OOXML earlier this month."