Bonum Certa Men Certa

OOXML and ECMA: Same Scandal, Different Day

Confusion, obscurity, uncertainty

There appears to be plenty of energy dedicated to make the whole standardiatino effort cumbersome, secretive, and immune to outside scrutiny and innervation. This is unacceptable.

It's bad enough that companies like Corel and Novell seems to have been 'bought' (bribed) to defect to Microsoft's side, with other possibilities as well. It's even worse when you are not allowed to know what's going on in a process that must thrive in transparency. Aren't transparency and openness what standards are all about?

Abuse in Disguise



First, consider this loud complaint about EMCA (aka Microsoft) shutting people out.

What is needed now is the public and unconditional access to the works of the TC 45. What is needed now is for the Ecma to give the password to their page. Give us the password!


Why is Microsoft so afraid of spectators? Why are there so many barriers? Isn't the 'openness' of their standard something to boast and brag about? Or is it something to be embarrassed of and hide?

Gaming the Rules Again?



Andy Updegrove is already concerned. We're still months ago from the BRM and questionable practices are all too commonplace.

A particularly contentious issue has been whether Ecma is trying to make it as easy as possible, or is trying to make it as difficult as possible while still scoring PR points, for interested parties to view proposed dispositions of comments, and whether it does, or does not, have the latitude under ISO rules to be more transparent. The fairly opaque, and sometimes contradictory nature of those rules, has not made the debate any easier, and gives rise to the possibility of confusion, at best, and serious mistakes, at worst, as Pamela Jones pointed out at Groklaw this morning.

The result is that there will be very little real data available to the general public until Ecma opens the curtains on January 19. And the import of what little data does become available is usually the subject of instant disagreement.


Here is the latest analysis from Groklaw. This must be one of the observations Andy spoke about.

I read that as saying that delegates attend the meeting, and then they go home and talk things over as a group, and if the group decides it wishes to change its country's vote, it has 30 days to do so.

However, if you visit ISO/IEC's JTC 1/SC 34 - Document Description and Processing Languages page, it seems to say a country can change its vote at the meeting itself. And later wording in the FAQ seems to confirm that understanding, as I'll show you. But we're also hearing that there may not be room for everyone to fit into the room booked for the meeting. So, I'm seeing a potential for some gaming of the rules.


There was an incident some months ago where Microsoft deceived those who would vote, leaving them little or no time to prepare (6 months for 6,000+ pages was never sufficient in any case). An analogy made at the time. Think of an election day where someone names that wrong date so that you can't vote. You show up when it's too late. The lies never stopped.

Oops! We did it again.



Check out the following report from the plenary meeting. [via Andy Updegrove]

...The meeting was well attended, both by (what might be called) the old guard, and by many new members who no doubt represent a wide spectrum of thinking on SC 34’s subject areas. There was no substantive discussion either of Ecma’s proposed maintenance agreement for OOXML (should it become a standard), or of the UK’s proposal to create a new working group for Office document formats. These will most likely be formally addressed in the next SC 34 meeting which will take place in Oslo in April 2008.

[...]

Finally, my own working group convenor Martin Bryan is stepping down in anticipation of his retirement next year.

[...]

Martin has been something of a mentor to me, guiding me along some of the more Byzantine passages of the ISO/IEC process. At the plenary Martin spoke to his paper which has been the subject of some comment in the blogosphere (and which was never intended for public circulation).


OOXML on the trash canThat is the report from the man who spoke about Microsoft's abuse of the whole process. It wasn't a man watching from the outside, but one who has seen (from the inside) Microsoft bringing his group down to its knees. How shameful is the fact that this was not intended for public circulation. Should people not be aware of abuse in the system that is intended to serve them?

Assimilate-to-Destroy Strategies



Remind yourself what motivates Microsoft to undergo this whole 'open' charade. Here is another good explanation [via Andy Updegrove] which ought to remind you that OOXML's purpose is merely to eliminate ODF. OOXML is still proprietary and it inherits the same legal threats as its predecessor/ancestor, which was entirely binary.

[The South African] Government's decision to adopt open document format is a bold one and will not come unchallenged. In the wider market, open document format (ODF) could have an enormously positive impact, but gaining the benefits offered by the format depends on several key factors.

[...]

The possibility that the whole world could one day use open standards for documents is a positive one. In March, it will be decided whether Open XML will be ratified as an open standard. Should Microsoft's standard successfully be approved, it will provide the company with much leverage to encourage doubt in government at its decision for ODF. By then, however, government will be well on its way to implementing the ODF standard and updating its departments, with a commitment to have finally completed the move by 2009. The public, therefore, should follow government's lead. It was a bold move for government to put its documents where its mouth is and it should encourage the private sector to do the same.


