10.17.09

Gemini version available ♊︎

ISO Urged to Invalidate OOXML as Microsoft’s Role Gets Shown; More Smears of ODF Come from Microsoft

Posted in Formats, Google, IBM, ISO, Microsoft, Office Suites, Open XML, OpenDocument, Standard, SUN at 5:11 am by Dr. Roy Schestowitz

Old car

Summary: Just like a filmography-style mafia, Microsoft and its allies proceed from corrupting ISO to bashing ODF from the inside and trying to control it too

MICROSOFT MAY hope that people will forget what it did for OOXML, but the past returns to haunt as more abusive behaviour gets seen. In light of the i4i case for instance [1, 2, 3, 4, 5, 6, 7, 8, 9, 10], Jomar Silva raises the point that Microsoft lied about patents in OOXML, with the assistance of its special friend Alex Brown [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21].

Here is what Silva wrote a few days ago:

They also defined the coordinator of the BRM, Alex Brown (who also played a crucial role in the outcome of OpenXML, but that’s subject for another post, because I didn’t revealed yet all I saw in Geneva), and he publishes on his blog a FAQ with the rules of the BRM. This FAQ also circulated as an official ISO document, and can be found here.

Look what is written in this document:

4.1 Will IPR issues be discussed at the BRM?

No. IPR issues in this process are the exclusive preserve of the ITTF. IPR decisions have previously been delegated by all the ISO and IEC members (NBs) to the CEOs of IEC and ISO, and they in turn have examined them and found no outstanding problems. NBs seeking reassurance in such matters must pursue them through other avenues than the BRM.

In other words, the CEOs of ISO and IEC (the highest authorities of the two entities) had assessed the intellectual property issues on OpenXML and found nothing, so no committee around the world have to worry about the issue… I remember that I’ve asked about it few times, and the answer was always the same: “Kid, you are doubting the CEOs of ISO and IEC ?”… but what about the i4i litigation ?

[...]

Most of the ECMA delegates I know are Microsoft employees or business partners of the company. This staff can be anything but “uninformed” and therefore I can’t believe that ECMA didn’t know the litigation too.

So, I change the question asked by Groklaw almost two months ago for a more direct one: Who fooled who?

We all know that all NBs was fooled, that the countries have seen their names used in an unscrupulous way and that all delegates and competent technicians has been fooled too.

I really hope to hear something from the cited parties cited, and I believe that all International Society expect the same. We no longer live in a world where a nonsense fact like this can be accepted, and I’ll not stop until I find an answer (and I know I’m not alone in this quest).

I also would like to know from the ISO/IEC what they have to say about all this. They knew the i4i litigation ?

To finalize, I appeal again to CEOs of ISO and IEC: The G-20 is a reality, and it’s never too late to correct an injustice !

In the comments, the president of the FFII writes:

ISO should pull down the ISO29500 immediately.

No one can implement this specification safely.

ISO29500 should be withdrawn “Now”.

Georg C. F. Greve, the founder of the FSFE, writes about the above: “The first rule of the #OOXML club? Don’t talk about the legal problems!”

Rob Weir has more to say about the role of Alex Brown:

Curiously, NBs were asked to make their final decision without actually seeing the text of the standard they were being asked to approve. ISO leadership denied requests from several NBs, a formal SC34 resolution requesting this text, as well as NB appeals, all which asked to have access to the “final DIS” text that would eventually be published. The ISO chief, in his response to the NB appeals, called the final text of OOXML “irrelevant” (prophetic words, indeed!) and would only permit NBs to have access to a list of over 1,000 resolutions from the BRM, many of which gave great editing discretion to the Microsoft consultant who would eventually produce the final text of the specification.

I discussed why the lack of a final DIS text was a problem back in May 2008:

We are currently approaching a two month period where NB’s can lodge an appeal against OOXML. Ordinarily, one of the grounds for appeal would be if the Project Editor did not faithfully carry out the editing instructions approved at the BRM. For example, if he failed to make approved changes, made changes that were not authorized, or introduced new errors when applying the approved changes. But with no final DIS text, the NB’s are unable to make any appeals on those grounds. By delaying the release of the final DIS text, JTC1 is preventing NB’s from exercising their rights.

Would you make thousands of changes to code and then not allow anyone to test it, and then release it internationally? Of course not. Doing so would amount to professional malpractice. But that is essentially what ISO did with OOXML.

Weir is very careful not to mention names (personalising issues), but it’s obvious who’s who, not to mention the current role these people play in derailing ODF. We shall come to this in a moment. To say that ISO was “gamed” is an understatement. ISO was hijacked and a lot of people corrupted and bribed. There is extensive evidence to show this.

On a more positive note, Bob Sutor (IBM) writes about new success stories for ODF, followed by feedback from Roberto Galoppini and also his colleague Rob Weir.

Roberto Galoppini also writes about the ODF plugfest and spreads the word now that the event is approaching.

