06.28.14
Gemini version available ♊︎‘Open’ Nastiness: Openwashing of OOXML in Order to Make Microsoft the Standard and Bury ODF
Summary: Another step in the long struggle to cast proprietary as ‘open’, especially when it comes to Microsoft’s last remaining cash cow and Facebook’s core business of mass surveillance
Openwashing has been a key ingredient of Microsoft’s strategy as of late, pretending that its privacy violations and patent racketeering are somehow outweighted by some kind of goodwill. This is something that not only Microsoft does but also the (partly) Microsoft-owned Facebook is doing quite a lot these days. It is truly disturbing.
Angus Kidman said that “Open [sic] XML is the format which Microsoft Office has used to store Office documents since Office 2007″ even though it is untrue. Almost nobody used it at the time, so Microsoft bribed and corrupted so many people and organisations, hoping to universally impose OOXML on people, pretending it was “open” even though it was all about proprietary Office. Nobody was going to use something so unnecessary, so Microsoft bribed many people for this, including large companies, as compatibility with existing formats had improved and the goalposts needed to be moved. Here is LibreOffice’s Meeks, who was surrendering to Microsoft’s proprietary OOXML rather than adhering to standards like ODF, probably because he was paid by Novell at the time (and Novell was bribed by Microsoft specifically — as per the contractual agreement — to promote and openwash OOXML).
“When the press is trying to insinuate that Microsoft (Office) and Facebook are open there is clearly something wrong with the press.”So once again they are using “Open Source” to promote proprietary lock-in. This is not a novel concept, Microsoft did this with Novell (converter). Phoronix says: “This work may benefit some open-source document editors / office suite software, with more commentary being available from Michael Meeks’ blog.”
How is being reliant on OOXML beneficial to anyone but Microsoft shareholders? This is a trap. We need to reject this format. Google too should stop its unhelpful backing of OOXML, which is getting more detrimental by the day (more of it in the company’s latest event was disclosed, affirming Google’s lack of commitement to document standards).
As noted by some bloggers and writers for the European Commission’s Web site: “To ensure preservation of digital assets, it is essential that specific file formats are implementable in open source software, concludes Björn Lundell, associate professor at the University of Skövde in Sweden. He recommends this should be made a requirement for digital asset strategies of public administrations, thus minimising the risk of losing control over these assets.”
Well, there are patents in OOXML and complexity which shows that it’s really just designed around one implementation in a proprietary form (Office). OOXML should be rejected, especially in the public sector. There is nothing open about it. It’s a massive lie.
Nicholas Miller from VentureBeat and others play a role in a similarly-disturbing campaign that seeks to paint Facebook as “open”. With press release-oriented ‘journalists’ out there it has been quite easy. The Facebook openwashing that we recently wrote about is further promoted by pro-Facebook sites that use semantic jokes to get across this illusion.
When the press is trying to insinuate that Microsoft (Office) and Facebook are open there is clearly something wrong with the press. These are systematic and very persistent (especially this year) openwashing campaigns that everyone should push back against because these deceive and help derail real Free software. █
ᶃ Gemini Space
This post is also available in 
Content is available under CC-BY-SA