In New Zealand, the NZOSS addresses the problems the right way, as opposed to what some have done in Australia, which is akin to the GNOME Foundation's mistakes.

At this stage of the ISO process the NZOSS would like to invite any technically and legally minded people in the free and open source communities to review ECMA responses: to New Zealand comments or to comments that might affect New Zealand interests.


Microsoft will be lobbying very heavily in all those countries that voted "No" or abstained. Given the corruption we've witnessed in the past, it will take more than good spirit to defeat the Microsoft Money Machine(R), which has even used people's jobs (putting them at stake) to blackmail. We're not dealing with a candidate standard here; we're deal with a bully that has an impressive track record.

Comments

Recent Techrights' Posts

GNU/Linux Has Become More Mainstream in the United Kingdom
It's a long weekend here and we guess some people dabble in GNU/Linux migrations, at least at home
IBM is "Taking the PIP" (Piss), People 'Retire' 'Voluntarily' to "Focus on Family"
IBM has a billion bucks for 'the butcher', but not a million dollars for critical projects and initiatives in Free software
It Should be Uncontroversial to Say That Social Control Media is a Weapon
Democracy is not compatible with the likes of Kapo-Berg and MElon controlling public discourse of billions
 
Gemini Links 30/08/2026: Photography, Paper Books, Linux Kernel and the Debian Projects Permitting Slop Plagiarism
Links for the day
Imagine a World Where Nobody Fights for Software (and Computing) Freedom
The community keeps fighting back, so some of these ambitions are delayed or watered down
FSF Has Grown (More Staff) After a Year of Financial Growth
On October 4 the FSF turns 41
SLAPP Censorship - Part 166 Out of 200: Garrett Wasn't Found Innocent Per Se, the Court Wanted More Evidence of Who Was Behind Particular Accounts Using Tor
It's complicated
Criminals Don't Obey Laws, California Does Not Enhance Online Safety
It has been a while since we last mentioned so-called 'age-verification' laws
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, August 29, 2026
IRC logs for Saturday, August 29, 2026
Links 29/08/2026: Stop the Hate, Goldfish Myths, and xmpp.nz
Links for the day
Links 29/08/2026: Wave of Social Control Media Bans, Suno Data Breach Class Actions
Links for the day
Links 29/08/2026: Microsoft GitHub Outage (Again), "Displaying Ads Directly on Your Monitor", and "Election Deniers Could Soon Control Elections"
Links for the day
Misuse of Bots (Now Sold as "Agents", "Hey Hi", "Automation", and "Efficiency")
They even try to rebrand robotics as "hey hi" and try to sell slop as "work"
Debian: Plagiarism OK, Just be "Responsible" About It
The result isn't the worst, but it's not good either
Don't Let Them Kill Activism
Are the oligarchs shutting the lid on activism and whistleblowers?
SLAPP Censorship - Part 165 Out of 200: Two Years Since My Wife and I Sued
In early September 2024 we hit back
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, August 28, 2026
IRC logs for Friday, August 28, 2026
Gemini Links 29/08/2026: Death Notice, Systems Biology, and Gopher
Links for the day
Links 28/08/2026: Chatbot Pushers Admit They're Used Heavily for Social Engineering Scams, Strong Backlash Against "Smart Glasses" (CCTV on Legs)
Links for the day
Michael Catanzaro's Latest Blog Post Affirms Rumours of Red Hat Changes and RAs/PIPs at IBM
reading between the lines, IBM is "spitting out" Red Hat staff
If Linux Was Written in Rust, 80% or More of Linux Developers Would Not Understand It (Same If It's Composed by LLM Slop)
The licence (GPL) is not enough when there are ways to bypass it
Gemini Links 28/08/2026: Absurd Tomodachi Summer, Screen Piggery, and Jugulans 1.0.3 Released
Links for the day
Links 28/08/2026: "UK Power Grid Has a Phantom Data Center Problem" and "Growth at All Costs is Cancer"
Links for the day
SLAPP Censorship - Part 164 Out of 200: Patent Troll SLAPPs, Defamation Trolls, and Stranglers From America
You start to wonder if the core issue is insecurity
Rumours of More PIPs and Layoffs at Confluent Just Months After IBM Bought It
It is meanwhile apparent IBM will have mass layoffs next week (September)
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, August 27, 2026
IRC logs for Thursday, August 27, 2026
After Many Waves of PIPs (Silent Layoffs) IBM Makes Non-Silent Layoffs, Effective Next Week (September)
What we heard is turning out to be true