08.02.14
Posted in Microsoft, Open XML, OpenDocument, OpenOffice at 3:39 pm by Dr. Roy Schestowitz
Summary: Microsoft continues to distort the office suites market and impede interoperability using the OOXML pseudo ‘standard’, essentially by branching out into “Strict” and “Transitional”, making it exceedingly hard for developers to deal with files generated by Microsoft Office and vice versa
TRYING to work with Microsoft is misguided. Just look and see what has happened to many companies, including — to name a recent example — Nokia. Microsoft has no honour for anyone but Microsoft itself. Microsoft was bribing officials and abusing sceptics in order to get its way when it comes to document formats. Nobody should forget the crimes that Microsoft committed in order to keep the world stuck with Microsoft Office. We reminded the British government of these crimes and very recently the UK adopted ODF. This was a very smart and timely move because based on people from The Document Foundation (TDF), the bogus ‘standard’ which is basically just an ‘open’-looking gown for Microsoft Office (proprietary) formats is now being further distorted in order to cause trouble for people who are not Microsoft customers. These abuses are even worse than before and Microsoft thinks it can get away with them because it bribed people to put an ECMA and ISO stamp on OOXML (no matters what happens to it later on).
As Charles from The Document Foundation put it the other day:
Regular readers of this blog will remember these glorious days, just before the big financial crisis, where Microsoft had created the so-called OpenXML standard that was supposed to be totally not competing against the OpenDocument Format, managed to have pretty much the entire standards community swallow it in the most creative ways possible, then fell short of actually implementing it in its own products. A good summary of the whole -technical- story is available here. The irony of life has the uncanny ability to devise ways to enchant us. Well, sort of. The format called “OOXML – Strict”, by comparison to “OOXML-Transitional” was the readable open part of the ISO 29500 standard, known as OOXML. For years, it was obvious that Microsoft Office implemented OOXML-Transitional (the heap of the more or less documented parts of the format alongside undocumented blurbs) and nothing else, creating a situation where one standard, OOXML was existing, and another format, OOXML, was fully implemented and spread all around, yet was an undocumented, proprietary specification. That’s the .docx, pptx, and .xlsx you see everywhere, and the one LibreOffice was busy reverse-engineering for all these years.
This unfortunate situation, we were told, was about to change soon, with the full adoption of OOXML-Strict by Microsoft Office. Helas, if you open a purely OOXML-Strict compliant file with Microsoft Office 2013, the file will be declared corrupt. If you open the same one with LibreOffice 4.3, the file will open and you will be able to edit its contents just like with any other format supported by LibreOffice. In other words, LibreOffice can claim to have a better support of OOXML than Microsoft Office, despite years of unfulfilled promises, pledges, and never met expectations by Redmond. I guess that, just like the old saying goes, promises only commit the ones who actually believe them.
IBM’s Rob Weir has just released another piece about document formats [1] and a new interview with Italo Vignoli of The Document Foundation [2] sheds more light on what Charles spoke about. To quote Vignoli: “MS Office locks-in the user not only with proprietary formats but also with the OOXML pseudo-standard format. This is due to the way the supposedly standard format is handled by MS Office.
“In fact, each version of MS Office since 2007 has a different and non standard implementation of OOXML, which is defined as “transitional” because it contains elements which are supposed to be deprecated at standard level, but are still there for compatibility reasons.
“Although LibreOffice manages to read and write OOXML in a fairly appropriate way, it will be impossible to achieve a perfect interoperability because of these different non standard versions.
“In addition to format incompatibilities, Microsoft – with OOXML – has introduced elements which may lead the user into producing a non interoperable document, such as the C-Fonts (for instance, Calibri and Cambria).”
When Microsoft speaks about following standards what it means to say is that “Microsoft is the standard” and everyone must just follow Microsoft. Only a fool would choose OOXML over ODF, especially now. Korea and China seem to be moving away from Office quite rapidly. █
Related/contextual items from the news:
-
And then there is a document as the record of what we did. This is implied by the verb “to document”. This use of documents is still critical, since it is ingrained in various regulatory, legal and business processes. Sometimes you need “a document.” It won’t do to have your business contract on a wiki. You can’t prove conformance to a regulation via a Twitter stream. We may no longer print and file our “hard” documents, but there is a need to have a durable, persistable, portable, signable form of a document. PDF serves well for some instances, but not in others. What does PDF do with a spreadsheet, for example? All the formulas are lost.
-
The UK government recently announced that they would use ISO approved document standard ODF for viewing and sharing government documents. It’s a very important move because it breaks Microsoft’s vendor lock where single US-based company ‘owns’ and ‘controls’ all the documents created on Earth. Microsoft is infamous for using unethical means to make it harder for other players to offer any kind of interoperability with their products which can threaten Microsoft’s market share.
So we reached out to Italo Vignoli of The Document Foundation, the organization responsible for developing LibreOffice which is a fork of OpenOffice, to understand the risks of using OOXML…
Permalink
Send this to a friend
07.24.14
Posted in Microsoft, Office Suites, Open XML at 1:39 am by Dr. Roy Schestowitz
Summary: Only “Microsoft as the standard” is the ‘standard’ Microsoft is willing to accept, as its response to the Cabinet Office’s judgment reveals
AT THE BEGINNING of this week we learned that the British (UK) Cabinet Office, a highly influential department with technology imperatives, did the correct thing by no longer requiring British citizens to become clients of Microsoft (and users of expensive spyware) to merely communicate with their government. The Cabinet Office “goes open source” is how one news site put it, but ODF, the OpenDocument Format, is not necessarily about Free/Open Source software. ODF is about many applications working together, not via formats that are designed around a single application and its various versions (that’s what OOXML is).
Techrights did not break this news. It was Andy Updegrove who did, along with Cabinet Office. Quoting Updegrove:
The U.K. Cabinet Office accomplished today what the Commonwealth of Massachusetts set out (unsuccessfully) to achieve ten years ago: it formally required compliance with the Open Document Format (ODF) by software to be purchased in the future across all government bodies. Compliance with any of the existing versions of OOXML, the competing document format championed by Microsoft, is neither required nor relevant. The announcement was made today by The Minister for the Cabinet Office, Francis Maude.
The Cabinet Office stated:
The open standards selected for sharing and viewing government documents have been announced by the Minister for the Cabinet Office, Francis Maude.
Not too shockingly, as one ought to expect, the following day Microsoft attacked this decision. despite claiming to have ‘embraced’ ODF. “Microsoft attacks UK government decision to adopt ODF for document formats” said one headline, stating: “Microsoft has attacked the UK government’s decision to adopt ODF as its standard document format, saying it is “unclear” how UK citizens will benefit.
“The Cabinet Office announced its new policy yesterday, whereby Open Document Format (ODF) is immediately established as the standard for sharing documents across the public sector, with PDF and HTML also acceptable when viewing documents.”
“Turning its back on Microsoft Office’s native formats, the UK government has adopted the Open Document Format for all its sharable documents,”
writes Steven J. Vaughan-Nichols, but if Microsoft is really all about openness, then Microsoft should welcome this decision, not attack it. It is quite revealing that Microsoft is not really interested in fair competition, interoperability, and openness.
“UK government makes “big step forward” on open document standards,” said the headline from Opensource.com (Red Hat).
We already wrote so much about it and warmed the Cabinet Office about Microsoft’s abusive responses, which include trying to get people fired, bribing some other people, using (or exploiting) disabled people to attack people’s rational decisions, and so on.
Dr. Glyn Moody wrote about “Massachusetts ODF fiasco a decade ago” and said about this important milestone: “Let’s Not Mess it up””
While celebrating this great news, I really want to emphasise Bracken’s point about managing the switch properly. We can be absolutely certain that Microsoft will fight this decision in every way possible. It will certainly seize on any problems that arise during the implementation as “proof” that it was the wrong choice. That makes it crucial that the open source community do everything in its power to aid the Cabinet Office here.
One particular area that concerns me is cross-compatibility. I’m hearing stories about difficulty in transferring ODF files from LibreOffice to Apache OpenOffice, with formatting of things like tables being messed up in the process. This is completely unacceptable: one of the benefits of adopting an open standard is the ability to swap in and out different applications. If that theory proves impossible in reality, we have a huge problem.
I would therefore like to entreat all the open source projects and communities that work on ODF to get together and sort this out. In the wake of the fantastic – and brave – move by the Cabinet Office, providing full interoperability among open source implementations must be a priority.
Yesterday’s news is truly a unique opportunity to show the power of open standards, to promote the benefits of open source, and to bring about its wider dissemination both in government, and among home users. The price of failure here would be extremely high: yet more years in the wilderness, as happened after the Massachusetts ODF fiasco a decade ago. So let’s not mess it up.
The Mukt, which covered this important development. delivered yet another call for Google to adopt ODF as the default document format, ending Google’s cowardly approach towards document formats.
We feel as though we played some role in the above (being among hundreds of people who wrote to the Cabinet Office). We not only wrote a lot about it and also wrote to the Office itself almost a dozen times, engaging in a discussion with members of staff. █
Permalink
Send this to a friend
05.11.14
Posted in Europe, Free/Libre Software, FUD, Microsoft, Open XML, OpenDocument at 4:39 am by Dr. Roy Schestowitz
Image from the 10 Downing Street Web site
Summary: A roundup of resistance to OpenDocument Format (ODF) and Free/Open Source software (FOSS) in the British public sector
AS ONE ought to expect, especially based on past experiences, a migration to FOSS won’t happen without resistance from an old generation of Microsoft proponents. Just watch how Microsoft rallied its partners to object to a pro-ODF consultation (we explained Microsoft's very dirty tactics to the Cabinet Office). It didn’t quite end there.
Despite the fact that a foreign government is cracking PCs with Windows on them (and seeking to make this practice legal), some people in suits here in Britain insist that Windows in the public sector is an acceptable risk. It’s not. It should be banned. Well, some government departments quietly move towards FOSS (I work with them) and numerous keep quiet about it for fear of retribution from Microsoft and/or its partners, who view FOSS like it’s some kind of Communism that’s spreading.
Continued resistance from Luddites and “tribe elders” of technology (who grew up in another type of world and dined with executives of proprietary software vendors) was expected all along. The ODF consultation showed just one portion of it (publicly-visible, unlike some stories I know of but cannot share).
One reader asked me yesterday: “what became of that government consultation?”
Well, nothing so far, as far as we know. This new article that this reader sent us states: “if you blithely email someone a .docx file you are effectively condemning them to pay rent to Microsoft for ever.”
Indeed, and this too is a reason to shun Microsoft, not just the back doors. The author continues by stating: “One way to loosen the corporate stranglehold would be for everyone to adopt the set of standards called Open Document Format, designed so the files work the same whatever software or computer type you use.”
Yes, indeed, but there are people who stand in the way of implementing national (top-down) policy.
Earlier this month there were a bunch of Microsoft-friendly British articles (at least 3), the latest of which is this one. They all cite Jos Creese (the original/seminal article was this, but it led to some more, even overseas), relaying claims that “Microsoft is cheaper” (than FOSS).
This is wrong on so many levels. It very much depends on what’s calculated and how. OOXML is massively dangerous lock-in. Microsoft had to corrupt the world’s standards bodies to get it where it is today. The bribery for Windows-only formats was documented here half a decade (or more) ago and it was coupled by patent extortion, bribing of companies, and all sorts of other criminal acts. To say that Microsoft is cheaper is almost like saying that robbing a bank is cheaper than working (labour) for the same money. To use a better analogy, to get oneself locked into one vendor is not “cheap”. It has been reported that the British government pays ~$10,000 per Windows desktop per year. Cheap, eh? It’s more like extortion. There is a monopoly on support.
Concurrently, Adrian Bridgwater offers some convenient hogwash that ‘vanishes’ Microsoft’s criminal activities against GNU/Linux, pretending that there is something inherently wrong with FOSS and/or GNU/Linux and that this is the reason it does not (yet) dominate the desktop. Never mind OOXML abuses, bribes against GNU/Linux (we documented some), and many other forms of manipulation. This is the type of revisionism that Microsoft requires right now, creating the illusion that FOSS is inadequate for desktop use, even though Chromebooks are taking off (they run GNU/Linux), defying Microsoft’s vicious attack ads.
One commentator at IDG alluded to the above people as “clueless CIOs” in his headline, stating that “companies are using open source to bring their legacy apps up to code, but all too many CIOs are still clueless about how often open source is being used in their own organizations.”
It wasn’t just clueless CIOs like Jos Creese who offered Microsoft lip service in the British press earlier this month, proposing lock-in rather than freedom because lock-in is supposedly “cheaper”. Another article, citing another bunch, speaks about LibreOffice/OpenOffice, focusing on Microsoft macros lock-in and OOXML lock-in to make FOSS seem inadequate. Titled “Open source ‘fails to excite councils’”, the article makes arguments like the following:
It added that open source software is seen to be difficult to replicate automated interfaces to Microsoft Office products which connect with council systems.
This is precisely the reason to dump Microsoft, not to avoid dumping Microsoft. This is evidence of lock-in and the better one gets out of the lock-in, the better.
On a brighter note, there is a new article from Ireland titled “open source is where I think the future is headed in local government…”
It is not a formal article, but it shows that people — influential people even — do in fact promote FOSS. To quote:
So, I’m in Dublin tomorrow for the OGP Europe Regional conference in Dublin in advance of next week’s Digital Lunch asking if Northern Ireland is ready for an open government partnership? If you are interesting in the subject, do keep an eye on Twitter throughout the day, and I’ll update with a blog report on Friday morning before I leave again.
It is expected that in the coming months or even years some vassals of Microsoft will go public (to the press) bashing FOSS with FUD, misdirection, miscalculations and stereotypes, sometimes criticising FOSS for not being sufficiently Microsofty (e.g. dealing with OOXML). Their arguments often insinuate that abandoning Microsoft would be wise (the opposite of what they mean to say); the British public sector got caught up in expensive and dangerous (back doors for starters) dependence. Free software would give Britain back its sovereignty. Technical autonomy is priceless; it is invaluable. █
Permalink
Send this to a friend
04.06.14
Posted in Europe, Microsoft, Office Suites, Open XML, OpenDocument, OpenOffice at 9:31 am by Dr. Roy Schestowitz
Preservation a priority
Summary: The Document Liberation Project makes the press and software such as LibreOffice plays a role while other players, such as Open-Xchange, are also hopping on the ODF bandwagon
IN THE MONTHS of February and March we revisited ODF because of a policy that had been promoted in the UK — one which favours disseminating government documents not just to customers of Microsoft (who purchased proprietary software like Microsoft Office).
The problems caused by OOXML are explained again by one whom we interviewed in episode 74 of TechBytes. His name is Charles-H. Schulz and he is from LibreOffice. He says that “Microsoft Office had been released and with it an undocument format called OOXML which, as far as experts were concerned, had little to do with the ISO 29500 (aka OOXML) standard. While Europe and Brazil were struggling to migrate their public sector’s documents to ODF, any company or government, let alone any individual acquiring Microsoft Office 2010 migrated to the new and shiny OOXML, officially without remorse or complaint. The ODF advocacy groups here and there were launching all sorts of events and meetings to guide and assist migrations to ODF. Results were mixed. We had victories. We had defeats. At the end of the day what was at stake was fear of failure and change from CIOs and IT services. That’s still the case today. But while these are mostly human factors, there is one thing we hadn’t tried yet, or at least hadn’t been tried enough: turning the hundreds of thousands of files that are out there and locked up in various proprietary file formats to ODF documents.”
Another advocate of ODF, Andrew Updegrove, tells the story of Microsoft’s attacks on officials who ‘dared’ to promote ODF. Updegrove recalls: “By the end of December 2005, I had been blogging on ODF developments in Massachusetts for about four months, providing interviews, legal analysis and news as it happened. In those early days, not many bloggers were covering the ODF story, and email began to come my way from people that I had never met before, from as far away as Australia, and as near as the State House in Boston. Some began with, “This seems really important – what can I do to help?” Others contained important information that someone wanted to share, and that I was happy to receive.”
We are not going to go about a decade into the past again, but the point worth making is that OOXML remains a huge issue. Microsoft’s worldwide bribery was not in vain. My wife reports that OOXML crashes LibreOffice (on GNU/Linux) for her, sometimes even freezing the entire operating system.
Making the news these days is the Document Liberation Project [1-3], which even Updegrove wrote about [4]. For those who think that ODF is old news, be aware that Open-Xchange is entering the online office suites business [5,6] and “support for the Open Document Format (ODF) is forthcoming, probably within the next three months, a company spokesman said.” (source: IDG)
Later this year we are going to see if the British government, owing to Cabinet Office, goes ahead with plans of making ODF the default format for editable document exchanges. This could set an important precedence for other nations to follow, ensuring that their documents down fall down the digital ashtray with Microsoft’s proprietary formats. █
Related/contextual items from the news:
-
Ever been in a situation when no maintained software reads your old files? During Libre Graphics Meeting 2014, Document Foundation announced a new project called Document Liberation.
This project unites developers who help users to access data in file formats that are locked to proprietary and even abandoned software.
Essentially it’s a new face of the existing joined team from LibreOffice and re-lab that is already “responsible” for libraries to read and convert Corel DRAW, Microsoft Visio and Publisher, Apple Keynote and Pages files. Implementations in end-user software include (but are not limited to) LibreOffice, Inkscape, Scribus, and Calligra Suite.
-
New open source developer consortium promises to end upgrade arms race, enabling users to reclaim orphaned documents
-
-
You’ll recall that I noted above Document Freedom Day awareness is limited in the U.S. So is participation in DFD activities, as you can see from the image at left, which shows where they are being held this year. That’s a shame, because document freedom is a universal, and not a regional or national concern.
-
Open source collaboration software vendor Open-Xchange has added a spreadsheet function to its open-source, web-based productivity suite, allowing the online editing and sharing of Microsoft Excel documents.
-
Permalink
Send this to a friend
03.26.14
Posted in Europe, Microsoft, Office Suites, Open XML, OpenDocument at 11:40 am by Dr. Roy Schestowitz
Summary: The long battle against comment censorship and the outcome of watering down of text regarding Microsoft’s OOXML abuses
TODAY is the annual celebration of ODF, as we noted earlier this week. This means that we need to remind ourselves of the importance of ODF, or contrariwise for OOXML and other binary formats, the travesty which is corruption-backed and monopoly-enabling lock-in.
Here in the UK there is some policy to be proud of. Despite a history of Microsoft lock-in, there are many moves right now which indicate that the government is changing its colours. In my daytime job I have about 5 British government clients, so I can see that they are genuinely transitioning/migrating to Free software (without announcing it), little by little, piece by piece. Liam Maxwell was quoted yesterday in the press as suggesting that the British government’s open source code is one of UK’s best exports [1]. This may as well be true. Coming out of the projects with British government clients there’s some source code and expertise. One day in the future, when the fury of proprietary software giants becomes a lesser powerful force (just see what happened in Munich), the British public will probably hear more about this.
Out of sincere concern, a month or so ago I wrote to Cabinet Office and exchanged numerous E-mails with Cabinet Office staff. The staff was polite and conversational, but it was reluctant to facilitate free speech to its fullest. Here is the story in full.
In posts that we published in some recent weeks we called for people to submit comments on a consultation which suggested ODF as the document standard in the UK. After publishing a comment we were rather appalled to see continuous attempts to censor and then, after some pressure from us, to water down the comment and finally not to even publish the watered-down comment (until further insistence from us). This should be noted because the Cabinet Office is funded by taxpayers like myself; it oughtn’t act as a gatekeeper against frank assessment from those who are funding it. People like Andy Updegrove [2] and Susan Linton [3] at OStatic [4] (who wrote about this) are US citizens, so they are not funding the Cabinet Office and it would be almost acceptable for the Cabinet Office, which is designed to serves UK interests, to discard comments from them (no offence intended to US citizens). The same goes for Microsoft’s comments and arguably for the FSFE, which is mostly Germany-based but submitted comments [5], adding to hundreds more [6]. There is some belated coverage of this from the British news sites like Computer Weekly [7,8] and PC Pro [9], which paraphrases LibreOffice as saying “ignore Microsoft’s “nonsense” on government’s open source plans” (Microsoft cares only about Microsoft, not British citizens).
I would like to outline my conversations (behind the scenes) with Cabinet Office staff, at the very least because it can serve as a warning to anyone who thinks that Cabinet Office is open to feedback from all British citizens, even those who know what they are talking about, are polite, and if I dare say professional (my connections to the Cabinet Office are indirectly professional and contractual).
Putting it a little more chronologically but also contextually, the Cabinet Office staff told me after my comment had been rejected:
Hi Roy
We’ve extended the comment period to 5pm Friday due to the server issues we encountered last night.
One of our moderator’s is currently reviewing the email draft you sent in last night – we’ll get back to you on that before you resubmit through the Hub just in case there is anything else that doesn’t meet the moderation policy.
Thank you so much for your patience and persistence.
I resubmitted earlier that day when it was made possible again. This was after some failed attempts to do so. It probably took me 5 times more time revising my comment than it took me to originally write and ghost-read it.
Submitting a comment should not be as hard and time-consuming as submitting an academic article to a top journal, but when barriers are put up it discourages participation and waters down a message. This is the kind of thing that led me to quitting Datamation, where I had done some journalism around the time of OOXML scandals. Entire sentences would be omitted by the editors and inflammatory/provocative headlines replace my own, removing my ability to give an accurate assessment of the situation, knowing that Microsoft was an advertiser but not letting this induce self-censorship. This is how the gatekeepers of business-friendly people (supposed gentleman’s style) typically work, marginalising voices of honesty and reason.
It’s worth repeating: I spent about five times more time revising the text to appease the moderators than I did actually writing my original text. I was close to just giving up at numerous points during the process, but knowing that this ordeal in itself would be useful to report on kept me going. A submission to the Standards Hub is not easy, unless one posts ‘softball’ points that challenge little or nothing, bringing nothing new to the table.
Here again is what I was told:
Thanks, Roy
Please could you also ensure that anything that might be considered defamatory that is an allegation rather than a proven (legal) point is clearly described as such.
But there was nothing defamatory. To say “defamatory” is to simply claim that any strong claim is not worthy of consideration, irrespective of evidence that supports it.
Here is my response:
Without a specific pointer this is too broad for me to address. Allegations, e.g. in a court case, are points which are yet to be affirmed by lengthy judgment, based on presented evidence. I have a lot of evidence but no judge to assert that it establishes guilt and punishment. The OOXML-related misconduct already took the BSI to court in the UK — a case which was no longer pursued because of the associated costs. The plaintiff was deterred by financial costs incurred by each motion. I am not trying to be cynical about the justice system, just to say that requirements such as “proven (legal) point” would basically disqualify almost every comment left in the consultation so far.
What I am also trying to point out is, sometimes we need to accept statements even without an expensive trial process. Without this leeway we can reject almost every view which we do not like or do not wish to take responsibility for.
I will gladly modify any item you specify, but the above paragraph is vague enough to apply to nearly 100 points that I made. Feel free to water down my comment as you see fit; I am not trying to cause trouble, just to share my findings based on thousands of hours of research/readings (mostly in 2006-2009).
And more from Cabinet Office:
As mentioned, we are trying to keep the focus on the standards and the proposal rather than on wider issues. However, we are also keen that you can express your views on anything that you consider is relevant to our consideration of the standards proposed.
I replied as follows:
My response was focused on a fallacy which was perpetuated and even manufactured by one single entity — the notion that ODF is somehow “anti-corporate” (although it is backed by many corporations) and that OOXML was on equal footing while many who were involved in standardation efforts know this to be charade of misconduct. The ISO came under enormous pressure at the time. I wanted to tackle attempts at revisionism, capitalising on people’s short memory span and loss of journalism from around that time (so-called ‘Internet rot’).
Lobbying along these lines is common and it exploits people’s trust in brands. Several years ago Wikileaks released diplomatic cables which showed that Microsoft had used state representatives to lobby governments and other officials around the world to drop ODF, based on complete fabrications. I want to ensure those who are involved in the process in the UK do not get bamboozled, or at least have access to information of relevance, refuting false claims.
I asked a friend for an opinion regarding my original text and he said:
This part hits one something really important.
The European Commission said it would investigate this, but the huge extent of Microsoft’s abuses are,*according to the Commission itself*, why it no longer pursued this, even after it said it would (too many resources would be required because of the international scale)
MS basically overwhelms with its ability to be corrupt and act illegally and unethically. The result is that most people and governments throw up their hands and give in. That’s the opposite reaction as what is needed.
Also this:
It’s not a British company and it is not an ethical company
both points need to be accepted by the government. The interests of the government should take into account only the benefits of its citizens and agencies, not hostile, foreign companies. It’s not British. (Then again, neither am I.)
Microsoft tried using other British companies as proxies, trying to make it seem as though Microsoft’s interests were Britain’s interests (maybe for a fraction who are Microsoft partners).
Well, a day later, seeing that they had not published my comment, I assumed it could have been lost by mistake, so I posted it again.
Still nothing. Stonewalled.
I then mentioned it in social networks including Twitter. I chastised Cabinet Office in public, whereupon I got a private E-mail from Cabinet Office. If I hadn’t criticised Cabinet Office’s deleltionism (and had thousands of followers in Twitter) I probably wouldn’t have heard anything from them. That’s a crucial point. Silent censorship is probably the worst type of censorship. Nobody even knows about it.
Towards the end of the correspondence with Cabinet Office there was more watering down of words, e.g.;
Hi Roy
Thank you for spending time on this. Much appreciated.
Just one remaining concern:
“Bribed officials (e.g. costs covered to stuff panels) are just the tip of the iceberg.”
As bribery is a legal term, please could you consider expressing this differently?
“Sure,” I said. “I will amend the wording and resubmit.” And so I did. I was also given this assurance:
Hi Roy
I’ve copied your text below and highlighted the statements in response to your request.
The Standards Hub is able to feature links to external sources in comments. You should not encounter any issues with a spam filter.
Regards, Linda
I spent a long time revising the text based on comments and then replied as follows:
Thank you for taking the time highlighting the bits of text which you thought would benefit from links. Many of the links I had gathered 7 years ago are no longer accessible (sites offline or change of CMS), but I spent the past hour trying to find alternative URLs, Web Archive URLs, and various reports that are still online.
I posted the amended comment.
“Many thanks for your contribution. It will appear on the site very shortly, just as soon as we have confirmed that it meets the Terms and Conditions.
Thanks for your consideration.
Best regards,
Roy
The references ought to have been enough to support my claims, addressing concerns that that they may be “defamatory or libellous.” To quote the first message that I received:
Dear Dr Schestowitz
Thank you for providing input to the Standards Hub on the document format proposal.
We are keen to publish as many views as possible so that we can make sure that the debate is transparent.
Our moderation policy includes the following statements about what users of the site should not do:
* Make any personal or professional references which might reasonably be considered inappropriate, defamatory or misleading * Break the law (this includes libel, condoning illegal activity and contempt of court)
Regarding your submission, there are a few statements that may be considered to be defamatory or libellous.
We value all contributions and would therefore be grateful if you could either:
1) Amend and resubmit your response to remove statements that could be considered to be defamatory or libellous; or
2) Edit your response to include links to support the information presented such as court cases or Commission statements which offer evidence of these events having occurred.
I appreciate this may be frustrating but we need to keep the focus on the standards being considered.
*Please remember the submissions will close by end of day today – Wednesday 26 February.*
My response was as follows:
Thank you for responding. Can you please highlight the part which you deem in need of references and those which you prefer omitted? I usually omit links from such submissions simply because excessive use of links tends to be treated — automatically — as spam. I can link to the original sources where you deem it necessary or omit sentences altogether.
I appreciate you try to cover yourselves in case a complaint is made, but if we do not allow strong statements to be made, then we are limiting free speech in such a way that can be exploited by wrongdoers (UK libel law has probably spiked many important articles we’ll never know about).
I have accepted about 50,000 comments over the years and never deleted a single one (except spam), even when I was faced with libelous and racist personal attacks. Free speech means free speech; libel is another thing. There are laws to deal with libel. There are also laws to deal with identity theft, copyright infringement, etc.
I asked an old friend for his assessment of this situation and he said the following:
Interesting – I recall they have done this before, so they’re obviously v cautious here. Also, MS might seize on it as “proof” of the process’s lack of legitimacy etc etc, so perhaps moderating it would ultimately be more effective…
My response at the time was:
I can see the point, but it goes something along the lines of “Microsoft can portray ODF proponent as “radicals” (against crime)” and sometimes it’s more important to show the crime than to hide it for the sake of “professionalism”.
I’d rather amend my comment (if they send me guidance to that effect) than let it be marginalised altogether.
If they don’t help amend it to their “standards” (they have not mailed me back yet), then I will politely point this out. Censorship is one of those things that have “repeat offenders” and unless you speak about censorship it’ll never be noticed. You’d be shocked to see the kind of comments of mine that ZDNet deleted. People contacted me later to say that they too had been censored (by CBS/ZDNet).
Eventually, after several iterations, I amended all the text as Cabinet Office suggested. I could not access the site at that moment in order to submit the comment before midnight. The site was not responding; It was totally down. Thankfully, the deadline got extended.
Here is my near-final text (which would be moderated/watered down further):
The only opposition to ODF comes from one single entity: Microsoft. It’s not a British company and it is not an ethical company, to say the very least.
Microsoft would like us to believe that “Open” XML (an Orwellian name) is a “standard” without telling how it became a “standard”, starting with ECMA, where key officials publicly gloated about the bad process (e.g. watch this video starting 4:10; that is Jan van den Beld, former Secretary General of ECMA, saying that the mentality is: “You are well paid, shut up”), and the ISO, from which key/top members resigned following what Microsoft had done (while specifically citing what Microsoft had done). To give one notable example, the very Convenor (top position) of ISO/IEC JTC1/SC34 WG1 wrote about the vote-rigging: “This year WG1 have had another major development that has made it almost impossible to continue with our work within ISO. The influx of P members whose only interest is the fast-tracking of ECMA 376 as ISO 29500 has led to the failure of a number of key ballots. Though P members are required to vote, 50% of our current members, and some 66% of our new members, blatantly ignore this rule despite weekly email reminders and reminders on our website. As ISO require at least 50% of P members to vote before they start to count the votes we have had to reballot standards that should have been passed and completed their publication stages at Kyoto. This delay will mean that these standards will appear on the list of WG1 standards that have not been produced within the time limits set by ISO, despite our best efforts.
“The disparity of rules for PAS, Fast-Track and ISO committee generated standards is fast making ISO a laughing stock in IT circles. The days of open standards development are fast disappearing. Instead we are getting “standardization by corporation”, something I have been fighting against for the 20 years I have served on ISO committees. I am glad to be retiring before the situation becomes impossible. I wish my colleagues every success for their future efforts, which I sincerely hope will not prove to be as wasted as I fear they could be.”
Systematic corruption cannot be ignored and the debate cannot be framed as one where we look at stamps of approval alone.
As a researcher, a former journalist, and a webmaster of sites which receive hundreds of millions of hits annually, I already wrote almost 1,000 articles on the topic of OOXML, sacrificing a lot of my time because this classic case of a bad process was too serious to be ignored. The European Commission said it would investigate this (one of several different investigations in Europe).
Microsoft allegedly went as far as pushing senior people out of their jobs if they dared to oppose OOXML (one notable example is Peter Quinn because it was widely covered at the time). There are documented examples as such. Sadly, as much of this happened 7 years ago, many of the links are now broken/articles gone and the Web Archive (let alone search engines) does not always retain a copy.
This is not atypical for Microsoft; Microsoft had done similar things (and got caught) a decade earlier when it faced antitrust charges (c/f US DOJ vs Microsoft). Alleged ballot stuffing, alleged insiders in committees, alleged financial favours etc. are Microsoft’s way of doing business and here too we should expect to see it.
I wrote extensively about technical issues in OOXML, as well as legal issues such as patents. Some of the letters to you may have already covered at least a small subset of those. There were protests in numerous places including Poland and Norway, where members of the standardisation process marched the streets in protest. That’s how bad it was.
There was a BRM in Switzerland — a jaw-dropping case of a ludicrous process. This was part of how Microsoft got its “standard”, ignoring thousands of listed and properly enumerated issues. It would be impossible to list these exhaustively in a letter because there were literally thousands of pages detailing technical issues. These were discarded, ignored, and the attendees appalled by what they clearly considered to be a deeply rigged process.
Microsoft was flying journalists to Seattle (at Microsoft’s expense) in order to manufacture favourable articles (“Brett Winterford [the author] travelled to Redmond as a guest of Microsoft”). Microsoft offered delivered presentations and studies from so-called ‘independent’ experts who would soon thereafter be hired to work full time at Microsoft. There were attempts to equate ODF with one single company (notably IBM) and attempts to equate ODF with a particular piece of software when ODF was in fact backed by hundreds of entities, both from the private and public sector. Many programs support ODF, and they support is very well. OOXML is just a rebranding of closed Microsoft formats (legacy), propped up by companies which Microsoft paid specifically for the purpose of backing OOXML (there are publicly accessible documents that clearly support these allegations). OOXML is about protecting the common carrier, Windows, creating lock-in for a cash cow. British taxpayers cannot bear these costs anymore.
I would like to quote a leaked Microsoft document which was presented in a case against Microsoft in the United States. The internal document stated: “A stacked panel, on the other hand, is like a stacked deck: it is packed with people who, on the face of things, should be neutral, but who are in fact strong supporters of our technology. The key to stacking a panel is being able to choose the moderator. Most conference organizers allow the moderator to select die panel, so if you can pick the moderator, you win. Since you can’t expect representatives of our competitors to speak on your behalf, you have to get the moderator to agree to having only “independent ISVs” on the panel. No one from Microsoft or any other formal backer of the competing technologies would be allowed -just ISVs who have to use this stuff in the “real world.” Sounds marvellously independent doesn’t it? In feet, it allows us to stack the panel with ISVs that back our cause. Thus, the “independent” panel ends up telling the audience that our technology beats the others hands down. Get the press to cover this panel, and you’ve got a major win on your hands.”
This basically sums up what Microsoft is allegedly trying to do in order to derail British standard policies at this moment. This was done before in many places and at different times. As one who works for British government clients I am very familiar with some of the ways in which Microsoft tries to interfere with standards and with competition, claiming to pursue “choice”. Do not be misled by claims of victimhood and appeals to fairness which are actually just self interest, designed to increase licensing costs and dependence of software from the United States.
Microsoft’s OOXML is so “open” that when I leaked it on my Web site (should be fine for “open” document) I received legal threats. The purpose of the leak was to highlight many technical flaws which Microsoft hid using restrictive access and prohibitive costs, leaving information to only a few insiders in the know, much like TPP and other secret “free trade” negotiations.
Be strong in the face of bullying and pressure. Microsoft would not permit open standards to be accepted. That would give people a choice of platform, a choice of an office suite, and the choice of long-term preservation of their data.
Further modification to change words (notice how it’s made more gentle):
The only opposition to ODF comes from one single entity: Microsoft. It’s not a British company and it is not an ethical company, to say the very least.
Microsoft would like us to believe that “Open” XML (an Orwellian name) is a “standard” without telling how it became a “standard”, starting with ECMA, where key officials publicly gloated about the dodgy process (e.g. watch this video starting 4:10; that is Jan van den Beld, former Secretary General of ECMA, saying that the mentality is: “You are well paid, shut up”), and the ISO, from which key/top members resigned following what Microsoft had done (while specifically citing what Microsoft had done). To give one notable example, the very Convenor (top position) of ISO/IEC JTC1/SC34 WG1 wrote about the vote-rigging: “This year WG1 have had another major development that has made it almost impossible to continue with our work within ISO. The influx of P members whose only interest is the fast-tracking of ECMA 376 as ISO 29500 has led to the failure of a number of key ballots. Though P members are required to vote, 50% of our current members, and some 66% of our new members, blatantly ignore this rule despite weekly email reminders and reminders on our website. As ISO require at least 50% of P members to vote before they start to count the votes we have had to reballot standards that should have been passed and completed their publication stages at Kyoto. This delay will mean that these standards will appear on the list of WG1 standards that have not been produced within the time limits set by ISO, despite our best efforts.
“The disparity of rules for PAS, Fast-Track and ISO committee generated standards is fast making ISO a laughing stock in IT circles. The days of open standards development are fast disappearing. Instead we are getting “standardization by corporation”, something I have been fighting against for the 20 years I have served on ISO committees. I am glad to be retiring before the situation becomes impossible. I wish my colleagues every success for their future efforts, which I sincerely hope will not prove to be as wasted as I fear they could be.”
Systematic corruption cannot be ignored and the debate cannot be framed as one where we look at stamps of approval alone.
As a researcher, a former journalist, and a webmaster of sites which receive hundreds of millions of hits annually, I already wrote almost 1,000 articles on the topic of OOXML, sacrificing a lot of my time because this classic case of bad process was too serious to be ignored. The European Commission said it would investigate this (one of several different investigations in Europe), but the huge extent of Microsoft’s abuses are, according to the Commission itself (as reported at the time by the Foundation for a Free Information Infrastructure’s (FFII)), why it no longer pursued this, even after it said it would (too many resources would be required because of the international scale).
Financially incentivised officials (e.g. costs covered to stuff panels) are just the tip of the iceberg. Spamming officials with letters (not just through partners but also lobbyists, “sockpuppets” who are operated by peripheral staff etc.) is just one of many tactics as well. Microsoft went as far as pushing senior people out of their jobs if they dared to oppose OOXML (one notable example is Peter Quinn because it was widely covered at the time). There are documented examples as such, such as Lassi Nirhamo in Finland. Sadly, as much of this happened 7 years ago, many of the links are now broken/articles gone and the Web Archive (let alone search engines) does not always retain a copy.
This is not atypical for Microsoft; Microsoft had done similar things (and got caught) a decade earlier when it faced antitrust charges. Ballot stuffing, insiders in committees, financial favours etc. are Microsoft’s way of doing business and here too we should expect to see it.
I wrote extensively about technical issues in OOXML, as well as legal issues such as patents. Some of the letters to you may have already covered at least a small subset of those. There were protests in numerous places including Poland and Norway, where members of the standardisation process marched the streets in protest. That’s how bad it was.
There was a BRM in Switzerland — a jaw-dropping case of bad process. This was part of how Microsoft got its “standard”, ignoring thousands of listed and properly enumerated issues. It would be impossible to list these exhaustively in a letter because there were literally thousands of pages detailing technical issues. These were discarded, ignored, and the attendees appalled by what they clearly considered to be a deeply rigged process.
Microsoft was flying journalists to Seattle (at Microsoft’s expense) in order to manufacture favourable articles (“Brett Winterford [the author] travelled to Redmond as a guest of Microsoft”). It seems to be doing something similar in the British press right now (e.g. The Register, which had a search and advertising deal with Microsoft some years back, collectively calls ODF proponents “zealots”). Microsoft offered delivered presentations and studies from so-called ‘independent’ experts who would soon thereafter be hired to work full time at Microsoft. There were attempts to equate ODF with one single company (notably IBM) and attempts to equate ODF with a particular piece of software when ODF was in fact backed by hundreds of entities, both from the private and public sector. Many programs support ODF, and they support is very well. OOXML is just a rebranding of closed Microsoft formats (legacy), propped up by companies which Microsoft paid specifically for the purpose of backing OOXML (there are publicly accessible documents that clearly support these allegations). OOXML is about protecting the common carrier, Windows, creating lock-in for a cash cow. British taxpayers cannot bear these costs anymore.
I would like to quote a leaked Microsoft document which was presented in a case against Microsoft in the United States. The internal document stated: “A stacked panel, on the other hand, is like a stacked deck: it is packed with people who, on the face of things, should be neutral, but who are in fact strong supporters of our technology. The key to stacking a panel is being able to choose the moderator. Most conference organizers allow the moderator to select die panel, so if you can pick the moderator, you win. Since you can’t expect representatives of our competitors to speak on your behalf, you have to get the moderator to agree to having only “independent ISVs” on the panel. No one from Microsoft or any other formal backer of the competing technologies would be allowed -just ISVs who have to use this stuff in the “real world.” Sounds marvellously independent doesn’t it? In feet, it allows us to stack the panel with ISVs that back our cause. Thus, the “independent” panel ends up telling the audience that our technology beats the others hands down. Get the press to cover this panel, and you’ve got a major win on your hands.”
This basically sums up what Microsoft is trying to do in order to derail British standard policies at this moment. This was done before in many places and at different times. As one who works for British government clients I am very familiar with some of the ways in which Microsoft tries to interfere with standards and with competition, claiming to pursue “choice” when what it actually means is proprietary software, privacy infringement, lock-in etc. disguised as “choice”. Do not be misled by claims of victimhood and appeals to fairness which are actually just self interest, designed to increase licensing costs and dependence of software from the United States.
Microsoft’s OOXML is so “open” that when I leaked it on my Web site (should be fine for “open” document) I received legal threats. The purpose of the leak was to highlight many technical flaws which Microsoft hid using restrictive access and prohibitive costs, leaving information to only a few insiders in the know, much like TPP and other secret “free trade” negotiations.
Be strong in the face of bullying and pressure. Microsoft would not permit open standards to be accepted. That would give people a choice of platform, a choice of an office suite, and the choice of long-term preservation of their data.
The top of the page said “View published”, but I was unable to find my submission or to even submit it again when the site was back online. This was a frustrating experience. It felt like submitting an academic paper, not a comment.
Here is Cabinet Office explaining the issues of delay:
Since sending my previous email, I’ve had another moderator take a look at your latest comment. I’m afraid that we do have remaining concerns that mean that I’m not able to publish the current version.
We are keen to include views from everyone with an interest and expertise on the topic but we cannot edit submissions on behalf of respondents.
Unfortunately time is also against us. This is frustrating for us all, especially considering the time and effort you have put in.
I’ve pasted below highlighted text which shows where the remaining concerns are – it appears that many of these are allegations. If they could be described as such, this would help to address these concerns.
I appreciate it may become too late for you to amend and resubmit your response through the comment functionality on the Hub as this automatically closes around midnight. For information we are currently experiencing some difficulties accessing the site so would be unable to moderate a new version (you may also be unable to submit).
If it’s not possible to submit through the Comment functionality, please send your comments via Contact Us on the site or directly via email to me and we will still consider your comment in our review.
If you would like to discuss this, perhaps we could speak in the morning.
Thanks for your patience so far.
Another E-mail:
There are just a couple of highlighted areas that you may have missed.
The first (below) we think may be open to interpretation – describing this as what you consider to be a bad process may be a less inflammatory statement.
On the second, we think this may be suspected abuses, rather than proven.
Apologies for asking you to submit again, but grateful if you could consider these comments.
This was actually due to so many versions being abound, after several cycles of revision. I could soon see what had happened. The moderation process led to a confusion, which caused even more frustration. I had two versions of the text in view and I edited both by mistake, so some changes were made in the wrong version. I later submitted what I believed to be a new version incorporating all the changes (lots of work going into it).
The good news came days later:
Hi Roy
Many thanks, just passing it through the moderation and onto the site now. It may take up to 15 minutes to appear.
So this is how hard it has been to post a comment, one among hundreds of comments.
My very watered-down comment was published in this page (nearly the last comment). I had exchanged about a dozen emails with Cabinet Office staff in order to get this done. It’s good in a sense because my arguments penetrated their minds and they followed links. This exposed them to information they would otherwise not be aware of.
“Excellent,” said one of our readers. “I hope that they no longer feel that they have to give Microsoft any favors.” One month later (today), when things have mostly calmed down, I decided write about my ordeal trying to just leave a comment. It’s a long story. “I wonder how many other people they tried to pressure into changing their comments,” said a reader to us, alluding to silent censorship (as mentioned before). Mind the fact that they only tried to change it after I had protested in social media such as twitter, accusing them of censorship. They would not have bothered giving it a chance if I hadn’t worked hard for 5 hours, e.g. fetching old referefences from Web Archive (thankfully it still exists). Whether it was all worth it remains in doubt, even in my own mind (if I knew how much effort this would take I never would have bothered). I hope it stays a prominent comment in the page as it gives Microsoft’s behaviour more visibility. Either way, Cabinet Office staff (several people) read it numerous times and followed the links. In a sense, they had first tried to delete it, but persistence from me and bad publicity for them changed the course of events. I submitted my comment about half a dozen times and it never showed up until the very last attempts. I only received the E-mail offering feedback after I had shamed them over it in public — something that most people cannot do as they don’t have a large audience.
As a side note, our reader argues that “[i]t’s amazing how little coverage Google News gives ODF. None of the recent articles are listed.
“Interesting. Can you spot what’s excluded?”
At the time (end of February) there was very scarce coverage of ODF, irrespective of the Google News algorithm. What we need today is lots of blog posts about ODF and document freedom. This matter has been largely neglected by much of the FOSS community. █
Related/contextual items from the news:
-
The open source code that the government runs is one of Britain’s “great” exports, according to government CTO Liam Maxwell.
Maxwell told the Think Cloud for Government conference in London that the UK benefits from an exchange of knowledge by being open. Most of Gov.uk code is open source, allowing other countries to use it for their own government digital services.
-
Last week I highlighted the fact that Microsoft was urging its business partners to comment at the British Cabinet Office’s Standards Hub on a standards-related proposal. That proposal would limit government procurement to office software that complied with the ISO ODF standard, but makes no mention of the ISO OOXML standard promoted by Microsoft. I also noted that anyone could comment on the proposal, and that the deadline for comments would close on February 26, Greenwich time. I closed by urging readers to let their opinions on the subject be heard.
-
-
The U.K. government is considering a broad move to Open Document Format (ODF), and possibly Libre Office instead of Microsoft Office. That’s not sitting so well with Microsoft, though.
-
The UK government is making progress towards less vendor lock-in. In January, they published a few principles for future government IT contracts. They want to break the dominance of the big software companies who provided the vast majority of software and services to the UK government.
Now they are asking for comments on the standards they should use for “sharing or collaborating with government documents”. Among other things, the government proposes to make ODF the sole standard for office-type documents. The FSFE has submitted comments on a proposal by the UK government to use only document formats based on Open Standards in the future. Microsoft also submitted a lengthy comment, urging the government to include OOXML in its list of standards, to which we responded as well.
-
On 28 January, the UK government asked for public comments on its proposal for standards involved in sharing and working with government documents. Introducing the proposal to use ODF and HTML: “Citizens, businesses and delivery partners, such as charities and voluntary groups, need to be able to interact with government officials, sharing and editing documents. Officials within government departments also need to work efficiently, sharing and collaborating with documents. Users must not have costs imposed upon them due to the format in which editable government information is shared or requested.”
-
It’s now almost six years since I wrote a paper entitled Open Source and Open Standards: Reforming IT Procurement in Government for George Osborne, suggesting that, if elected, the Tories should place the rigorous pursuit of open standards at the heart of their approach to IT.
-
The UK government’s consultation on the use of open document formats has closed, and we now wait for the acid test of the Cabinet Office commitment to open standards.
-
The makers of LibreOffice have slammed attempts by Microsoft to derail the government’s move to open source, accusing the company of protecting its own interests rather than users.
Permalink
Send this to a friend
02.25.14
Posted in Europe, Microsoft, Open XML, OpenDocument at 10:52 am by Dr. Roy Schestowitz
Summary: A call for people to leave a comment/digital letter to British officials who elected ODF as the only document standard for communication with the public
TOMORROW is the last chance to leave feedback on this British consultation (must be registered to leave one’s comment) which we covered in some recent days. Today, in the latest of three previous posts, we covered the disgusting flame and biased coverage from Microsoft apologists who try to incite. They try to make ODF proponent look like a bunch of radicals.
Here is my feedback:
The only opposition to ODF comes from one single entity: Microsoft. It’s not a British company and it is not an ethical company, to say the very least.
Microsoft would like us to believe that “Open” XML (an Orwellian name) is a “standard” without telling how it became a “standard”, starting with ECMA, where key officials publicly gloated about the corruptible process, and the ISO, from which key/top members resigned following what Microsoft had done (while specifically citing what Microsoft had done).
Systematic corruption cannot be ignored and the debate cannot be framed as one where we look at stamps of approval alone.
As a researcher, a former journalist, and a webmaster of sites which receive hundreds of millions of hits annually, I already wrote almost 1,000 articles on the topic of OOXML, sacrificing a lot of my time because this classic case of corruption was too serious to be ignored. The European Commission said it would investigate this, but the huge extent of Microsoft’s abuses are, according to the Commission itself, why it no longer pursued this, even after it said it would (too many resources would be required because of the international scale).
Bribed officials are just the tip of the iceberg. Spamming officials with letters (not just through partners but also lobbyists, “sockpuppets” who are operated by peripheral staff etc.) is just one of many tactics as well. Microsoft went as far as pushing senior people out of their jobs if they dared to oppose OOXML. There are documented examples as such.
This is not atypical for Microsoft; Microsoft had done similar things (and got caught) a decade earlier when it faced antitrust charges. Ballot stuffing, insiders in committees, bribes etc. are Microsoft’s way of doing business and here too we should expect to see it.
I wrote extensively about technical issues in OOXML, as well as legal issues such as patents. Some of the letters to you may have already covered at least a small subset of those. There were protests in numerous places including Poland and Norway, where members of the standardisation process marched the streets in protest. That’s how bad it was.
There was a BRM in Switzerland — a jaw-dropping case of corrupt process. This was part of how Microsoft got its “standard”, ignoring thousands of listed and properly enumerated issues. It would be impossible to list these exhaustively in a letter because there were literally thousands of pages detailing technical issues. These were discarded, ignored, and the attendees appalled by what they clearly considered to be a deeply rigged process.
Microsoft was flying journalists to Seattle (at Microsoft’s expense) in order to manufacture favourable articles. It seems to be doing something similar in the British press right now. Microsoft offered delivered presentations and studies from so-called ‘independent’ experts who would soon thereafter be hired to work full time at Microsoft. There were attempts to equate ODF with one single company (notably IBM) and attempts to equate ODF with a particular piece of software when ODF was in fact backed by hundreds of entities, both from the private and public sector. Many programs support ODF, and they support is very well. OOXML is just a rebranding of closed Microsoft formats (legacy), propped up by companies which Microsoft paid specifically for the purpose of backing OOXML (there are publicly accessible documents that clearly support these allegations). OOXML is about protecting the common carrier, Windows, creating lock-in for a cash cow. British taxpayers cannot bear these costs anymore.
I would like to quote a leaked Microsoft document which was presented in a case against Microsoft in the United States. The internal document stated: “A stacked panel, on the other hand, is like a stacked deck: it is packed with people who, on the face of things, should be neutral, but who are in fact strong supporters of our technology. The key to stacking a panel is being able to choose the moderator. Most conference organizers allow the moderator to select die panel, so if you can pick the moderator, you win. Since you can’t expect representatives of our competitors to speak on your behalf, you have to get the moderator to agree to having only “independent ISVs” on the panel. No one from Microsoft or any other formal backer of the competing technologies would be allowed -just ISVs who have to use this stuff in the “real world.” Sounds marvellously independent doesn’t it? In feet, it allows us to stack the panel with ISVs that back our cause. Thus, the “independent” panel ends up telling the audience that our technology beats the others hands down. Get the press to cover this panel, and you’ve got a major win on your hands.”
This basically sums up what Microsoft is trying to do in order to derail British standard policies at this moment. This was done before in many places and at different times. As one who works for British government clients I am very familiar with some of the ways in which Microsoft tries to interfere with standards and with competition, claiming to pursue “choice” when what it actually means is proprietary software, privacy infringement, lock-in etc. disguised as “choice”. Do not be misled by claims of victimhood and appeals to fairness which are actually just self interest, designed to increase licensing costs and dependence of software from the United States.
Microsoft’s OOXML is so “open” that when I leaked it on my Web site (should be fine for “open” document) I received legal threats. The purpose of the leak was to highlight many technical flaws which Microsoft hid using restrictive access and prohibitive costs, leaving information to only a few insiders in the know, much like TPP and other secret “free trade” negotiations.
Be strong in the face of bullying and pressure. Microsoft would not permit open standards to be accepted. That would give people a choice of platform, a choice of an office suite, and the choice of long-term preservation of their data.
Remember that the deadline is tomorrow (Wednesday), so now is a good time to leave a comment. █
Permalink
Send this to a friend
Content is available under CC-BY-SA