Red Hat, patents, software

I am here speaking software patents. I was replying to a thread on G+, and wrote a very long reply, that indeed is a post. It's on Red Hat patent promise, which has some unfortunate language that can be interpreted as "in general software patents impede innovation", meaning that in some cases they don't. I think that my reply can be of more general interest and make an excerpt here, with a few minor edits.

The post

I hate to defend rich companies and not getting paid for it (not that it would be the first time ;-), but in this case I will make an exception, also because the people who conceived the strategy of registering software patents for defensive purposes are good friends and trustworthy Free Software friends. Red Hat is a company full of cash, which is eating chunks of market away from even richer companies. It makes software, Free Software, it contributes heavily to Linux, it has no proprietary exploitation of the software it makes.

Microsoft v. Commission, last take-away points

This is it, it's over. The last remaining pending issue spawning from the 2004 Decision (the so called "Monti decision"), by which the European Union slapped Microsoft with an unprecedented antitrust remedy, has ended, barring an unpredictable appeal. A decision imposing 899 million euro fine, for non compliance with the obligation to provide complete and accurate interoperability information under Reasonable And Non Discriminatory conditions, was by and large upheld by the General Court in case T-167/08, where I represented the FSFE and the Samba Team, intervening in support of the Commission.

I have now read the decision in its all 26 printed pages. Among many details concerning procedural fine points that would bore to death most of the readers, I have found some points that are worth pointing out, since they confirmed my/our positions that we put forward since 2005. That's when the whole "implementation" phase started, after the President of the Court of First Instance (that was the General Court called back then) refused to suspend the 2004 Decision pending judgement on the merits.

Two bees make an eagle. US Judge says API not copyrightable

In Italian "api" means "bees" (plural). API in computer science means "Application Programming Interfaces", which are bits of code in a computer program that expose functions and calls to other computer programs so that they can interact. For instance, a platform (say, Gnome or MS Windows) can expose a function to call upon a printing dialog, and all application running on it only needs to invoke that function and an interaction can happen, so the application can print. The internals of the same API can be reimplemented many times without changing the outward facing interfaces, so that the applications written against them remain workable ‒ actually this happens on a regular basis.

A Federal Judge for the Northern District of California has ruled that the source code that declare a method to invoke the same function as in the API (thus representing the outward facing part) is not subject to copyright. This follows a quasi identical ruling of the European Court of Justice in the SAS case [Case C‑406/10].

A modest proposal to give Free Software equal legal standing as proprietary.

Note: Updated to include lock-in and tying. Some changes on moral rights to clarify that

Laws are more often than not an annoyance, despite their aim to improve the legal framework in any given field. Free Software (AKA "Open Source") has thrived despite the absence of any legal recognition by the law, if not in spite of rules that clearly are shaped around proprietary software. In many jurisdictions it has passed the enforceability test. So, no laws seem necessary to make it work. Yet, can some legal principle be put forward, and included in some laws, to help?

"If it works don't fix it", so goes the common saying. But if it works now doesn't mean it will work forever. It is nevertheless upon lawyers, and legislators alike, to foresee problems ahead of their actual happening, and brace for the potential harmful event. But any laws that would regulate Free Software would likely harm some parts of it, and change the games to favor one kind over another, or impose conditions that are not welcome or productive – something that legislator, even with the best intentions, often do – and in general could cause as many troubles as they would produce benefit. "Primum non nocere" is the paradigm for medical actions, even though drugs by definition only produce a net benefit by inflicting some limited damage. Is there a medicament that has entirely good effects without any negative ones? Arguably there is not. But with laws we can achieve something closer to this optimal benefit, which economists know as "Pareto Efficiency".

So this is a call for Pareto Efficient Laws, and Pareto optimal only laws.

Doors opened at Openoffice

A few minutes ago, Oracle has announced that, the ODF-based Free Software suite for office productivity, will become a community developed project. In plain English, no more dual licensing, no more proprietary version, go ahead to incoming patches. Woot!

I am very happy to hear about this move, which was not entirely unexpected (by me, at least). To tell all the truth, reaching this point was my secret plan when I have started helping Oracle in the merger control procedure opened by the European Commission last year, where the acquisition of Sun was under scrutiny. I was telling everybody that the dual licensing approach was going to die, that id did not make much sense anymore, that it was "moot" – I actually mentioned MySQL there, but the same applies to, actually. As it turns out, I was right.

Ifosslr, nuovo numero pubblicato

front page Un nuovo numero della International Free and Open Source Software Law Review è stato pubblicato. Questo numero contiene, tra gli altri, un interessante articolo del mio amico Maurits Dolmans circa l'interazione tra i brevetti e gli standard, con un appello per gli Open Standards. Merita assoultamente di essere letto. Altrettanto notevole è un'introduzione a un documento che cerca di chiarire come le varie modalità di linking e altre interazioni tra software di differente provenienza possa funzionare – o non funzionare – in ambito copyleft, di Malcolm Bain.

Altre questioni "calde" coperte sono la brevettazione di software in Europa, di Noam Shemtov, e un articolo sul progetto, in qualche modo controverso, chiamato Project Harmony. Il suo scopo e funzionamento viene spiegato dall'Avvocato Amanda Brock. Per coloro che si interessanto di gare pubbliche, l'articolo di Mathieu Paapst spiega alcuni aspetti delle azioni agevolatrici in favore dell'open source, principalmente da un punto di vista economico, il che fa da appropriato complemento al mio articolo contenuto nel precedente numero. Coloro che amano leggere autori controversi, avranno piacere nel dissentire dall'articolo-piattaforma di Matt Asay.

Dài, andate a scaricarlo è [Libero | Gratis]!