If you think software patents are a pain, try software copyrights

The judges who sit in the Court of Justice of the European Union must by now be thinking that the only way to stop Mr Justice Arnold sending them questions to answer is to have him appointed as a colleague. If you don't think so too, consider the case of SAS Institute Inc v World Programming Ltd [2010] EWHC 1829 (Ch), a Chancery Division (England and Wales) decision of Mr Justice Arnold, which was handed down last Friday, 23 July. It's a real whopper, too, the sort of judgment you'd expect on a complex topic on which the parties spent 12 days arguing with one another in court.

In short -- if that word is ever applicable to a decision of this length -- SAS developed its own SAS analytical software system, this being an integrated set of programs that enabled users to perform a wide range of data-processing and other tasks, and especially statistical analysis. The IPKat isn't surprised that it could do lots of tricks, since it had been around for some 35 years, generating income for SAS in excess of £2 billion. At its heart was "Base SAS", which let users write and run application programs ("scripts"), written in SAS language, in order to manipulate their data.

Base SAS's functionality could be extended by using additional components -- in this case SAS/ACCESS, SAS/GRAPH and SAS/STA. Over the years, SAS's customers had created thousands of apps in the SAS Language -- some were short and simple, while others were vast. Anyone wanting to run their existing apps or create new ones had to take a licence to the SAS components. Other suppliers of analytical software existed in the market, but anyone wanting to change to another software would have to rewrite all its apps in another language, which would be a pain (and an expensive one, too).

World Programming ('WorldProg'), spotting the huge potential market for software to execute SAS-based apps for use elsewhere, developed World Programming System (WPS) -- which inevitably emulated much of the functionality of SAS's components in order to ensure that they worked the same. It was not alleged that WordProg had access to SAS's source code or copied it, or even that it copied any of the structural design of the components' source code. WordProg also created a WPS manual, which described the functionality of various elements briefly by reference to syntax diagrams, plus a set of WPS guides --four quick reference guides which simply listed elements of the SAS language and indicated whether the current edition of WPS supported it.

In September 2009 SAS commenced proceedings, alleging copyright infringement in its software and in its own manuals, as well as breach of SAS's licence terms with regard to the Learning Edition of the SAS System.

Remarkably, the case came to trial as early as this June and, having devoured a vast quantity of raw law as well as legal submissions and complex facts, Arnold J ruled as follows:
* Computer programs were protected by copyright just like any other literary works within the meaning of the Berne Convention by Article 10(1) of TRIPS, Article 4 of the WIPO Copyright Treaty and Article 1(1) of EU's Software Directive, subject to ant specific exceptions to the contrary.

* Both Article 9(2) of TRIPS and Article 2 of the WIPO Copyright Treaty distinguished between 'expressions' -- which are protected by copyright -- and 'ideas, procedures, methods of operation and mathematical concepts as such', which are not.

* United Kingdom courts must interpret both the Software Directive and domestic law in conformity with TRIPS and the WIPO Copyright Treaty, both as a matter of EU law and under domestic law. Accordingly, they have to protect 'expressions' as copyright works, but not 'ideas, procedures, methods of operation and mathematical concepts as such'. For this reason it is necessary to distinguish between the two, the former being protected by copyright and the latter belonging to the public domain.

* Skill, judgment and labour in devising ideas, procedures, methods of operation and mathematical concepts are not protected by the copyright in a literary work but skill, judgment and labour in devising the form of expression of the literary work are.

* Pumfrey J could not be said to have erred in Navitaire v easyJet (noted briefly by the IPKat here) when he concluded that programming languages were not copyright-protected. His distinction between a [copyright-protected] computer program and the language it was written in was, despite his hesitancy on the point, consistent with the distinction between expression and ideas, procedures, methods of operation and mathematical formulae.

* Under Article 1(2) of the Software Directive, "Protection ... shall apply to the expression in any form of a computer program. Ideas and principles which underlie any element of a computer program, including those which underlie its interfaces, are not protected by copyright under this Directive". The correct interpretation of this provision in relation to computer languages and interfaces was not acte clair and would therefore need a reference to the Court of Justice of the European Union to establish what it actually meant.

* Assuming that Pumfrey J in Navitaire was right (and the Court of Appeal in Nova v Mazooma was happy enough with his decision), WorldProg hadn't infringed SAS's copyrights anyway.

* It was not an infringement of the copyright in a manual describing certain functions to use that manual as a specification of those functions that needed replication and, to that extent, to reproduce the manual in the source code of the new program. This too was not acte clair, though.

* If Article 2(a) of the Information Society Directive is to be interpreted in the same way as Article 1(2) of the Software Directive, WorldProg didn't infringe copyright in SAS's manuals by producing or testing its own WPS product.

