Resumen: Recordemos El lado Feo de Microsoft

De Linux Magazine (artículo 2008): “Los activistas en el foro Boicot Novell han puesto de manifiesto el documento más de 5.500 páginas en formatos PDF, HTML, hojas de cálculo, y varios otros formatos en su página web. A pesar de que OOXML ha sido certificado como un estándar ISO bajo circunstancias TURBULENTAS e INESTABLES, la ISO (Organización Internacional de Normalización) ha querido conservar la documentación completa en secreto. Los activistas Boicot Novell describen la exposición documentación como una reacción al “abuso sistemático y el paso a la irrelevancia de ISO.” Alex Brown, quien fue en parte responsable del proceso de OOXML en ISO, describe la exposición en su blog como un “descarado acto de violación derecho de autor.”

“Brown va a decir que “los piqueros incluso han sido tan buenos como para jactarse de los requisitos de banda ancho que sus crímenes han ocasionado “y termina con las palabras:”Incluso ahora, puedo escuchar los abogados de Ginebra lamiendo sus labios sobre esta … ” Boycott Novell webmaster Roy Schestovitz no se inmutó por la posible legalidad. Y añade: “No dude en pasar esto (o incluso ridículizó) los ~60 megabytes de LOCK-IN, que MICROSOFT NO TE DEJA VER.” Él no está solo en esta opinión: los numerosos comentarios en curso están etiquetados con los autores los nombres.

“Los contribuyentes sitio web también apuntan a la reciente “llamada provocativa” de IBM, para la que la ISO “haga un mejor papel”, con IBM haciendo difícil su participación en el proceso (información aquí).”