The second in a series of events that will bring together implementors of OASIS OpenDocument Format/ISO 26300 to unilaterally test and discuss implementation issues of ODF with each other. All ODF implementors and/or those looking into the matter are invited to participate in this event on behalf of the Netherlands government and OpenDoc Society.

We wrote about those plugfests before, e.g. in [1, 2, 3, 4, 5, 6, 7, 8 9 10, 11, 12]. Microsoft (and its ecosystem) attended plugfests to throw some criticism at this standard, which it hates but at the same time must watch over. Alex Brown’s friend, who has always been hostile towards ODF, drops Microsoft’s talking points to be used against ODF while Microsoft’s Doug Mahugh makes fun of ODF as well. Those who are not employees of Microsoft often feed the company by insulting ODF “by proxy”, so to speak.

“Those who are not employees of Microsoft often feed the company by insulting ODF “by proxy”, so to speak.”In the latest example seen above, we are witnessing a familiar old pattern of deception. As our reader puts it, “Microsoft is able to spin it as Microsoft vs 1 company (either IBM or Sun depending on the circumstances) with amnesia about the rest. Via OASIS, 600 companies, universities and government agencies were behind the initial development of the first try at a universal office format. About two dozen were taking the lead in development.” This politicisation of the issue (courtesy of Microsoft) has gone on for years.

Anyway, those who are speaking about the ODF plugfest now include Glyn Moody, Gwynne Monahan, Jomar Silva, Thomas Zander (Nokia), Rob Weir, and the “elephant in the room” Doug Mahugh. The Microsoft crowd is still trying to 'tame' or dethrone Rob Weir, so Jomar Silva sarcastically writes: “Oh my God ! Mr. Vadar is the chair of the ODF TC ! We must be the bad guys ! (M$ fan boys are impressive)”

Microsoft is still striving to control ODF like it controls ISO and Weir must be polite. That’s probably why he also omits names and does not write about the OOXML scandals as much as he used to.

Microsoft’s hijack attempts affect not only the ODF TC. Watch who is involved in the Document Interoperability Initiative: Microsoft, Microsoft allies, and Microsoft-funded groups.

* I’ll be covering the Office 2010 extensions (as was covered by the Office program managers in last month’s DII workshop in Redmond). I will also present the latest news on how we’re working to improve ODF interoperability between Office and other popular applications, and talk about our plans for the future.
* Alex Brown will be covering present and future plans for the Office-o-tron validator project.
* Klaus-Peter Eckert of Fraunhofer FOKUS will present the latest status of the document test library project and other work Fraunhofer is doing to improve interoperability.

Microsoft attempts to control the whole thing, including so-called interoperability. We showed a lot of evidence before [1, 2, 3].

Even in Wikipedia, ODF-hostile content gets injected into the article about ODF by the Microsoft folks, as last shown some days ago. Some references to Microsoft blogs are now being removed, as well as the poison that they have injected.

A more detailed account of how Microsoft subverts Wikipedia (on ODF) can be found in, e.g.:

Microsoft leads people to confusion, fear, and absorption of disinformation using those people who only pretend to be friends of ODF. Here for instance is a person who was unfortunately led to making a false claim given new software like Androffice. ODF does a lot better than Microsoft would have people believe.

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.

DecorWhat Else is New


  1. Virtually (i.e. Online) and for Only One Hour the EPO's Staff Representation Was Allowed to Discuss Many Lingering Concerns

    “Report on the LSCMN meeting with VP4 of 9 November 2022″ (i.e. one month ago) is being circulated this week; “On 9 November 2022,” says the union or the local officials (Staff Union of the EPO, or SUEPO for short, has overlaps), “the Local Staff Committee Munich (LSCMN) met with VP4, Ms Nellie Simon, to discuss a number of prevailing local matters in a virtual meeting which had been scheduled, as had the previous one, for one hour only.” (the usual; they intentionally don’t allocate sufficient time)



  2. [Meme] António Campinos-Controlled (EPO-Commissioned) Surveys Are Just for Show (to Help 'Validate' Lies)

    The real EPO survey is not that one conducted by (and for) António Campinos



  3. European Patent Office (EPO) on the Decline, According to the Fifth Edition of the Technologia Staff Survey

    Today we share some documents that circulated amongst EPO staff yesterday; it's about this year's staff survey that was not conducted by the EPO itself (to serve EPO management and its twisted agenda



  4. Free Software is So Robust That Its Opponents Need to Travel 12 Months Back in Time in Order to Find Fear, Uncertainty, and Doubt (FUD) Material

    Microsoft- and Linux Foundation-connected sites help smear or stigmatise Free software (citing hostile 'experts'); this week they borrow news from 12 months ago to make a point



  5. IDG Has Resorted to Microsoft Marketing SPAM Instead of Actual Journalism

    Microsoft puff pieces are published as "opinions", disguised as "news" while in fact serving no purpose other than marketing



  6. Open Invention Network (OIN) Protects Amazon and AWS From Activists Like Us Who Want to Abolish Software Patents Through Reforms of the Patent Systems

    The Open Invention Network (OIN) does not exist to serve the Free software community but to work against it; the latest joining (AWS) proves this



  7. Sirius ‘Open Source’ and the Money Missing From the Pension

    Sirius ‘Open Source’ is unable to cope with basic legal requirements such as sending payslips to staff (this hasn’t been done for months already!) and such issues have gone on for almost 4 years already



  8. IRC Proceedings: Wednesday, December 07, 2022

    IRC logs for Wednesday, December 07, 2022



  9. Links 07/12/2022: ArcoLinux Beta 23.01 and Cryostat 2.2

    Links for the day



  10. [Meme] Where Did the Money Go?

    Sirius ‘Open Source’ became a company that cannot even do accounting right; pertinent technical employees had to do a lot of chasing for years just to get the basics rectified



  11. Evidence of Sirius ‘Open Source’ (or Sirius Corporation) Failing to Pay Pensions, Failing to Inform Staff, Not Responding to Staff

    The job my wife and I left this past Friday (after about 21 years combined) had turned sour years ago; hoping that this serves as a cautionary tale to others, we've decided to show pension lapses, lack of payslips, and excuses that accompanied that for years



  12. Links 07/12/2022: Blender 3.4 and Apple GPU Drivers Now in Asahi Linux

    Links for the day



  13. IRC Proceedings: Tuesday, December 06, 2022

    IRC logs for Tuesday, December 06, 2022



  14. Links 07/12/2022: Kali Linux 2022.4, GNUnet 0.19.0, and Pgpool-II 4.4.0

    Links for the day



  15. Subsidising the Likes of Rupert Murdoch is Not Supporting Journalism

    There are yet more attempts to tax citations; not only does that make no practical or moral sense, it's being lumped in or joined together with a must-pass "defence" (military) bill in order to suppress opposition



  16. Microsoft Layoffs Again

    The company behind Windows is in a bad state, but it is being propped up by the taxpayers; if rumours are true, Microsoft might get a lot smaller next year



  17. Microsoft is Killing Hospital Patients With Its Insecure-by-design Windows Operating System

    Many people continue to needlessly die because many hospitals still foolishly deploy Windows on mission-critical life-saving machines



  18. Sirius ‘Open Source’ Failing at the Most Basic Employment Regulations

    The company we left behind last week was a repeat violator of employment laws; to make matters worse, it led to its long-term or long(time)-serving staff becoming very baffled, having to contact the pension provider for clarifications



  19. Sirius ‘Open Source’: When the Company Stops Paying Your Pension and You Don't Know Until the Pension Provider Keeps Sending Physical Post to Alert You

    Today we turn our attention to pension blunders at Sirius ‘Open Source’; in recent years even something basic like pension contributions wasn’t smooth sailing



  20. [Meme] Sirius Open Source, Closed-Minded Bossing

    At Sirius ‘Open Source’, decisions are made in the dark without consultation with staff and many things go wrong as a result; of course the culprits never hold themselves accountable



  21. Links 06/12/2022: LibreOffice 7.5 Alpha and digiKam 7.9.0

    Links for the day



  22. Rumour: Very Large Microsoft Layoffs (Another Round) Next Month, Lists Already Being Prepared





  23. Benoît Battistelli in 2015: EPO is Ready to Start Unified Patent Court (UPC), Expect UPC in 2016

    We’re almost in 2023 and UPC is being delayed again; this is what EPO President Benoît Battistelli said way back in 2015 (official video from the EPO; 3:45-4:34 cropped apart)



  24. IRC Proceedings: Monday, December 05, 2022

    IRC logs for Monday, December 05, 2022



  25. Links 06/12/2022: FreeBSD 12.4 and Inkscape 1.2.2

    Links for the day



  26. Sirius Not-So-‘Open Source’: Cannot Talk to Colleagues, Cannot Speak About Work

    Cover-up and lies became a corporate pattern at the company where I had worked since 2011; it was time to go in order to avoid cooperation in unethical activities



  27. [Meme] Guilt by Association

    Sirius ‘Open Source’ has a history of hostility towards people with disabilities; the company got sued over this, but kept the lawsuit secret



  28. That Time Sirius 'Open Source' Fired a Blind Lady While Gagging Sympathetic Staff

    Sirius 'Open Source' was taken to court after it had wrongly fired a couple of employees, one of whom was blind; this was accompanied by lies about why the staff's communication server was shut down



  29. Links 05/12/2022: Gnoppix Linux 22.12 and Armbian 22.11

    Links for the day



  30. Unified Patent Court (UPC) is “Real Soon Now!” Since 2014

    The Unified Patent Court (UPC) lobby is once again forced to admit issues and delays; we've seen this time and time again for nearly a decade already


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