Currently, SAS Institute, Inc. is suing World Programming for copyright infringement. SAS claims that by implementing the same functionality, using the same programming language, as is present in SAS' software, World Programming is violating SAS' copyright. The crucial thing here is that World Programming has not had any access to SAS' source code.
SAS creates something known as the SAS System, a set of software programs to collect, store, analyse, and manipulate data. Using the SAS Language, people can extend the functionality of the SAS System. The problem was that if a customer wanted to switch away from SAS, he had no choice but to rewrite his programs; the SAS Language only works with SAS' software, meaning total vendor lock-in.
This is where World Programming comes in. They developed an alternative to the SAS System, dubbed the WPL System, which allowed customers to run programs written in the SAS Language without using the SAS System. They had no access to any of SAS' source code whatsoever, so they had to write it from scratch.
As a result, SAS sued World Programming, arguing that reverse engineering SAS constituted copyright infringement - not just of the source code itself, but also the manuals for the SAS System (since the functionality was alike, I presume). In addition, SAS also contents that World Programming violated the license of the SAS System Learning Edition (probably by using it to better understand SAS, and therefore, violate a non-commercial clause in the license).
The High Court of England and Wales already ruled in July last year that SAS had no case, and that the functions provided by computer systems, or the language they're written in, cannot be protected by copyright. The case then escalated to the Court of Justice, which is set to rule next year. Yves Bot's non-binding opinion, published today, reiterates The High Court of England and Wales' ruling.
Bot comes to the conclusion that under current EU law, the functionality provided by a computer program cannot form the object of copyright protection. His example to illustrate his point, interestingly enough, is not altogether different from how most programmers argue against software patents.
There are, however, many means of achieving the concrete expression of those functionalities and it is those means which will be eligible for copyright protection under Directive 91/250. As we have seen, creativity, skill and inventiveness manifest themselves in the way in which the program is drawn up, in its writing. The programmer uses formulae, algorithms which, as such, are excluded from copyright protection because they are the equivalent of the words by which the poet or the novelist creates his work of literature. However, the way in which all of these elements are arranged, like the style in which the computer program is written, will be likely to reflect the author's own intellectual creation and therefore be eligible for protection.
In other words, the actual written code behind a function is protected by copyright, but the function is not. So, if you arrive at the same function but with entirely different code, you are not infringing any copyright. "To accept that a functionality of a computer program can be protected as such would amount to making it possible to monopolise ideas, to the detriment of technological progress and industrial development," Bot writes.
Well paint me red and call me a girl scout - that sounds a hell of a lot like how we argue against software patents.
Moving on to the issue of the programming language, Bot also comes to the conclusion that it, too, cannot form the object of copyright protection.
Moving on to the matter of the data files SAS stores information in. To achieve interoperability with these data files, World Programming had to decompile certain parts of the SAS System. Bot argues that an inherent function of the data files is to enable interoperability, and that EU law allows decompilation in cases where the necessary information to achieve interoperability has not been made readily available. In other words, exactly because SAS did not publish the information needed for third parties to read from and write to the data files, World Programming was allowed to decompile.
However, Bot adds that "in my view, the use of the terms 'indispensable' and 'necessary' illustrates the desire of the European Union legislature to make decompilation an exceptional act. To my mind, the licensee will have to demonstrate the absolute necessity of reproducing the code or of translating the form of the code for the purposes of interoperability with the elements of his own program."
This is reasonable, in my eyes. If the information to create fully interoperable third party programs is readily available, then there's no need to decompile or reverse engineer anything. If such information is not readily available, however, third parties should legally be allowed to decompile the information.
Lastly, we have the manuals. World Programming only took "keywords, syntax, commands and combinations of commands, options, defaults and iterations" out of the SAS manuals. As you can probably deduce from what we've covered so far, Bot does not believe these elements are covered by copyright protection.
I have to say that this is the second time the EU Court of Justice has blown me away with the clarity of their rulings and opinions. The language used is not overly legalese, it's relatively easy to understand, and the arguments made are based on technical understanding. It naturally helps that I find myself in full agreement with the opinion, but still.
We can only hope that the Court of Justice adopts Bot's opinion, but we'll have to wait until next year before we find out.