12.13.07

Gemini version available ♊︎

OOXML and ECMA: Same Scandal, Different Day

Posted in Australia, Deception, ECMA, GNOME, ISO, Microsoft, Novell, Office Suites, Open XML, Standard at 7:37 pm by Dr. Roy Schestowitz

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.

Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

Decor ᶃ Gemini Space

Below is a Web proxy. We recommend getting a Gemini client/browser.

Black/white/grey bullet button This post is also available in Gemini over at this address (requires a Gemini client/browser to open).

Decor ✐ Cross-references

Black/white/grey bullet button Pages that cross-reference this one, if any exist, are listed below or will be listed below over time.

Decor ▢ Respond and Discuss

Black/white/grey bullet button If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

2 Comments

  1. Robert said,

    December 13, 2007 at 8:41 pm

    Gravatar

    >leaving them little or no time to prepare (6 months for 6,000+ pages was >never sufficient in any case)

    Actually some important counties complained about this as an only comment:

    China: “it is a very complex technology which needs further more time to establish testing environment for thoroughly and deeply evaluation. We think the fast-track procedure is not suitable for this DIS”.

    Thailand: “We disapprove the draft ISO/IEC 29500 for the reason that the time given by the fast-track processing is not enough for consideration of this important draft.”

    and others…

    Obviouslly, MS new there was not enough time but still went ahead with the Fast track hoping that they can bang it threw ISO, another example of thier lack of regard for fairness and total disregard for all who will be effected by this format and the principles of open standards.

  2. Roy Schestowitz said,

    December 13, 2007 at 10:25 pm

    Gravatar

    I’ve compared this to a DDOS attack in the past (too much, too little time).

    Also see:

    Any criticism of the specification can automatically be dismissed as nitpicking. For example, if you are presented with a list of 500 faults in a 6,000 pages specification, you can respond, “That is less than 10%. You are just nitpicking. We can fix that in release 1.1″. Or you can even just rely on the familiar justification, “Shipping is a feature”. Any finite list of defects can be made minuscule by a sufficiently large specification.

DecorWhat Else is New


  1. Links 20/03/2023: Amazon Linux 2023 and Linux Kernel 6.3 RC3

    Links for the day



  2. IRC Proceedings: Sunday, March 19, 2023

    IRC logs for Sunday, March 19, 2023



  3. An Update on Sirius 'Open Source' Pensiongate: It's Looking Worse Than Ever

    It's starting to look more and more like pension providers in the UK, including some very major and large ones, are aiding criminals who steal money from their workers under the guise of "pensions"



  4. Services and Users TRApped in Telescreen-Running Apps

    TRApp, term that lends its name to this article, is short for "Telescreen-Running App". It sounds just like "trap". Any similarity is not purely coincidental.



  5. Links 19/03/2023: Release of Libreboot 20230319 and NATO Expanding

    Links for the day



  6. Great Things Brewing

    We've been very busy behind the scenes this past week; we expect some good publications ahead



  7. Links 19/03/2023: LLVM 16.0.0 and EasyOS Kirkstone 5.1 Releases

    Links for the day



  8. IRC Proceedings: Saturday, March 18, 2023

    IRC logs for Saturday, March 18, 2023



  9. Links 18/03/2023: Many HowTos, Several New Releases

    Links for the day



  10. Links 18/03/2023: Tor Browser 12.0.4 and Politics

    Links for the day



  11. Links 18/03/2023: Docker is Deleting Free Software Organisations

    Links for the day



  12. IRC Proceedings: Friday, March 17, 2023

    IRC logs for Friday, March 17, 2023



  13. New Talk: Richard Stallman Explains His Problem With Rust (Trademark Restrictions), Openwashing (Including Linux Kernel), Machine Learning, and the JavaScript Trap

    Richard Stallman's talk is now available above (skip to 18:20 to get to the talk; the volume was improved over time, corrected at the sender's end)



  14. Links 17/03/2023: CentOS Newsletter and News About 'Mr. UNIX' Ken Thompson Hopping on GNU/Linux

    Links for the day



  15. The European Patent Office's Central Staff Committee Explains the Situation at the EPO to the 'Yes Men' of António Campinos (Who is Stacking All the Panels)

    The EPO’s management is lying to staff (even right to their faces!) and it is actively obstructing attempts to step back into compliance with the law; elected staff representatives have produced detailed documents that explain the nature of some of the problems they’re facing



  16. Links 17/03/2023: Linux 6.2.7 and LibreSSL 3.7.1 Released

    Links for the day



  17. GNU/Linux in Honduras: 10% Market Share? (Updated)

    As per the latest statistics



  18. Links 17/03/2023: Update on John Deere’s Ongoing GPL Violations and PyTorch 2.0

    Links for the day



  19. IRC Proceedings: Thursday, March 16, 2023

    IRC logs for Thursday, March 16, 2023



  20. RMS: A Tour of Malicious Software, With a Typical Cell Phone as Example

    Tonight in Europe or this afternoon in America Richard M. Stallman (RMS), who turned 70 yesterday, gives a talk



  21. Skyfall for Sirius 'Open Source': A Second Pension Provider Starts to Investigate Serious (Sirius) Abuses

    Further to yesterday's update on Sirius ‘Open Source’ and its “Pensiongate” we can gladly report some progress following escalation to management; this is about tech and “Open Source” employees facing abuse at work, even subjected to crimes



  22. NOW: Pensions Lying, Obstructing and Gaslighting Clients After Months of Lies, Delays, and Cover-up (Amid Pension Fraud)

    The “Pensiongate” of Sirius ‘Open Source’ (the company which embezzled/robbed many workers for years) helps reveal the awful state of British pension providers, which are in effect enabling the embezzlement to carry on while lying to their clients



  23. Links 16/03/2023: War Escalations and More

    Links for the day



  24. Links 16/03/2023: OpenSSH 9.3 Released and WordPress 6.2 Release Candidate 2, Lapdock News

    Links for the day



  25. IRC Proceedings: Wednesday, March 15, 2023

    IRC logs for Wednesday, March 15, 2023



  26. Links 16/03/2023: OpenSSL 3.1 Released, 10,000 More Staff Cut in Facebook, and Windows Loses 10% in Speed

    Links for the day



  27. Links 15/03/2023: Transmission 4.0.2 and Lots in Geminispace

    Links for the day



  28. Links 15/03/2023: Qubes OS 4.1.2, Mozilla Swallows Buzzwords

    Links for the day



  29. Founder of the Free Software Movement, Richard Stallman, Turns 70

    In some parts of the world it is already the 16th of the month; that’s the 70th birthday of Richard Stallman



  30. Links 15/03/2023: DietPi 8.15 and digiKam 7.10.0

    Links for the day


RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts