EditorsAbout the SiteComes vs. MicrosoftUsing This Web SiteSite ArchivesCredibility IndexOOXMLOpenDocumentPatentsNovellNews DigestSite NewsRSS

10.17.09

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 this post: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • Reddit
  • co.mments
  • DZone
  • email
  • Google Bookmarks
  • LinkedIn
  • NewsVine
  • Print
  • Technorati
  • TwitThis
  • Facebook

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

What Else is New


  1. GitHub is All About Control

    GitHub is not a platform for sharing and collaboration but social control and manipulation of the Free software community



  2. 2019 in Review: Worst Year Ever for Software Freedom

    A look back (and ahead) as the year's end fast approaches, marking the end of a mostly bad year



  3. Links 15/12/2019: Hacker-Friendly Hardware Success Stories and Mozilla Woes

    Links for the day



  4. European Patents Losing Their Appeal, Lustre and Glamour

    Years of assaults on EPO staff — including EPO judges — have taken their toll and the quality of patents is nothing like it used to be



  5. Software Freedom and The U.S. Constitution

    “We need to stand for the freedom to not use the software — we need to enjoy that freedom without giving up the rest of the existing Free software ecosystem.”



  6. IRC Proceedings: Saturday, December 14, 2019

    IRC logs for Saturday, December 14, 2019



  7. Links 15/12/2019: Wine 5.0 RC1 Released, KDE Frameworks 5.65.0, Qubes OS 4.0.2 RC3

    Links for the day



  8. It Matters a Lot What You Call the System

    Why the best name for the best operating system would be "GNU", not "Linux" (media has twisted the words so as to marginalise GNU and its politics/philosophy)



  9. Only the EPO Goes as Far as Bribing Publishers (the Media) to Promote Software Patents and Publish Fictional Stories

    The world’s patent offices are growing tired of granting software patents which courts later toss out (because these patents are not valid); not only does the EPO advocate such patents — typically using a bundle of buzzwords — it’s also bribing the media to help



  10. EU Needs to Show That It Cares About SMEs and Not 'European Champions' That Are Actually Foreign Monopolies

    Judging by the EU’s nearly blind and unconditional support for the management of the EPO — no matter how abusive and corrupt it has gotten — one has to wonder if the ex-EU official in charge of the EPO reveals a profound democracy deficit as well as growing dangers to Europe’s businesses — the productive firms to which patent maximalism often represents far more risk than opportunity



  11. Guest Article: The Free Software Movement Should Come Out From the Box

    "From now onwards we have to think from a user’s rights perspective and mobilise users of Free software. They should know what rights they ought to get."



  12. IRC Proceedings: Friday, December 13, 2019

    IRC logs for Friday, December 13, 2019



  13. Links 13/12/2019: QEMU 4.2.0, GNU Guile 2.9.7

    Links for the day



  14. Links 13/12/2019: Zorin OS 15.1, Vim 8.2

    Links for the day



  15. Linux Foundation Has Outsourced All the Licence Compliance Stuff to Microsoft, a Serial GPL Violator

    OpenChain Specification/OpenChain Project and Automated Compliance Tooling (ACT) are yet more examples -- the latest of many -- of the Linux Foundation being outsourced to Microsoft, not only for code but also documentation and hosting



  16. IRC Proceedings: Thursday, December 12, 2019

    IRC logs for Thursday, December 12, 2019



  17. Copyleft: Keeping Code Free

    Now that news about "Linux" is dominated by promotion of proprietary software we ought to remember what perpetrators of such a strategy seek to eliminate



  18. Plans That Worked, Plans That Failed

    "I am still looking for good news, but the more good I try to find, the more nastiness I uncover. This is by far, Free software's worst year ever. 2019 Sucks!"



  19. Links 12/12/2019: KDE Applications 19.12, Qt Creator 4.11, New VirtualBox

    Links for the day



  20. Brand Dilution in Action

    Microsoft's proprietary software which spies on people and businesses is getting a "free ride" on the "Linux" brand; and nobody seems to care, nobody seems to notice how perverse that it



  21. At the EPO Money -- Not Quality -- is King

    Financiers are ruining quality



  22. The EPO's Strategic Failure 2023

    Potemkin social dialogue



  23. IRC Proceedings: Wednesday, December 11, 2019

    IRC logs for Wednesday, December 11, 2019



  24. EPO Promoting Software Patents in Countries Where These Are Illegal

    The EPO's vision of 'unitary' software patents (patents on algorithms in countries that disallow such patents, as per their national laws) won't materialise, but in the meantime a lot of Invalid Patents (IPs) are granted in the form of European Patents (EPs) and this is wrong



  25. We Support GNU and the FSF But Remain Sceptical and Occasionally Worry About an RMS-less FSF

    Richard Stallman (RMS) is not in charge of the FSF anymore (it's Stallman who created the FSF) and there's risk the decisions will be made by people who don't share Stallman's ethics or the FSF's spirit



  26. Links 11/12/2019: Huawei Lobbied by Microsoft (Because of GNU/Linux) and Microsoft Still Googlebombs Linux to Promote 'Teams'

    Links for the day



  27. Links 11/12/2019: Edge Native Working Group, CrossOver 19.0 Released

    Links for the day



  28. Instead of Fixing Bug #1 Canonical/Ubuntu Contributes to Making the Bug Even More Severe (WSL/EEE)

    Following one seminal report about Canonical financially contributing to Microsoft's EEE efforts — celebrated openly by GNU/Linux opponentsclosing bug #1 Ubuntu basically decided not that it was fixed but that it would no longer attempt to fix it (“wontfix”)



  29. IRC Proceedings: Tuesday, December 10, 2019

    IRC logs for Tuesday, December 10, 2019



  30. Today's Example of Microsoft's Faked 'Love'

    “On 7 September 2017, users began noticing a message that stated “Skype for Business is now Microsoft Teams”. This was confirmed on 25 September 2017, at Microsoft’s annual Ignite conference,” according to Wikipedia


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