Como alguien señaló en los comentarios, “Alex Brown cada vez más se parece a un TITERE de MICROSOFT haciéndose pasar por un oficial de la ISO imparcial” (afirmación correcta)[http://techrights.org/2009/10/30/alex-brown-the-fox/] y vamos a escribir sobre el tema de nuevo muy pronto. Esto también se relaciona con Novell.

Como la saga del OOXML (“Open” Office XML) ayudó a mostrar que Microsoft es una empresa CORRUPTA que matonea a sus críticos. Ellos -MICROSOFT- tratan de hacer que sea un riesgo para exponer SU MALA CONDUCTA. Pero eso no importa, mirar Relaciones Públicas en su lugar es mucho más reconfortante que hacer frente a los males de este mundo.

“El mundo tiene muchos problemas y que necesitan ser reformados. Y sólo se vive una vez. Cada persona que tiene cierta capacidad para hacer algo al respecto, si es una persona de buen carácter, tiene el deber de intentar solucionar los problemas en el medio ambiente en el que viven.”

“Eso es un valor, que sí, que proviene en parte de mi temperamento. También hay un valor que viene de mi padre, que es que los hombres capaces, generosos no crean las víctimas, si no que tratar de evitar que las personas se conviertan en víctimas. Eso es lo que tienen la tarea de hacer. Si no lo hacen es que no son dignos de respeto o no son capaces.”

-Assange Julian 21 de diciembre 2010 Transcripción de la BBC: El Assange

Eduardo Landaveri adds to the above translation:

This pharisee -Alex Brown -dared to attack you personally as well as Groklaw, years have passed & now he’s sobbing about how MS never complied following its duties to ISO but he never issue an apology about his accions.

Instead of threatening people he should be investigated & audited before he retires. I hope the EU does something about him

Or in Spanish:

Este fariseo se atrevió a atacar a usted personalmente, así como Groklaw, los años han pasado y ahora está sollozando acerca de cómo Microsoft nunca cumplió sus funciones hacia la ISO, pero nunca emitió una disculpa por su acciones.

En lugar de las que amenazan la que debe ser investigado y auditado antes de retirarse. Espero que la UE haga algo al respecto.

Many thanks to Eduardo for his quick translation. █

Summary: Novell is slammed by a longtime stickler for helping promote Microsoft’s proprietary rival to ODF, which is the international standard for documents

PEOPLE have begun leaving for their vacation, but earlier on Groklaw decided to speak about Novell’s massive betrayal (translation to Spanish), which is not exactly news at all. Novell’s betrayal has been clear to us for over 4 years and we wrote thousands of posts on the subject.

Groklaw turns to Comes exhibits, specifically IBM exhibits. Rob from IBM has just posted this chart which shows what an utter mess Microsoft Office can be for ODF (pretty much by design [1, 2, 3, 4, 5, 6, 7]) and Groklaw links this to what Novell did with Microsoft and what Microsoft did to IBM a couple of decades ago. To quote some parts:

First quietly create incompatibilities to make sure that Microsoft applications wouldn’t run right on OS/2. Then tell the world that they shouldn’t buy OS/2 because Microsoft applications wouldn’t run right on OS/2.

But 1991 is a long time ago, I hear some of you say, and there is a new Microsoft. Oh? Let’s see if that’s so by highlighting one of the recent Novell filings with the SEC, its work agreement with Microsoft titled “Improving Microsoft-Novell Interoperability through Open XML” and dated March of this very year.

It’s regarding work Microsoft was willing to pay Novell to do to make Microsoft’s cynically misnamed Open XML seem like it allows interoperability. Novell has been at work since March to make Novell’s version of OpenOffice.org interoperate, sort of, but as you will see not completely with Microsoft Office 2010 so that it would at least look like Open XML works and that somebody is implementing it.

What a role for Novell to agree to play. We’ve had our suspicions for years, since Microsoft and Novell entered into its patent peace agreement and technical work agreement, and now we know that everything we suspected Novell was doing with its version of OpenOffice.org, it was. It is. This is the smoking gun. And the work agreement runs through November of 2011, so this story isn’t over yet.

[...]

Remember that one of the big objections to OOXML becoming a standard in the first place was that it allowed for proprietary extensions, which it was pointed out would make it difficult and indeed impossible for anyone but Microsoft and any chosen pals to interoperate with the “standard”. And here you see it in real life. Under criticism, Microsoft hires Novell to be a Microsoft pal and to try to figure out a way to make Microsoft Office look like it interoperates with OpenOffice.org up to a point, not any version of it, but just Novell’s version of OpenOffice.

You are not supposed to have to hire people to figure out a private way to be compatible with a true standard.

[...]

Oh, Novell. What were you thinking? Why would you agree to this? I can read these words, so why couldn’t you? They say you are being used to prop up the reputation of Open XML, while not really making it compatible in the end. What kind of goals are these? For a *standard*? For a company selling GNU/Linux?

[...]

Irony is dead. Here you have a so-called standard being used for exclusivity, so Microsoft and Novell have special interoperability that others can’t enjoy.

And as for Novell’s awful role, obviously, Novell executives never grasped the essence of Linux or FOSS. That explains a lot, including the company’s downfall in the end, don’t you think? Selling out the community in secret does not a long-term business plan make. And to everyone who pushed for or accepted Novell’s version of OpenOffice.org, what’s the plan now? Seriously. Time to really make a plan. Microsoft does. How about the community? How stupid are we?

Groklaw also appends the exhibit (we will hopefully have its Spanish translation soon, courtesy of Eduardo Landaveri) and Microsoft’s booster/insider Alex Brown gets slammed for his role in this whole process (he is a Microsoft “mercenary” as Landaveri would probably call him). He is criticised severely not just for his abuse as OOXML convenor but also as a Microsoft booster after all these incidents. Brown also threatened me after I had leaked OOXML, for all the misconduct associated with it (even corruption like bribes). That’s the type of crowd Microsoft surrounds itself with, in order to defend itself from prosecution for crimes.

For those who can recall the debate from 2008, OOXML is filled with RAND traps although it’s not the only issue with this proprietary format. The news about EIFv2 [1, 2, 3] (also in Spanish) suggests that Europe will not exclude OOXML for its unacceptable RAND terms and there is a new analysis (supposedly impartial) of what EIFv2 will mean to Europe:

Whether or not by indirect reaction to some of these developments, Red Hat has this week issued a blog post outlining the European Interoperability Framework (EIF), which has been set out by the European Commission. The commission recognizes that open technologies are key to achieving interoperability and therefore recommends that public administrations should aim for openness at all times.

If the European Commission is right to back this initiative with its emphasis being on “open specifications” and open standards being implemented in practice, then it may help the wider cause of free and open source software application development (in the public sector at least) from the following perspectives:

* The promotion and support the delivery of public services by fostering cross-border and cross-sectoral interoperability;
* To guide public administrations in their work to provide public services to businesses and citizens; and
* To complement and tie together the various National Interoperability Frameworks (NIFs) where they exist.

Although this model is confined to Europe under the auspices of the European commission, if effective it may prove telling for procedural adoption in other developed countries of the Western world from the United States and beyond.

The EIF is more than just a typical paper from another government committee. It is the result of a multi-year, multi-stakeholder effort that sets out to shift the paradigm for IT deployment in the public sector. Indeed, in the words of the EIF, it… “should be taken into account when [governments are] making decisions on public services that support the implementation of policy initiatives… [and] should also be considered when establishing public services that in the future may be reused as part of public services.”

OOXML was never supposed to get anywhere near ISO, but Novell helped it along the way, in order to appease Microsoft which had paid Novell hundreds of millions of dollars. Boyott Novell and whatever comes after it (AttachMSFT is buying Novell, so the name of the target will change). █

Summary: Lessons to be taken from the i4i vs Microsoft case and the real story behind amicus briefs in this case

THE i4i vs Microsoft case has led to OOXML troubles. Microsoft knew about it all along [1, 2, 3], which is why ISO was urged to invalidate OOXML after it had foolishly sold out.

Microsoft’s booster/insider Alex Brown keeps provoking about OOXML and patents right about now, but we’ll leave that alone for the time being because it’s not worth stirring up this hornet’s nest again. He too knew about this problem, but as the BRM convenor for OOXML he kept quiet about it. He had a job to do and that job was seemingly to promote Microsoft, not do the duties he was assigned to carry out for ISO.

Microsoft is currently trying to escape the trap set up by i4i after the very shrill Microsoft cheated i4i and even took some pride in it. Microsoft wants to get rid of i4i’s patent/s and spinners of this (mobbyists in particular) take it out of context by pretending that Microsoft’s patent policy is reasonable and that the EFF supports Microsoft. As the FFII puts it, this is just a case of:

#EFF against i4i #XML patent

It’s a software patent and Microsoft et al. knew about it years ago yet hid the issue in order to market OOXML, which is a story of corruption.

Ryan Paul wrote about it and so did Groklaw which has a full amicus brief presented as text:

Seriously, Google, Verizon, Dell, HP, HTC, and Wal-Mart, if you can believe it, have together filed an amicus brief [PDF] in support of Microsoft’s petition for writ of certiorari [PDF] in the i4i patent litigation case Microsoft lost both at the District Court level and on appeal to the Federal Circuit. HP and Dell submitted amicus briefs before in support of Microsoft, back when the case was being appealed to the Federal Circuit, but after Microsoft lost again there, the crowd in support has grown. And they all give the court an earful about just how messed up the patent system has become.

It’s a new day, ladies and gentlemen, when Wal-Mart gets it that the patent system is destructive to business and destroying innovation. A number of others have also filed amicus briefs, including EFF together with the Apache Software Foundation, Public Knowledge, and the Computer & Communications Industry Association. You can find more amicus briefs in Nick Eaton’s article in the San Francisco Chronicle, but I thought you’d particularly like to see the Google brief, so I’ve done it as text, because Google uses the same firm that represents them against Oracle in the patent litigation regarding Java and Android, King & Spalding.

Rob Weir is meanwhile showing that ISO is a farce. “Costs over $100 to view,” he writes “#FAIL RT @isostandards: ISO/IEC standard for special mathematical functions (C++) http://ow.ly/2MiPR”

If ISO allows patent traps (even from trolls) to become “standards”, then ISO renders itself obsolete. █

Summary: Microsoft is preaching about standards and open source again, having just had managers vilify both (sometimes resorting to outright corruption); IE9 another new example of harming Web standards and snubbing Open Source

IDG’s pseudo-open source blog has a new hit today. It’s Microsoft’s Walli [1, 2] again and he wants to educate us dumb communists, explaining to us what “Open Source” really means. “Please Don’t Confuse Standards with Open Source Software” says his headline and one can imagine the rest of those Microsoft talking points. Microsoft loves proprietary software development methods and when it comes to standards, it loves labeling its own proprietary APIs/protocols “standards” (recall what Microsoft did to ISO).

“They call it open source for marketing purposes,” explained to us gnufreex a couple of hours ago, “but they are doing business by GNU manifesto.” [update 18/9/2010: gnufreex asked to emphasise he referred to Red Hat here]

As we showed earlier today, Microsoft pretty much admits that it hates Open Source (not just Free software). It’s good that the technology press has been paying attention to it. “Microsoft slags off Open Sauce” says the headline from TechEye:

While software giant Microsoft has been trying to tell the world plus dog that it really loves Open Sauce, there are signs that some company executives did not get the memo.

Hernan Rincon, president of Microsoft Latin America, has been hitting the press claiming that “open” really is a way of saying “incompetent”:

He claimed when software companies cannot compete they are declaring their product to be “open”. This apparently “masks incompetence”.

“When convenient, the companies say they are open and they they use it for your own benefit, ” he added in our Babelfish translator.

It’s not just Open Source that Microsoft is clearly hostile towards (to the point of violating licences repeatedly after exploitation). At Microsoft there is still hostility towards the Web, with obvious examples like Silverlight (very anti-Web standards) and even Internet Explorer 9 (IE9), which Microsoft boosters say will fracture of the Web. We wrote about the subject earlier today and Swapnil Bhartiya says more by claiming that IE9 is a Chrome and Firefox “rip-off” (his own headline).

The browser seems to an obese boy, unlike lean Chrome and Firefox. The setup file itself was twice the file size of Mozilla Firefox 4.

Firefox was smaller in size (10MB), almost half the size of IE9. It installed fast and was up and running while IE was still installing.

Typical of Microsoft’s flint-stone age approach, you have to ‘re-start’ your machine in order for IE 9 to work. Doesn’t matter how much important work you are doing, you have to restart.

IE9 is bad for other reasons [1, 2, 3] and no component of it is available for code audit, let alone for sharing. Just about any other Web browser — Opera and Safari included — has at least something that’s Free software inside it. Microsoft loves Open Source? Don’t bet on it [1, 2, 3, 4, 5]. █

Summary: News about ODF, SC34 which is a farce, and some of the latest heckling from Microsoft proponents who masquerade as pro-openness or impartial

DESPITE interference from Microsoft intruders [1, 2], the OpenOffice.org conference in Hungary went pretty well based on numerous reports. People in attendance learned about the need for Open Document Format (ODF) and there are other pro-ODF articles in the press these days. The Guardian, for instance, is still making waves.

A good piece from the Guardian’s Charles Arthur yesterday, reporting teacher and Windsor & Maidenhead councillor Liam Maxwell’s analysis, of how much councils could save by switching to Open Document Format, as used in OpenOffice.org: some £200M if all councils did this for all their staff. There was some background to this, about the problems encountered by Windsor and Maidenhead, on Computer Weekly’s site on Wedensday.

The key stumbling block for councils, as for schools, appears to be compatibility with others systems, most notably those supplied by Capita. Liam calls for the Cabinet Office to strengthen its present position on open source and open standards by mandating ODF as a standards across the public sector, were this to happen I don’t doubt that we’d see Capita quickly make SIMS and their other products compatible with OpenOffice.org, making it far easier for schools and councils to choose their office suite from all those available, rather than forcing them to pay for MS Office, bundled with ‘features’ which many will rarely if ever use. Charles seems to think that such a requirement is far more likely with Francis Maude at the Cabinet Office than it had ever been under the previous administration, even in Tom Watson’s day.

Microsoft is not done throwing wrenches at ODF.

Bart Hanssens recently stated that “odf 1.2cd05 60-day review ended, comments received” (these comments are part of the openness of this system). Rob Weir, who works alongside Hanssens on ODF, found himself having to confront Microsoft minions again. Microsoft’s booster and insider Alex Brown, who was the BRM convenor for OOXML while he smeared ODF, is not being left alone by Weir, who writes about another scandalous SC34 (see coverage from SC34 in 2008 and SC34 in 2009): “If you are looking for OOXML defects to fix, how about going back to 100′s of NB issues you gaveled away at the BRM?”

Weir is then met by opposition from Brown’s longtime right-winger, the ODF-hostile Jesper Lund Stocholm [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]. He is a known Microsoft booster and Weir’s responses to him go like this:

- “Are you saying that there are zero issues remaining from the OOXML ballot that should be addressed? Really? Zero?”

- “So if I understand correctly, you are asking NB’s to resubmit defect reports for issues not resolved at the BRM?”

- “It wasn’t clear. I assumed WG4 would look at the defects already submitted during BRM. You are saying they are not.”

- “You should send note to all NBs telling them that they need to resubmit relevant defect reports from the OOXML ballot”

- “With ODF we do it differently. Our defect log includes all ballot comments received for ODF 1.0. No need to resubmit”

- “I understand how to submit comments. But I wasn’t aware that the previously submitted comments were being ignored.”

- “Deferred ballot comments are either in WG4′s defect index or not. Simple question. What is the answer?”

- “Earlier Alex suggested lack of interest explained the lack of comments. Maybe NBs think they have already submitted? I did.”

“NB issues should be solved,” says the FFII to this booster (the FFII’s member also participated in squashing OOXML).

Watch Jesper Lund Stocholm belittling OpenOffice.org by implying that it’s a ripoff of Microsoft Office. Typical.

Weir finally responds to Brown by writing: “I’m not suggesting a new process. Just asking status of those defects. Sounds like they need to be resubmitted, right?”

“BRM comment processing rates can range from 0.5-1000 comments/hour,” says Weir to Mary McRae from OASIS (maintainer of ODF).

Not surprisingly, throughout this conversation the two Microsoft boosters (Microsoft is fronting with them) tried to defend Microsoft by attacking its competition. For instance, they turn to dismissing and attacking ODF, simply because they cannot defend their dirty handling of their proprietary OOXML. The conversations can be found in Twitter, so they don’t need additional exposure here.

Bart Hanssens adds: “The ironic thing is that Ecma never made public the public comments they received on OOXML. But for ODF this is an open book.”

On and on it went for a couple of days and at the end Weir gave up feeding those Microsoft minions. Microsoft rarely speaks directly about such issues, it just sends out MVPs or something else that may seem impartial to an outsider. Weir then posted a rant about ISO, which is captured by the vendor called Microsoft as far as document formats are concerned. To quote part of this rant:

We saw during the OOXML ballot, and especially at the BRM, how this totally fell apart. It was raised several times that Microsoft was dominating the committees, sometimes representing more than 50% of the people in the room. But ISO leadership dodged the issue, saying there was nothing they could do about it, based on their rules. This may be true. But that is just acknowledgment that their rules are not able to prevent domination problems.

And on Balance, ANSI says:

The standards development process should have a balance of interests. Participants from diverse interest categories shall be sought with the objective of achieving balance.

Like committees containing almost exclusively Microsoft Business Partners? Fail. In fact you can go up and down the list and ISO fails to meet these minimum requirements.

ISO got poisoned some years ago, at least the parts of ISO which Microsoft had to ‘stuff’ with workers who are in Microsoft’s pocket. We did give examples at the time. Other Microsoft minions are harassing the FFII right now, but the FFII is not alone among their victims. Microsoft Florian, for example, is labelling Eben Moglen “Fidel” (as in Castro) and calling him that many times. How low has Microsoft sunk in its battles against the SFLC/FSF? Microsoft’s MVP Miguel de Icaza is also attacking the FFII right now. Anyone who still believes that this man exists in the GNU/Linux world in order to serve an agenda not of Microsoft need look no further than some of this man’s most recent actions. He apparently still trolls ODF too. The FFII wrote to him: “Feel free to submit ODF1.2 bug reports to @rcweir and Oasis, 5 days to go.” There is increased friendship and collaboration between the Mono camp and Microsoft Florian, both of which attack the FFII, trying hard to cause trouble. Microsoft Florian maintains his rude habit of mass-mailing people to achieve his goals. █

–George Orwell

Summary: Microsoft and its proponents/minions are still pushing an old propaganda line by claiming that Windows and OOXML will bring “choice”

THE NEWS is aflood with reports that IBM comes under scrutiny in the EU. Little is being said about the fact that IBM is being attacked SCO-style by Microsoft and its “satellite proxies” (IBM's words). We care about this because IBM’s mainframes run GNU/Linux — a fact that people like Florian Müller could not care less about (and this matters because “FlorianMueller” is the one who also pushed the news into Slashdot with his own convictions and bias). See the conversation in the previous post where Müller admits using Vista 7 (he seems like a permanent Windows user) and does not care so much if his stance is helping Microsoft. He’s apathetic to it. He also spins/subverts the word "choice" in the same way Microsoft does (same with the word “openness”^*). It’s done just as Microsoft Malaysia did it to ODF and other branches of the company do under all sorts of situations. It’s a language game. Standards are about limiting choice at some level of granularity in order to ensure that different implementations work well with one another. Microsoft’s hypnosis strives to confuse people about choice; it’s about office suites, not formats.

Rob Weir has just informed his peers and supporters of ODF that Microsoft is restricting choice (abolishing and harming ODF’s status) using language games.

Microsoft’s talking points go something like this:

If you adopt ODF instead of OOXML then you “restrict choice”. Why would you want to do that? You’re in favor of openness and competition, right? So naturally, you should favor choice.

You can see a hundreds of variations on this theme, in Microsoft press releases, whitepapers, in press articles and blogged by astroturfers by searching Google for “ODF restrict choice“.

This argument is quite effective, since it is plausible at first glance, and takes more than 15 seconds to refute. But the argument in the end fails by taking a very superficial view of “choice”, relying merely on the positive allure of its name, essentially using it as a talisman. But “choice” is more than just a pretty word. It means something. And if we dig a little deeper, at what the value of choice really is, the Microsoft argument falls apart.

So let’s make an attempt to show how can one be in favor of choice, but also be in favor of eliminating choice. Let’s resolve the paradox. Personally I think this argument is too long, but maybe it will prompt someone to formulate it in a briefer form.

Glyn Moody remarks on this post by calling it a “nice debunking of a sneaky Microsoft trope about choice” and he also shares this word of warning about a new Google Docs “format”.

“I’m having trouble searching for just ODF formats, Did Google remove the ability?”
      –AnonymousI asked Weir about it and he said that he “Can’t tell much from the screenshot. Not clear that it is a format. Maybe Punch is an app? Or internal test system?”

As a reminder, Google officially opposed OOXML when Microsoft was corrupting standards bodies all over the world, but Google never showed much active support for ODF, either. Google has been mostly passive and there are recent examples where Google exlcuded ODF support and was criticised for it (although not in a major way).

One person has just mailed us to say: “I’m having trouble searching for just ODF formats, Did Google remove the ability?”

“In general I’m losing it for Google,” said this person to us, “they support OS [open source] only when it suits them. They [are] really not our friends.”

Google Docs is of course proprietary. █
_____
^* When Microsoft says “openness” it never means “Open Source”. In cases where Microsoft is excluded or chooses to be excluded it advocates “choice” as means/route to depart from standards and embrace proprietary offerings instead.

NOVELL’S SUPPORT of OOXML was mentioned in the previous post, which also helped put Mono in context. Mono will soon comprise Microsoft code licensed under Microsoft licences. It’s almost as though Novell is just a proxy for putting Microsoft stuff inside GNU/Linux. We’ll leave this discussion for another day though. More interesting news happens to have come through Rob Weir a few hours ago. It is a new post titled “Are Standards Organizations Relevant?”

Recently I was in a brief conversation about the use of the IEEE. They are an institution that, like many (all?) other standards organizations, seems to exist largely or entirely to standardize the reason for their existence. While it is generally agreed that we would greatly prefer a world with standards organizations to one without, it’s evident that standards organizations need to do more than they currently are to remain relevant. Given the complaints about standards organizations, the solution to this may actually be more standardization.

[...]

Another important point is careful control over what exactly becomes a standard. Standards must be fully defined with nothing critical being dependent on any particular implementation. If I pick up the document defining the standard for a document format, that document should contain all the information I require to create an application which handles that format in a manner identical to the reference implementation. For the Open Document Format (ODF) standard, this is possible. For the Microsoft Office OpenXML (MSOOXML) document format, this is impossible. The MSOOXML definition refers to the behaviour of previous versions of Microsoft Office applications without providing any documentation on how to properly produce that behaviour or even what the correct behaviour should be. Even worse, the MSOOXML definition defines an “arbitrary binary data” field — neither open nor XML, and by definition impossible to define. It is therefore possible for an application to create a MSOOXML document which would appear to be completely adherent to the document specifications but which could not be properly read by any other application.

We have covered to death the corruption that occurred amidst ISO’s decision. This was an extraordinary display of Microsoft’s criminal nature, which it showed not just once but possibly hundreds of times in a short period of time (we documented many examples).

In better news, a proposal has just been made for the British government to make ODF the national standard.

Establish the Open Document Format as the standard for use in all Government departments rather than continually upgrading to the latest version of Microsoft Office at a cost of many millions of pounds. This is a process which is already taking place in other European countries and one which should be started in Britain at the earliest opportunity.

Supporting OOXML in any way is acknowledging that abuse of the system is acceptable and that open standards no longer mean anything. The British Standards Institution has already been sued for what it did regarding OOXML. █

Summary: A back door to software patents is left open by the competition commissioner, who would be wiser to forbid FRAND-encumbered standards

Joaquín Almunia, the Vice President of the European Commission in charge of competition policy (some background in [1, 2]), is promoting FRAND in his new speech. This is an implicit endorsement of software patents inside standards. From the transcript we have:

Standards and Protocols

When it comes to standards some minimum requirements must be met to ensure that the positive effects of standardisation can fully materialise. We have identified these requirements in the Commission’s draft guidelines on horizontal agreements which include an extensive discussion of standardisation.

The starting point is transparency: if technology is to be incorporated into a standard, then participants that own intellectual property that covers that technology should disclose their ownership. Without transparency, efficient decisions cannot be made.

For a standard to serve its purpose there should be a commitment to license on fair, reasonable and non-discriminatory terms. If so called “FRAND commitments” have been given, they should be adhered to. Moreover, those standardisation bodies that require full disclosure of the proposed terms and conditions of licensing can be assured that they will not infringe EU competition law by doing so.

Permitting FRAND is not a good idea. It permits more of the same abuse of bodies like ISO, on which Microsoft dumped patent traps. There was also the controversial process around MPEG, which essentially helped create another patent troll [1, 2, 3, 4, 5, 6].

ISO allowed itself to be abused in this way and action is taken in response to Microsoft’s sheer abuse. It is far too little, far too late (over two years late). Jan Wildeboer says: “One can see this as admitting the process of OOXML standardisation was flawed.”

Here is how Rob Weir put it:

ISO/IEC JTC1 Revises Directives, Addresses OOXML Abuses

[...]

First, we see the elimination of the contradiction phase in Fast Track processing. If you recall, under previous rules, a Fast Track begin with a 30-day NB review period, sometimes called the “contradiction period”, where NBs were invited to raise objections if they think the Fast Track proposal contradicts an existing ISO or IEC standard. This was followed by a 5-month ballot. The problem was that the word “contradiction” was not defined, leading to various irreconcilable interpretations. In the case of OOXML 20 JTC1 National Bodies (NBs) raised contradictions. Evidently, the passage of time has lead to no progress on defining what exactly a contradiction is, so the contradiction period has been eliminated entirely. Instead, looking for “evident contradictions” (still undefined) is given to JTC1 administrative staff, which is the surest way of guaranteeing that we never hear of contradictions again. The Fast Track DIS ballot remains at 5-months, so net-net this accelerates processing by one month.

Next, we see some clarification around how NBs should vote on Fast Tracks. Back, during the OOXML ballot, Microsoft made a huge effort to convince NBs to vote “Yes with comments” if they found serious flaws in the text, with the promise that they would all be addressed at the BRM. Well, we now know that this was a big lie. Very few issues were actually discussed and resolved at the BRM. And most of them were addressed by merely saying, “Sorry, no change”. At the time I argued that the rules were quite clear, that disapproval should be voiced by a “No, with comments” vote. Well, we now see another small slice of vindication.

[...]

Another change is that if the DIS ballot fails to get sufficient votes, meaning less than 2/3 approval of ISO/IEC JTC1 P-members, or more than 25% disapproval overall, the proposal dies at that point. It doesn’t go on to the BRM. Game over. If this rule had been in place back in 2007, OOXML would not be an ISO standard today.

OOXML is a patent trap with RAND and it is also a proprietary format which nobody implements as it cannot be implemented. What the European Commission ought to do is stick to abolishment of software patents and perhaps an exclusion ZRAND. There is enough time for this to be done. █

Summary: Alan Bryden of ISO infamy may now be hurting Europe as well, essentially by using ‘standards’ to help bring software patents to the continent

IS Alan Bryden the new Van Der Beld [1, 2, 3]? Two years ago we showed how Bryden helped Microsoft deny its corruption (he was also mentioned in [1, 2]) when Microsoft resorted even to bribery in order to derail/exploit ISO.

Alan Bryden is coming to Brussels (see page 41 of this document [PDF]) and according to this short report his agenda is potentially similar to that of Microsoft lobbyists, who want to put (software) patents inside standards in a continent which is against such patents.

Wednesday morning, 23 June 2010 Alan Bryden, the former ISO general secretary who let it happen and made European standard setting organisations a laughing stock of an US corporation, would speak about “European standardisation in a global environment” in the European Parliament “Internal Market and Consumer protection (IMCO) committee.

Bryden was also a member of the Commission’s EXPRESS “expert panel” group on the future of European Standardisation which report advises for strong IPR policies against open standardization. The IMCO meeting relates to the Parliament phase of the EXPRESS process and the Future of European Standardisation. Read what the winding lobby snakes write in their report to actually promote standards locked down by software patents

Glyn Moody has remarked on these findings as well as others which we covered this morning [1, 2].

Let’s be frank: standards are pretty dull; but they are also important as technological gatekeepers. As the shameful OOXML saga showed, gaining the stamp of approval can be so important that some are prepared to adopt practically any means to achieve it; similarly, permitting the use of technologies that companies claim are patented in supposedly open standards can shut out open source implementations completely.

Against that background, the new EU report “Standardization for a competitive and innovative Europe: a vision for 2020” [.pdf] is a real disappointment. For something that purports to be looking forward a decade not even to mention “open source” (as far as I can tell) is an indication of just how old-fashioned and reactionary it is.

The president of the FFII says that the “EU [is] promoting the RAND term, aims to get rid of Free Software”; Separately today he wrote that the “EU [plans] to abandon its powers of harmonization of patent laws in favor of an autonomous international patent system [PDF]”

What is happening in Europe? Have enough lobbyists been gathered to impose software patents upon Europe through standards, which are almost the antithesis of monopoly, at least in principle? █

Summary: Harsh words for MPEG-LA and also for Novell’s Banshee, which is a Mono patents Trojan that inflects Moovida (while masquerading as “a standard”)

THE patent trolls who run MPEG-LA are a subject that we wrote about in posts such as:

• Canonical Needs to Tell Ubuntu Users How Much It Paid MPEG-LA for Patent ‘Protection’
• Microsoft and MPEG-LA Called “Patent Trolls”, Antitrust Complaint Filed
• Patent Troll (MPEG-LA) May Own Your Personal/Family Videos
• Alexandre Oliva Explains Why the Patent Troll Larry Horn (MPEG Cartel) is Bluffing
• “We’re in the Era of Digital Video, and It’s a Mess,” –Steve Jobs, MPEG-LA Proponent/Lobbyist

Simon Phipps (OSI) has tagged one of the following news items “troll” and commented as follows:

To be clear, MPEG-LA is a parasite using standards bodies as its host, whether they want it or not. This page makes it clear that the parasite is looking for new hosts. Patent reform is now way overdue.

Going by this definition of “troll”, one might extend the scope to account for Microsoft’s racketeering [1, 2, 3, 4, 5, 6, 7] (Phipps is a friend of neither). Novell makes a piece of software called Banshee which it knows very well to be excluded from Microsoft's MCP and thus a patent threat to anyone who uses it (except SUSE customers). This trap pretends to be a standard and Moovida turns out to be inheriting this Mono mess:

Moovida, the popular cross-platform GStreamer-using media centre, are lunching a new desktop media player application – called Moovida Core – as part of its’ ‘Moovida 2.0’ strategy. The player, which uses Banshee as its backend, is currently available for download on Windows with Linux and OS X versions to follow shortly.

Sebsebseb blames a Novell hackfest (“annual hack week”) and also shows us that some people want this patent liability inside Ubuntu 10.10 (which recently got rid of F-Spot [1, 2]).

It should be noted that this issue is, reportedly, one of the significant issues keeping Banshee from becoming the default media player in Ubuntu 10.10. Perhaps if Alan’s work goes well, and given we’re quite far from Mavericks’ feature freeze, Banshee could still be in with a shot at being the default media player in Ubuntu 10.10?

“Crapple emulation using Monoposoft technologies on Linux,” calls it Ryan Farmer, “I know you don’t care much about Banshee, but if there is already what is basically a proprietary version for Windows, the first link, then I guess it will be ported over to Windows soon and if it gets ported to Windows it will go to Mac as well I guess, but those versions won’t use Mono?” █

Summary: Crimes aside, the obvious technical pitfalls of OOXML are made more apparent, whereas ODF proves to be future-proof because of its reuse of existing standards

A FEW YEARS after Microsoft corrupted national bodies and corrupted ISO, the convicted monopolist begs for people to forget the past and actually believe that OOXML is a standard.

Not only is OOXML not a standard, it is hardly even a format because nobody has ever implemented it. It’s just some words on paper with errata weighing thousands of pages (and nobody bothering with them). OOXML is a great example… of why Microsoft is still a criminal company. Those who do not understand why this is so probably ought to look back because it’s well documented. There is nothing Microsoft won’t do for its stagnating cash cow, even if it’s lying, intimidating, throwing people out of their jobs, hiring AstroTurfers, and bribing many people.

Stéphane Rodriguez, who is intimately familiar with the mechanics of Microsoft Office, has published a long post titled “The OOXML interoperability scam,” wherein he gives detailed examples.

Every time the Microsoft Office team pushes a comment on the wire, there is another pledge for interoperability. It has been so common for the last few years that if you haven’t actually watched what it might mean, pretty much OOXML is synonym with interoperability.

Of course, it does not matter that the word interoperability alone does not mean anything. That is why Microsoft uses it so much. You can pretty much put an interoperability label to anything as long as it is not accurately defined. Does it mean document-level interoperability? Application-level interoperability? Or, perhaps is it just Microsoft-only interoperability (a good guess!)?

The pledge for interoperability cannot possibly mean document-level interoperability since we are not there : OOXML is full of non-XML streams, barely defined at all (the official papers lack everything related to international features, and that is just one example), so that ends any serious discussion precociously. In the remainder of his article, I’ll be taking a look at application-level interoperability, in case Microsoft means that.

[...]

Simple tests like this leave me a bit speechless when you see that Microsoft Office is supposed to be the rolls royce of Office programs in the world, the de facto standard. And in fact it’s just crap. On the contrary OpenOffice, the free suite, is actually a more serious product when it comes to application-level interoperability. This had to be said…

Compare the proprietary mishmash that OOXML contains to something more elegant like ODF, which actually reuses international standards like SVG, MathML, and doesn’t have pseudo-leap years to contain one program’s bugs inside formal specifications. Here is a new post about that:

After a few posts around the net talking about the now 5 years of ODF. I want to talk about what I have lately been talking on what would this new web era can bring to ODF. For the most part of those 5 years I have heard and listen to talks about the future of ODF, it’s integration with semantic web. It’s advantages over security, digital signatures, third party applications and further development within OpenOffice.org.

We are now going into the era of HTML5 which is supposed to come with so much more advantages for the web and ODF would find a new niche were to grow and expand. So HTML5 have been talked about producing new technical advantages such as:

* Geodata
* Storage API
* Simple scripting (no namespaces)
* Audio and Video
* Interactivity like Drag and Drop

[...]

So why we keep comparing ODF and whatever happens on the web? Certainly ODF has always done this, with standards like Dublin-core, MathML, and other standards. Microformats, and Geo locational web can certainly be in that train of thought. If the applications support it or not, let’s be clear, ODF should mark the leadership, and the apps should follow, so is meant to be that the apps should catch up to ODF and not the other way around.

This ought to also address the CDF noise from the OpenDocument Foundation.

The links above were found in the blog of Rob Weir, who also included this link about Free/Open Source software in government [PDF] and an interview with himself.

Last month OASIS ODF Adoption TC member Rob Weir sat down with Svante Schubert at the Plugfest in Granada to discuss a range of topics, including ODF 1.2′s RDF-based metadata and Svante’s work on ODFDOM. You can listen to this interview in our first episode of the ODF Podcast.

IBM has done a lot to help ODF. It’s time for IBM to also bury software patents, not promote them. And we know, we know… it’s not Weir’s department, so to speak. Bob Sutor deletes comments that ask about it while others in IBM ignore E-mails that inquire about software patents. █

Summary: Europe’s policy-making process is serving the hands of multinationals or monopolies with vested interests in lock-in and reduced competition; new patent lawsuits against Apple

EXTENSIVE lobbying from Microsoft, its cronies, and European allies seems to be paying off.

The EBoA has not been discussed here for a while (I too made a submission to it), but it was an opportunity to squash ambiguity regarding software patents in Europe.

Here is the official response [PDF]. It is about 100 pages in length and there is also this summary:

Today the Enlarged Board of Appeal of the EPO handed down its opinion on referral G 3/08, taking the opportunity to set out and confirm the approach of the EPO regarding the patentability of computer programs under the European Patent Convention (EPC).

The opinion relates to four questions referred to the Enlarged Board in October 2008 by the President of the EPO concerning points of law of fundamental importance for the Office’s patenting practice in this field.

The Enlarged Board analysed in detail the development of relevant case law, and found that there was a divergence between two decisions of Technical Boards of Appeal. However, recognising that the “case law in new legal and/or technical fields does not always develop in linear fashion, and that earlier approaches may be abandoned or modified”, the Enlarged Board found that this constituted a legitimate development rather than a conflict of case law.

In the absence of conflicting Board of Appeal decisions, the Enlarged Board concluded that the legal requirements for a referral were not met. Nevertheless, the Board affirmed the right of the President of the EPO to “make full use of the discretion granted by Article 112(1)(b) EPC” in making a referral, and provided further guidance on how these requirements for such a referral should be interpreted.

The president of the FFII, Benjamin Henrion, says that the “EPO can continue to grant numerous software patents as it is doing for more than a decade” and Florian (from another push against software patents in Europe) says:

To answer your Twitter question to Benjamin, it’s not the end of the story. It just means the EBoA didn’t determine a significant difference in case law. I haven’t read the detailed ruling yet but the EBoA certainly doesn’t have the authority to overrule national court decisions. That’s for sure and doesn’t have to be verified by reading the EBoA’s statement.

BTW, I’ve participated very actively in today’s slashdot discussion related to Benjamin’s submission on the SUEPO letter. Tried to provide additional information and clarifications where people needed help.

To be honest, Florian has moved away from some dubious stances we saw before and more people — inside the FFII included — start to view him as trustworthy. He did disclose his interests to us, privately.

Regarding this Slashdot post which we mentioned the other day, Red Hat’s Wildeboer says: “Evil #swpat through the backdoor. EU parliament upset.”

“EPO can continue to grant numerous software patents as it is doing for more than a decade”
      –Benjamin Henrion, FFIIBenjamin also alerts us about this document [PDF] from Bruno van Pottelsberghe which is titled “Europe Should Stop Taxing Innovation”. The title is deceiving because the document is actually calling for the back door that may include software patents. The summary says: “The European Union failed to achieve its Lisbon agenda target of spending three percent of GDP on research and development, and so, in the EU2020 strategy, has given itself another decade to meet this goal. Meanwhile, the EU has been leapfrogged by China in terms of business R&D spend. One key element to stimulate innovation and ultimately drive European growth would be to create the long-awaited single EU patent. Today’s fragmented European patent system is poor value for money and overly complex, not least because national patent systems still have the last word over all European patents on their territory. After nearly 50 years of failure to create the EU patent, language issues and the design of a centralised patent litigation court remain unresolved. The recent EU Council deal on an ‘enhanced’ European patent system is potentially a step forward, though many problems remain unresolved.”

The aspects they don’t cover actually include increase of damages and scope (good for lawyers). Here is what the solicitors-targeted crowd from IAM have to say about Pottelsberghe:

What is absolutely clear to me is that a lot of people have a lot invested in the current system and want to see it changed as little as possible. National patent offices currently control the EPO, for example, and make a lot of money from it. They would still get substantial amounts of cash under van Pottlelsberghe’s proposals, but their influence would wane and they would no longer grant national patents. Then there is the legal profession. Just a couple of lines from the paper make it abundantly clear why so many patent attorneys and lawyers in Europe (not all, it is important to point out) are opposed to reform.

This is funny coming from lawyers. They too are interested in the same thing because it gives them revenue at the expense of those who suffer in this system.

Former MEP David Hammerstein, who provided valuable information about what Microsoft did to the EU Commission [1, 2, 3], has just said that Kroes is falling for Microsoft’s lobbying. “Open standards [are] out of EU Digital Agenda for ambiguous open architecture,” he writes, “Kroes back tracks on binding openness. for procurement and EIF” (there is no further information or links).

Only moments ago Glyn Moody wrote about a leak that says more.

European Commission Betrays Open Standards

Just over a month ago I wrote about a leaked version of the imminent Digital Agenda for Europe. I noted that the text had some eminently sensible recommendations about implementing open standards, but that probably for precisely that reason, was under attack by enemies of openness, who wanted the references to open standards watered down or removed.

Judging by the latest leak [.pdf] obtained by the French site PC Inpact, those forces have prevailed: what seems to be the final version of the Digital Agenda for Europe is an utter travesty of the original intent.

For example, the draft version [.doc] dealing with interoperability was headed “Open Standards and Interoperability”; this has now become just “Interoperability and standards”.

[...]

In short, this latest version of the Digital Agenda for Europe is an utter disgrace, and shows how beholden the European Commission remains to “significant market players”. There are no benefits for European citizens here: the Commission has abandoned them for who knows what reason, and ensured that millions of Euros will flow out of their pockets – and Europe – for costly software licences at a time when the European economy can ill afford such unnecessary expenses.

This disgraceful evisceration of the earlier sensible draft shows yet again why we need full transparency at the European Commission. We need to know who met with whom, and what was said. Until we do, these kinds of last-minutes stitch-ups will continue to occur, and will continue to add further blots to the Commission’s already besmirched record in this regard.

For some information about Microsoft’s involvement, see:

1. European Open Source Software Workgroup a Total Scam: Hijacked and Subverted by Microsoft et al
2. Microsoft’s AstroTurfing, Twitter, Waggener Edstrom, and Jonathan Zuck
3. Does the European Commission Harbour a Destruction of Free/Open Source Software Workgroup?
4. The Illusion of Transparency at the European Parliament/Commission (on Microsoft)
5. 2 Months and No Disclosure from the European Parliament
6. After 3 Months, Europe Lets Microsoft-Influenced EU Panel be Seen
7. Formal Complaint Against European Commission for Harbouring Microsoft Lobbyists
8. ‘European’ Software Strategy Published, Written by Lobbyists and Multinationals
9. Microsoft Uses Inside Influence to Grab Control, Redefine “Open Source”
10. With Friends Like These, Who Needs Microsoft?

Regarding this “Public consultation on the review of the European Standardisation System”, Glyn Moody suggests telling/asking them whether it’s “time to replace ISO?” (we have a fairly new Wiki page about ISO’s internal corruption, but it focuses on OOXML and not on the MPEG cartel, for example).

Nokia, one of Europe’s biggest lobbyists for software patents and an enemy of Ogg Theora, is currently suing Apple some more and so do other new claimants like SoftView.

Nokia is not the only company taking Apple to court over infringement of its patents. The latest mobile technology company to make that move is SoftView, a small startup based in Washington.

AT&T is also involved:

• SoftView Files Suit Against Apple, AT&T
• News: Apple sued by SoftView over Mobile Safari rendering
• Apple sued by SoftView over Mobile Safari rendering
• News: Apple sued by SoftView over Mobile Safari rendering
• SoftView files patent suit against Apple, AT&T

SoftView is not a patent troll, unlike Acacia whose defeat against Red Hat (and Novell) is still being covered by Rob Tiller. We also wrote about the subject in:

• Acacia’s Case Against GNU/Linux is Dead
• Red Hat Appears to Have Done More Against Acacia (Patent Troll)
• Behind the Microsoft Puppetmaster: SCO-Type Libel, Acacia-Type Patent Trolls, and Novell-Type Patent Deals to Make GNU/Linux Not Free (Gratis)
• Patents Roundup: Red Hat on Patent Trolls; Apple Antitrust; Microsoft Attacks Theora, Which is Needed to Save Our Video Culture
• The Cost of Patent Trolls Who Attack Linux
• HTC-Microsoft Was Not an Agreement, It Was Apparently an Extortion
• After Acacia Case Red Hat is Free, SUSE is Still Not Free
• AMD Should Have Given RadeonHD Driver Project to Red Hat
• Patents Roundup: Cracks in the USPTO, Patent Trolls, and More About Theora

Apple is also said to have been sued by HTC (we will get to it later on) after Apple sued HTC, but Florian disagrees with the claim. He writes:

HTC patent counterstrike against Apple appears weak; Google still on the sidelines

HTC made this announcement today:

http://www.htc.com/us/press/htc-sues-apple-for-patent-infringement/15

“HTC SUES APPLE FOR PATENT INFRINGEMENT”

The word “sues” in that headline appears to be a somewhat misleading overstatement of what’s actually happening. The press release only says that HTC lodged “a complaint with the United States International Trade Commission (ITC) to halt the importation and sale of the iPhone, iPad and iPod in the United States.” By way of contrast, Apple’s March 2 announcement (http://www.apple.com/pr/library/2010/03/02patents.html ) had said that Apple “filed concurrently with the U.S. International Trade Commission (ITC) and in U.S. District Court in Delaware.” So what’s missing from HTC’s announcement is a lawsuit in the traditional sense of the word, meaning a lawsuit that would be filed with a court. HTC appears to be less determined than Apple and much less sure of having a strong case because otherwise it would, like Apple, take concurrent action at both levels, or if it had to choose between the two, HTC would take Apple to a court of law. Only filing a complaint in hopes of a governmental agency doing most of the work looks weak.

Also, HTC asserts five patents while Apple asserted 20. HTC had to choose its five bullets out of a rather small arsenal while Apple could pick its 20 out of an arsenal amounting to thousands of patents, which makes it much more likely, in purely statistical terms, that Apple’s selection of patents poses a threat to HTC than vice versa.

Maybe HTC hopes that its announcement could build some kind of pressure on Apple via its customers and shareholders.

It’s unfortunate that the dispute between Apple and HTC now becomes a sue-me-sue-you game between closed source and open source, with Apple most probably having the upper hand and HTC just trying to create the appearance of a retaliatory measure. I have serious doubts that HTC’s apparently half-hearted counterstrike will scare Apple. HTC’s light warfare is probably no match for Apple’s heavy artillery. Just comparing the two different press releases that announced legal action, and knowing about the size of the patent portfolios of the two combatants, this is in all likelihood a very unbalanced battle.

Google:

There’s still no indication of Google [whose Android open-source project is the reason for which Apple sued HTC in the first place] entering the fray and trying to bail out HTC and, if necessary, other vendors who build Android-based phones. When HTC and other vendors decided to create Android-based products, they might have thought that Google would help them out if any patent issues came up. I’m wondering whether Google can really stay on the sidelines of this forever, not only with a view to Android but also its other open source projects — existing and future ones.

More about that shortly. It is relevant to Linux. █

Summary: Microsoft’s and Apple’s cultural threat with MPEG-LA; Canonical listed as H.264 licensee; Google perceived as potential game changer with YouTube

OGG THEORA has been a hot topic recently because it’s under attack from Apple and from Microsoft. Previous and very recent posts about that subject include:

• Microsoft Brings MPEG-LA-LA Land to the Web and Threatens GNU/Linux With Software Patent Lawsuits
• Patents Roundup: Red Hat on Patent Trolls; Apple Antitrust; Microsoft Attacks Theora, Which is Needed to Save Our Video Culture
• Behind the Microsoft Puppetmaster: SCO-Type Libel, Acacia-Type Patent Trolls, and Novell-Type Patent Deals to Make GNU/Linux Not Free (Gratis)
• “Behind the Open Codec FUD Attack, W3C Captured by Microsoft, Apple, Nokia and So On?”
• Apple’s and Microsoft’s New Motto: Do More Evil, Together
• Steve Jobs: “A Patent Pool is Being Assembled to Go After Theora and Other “Open Source” Codecs Now.”

The Microsoft Bott continues his war on Theora this week, so Chips B. Malroy responds by calling him “major Microsoft shill” (which is actually true because his career is dependent on Microsoft). Malroy added that “audio and video codecs and the patents on them, are in some ways, an attack on the right of free speech” and later he argued that: “Most of us do disdain software patents. They only help the monopolies. They do not promote science or innovation. But there is a worse form of software patents, its software patents on codecs. This should never have been allowed in any reasonable world. Software patents on multimedia codecs are basically a patent on sight and sound, two inalienable senses of the human experience.

“Beyond that the monopolies (Microsoft and Apple) want to use software patents as a way to block free operating systems, to control the web, and to profit by taxing those who have to use these multimedia video and sound software patents.

“Multimedia software patents are completely against the idea of standards, or even standards that can be freely used on the web. We must try to educate those in power to reject software patents on video and audio codecs and to get free standards on these codecs for a free web. Not a web that will be controlled and taxed further by unnecessary Microsoft and Apple lockin.

“It is not enough to just have Theora or the new free Google codec.”
      –Chips B. Malroy“As far as IBM and Google with their support of software patents. While we would be better off without the patents, in the meantime, Google has to play the patent game in some countries, as that is the law of the land in the USA. To be able to sue those who come against you, is a weapon that we should not say to Google; “do not sue MS or Apple.”

“It is not enough to just have Theora or the new free Google codec. All of these video and audio software codecs should be free if used on the web, as the web should be free. Free standards for a free web, should be the call. Invalidate the software patents on these video and audio codecs, and make them public domain.”

This point of view is further supported here:

Why Our Civilization’s Video Art and Culture is Threatened by the MPEG-LA

We’ve all heard how the h.264 is rolled over on patents and royalties. Even with these facts, I kept supporting the best-performing “delivery” codec in the market, which is h.264. “Let the best win”, I kept thinking. But it wasn’t until very recently when I was made aware that the problem is way deeper. No, my friends. It’s not just a matter of just “picking Theora” to export a video to Youtube and be clear of any litigation. MPEG-LA’s trick runs way deeper! The [street-smart] people at MPEG-LA have made sure that from the moment we use a camera or camcorder to shoot an mpeg2 (e.g. HDV cams) or h.264 video (e.g. digicams, HD dSLRs, AVCHD cams), we owe them royalties, even if the final video distributed was not encoded using their codecs! Let me show you how deep the rabbit hole goes.

Microsoft is of course choosing to lobby for MPEG-LA, of which it is a participant. Microsoft is going to use Internet Explorer^* to promote H.264 and Canonical’s old codec affairs won’t help, either:

Canonical licenses H.264 – Theora out for the count?

Canonical are currently the only Linux company to license H.264/AVC, the patented non-free technology used to compress video and favoured by companies such as Apple & Microsoft for HTML5 Video.

Neither RedHat, makers of Fedora, or Novell, makers of Suse, appear on the list of over 800 licensee’s.

What’s interesting is that the rival, if you will, to H.264 is the free and open codec Ogg Theroa which one would naturally assume would be the favoured choice for a Linux distribution’s parent to support.

Let us remember that MPEG-LA's CEO (Larry Horn) is a patent troll. TechDirt has just caught up with this news.

Joe Mullin has a great blog post, looking in detail at MobileMedia, a recently launched “company” that fits all the traditional characteristics of a “patent troll” or “non-practicing entity” (if you’d prefer). It doesn’t appear to do anything but hold patents, demand licensing fees and sue. So what’s so interesting about this one? Well, it’s a subsidiary of MPEG-LA, the company that manages some important digital video standards, and manages the patent pools related to them — and both companies have the same CEO.

[...]

What I find interesting, of course, is that many patent system folks have said that patent pools are the “answer” to issues like non-practicing entities filing crazy lawsuits. And yet, here we have an example of one of the major patent pooling administrators apparently deciding it’s more lucrative to get into the other side of the business instead…

In the meantime, while all this has been going on, it’s worth noting that Steve Jobs — one of the targets in this lawsuit — has apparently been telling people that MPEG-LA is getting ready to sue open video codecs, such as Theora, for patent infringement. Of course, such threats have been made before and never carried out — but if MPEG-LA now thinks that suing for patent infringement (rather than just alerting the patent holders to possible infringement) is the way to go these days, perhaps the lawsuits above were an opening salvo.

MPEG-LA is hardly a legitimate business if it bullies like this, but ISO, which is a farce that sells out to whoever has enough money to corrupt it, won’t do anything/much to stop this. As the president of the FFII put it yesterday, “ISO [is] pushing for a patent-free video codec, committee stuffing, yes you can do it [...] The analysis of patents is outside of the scope and competence of ISO and MPEG [...] MPEG believes that 20 years after its publication some technology will become royalty-free” (posted in Twitter).

One new writer at IDG puts it like this:

It’s Apple and Microsoft versus Google and Mozilla in a tag team match for the video codec in HTML5

[...]

As I wrote about earlier, there has been a horse race going on about which video codecs will be supported by HTML5. With the stakes so high, the race is starting to get a bit rougher. Now it is turning into a tag team match, with Apple and Microsoft on one side and Google and Mozilla on the other.

This past weekend both Apple (of the open standards according to Steve Jobs) and Microsoft (never afraid to assert an alleged patent claim) have supposedly put down the hammer that Ogg Theora (supported by Mozilla) and other open source video codecs may violate patents.

[...]

This sets up an interesting tag team match. On one side, the defenders of “open standards that we like” Apple and Microsoft. In the other corner, the open source champions Google and Mozilla. Hey maybe Adobe can be the guest referee? The winner of this match will determine what technology will underlie the video you watch on the web or your TV in the future.

Dana Blankenhorn has more to say about Apple:

Will Apple put its lawyers behind the open codec patent attack?

[..]

All this makes the pending decision in Bilski vs. Kappos, still unknown at this writing, so important. A decision that encourages Apple to proceed, especially against Google, may make for the biggest lawsuit of all time.

Apple has already sued Android through HTC.

Do not support Apple and Microsoft, though not just because they produce non-Free software and engage in anti-competitive activities (bad faith and conduct); they are also a threat to freedom in culture. This helps nobody but stakeholders like Disney, which Apple is tied to. █
_____
^* Not that Internet Explorer matters so much anymore. Even Microsoft-friendly meters like Net Applications (mostly from the US, secret data and secret methods, funded in part by Microsoft) say that Internet Explorer is losing browser share while about one in two Windows PCs is infected with no foreseeable solution, certainly not even snake oil marketing like this new example:

The word about Immunet’s free anti-virus solution is spreading fast. The agent installed on my computer tells me that there are currently 162,597 people in the Immunet Cloud, and that I’m protected from 12,637,576 threats. When I first installed it almost a month ago, the number of users was around 122,000.

Summary: Oracle’s attitude toward (or dedication to) ODF compares badly to that of Sun, IBM, and probably even Red Hat

LAST year was a fascinating year for Sun Microsystems. It was almost acquired by IBM, but the negotiations fell through at some stage. IBM’s hardware business, office suite, and many other software products (Eclipse comes to mind) nicely complement Sun’s portfolio and even IBM’s commitment to MySQL would have been better and more natural than Oracle’s.

“OpenOffice.org and many other office suites support ODF free of charge.”IBM is not perfect. Heck, IBM is far from perfect and the word “perfect” is rather silly to bring up. As the TurboHercules vs IBM case reminds us, IBM is not a friend when it comes to software patents^* (malice from TurboHercules withstanding), but IBM is a big proponent of ODF, for example. It’s one of those areas where an IBM-Sun merger would be suitable. The FSF is strongly in favour of ODF as it probably should be.

Oracle has rightly come under some fire for putting a price tag on an important enabler of ODF. This is bad move in general (not prioritising ODF), but maybe it would give reasons to just abandon Microsoft Office altogether. OpenOffice.org and many other office suites support ODF free of charge. Microsoft does not support real ODF [1, 2, 3, 4, 5, 6, 7] or even OOXML, it only pretends.

Oracle start charging for Sun’s Office ODF plug-in

[...]

According to Oracle, the support cost is in line with Oracle’s support policy of approximately 22% of the license fee and is not mandatory. But the $90 per user license fee is required. As the plug-in was never open source, Oracle has not gone back on any open source assurances it gave. Oracle would not comment on the fact that the plug-in is almost as expensive as the cheapest edition of Microsoft’s MS Office suite.

Maybe if Oracle bought Novell (which is up for sale), then it would also charge $90 to download Mono. That would be nice.

Walt Hucks says: “I saw that coming back when Sun itself started requiring an account and mktg info to download the plugin.”

In better news regarding ODF, IBM’s Rob Weir points to ODF Fuzzer, which seems like a new tool that’s all about ODF.

ODF Fuzzer is a file format fuzzer developed to test star writer of Open Office.org. This will attempt to find security vulnerabilities, bugs and code flaw errors of the star writer. It uses byte mutation and insertion methods to create fuzzed files. ODF Fuzzer have a simple built in module to execute the star writer with the fuzzed files and monitor it’s behaviour.

There are also signs that Documents To Go will implement ODF support. The Product Manager says: [via Rob Weir]

Rest assured that many of the features you’ve mentioned (PDF, Google Docs integration, swirl zoom, localization, ODF support, etc) are being evaluated by our developers as we speak.

Here is what IBM’s Arnaud Le Hors wrote about Alex Brown’s [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21] attempt to pretend that he did not expect Microsoft to disobey ISO [1, 2, 3, 4].

Well, let me give you a link to a prediction I made! In my post What Microsoft’s track record tells us about OOXML’s future of March 25, 2008 I wrote:

They can, and I predict will, ignore all these additions which are optional and stick to what they have. The only reason they were added was to remove reasons for National Bodies to vote against OOXML.

So, here we are. Two years later, Microsoft has done exactly that and Alex Brown is finally seeing the light.

One can only hope that the standards community will have at least learned a lesson from this sad story: you simply cannot take control away from a vendor who has a monopoly and isn’t willing to give it up through a mere standardization process.

One area where IBM has been helpful is ODF. It’s a shame that Oracle is not so serious about it, not based on its actions anyway. OpenSolaris comes to mind in relation to this strategy. █
_____
^* Here is another new analysis of the TurboHercules vs IBM case and more lobbying from Florian Müller, who criticises multimedia codecs with patents in them (he does not seem fond even of Ogg) and has harsh words for the film “Patent Absurdity” [1, 2]. From Müller’s new blog (for which he has just created a Twitter account):

I regret having had to say all of the above and I can only hope that someone else will do something better at some time, maybe with a more realistic goal, maybe with a bigger budget. But realistically, software patents won’t go away until the call for abolition is supported by some of the major players in the industry. Theoretically it could also work with small and medium-sized businesses but in my experience that just doesn’t work because those SMEs who oppose software patents don’t want to spend any significant amount of time and money on it. As long as it looks to politicians like mostly a cause for the FOSS community without major economic interests behind it, it’s hard to see how change could be brought about. Watching “Patent Absurdity” just reaffirms that view. Unfortunately.

–Benjamin Henrion, FFII

Summary: This past week of Document Freedom brings even more abysmal news for Microsoft’s corruption-riddled response to ODF (OpenDocument Format)

LAST NIGHT we wrote about attempts being made by Alex Brown to pass the blame to Microsoft, having actually helped Microsoft be where they are. What a fox. Does he really believe that people will forget what he did to promote OOXML while serving as a supposedly-independent participant [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21]? Tim Anderson, a longtime Microsoft booster, has mentioned Brown’s mea culpa and so did Andy Updegrove, who apparently foresees failure for OOXML.

In reviewing my RSS feed this morning, I found this interesting blog entry by Alex Brown, titled Microsoft Fails the Standards Test. In it, Alex makes a number of statements, and reaches a number of conclusions, that are likely to startle those that followed the ODF-OOXML saga. The bottom line? Alex thinks that Microsoft has failed to fulfill crucial promises upon which the approval of OOXML was based. He concludes that unless Microsoft reverses course promptly, “the entire OOXML project is now surely heading for failure.”

Wow.

Andy Oram points out in the comments: “The OOXML battle is no joke; it had serious repercussions throughout the public setting. Microsoft launched its OOXML campaign in the mid-2000s at a time when several countries and US states (notably the state Andrew and I live in, Massachusetts) made real efforts to move to ODF for the public good. The fake standardization of OOXML helped Microsoft’s propaganda campaign to keep MS Office in government use, although I’m sure it wasn’t the critical factor. The movement failed and history has moved on. Microsoft avoided the loss of customers and the PR boost open source could have achieved had ODF gotten into government agencies. Now the question is whether desktop office tools will be replaced by Software as a Service, so there’s little point in refighting the old battle. But open formats are more important than ever, and the new power of the movement for transparent government can correct the historical grievance.”

“The fake standardization of OOXML helped Microsoft’s propaganda campaign to keep MS Office in government use, although I’m sure it wasn’t the critical factor.”
      –Andy Oram, O’ReillyAs we pointed out before, fragmentation issues already plague OOXML (there have always been too many Microsoft implementations, none of which complied with the specifications). These are further exacerbated by the i4i case [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12], which revealed that Microsoft had hidden software patents affecting OOXML.

Some sources have spoken about a potential appeal in the i4i case (or a settlement), but OOXML seems to be dead in the water at least as a ‘standard’ because the i4i ruling is final, based on Reuters.

A federal appeals court denied on Thursday Microsoft Corp’s request that a full panel of judges rehear arguments in its long-running patent dispute with a small Canadian technology company.

One of the more troubling patent rulings in the past year involved a Canadian company, i4i, that held a patent (5,787,449) that appears to broadly (very broadly) cover editing a custom XML document, separate from the presentation layer of a document.

The 5^th anniversary of ODF is less than a month away. From Rob Weir’s Web log:

We’ll be hitting a significant date next month. It was on May 1st, 2005 that Open Document Format (ODF) 1.0 was approved by OASIS.

I hope we can all take time to reflect on far we’ve gone, with the specification itself, with the quality and diversity of implementations and with world-wide adoption.

A lot of coverage about “Document Freedom” has appeared over the past week (included in our daily links), which is evidence of continued momentum for a real standard that everyone can use and many vendors have already implemented. According to this new gem from Glyn Moody, Tim Berners-Lee refuses to accept Microsoft Office files.

We all knew that Sir Tim was a total star, choosing to give away the Web rather than try to make oodles of billions from it. Some of us even knew that he contemplated using the GNU GPL for its licence, before being persuaded that placing it in the public domain would help it spread faster.

Tim Berners-Lee is also against software patents. █

Summary: Microsoft back into its walled gardens after bribing, cheating, stuffing ballots, and lying to everyone for the sake of hurting document standards (ODF)

What a lovely Easter present. Even one of the people who are responsible for the OOXML fiasco [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21] admits the obvious and concedes that Microsoft was bluffing.

Alex Brown writes:

Microsoft Fails the Standards Test

[...]

Microsoft has many enemies who will no doubt see the current state of affairs as proof that Microsoft never even intended to be good standards citizens. Indeed standards and XML veteran Tim Bray, writing shortly after the standard’s approval, made a prediction which could now seem impressively prophetic:

“It’s Kind of Sad • The coverage suggests that future enhancements to 29500, as worked through by a subcommittee of a subcommittee of a standards committee, are actually going to have some influence on Microsoft. Um, maybe there’s an alternate universe in which Redmond-based program managers and developers are interested in the opinions of a subgroup of ISO/IEC JTC 1/SC 34, but this isn’t it.

I suppose they’ll probably show up to the meetings and try to act interested, but it’s going to be a sideline and nobody important will be there. What Microsoft really wanted was that ISO stamp of approval to use as a marketing tool. And just like your mother told you, when they get what they want and have their way with you, they’re probably not gonna call you in the morning.”

So Alex, how does it feel to have helped corrupt the integrity of ISO, which you purport to be a part of? Note the comment at the end, which says: “Alex, I am surprised, after all the allegations of stuffing, bribing and coercion of NB’s that were, until DIS29500, uninterested in XML document standards, that you seem surprised at the outcome thus far.” This doesn’t even mention the personal role of Alex in all that malarkey. █

“The ISO process, brutal and corrupt as it was, has been covered to death by everyone.”

–Tim Bray

MICROSOFT’S “Insider Friend, ‘the Fox’” Alex Brown [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21] is “Looking at the pubic review text of #ODF 1.2 pt 1″ and saying that “some bits still very ropey”

What an unsurprising statement coming from the man who essentially conspired to help Microsoft corrupt ISO’s integrity while he marketed OOXML around the UK.

“ISO is dead for software standards. Do you need an official funeral?”

–Benjamin Henrion, FFII

Moreover, just very recently Alex Brown was seen defending Microsoft’s deviation from ODF [1, 2, 3, 4, 5, 6, 7] — a deviation which is only fragmenting and complicating everything.

Brown is joined by Microsoft MVP Miguel de Icaza. They are acting like Microsoft reps, to whom Simon Phipps (Oracle) replies with: “My view is that ODF should now just transclude the OOXML formula spec, but that’s probably controversial”

“To an outsider, it would probably seem clear that de Icaza is a Microsoft employee or partner who wishes that ODF just went away.”De Icaza seems very eager to keep smearing ODF, which is a threat to the top cash cow of the company whose board he serves (CodePlex Foundation board). A little conflict of interests there, no? Anyway, he is linking to his colleague Morten Welinder, who is dissing ODF and closing comments, possibly in order to prevent rebuttals from being posted. Rob Weir responded to de Icaza by saying: “The spec that vendors are implementing is linked to from the ODF TC’s homepage. Novell is on the TC. You know this.”

Maybe he’s playing dumb. After all, he also has loyalties to Microsoft, not just Novell. And guess who else is linking to de Icaza and his colleague (the ODF smear)? That’s right, it’s more noise which feeds those at Microsoft who participated in the corruption of ISO and various standards bodies around the world. They quote de Icaza as though he’s their special buddy (which he is, as he even helped bug resolution in OOXML). To an outsider, it would probably seem clear that de Icaza is a Microsoft employee or partner who wishes that ODF just went away. Why are other Microsoft agents like Microsoft MVP Miguel de Icaza linking to that same post, which is damaging to ODF and not even factual? It’s stuff like this, which makes the question rhetorical.

Miguel de Icaza writes in response to the call-out: “Another Rob Weir swing from Bombastic troll when discussing OOXML to nuanced and apologetic when it comes to ODF”

He’s starting to sound just like another one of those Microsoft employees who are smearing Weir (sometimes by creating smear blogs or calling for resignation).

Weir responds with: “ISO approval is not my success metric for ODF, but rather adopters, users and implementors. By those measure I’m pleased.”

“[I]t seems that Morten isn’t following the ODF development at all.”
      –Jomar SilvaAddressing the actual source of the FUD, Morten Welinder criticises formula handling in ODF even though a lot of office suites (excluding Microsoft Office) successfully implemented ODF support for formulas that are also interoperable. Weir showed this using a table and several sample files about a year ago.

It is worth adding that the ODF smear comes from the same group (Gnumeric) that was helping OOXML get past ISO. We wrote about this at the time [1, 2], specifically when there were complaints about GNOME engaging or in general terms helping Microsoft in that regard (Jody Goldberg from Novell got actively involved for example).

Jomar Silva, who is a key person in ODF, says that “it seems that Morten isn’t following the ODF development at all. Simply pathetic !”

Let’s remember what these people are pushing for at ODF’s expense. OOXML is utterly flawed and it annoys so many users of Microsoft Office, based on this new analysis at INC.com: [via Bob Sutor]

For those using older versions of Microsoft Word, or other non-Microsoft word processing software, the new .docx format can be a real pain. It has caused dissension in some workplaces. How to cope with conflicting Microsoft Office formats.

It’s a funny article to read. Microsoft’s own customers loathe OOXML.

ODF is also important because it offers “equal opportunities”, as advogato.org put it:

It is possible to get people to listen if you want to instil Free Software principles, but they have to have a “handle” against which they are forced to act, within the organisation that they work. Or, if they agree with you in principle, but are otherwise hog-tied, they need that “handle” with which to justify their actions to their superiors.

Using the words “Discrimination” and “Equal Opportunities” in the same sentence seems to do the trick.

Jan Wildeboer says that “The ODF TC peeps should really read this gem,” which accurately dissects some of the deception from Microsoft and its promoters. Here is Miguel de Icaza hugging Jeff Atwood from Microsoft. The photo below (from Marcus Griep) is a very recent one and the description of de Icaza’s talk at this event (filled with Microsoft employees and content) goes as follows:

Miguel also showcased MonoTouch, building a simple program in MonoDevelop on Mac OSX, and demonstrating it in the iPhone simulator. Including lots of pro-Linux banter and some pokes at Richard Stallman, Miguel kept the audience interested and amused, which is exactly what the last presentation in an 8-hour day needs.

Yes, it’s the same guy we have come to know ever since he compared Stallman to George Bush. What does that make it his darling Microsoft? Either way, it’s nice of him to ridicule Stallman in front of an apparently Microsoft-dominated audience. It must be a new and entertaining pastime for them. █

From Marcus Griep

Summary: With the ending of the i4i case OOXML should be removed from ISO and cease to be used

THIS is a subject that we wrote about before, right after it turned out that Microsoft had deliberately lied by saying that OOXML had no patent issues. Microsoft was already struggling against i4i in court [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], knowing damn well the implications it would probably have when it comes to OOXML. Microsoft lied with pride. Microsoft also corrupted ISO with the help of insiders — “accomplices” as one might label them.

Sun’s Tim Bray has just said what many came to witness a few months back.

At the time of the huge OOXML dogfight, one of the reasons Microsoft claimed that the world needed OOXML, even though there was already a perfectly-good ISO-standard XML office-document format, was that it enabled this wonderful customization feature.

What Bray calls the “OOXML dogfight” was a phenomenal display of disregard for the law (see the OOXML Abuse Index), in which the BRM convenor, Alex Brown, personally participated [1, 2, 3, 4, 5, 6]. Over at Groklaw, Pamela Jones writes: “I wonder how Alex Brown and the gang will handle OOXML now that Microsoft has been found guilty of willful patent infringement in the i4i case and so must remove functionality from XML in its Word products? Does it mean that the standard is no longer “in use”? That it must be withdrawn due to a patent having been asserted against it?”

ISO is probably too corrupt and vain to withdraw OOXML, but that’s what it ought to be doing at this stage. Microsoft rammed something ridiculous under false pretenses, not just with bribery.

Speaking of patents, here is interesting news:

A recent Microsoft patent application applies a similar approach to defining navigational queries. The inventors of the patent filing tell us that queries can be generally classified as falling into a couple of broad categories: discovery queries and navigational queries.

More here:

He compares the Microsoft filing to a recent Yahoo patent filing that details what the Sunnyvale, Calif., company might look for when deciding whether a query was navigational or not. Slawski bases some of his analysis on Microsoft’s “best match” feature.

We previously wrote about the possibility that Microsoft would use patents against Google. █

“The ISO process, brutal and corrupt as it was, has been covered to death by everyone.”

–Tim Bray

Summary: The ups and downs of ODF, the latter being largely the result of Microsoft’s gentle blows

ODF (OpenDocument Format) is still doing pretty well, especially in developing countries like Brazil (also here) and nations where corruption rates are low (notably Scandinavia).

According to this report from IDG, Holland is prepared to help Denmark with ODF, resisting the infinite cronyism of Helge Sander.

The Dutch government has provided Denmark with information regarding the Dutch national plan Heemskerk for open government IT.

In Denmark, there is heated debate about the approach for open IT usage by the government. One of the obstacles is the open file format for mandatory use by the government and government organizations. ODF (Open Document Format) and OOXML (Open Office XML), originally developed by Microsoft, are the candidates for use.

The Dutch Ministry of Finance shared with Denmark the experience and knowledge it has gained from the national plan Heemskerk and the resulting action plan “Nederland Open in Verbinding” (NOiV). Finance spokesman Edwin van Scherrenburg confirmed to Dutch IDG news site Webwereld that the two governments are in contact. “We have shared all information regarding NOiV,” he said.

Further up in Norway, one person writes: “New task: write report for Norwegian government on whether to recommend/require ODF and/or OOXML in Norwegian public sector” (a response to which is: “I did the same for the Danish goverment about 2 years ago, “comparing” ODF, OOXML and PDF. Did I make a difference? I’d like to know”).

“On the menu: one of the smallest cities in Belgium – Nieuwerkerken – needs some new and fancy automatically generated documents in #odf,” says this gentleman from Belgium and ODF is also mentioned in German news sites.

Europe is clearly warming up to ODF and so do developers (new examples here and here).

Bart Hanssens writes from Belgium (a meeting was held in France): “uploaded proposal for #odf 1.1 Interoperability Profile http://www.oasis-open.org/committees/document.php?document_id=35565″

“ODF TC done,” writes Cherie Ekholm, “starting PDF/UA.” Dennis Hamilton announced: “ODF TC e-ballot on #ODF 1.2 Part 1 CD04 as Public Review draft ends tonight, expected to pass easily based on current votes.”

In addition he wrote: “ODF TC discussed whether to align OSI/IEC IS 26300 and #ODF 1.1 or would ODF 1.2 overtake the effort and time to accomplish. Unresolved.”

Later came: “#ODF TC Approves ODF 1.2 Part 1 Committee Draft CD04 to submit for first-ever Public Review. OASIS to announce after docs all set.”

Bart Hanssens took note and so did Pim Bliek. Mary McRae (the key person for ODF at OASIS) has also responded.

An important subject which was brought up by several people has also been shared by an OpenOffice.org guy, who wrote:

Locked out by design

[...]

Software vendors have tried on and off to lock these documents so users needed the original software to use them. This can go horribly wrong, as some users of Microsoft Office 2003 have just found out to their cost, when the software refused to let them get at their documents – their own intellectual property. This is a design feature of Microsoft Office software which happened to misfire.

What it highlights is that no-one outside Microsoft has a clue what is hidden inside their secretive software. It also highlights the importance of not using a secret format to store valuable office documents. The safe way to store valuable documents is in OpenDocument Format (ODF) – an ISO approved open standard which isn’t owned by any one company. It’s the best guarantee against being held to ransom one day by a software supplier.

We wrote about this a few days ago and so did Microsoft. Wolf Corcoran-Mathe writes: “[Microsoft Fixes Office 2003 Document Lockout] Great. Now if they could only stop breaking ODF.” He is referring to Microsoft’s inability (or unwillingness) to obey interoperability needs [1, 2, 3, 4, 5, 6, 7].

“Brown’s private firm benefits from Microsoft as we showed many times before, so he never relents.”Now we get to the ugly parts where Microsoft is attacking ODF, as usual. Alex Brown [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22] is sticking his nose again, trolling/heckling John with some poison against ODF (see the comments in the blog above). Brown’s private firm benefits from Microsoft as we showed many times before, so he never relents. Microsoft’s very unethical Doug Mahugh is also pushing the same Microsoft line, which gets passed around by others who are associated with Microsoft. It's like a cult of money and power. Corruption is a key ritual, which the heavily-spammed ANSI pretends never happened. But to quote Brown’s predecessor: “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.”

It indeed became impossible and ISO is now corrupt [1, 2, 3, 4].

So, Microsoft got away with misconduct, who cares? Many people said the same thing when George Bush stole the elections. Whatever.

A post that we cited the other day comes from Rob Weir and Glyn Moody calls it a “good summary of where we are, and why Microsoft’s moves are fishy…”

Microsoft’s obligations are by definition unethical and very much against ODF. That’s just how the company operates, for its shareholders. “[T]hat’s super screwy because “O”OXML is Microsoft’s format. ODF is the REAL open format,” says this one person to a peer/friend, later adding that the nature of this situation is “making ODF far more resilient against bugs, because they can easily be patched.” █

Summary: Several more advancements for ODF and another eye-opening reminder that poorer countries are discriminated against by the Microsoft-faithful crowd

LAST week we wrote about Slovakia and ODF. Supporters of open standards should be pleased to know that the international standard, ODF, is gaining ground very rapidly. Here is a small update from Slovakia: “SK committee for e-standards if the government agreed to change ODF 1.0 to ODF any version up to 1.2 (1.0,1.1,1.2)…“

And it’s not just Slovaks who are likely to enjoy the ability to access and share documents from almost any office suite. In Japan too there is great progress, as Murata says that the Japanese standard for ODF is finally released: “The ODF JIS has been approved finally. We trust in better maintenace by SC34/WG6 and the ODF TC…”

“The ODF JIS has been approved finally. We trust in better maintenace by SC34/WG6 and the ODF TC…”
      –Dr. MurataFellow countrymen spread the word even further, but SC34/WG6 cannot be trusted for maintenance. We’ll come to this in a moment. One person from elsewhere says: “Good to see some practical changes — more colleagues will be using ODF format for docs, so much better for cross platform”

Another person argues that “we need to specific data format (e.g., ODF) not software suite”

This brings us to some ugly stuff involving Microsoft’s “Insider Friend, ‘the Fox’”, whose name in this case is Alex Brown. He has done a lot to deserve people’s disdain [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21] because he seems more interested in Microsoft’s interests than in standards.

Several months ago Microsoft tried to kick IBM/Weir out of the ODF TC (technical committee). Jomar Silva, who helped expose the mischiefs of Alex Brown and his beloved Microsoft, is now being pressured out (along with his country) by Alex Brown. [same article in Portuguese]

Alex Brown wants Brazil out of the ISO !

As if the dirty things he did with Brazil during the OpenXML BRM in ISO wasn’t sufficient, now Alex Brown suggests in his blog that Brazil shouldn’t be a SC34 member at JTC1. Reason: Brazil did not send delegates to the SC34 WG’s meeting in Paris last week!

Brazilian people are rightly furious [1, 2, 3, 4, 5]. Microsoft and its minions would love to push resistance out of the table, leaving just the corrupt and the rich (some of the former funded by the latter) to discuss matters, all at the exclusion of the developing nations that dared to file formal complaints to ISO. In turn, ISO, which is also run by the rich and the corrupt, rudely threw away all these complaints.

Speaking of this Microsoft-stuffed [1, 2, 3, 4] SC34 meeting in Paris, Mary McRae from OASIS writes to Alex Brown that he “went to Paris and ate too many croissants. Washed down with brandy.”

Brown was baffled by it because he does not get British humour [1, 2, 3] (yes, it’s rather ironic) and Aslam from South Africa (which filed the first complaint to ISO) said that he “would watch the BRM re-run RT @fiberartisan: @BartHanssens #oasis I think some of them would make better reality TV shows…”

Boycott Novell has good record of the corruption that occurred at the BRM, e.g. [1, 2, 3, 4]. Speaking of which, one reader sent us these thoughts a few days ago, in reference to Microsoft crime and inability to serve the industry:

Dumped in a landfill is even less ceremonious than dumping in a mass grave.

Where there are Microsoft partners and distributors, there are Microsoft products and the One Microsoft Way of thinking:

How much can be attributed to Sharepoint? LSE didn’t have much luck with Sharepoint. It’d be hard to imagine that a smaller budget would have better luck specially if they’re so ideologically driven as to ignore the established, faster, cheaper, better, easier FOSS solutions.

Another reader wishes to remind people of the real history of Microsoft Office, which Microsoft sympathisers try to rewrite:

Here’s a subtle piece of Microsoft Revisionism.

Ah, now I see, it’s Joe Wilcox. This kind of thing is typical of his flamebait that I’d rather not draw attention to, but I thought I’d share my analysis.

While pretending to analyze a Microsoft failure, he creates a false impression of their products excellence as a means of success:

“Microsoft Office achieved two important goals by the mid 1990s. Established format standards that resolved problems sharing documents created by disparate products. Ensured that Microsoft file formats would become the adopted desktop productivity standards.”

Office did not work then and it does not work now. The success of Microsoft Office was the end result of hardware economics and targeted dumping. In the late 80s and early 90s, IBM hardware was all most people could afford and Microsoft made sure it came with nothing but Microsoft DOS. Microsoft did a good job of getting Office to people who would be in a position to ram it down other people’s throat. Those who actually did the work preferred Word Perfect and other superior products. I saw this every place I worked at the time. They used the same kind of panel stuffing that they would later brag about in their training documents and that was so obvious in the OOXML ISO process.

Wilcox should know better than this and actually includes the information he needs in the same article,

“‘Browsing the Web, you find almost no Microsoft file formats,’ Gates wrote. He observed not seeing a single Microsoft file format ‘after 10 hours of browsing…’”

Yes, in 1995 people with a clue were using other things. They still are today and, thanks to the Internet, we can derail Microsoft corruption. In all that time, despite great effort, Microsoft has yet to destroy Adobe’s document formats that actually work. It’s not from lack of trying, it’s from lack of product that works. Wilson ignores the rise of in house Wikis as a replacement for the usual, tedious Microsoft network and emailed revision train wreck.

Wilcox goes on to cover up Microsoft’s failure at “Consumer” as some kind of ordered retreat. In the last ten years Microsoft has wasted tens of billions of dollars trying to dominate media distribution. Windows Media Center, Zune, Xbox, various forms of Microsoft TV have all been colossal technical failures. In the competitive consumer market, where stacked panels don’t work, Microsoft was unable to win despite some key hardware format victories. Every cheap music player in the world works with Windows media formats but very few will do ogg vorbis, flac and other superior and royalty free formats. Microsoft blew that tremendous advantage with obnoxious digital restrictions and software that everyone hated. They failed there for the same reason they are failing elsewhere, Microsoft is just not competitive.

Watch what Microsoft is doing right now to people who try to do their job and cover events:

Microsoft PR outlaws iPhone talk

A Microsoft manager created a bit of a fuss by advising a journalist not to mention the iPhone at a Microsoft event in Germany, betraying frayed nerves in the MS camp.

The journalist was apparently guilty of expressing his opinion that no mobile phone was easier to use than an iPhone. We might disagree with that opinion*, but we wouldn’t demand he stop mentioning Apple products, as one Microsoft manager did.

This would not be the first time that Microsoft behaves in this way.

We wish not to end with a negative tone, so here is some good OpenOffice.org news, which ought to reflect positively on ODF too.

There are some nice (and rather major) changes coming to OpenOffice.org and KOffice too is supporting ODF with Nokia’s help and in collaboration with OpenOffice.org. The replies in posts like this one bode well for ODF and one person has published the article which is titled “ODF – The Future of Literate Programming?”

Which brings me to the ‘what if’ question. What if we leveraged the fact that there is now a non-proprietary standard XML representation for richly formatted office documents called ODF[2]. What if we used ODF compatible tools like OpenOffice[3] to write our programs? How would we extract the lines of code to feed to our compilers? We could just use paragraph styles that indicate Èfeed this to the compilerÉ.

For documentation, an embarrassment of riches would then be instantly available. We could use level heading to split up the code/documentation into hierarchical chunks. We could generate tables of contents from these level headings. We could insert pictures wherever we need them along with tables, cross references, index entries and so on. Heck we could even embed spreadsheets, photographs taken of white-boards at planning meetings, the whole shebang.

WYSIWYG literate programming with ODF? I do not see why not.

OpenOffice.org plans to reach a broader market under the slogan “open for business”:

Open for Business logo couple of years ago we came up with a slogan for OpenOffice.org – Open for Business – to get across a couple of messages:

* OpenOffice.org software may be used by commercial businesses completely free of any licence fees
* OpenOffice.org software is also a great platform to build businesses around – training providers, systems integrators, PC manufacturers to name but a few

With OpenOffice.org 3.1.1 already out there, the Sun engineers are testing version 3.2 and publishing their results.

Automated tests on milestone OO320m7 are finished. Automated testing team reported a ‘green state’ for all automated tests. Just a small problem in w_updt.bas bother the consistent picture of all platforms marked green in QUASTe. This issue wasn’t easy to find but at the end we solved the problem in showstopper CWS ‘jl146′ with issue 107038. Depending on desktop respectively OpenOffice.org window size the document is middle or left aligned with automatic view layout (which is default). This lead to the problem sometimes the objects in writer document were drawn outside of the documents area by autotest. Finally we found and fixed it by correcting view layout before testcases run. Some additional minor fixes for more stability were also done in this CWS. Punctually with release of RC1 next week the autotests are expected to deliver a ‘green state’ on initial testrun.

IBM has published this new article about ODF and lpOD (first mentioned here) has a new release, in addition to this new release of odsPhpGenerator.

odsPhpGenerator is a small and easy library to generate OpenDocument Spreadsheets. It requires only PHP 5.0, DOM, and zip support.

Projects that support ODF just carry on coming. So, all in all, the real standard is winning. █

“ISO is dead for software standards. Do you need an official funeral?”

–Benjamin Henrion, FFII