A Gentleman's Code - The Copying of Software Code and Copyright

Computer programming, especially to the layman, can be both incredibly daunting and very confusing, as the languages, while logical, can be quite impenetrable. Since computers and computing have become near ubiquitous in modern society, so has programming become a part of our lives, even if not directly. Due to this, the value of code and programs can be substantial, especially for ones that are lucky enough to become standards, or just plain popular. Code and copyright rarely meet, but in the vein of the above, can code be construed as a copyright protected work, and if so, how much can you copy before you're infringing the rights attached to the code?

The case of IPC Global Pty Ltd v Pavetest Pty Ltd (No 3) dealt with equipment used to test asphalt and construction materials, built by IPC, which included custom programming to enable the user to test said materials and view results. This piece of software was installed on the users' computer. Two individuals, Con Sinadinos and Alan Feeley, worked at IPC (with the latter working as a consultant as a part of Alueta). The pair then resigned from IPC in 2012, establishing a competitor company, Pavetest, which launched competing testing products. Mr Feeley had in his possessions copies of IPC's programs on his computer that he took with him when leaving IPC. He then provided them for a programmer who made copies of the programs, leaving some parts of the Pavetest identical to that of IPC's programs. IPC then took Pavetest (and the individuals) for, among other claims, copyright infringement and breach of confidence.

Although Justice Moshinsky had a wide array of issues to decide, focus for the purposes of this article will remain on the question: "...did Pavetest infringe copyright in the UTS software by the creation of version 1 of the TestLab software? In particular, did version 1 of the TestLab software reproduce a substantial part of the UTS software?"

After discussing, at length, the companies and the development of the two competing pieces of software, the court focussed on the matter of copyright infringement.

Original code? Nah... (Source: xkcd)

The courts have struggled with defining what amounts to a 'substantial amount', as per section 14 of the Copyright Act 1968, which was discussed by the High Court of Australia in IceTV: "The case law does disclose that special difficulty has been encountered in considering the relationship between the phrase “a substantial part” in s 14(1) of the Act and the definition in s 10(1) of that species of “literary work” which is a “computer program”, being: “a set of statements or instructions to be used directly or indirectly in a computer in order to bring about a certain result.” (Emphasis added) The phrase emphasised suggests the importance of function, although this is usually encountered in patent and designs law, rather than in the “traditional” law of copyright respecting original literary works".

The courts have developed a test to determine whether a computer program has been infringed, there is ‘the need for some process of qualitative abstraction of the material features of the computer program in question’, and the copying of those features in the potentially infringing program (i.e. of a program calculates figures based on data, the program features of the calculation would be more important than the aesthetic function of the same under this context).

While the respondent conceded that the code is a copyright protected work, that substantial parts of the code were copied (but not to the degree of being a substantial part under section 14), and that this was done on behalf of Pavetest with the authorization of the individuals above, the court still had to consider whether the copying was indeed substantial under the law.

Due to the coder working for Pavetest to be able to rewrite the code so as the new version didn't infringe IPC's copyright, there clearly was a wide margin of expression in how the code could be implemented, while still having the same functionality. The writing of the code therefore included a degree of choice and judgment, making the expression of that functionality original under copyright. While some parts of the code would not be essential, Justice Moshinsky still upheld that they were original works equally to those parts that were essential. Finally, the amount of code, albeit a small amount (roughly 10,000 lines of code from about 250,000 lines), the copying was substantial, according to the judge, due to its necessity to achieve the desired functionality, rather than just simply through a quantitive measure. Pavetest had subsequently infringed the rights in the code.

The case is a very interesting one, and highlights a need for anyone copying others' code (which seems to be an industry standard, albeit only in parts of programming) to be cautious, and to rewrite anything that could be deemed to be a substantial copying. Software creation is incredibly complex and difficult, and one can appreciate the adoption of shortcuts, but the courts will clearly combat any abuses of others copyright works, even if it's just 'meaningless' code.

Source:  IP Whiteboard