* There was no breach of licence. If any of SAS's licence terms for its Learning Edition were contrary to Article 5(3) of the Software Directive, they would be void. Here too, the interpretation of Article 5(3) was not acte clair.

* On the facts, some of the bits of WorldProg's manuals copied text that expressed the intellectual creation of the authors of SAS's manuals, so some copyright infringement had indeed taken place -- but there had been no infringement in respect of WPS's guides, where similarities had occurred through the accretion of key terms.
Says the IPKat, if I'm right there are going to be five sets of questions referred for preliminary rulings ...

SAS here and here
If you think software patents are a pain, try software copyrights If you think software patents are a pain, try software copyrights Reviewed by Jeremy on Tuesday, July 27, 2010 Rating: 5


  1. I don't see how this procedures are more complicated than the patent ones.

    In my opinion, the primary problem with software patent is that they restrict the creation to alternatives to solve problems. What's wrong with World Programming creating another language, based on SAS language? They are not the same, just related. Why should SAS be able to stop the creative work of World Programming?

    I think software patents are not really a good way to go. They delay progress because of the nature of software.

  2. Marshal, in asking what the problem is, you're demonstrating it. You ask "What's wrong with World Programming creating another language, based on SAS language? They are not the same, just related. Why should SAS be able to stop the creative work of World Programming?". That's just the point -- we can't tell whether World Programme is infringing, because of lack of clarity in applying copyright principles -- which is why the court is going to have to ask all those questions of the Court of Justice, a court which has little familiarity with, and understanding of, copyright issues.

  3. Marshal,

    From the IPKat's summary it looks like the UK judge doesn't think that there's anything wrong (from a copyright point of view) with what World Programming have done, at least as far as the programming is concerned, and that SAS shouldn't be able to use copyright to stop them.

    However, this area of copyright is controlled by EU law from Brussels and the UK judge is of the opinion that the EU law is not sufficiently clear for him to be certain of what it means. Therefore he must ask the Court of Justice of the European Union to clarify the law for him. [The preceding two sentences are a massive simplification of EU law, but roughly correct I think]. The danger is that the Court of Justice of the European Union, which, as Jeremy says, has little experience in copyright, will produce some strange ruling saying that World Programming do infringe and that SAS can stop them. Because of the way European law works, the UK judge is obliged to follow the European Court's ruling, whether he agrees with it or not, so we will have to wait and see what the European Court has to say.

    In patent cases you don't get the added level of the European Court to confuse things, so in that sense they're simpler. Whether they're a good thing or not, is another question.

  4. Jeje I think the intonation of my comment got a little bit misunderstood. I was in no way attacking you or similar. Sorry about that.

    My comment's motivation was to ask what I believe are the fundamental questions in the case, based on copyright theory (and a little rant about software patents I admit :P ).

    For me, WP is not infringing at all SAS software, based on the fact that copyright protects expressions and not ideas. The source code are not the same, so what WP did was an expression of a software that makes similar actions than the SAS software, but not the same.

    Thanks to Anynymous that clarify the process of the trial (that I honestly didn't know). Let's hope that the EU Supreme Court sees the fundamental question, based on copyright theory.

    I hope my point is clarified.

  5. Marshal -- thanks for your clarification!

  6. @Marshal - But WPS doesn't do something similar to SAS - as WPL themselves admit, it acts on identical language keywords with identical results:

    73. WPL has also always openly admitted that, with limited exceptions, the response of WPS to SAS scripts and data is intended to be identical to the response of the SAS Components and is in fact identical. The reason why this is so is that that is what customers for WPL insist on. Dr Quarendon explained to me that, even though it was always intended that the response would generally be identical, he had been surprised at the extent to which customers perceived any deviation at all from an identical response as constituting a bug in WPS.

    So I think it fair to say that an exception to usual copyright law is required to avoid infringement of copyright in the choice of language keywords, at least - the expression/idea distinction isn't sufficient.

  7. It seems that World Programming has copied the interface of all functions to support sas base code. As far as I know the interface of software is covered by the authors' rights. I am curious what the european court is going to say.
    Maxim Ivashkov


All comments must be moderated by a member of the IPKat team before they appear on the blog. Comments will not be allowed if the contravene the IPKat policy that readers' comments should not be obscene or defamatory; they should not consist of ad hominem attacks on members of the blog team or other comment-posters and they should make a constructive contribution to the discussion of the post on which they purport to comment.

It is also the IPKat policy that comments should not be made completely anonymously, and users should use a consistent name or pseudonym (which should not itself be defamatory or obscene, or that of another real person), either in the "identity" field, or at the beginning of the comment. Current practice is to, however, allow a limited number of comments that contravene this policy, provided that the comment has a high degree of relevance and the comment chain does not become too difficult to follow.

Learn more here: http://ipkitten.blogspot.com/p/want-to-complain.html

Powered by Blogger.