EU Court Rules APIs, Programming Languages Not Copyrightable
itwbennett writes "The European Court of Justice ruled on Wednesday that the functionality of a computer program and the programming language it is written in cannot be protected by copyright. In its ruling on a case brought by SAS Institute against World Programming Limited (WPL), the court said that 'the purchaser of a license for a program is entitled, as a rule, to observe, study or test its functioning so as to determine the ideas and principles which underlie that program.'"
Interesting that computer "the format of data files" are not copyrightable!
"the Court holds that neither the functionality of a computer program nor the programming language and the format of data files used in a computer program in order to exploit certain of its functions constitute a form of expression. Accordingly, they do not enjoy copyright protection."
Very interesting.
...in which every book, song, movie, etc. is part of the syntax of the language, thus making them all uncopyrightable.
This seems strangely relevant to the Oracle vs. Google case that's going on right now over Android and its usage of Java APIs. Does anyone know how much of a coincidence this EU court ruling is, that it occurs in such close proximity to its US analogue?
Read what the decision actually says. The source code and object code which implement a system are covered by copyright, but the interfaces and algorithms implemented by that source code are not.
It's a fine distinction, but it essentially says that if you can reverse engineer the requirements of an API by observing it's behaviour, you are free to re-implement that functionality. i.e. You have to use so-called "clean-room" techniques, where the team that did the functional analysis of the APIs to write the specs have absolutely nothing else to do with the team that writes the implementation.
I do not fail; I succeed at finding out what does not work.
It's kind of always been like this though. Compatibility and data interchange have always been protected. Without that protection, people would be unable to move their data into other formats and legally, a vendor could kill a customer's access to their own data by discontinuing their software. Those things just can't be allowed.
What's "new" here is that it has been challenged in court and has been affirmed.
Now what interferes with some of that are software patents...
European court rules .... ... ... surprise surprise: not copyrightable
Sorry, this is law
A court is not "ruling" what is "law".
In europe we have laws that define what is "the case" what is "right" or what is "wrong"
I don't know the background, but going to court and asking for a rule if APIs are copyrightable is so plain stupid it is beyond believe. The law explicitly states: APIs or SQL data definition statements are
Seems half of the world does not understand how a court works. There is a law. There is a subject. And the judge decides if the subject is afflicted by the law.
Pretty simple.
Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
What, you think being clever will help you evade the law? If the people who drafted the law were not smart enough to close your loophole, you do not get to exploit it -- unless you are rich or a corporation.
Palm trees and 8
The biggest thing that I can think of is that the later versions of PSD formats are not freely licensed, which is why they are not in the gimp.
If I read this correctly it is possible for European software developers to use competitors file formats, which does not seem to be the case for American developers.
Work bio at MMWD
Interesting that computer "the format of data files" are not copyrightable!
"the Court holds that neither the functionality of a computer program nor the programming language and the format of data files used in a computer program in order to exploit certain of its functions constitute a form of expression. Accordingly, they do not enjoy copyright protection."
Very interesting.
The Format of the data file being non copyrightable is an excellent Idea. Most of the time the data in the file belongs to the user, and making the file format non-protected allows for data migration, whether by the user or a competitor's product. I've always maintained that user data belongs to the user.
The wording "the functionality of a computer program" may not be copyrighted pretty much says you can't copyright what your program does, but you may be able to copyright the actual code. This too allows migration, and prevents the "monopoly of ideas", and that might be what they wanted to protect.
My only worry is that wording "functionality of a computer program" is wide open to interpretation, and could be used to ban clones. But The court address this as follows:
In that context, the Court states that if a third party were to procure the part of the source code or object code relating to the programming language or to the format of data files used in a computer program, and if that party were to create, with the aid of that code, similar elements in its own computer program, that conduct would be liable to be prohibited by the author of the program. In the present case, it is apparent from the explanations of the national court that WPL did not have access to the source code of SAS Institute’s program and did not carry out any decompilation of the object code of that program. It was only by means of observing, studying and testing the behaviour of SAS Institute’s program that WPL reproduced the functionality of that program by using the same programming language and the same format of data files.
So if you simply write a program that produces the same output of some proprietary program, that is perfectly permissible. But If you had access to the proprietary source code and used any of that code you were liable for copyright infringement.
This pretty much sounds the death knell for applications that attempt to lock you in. They might not help you migrate, but they can't use copyright laws to prevent the development of competing products.
But rounded corners? Still protected?
Sig Battery depleted. Reverting to safe mode.
A grand total of 9 lines were copied, and as soon as they were identified they were removed from the Android sources. Furthermore, that RangeCheck function was so trivial that any Java beginner could have written it (this was stated in court testimony), so Oracle would get no substantive damages even if the jury denied the fair use defence for those 9 lines.
So yes, I have to agree with the parent that Oracle would lose in EU. They are likely to lose the copyright suit even in California.
Ok... here goes:
!1
Whew.. that was rough.
"You want to know how to help your kids? Leave them the fuck alone." -George Carlin
In the US, they can use patents. Consider the MICROS~1 extended filename patent for FAT.
Do you even lift?
These aren't the 'roids you're looking for.
It is not necessarily like this everywhere. Sure it's common sense, but the DMCA in the US forbids "reverse engineering" which can limit a lot of observing, studying, or testing of the program's execution. In this particular case, a program has been reverse engineered and emulated by another program and it did this without seeing or copying the original source code. Ie, a clean room implementation.
Actually, I should clarify. "Reverse engineering" means a lot of things, including disassembly. The court would forbid the disassembly here, however reverse engineering by duplicating observed functionality is ok.
There's a lot in between those two extremes though. Ie, you can reverse engineer by observing that the machine or operating systems is doing; what device registers it writes to, what library functions it it calling, what system calls it makes.
I'm not sure what the DMCA would have to do with it as PSD isn't access control software protecting a third parties copyrighted work.
There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
No, what the DMCA doesn't allow is the dissemination of tools derived from knowledge gained by reverse engineering an effective copyright control mechanism and there are a few significant exceptions like academic works and for interoperability.
There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
What's "new" here is that it has been challenged in court and has been affirmed.
Isn't this just the same as saying you can't copyright the "look and feel?" I'm pretty sure that went through the court system a quarter century ago.
but the DMCA in the US forbids "reverse engineering"
No, it does not. The DMCA prohibits "Circumvention of Technological Protection Measures", specifically circumvention of measures to access copyrighted materials, and circumvention of measures to copy copyrighted materials. It prohibits the act of circumvention as well as distribution of circumvention tools.
Reverse engineering is specifically *protected* in the DMCA, exempted from its prohibition, allowing you to circumvent access restrictions, if you need to achieve interoperability and the software is "lawfully obtained".
But rounded corners? Still protected?
It so happened that this morning when I woke up, I inspected the four corners of my mattress.
Holy Smithereens !!!
All the four corners of my mattress are round !
Am I gonna be sued now?
Muchas Gracias, Señor Edward Snowden !
WPS (the SAS-compatible software produced by WPL) is a pretty darned good SAS clone for a fraction of the cost. I'm positive that they thought suing was a good business decision, even if they knew they didn't have a leg to stand on. The impact of WPL's existence is going to hurt their bottom line much more than what they had to pay their legal team. I don't have anything in the fight (other than being a user of both), I'm just happy to see something that'll either make SAS drop the price, or that we've found a good replacement.
You zap the moderators with a wand of humor! The moderators resist!
To the Google-Oracle judge's ears. The jury have been specifically instructed to assume that APIs are copyrightable.
That said, Jonathan Schwartz' testimony on day 9 was seriously damaging to Oracle's case. He established a sound basis for the argument that Java APIs had been officially released for use without a licence, and that Sun had claimed a licence was only necessary to obtain the JCK to certify Java compatibility. STo the best of my knowledge, Sun didn't go bankrupt but were instead bought by Oracle, so those statements should still be in force. I'm thinking there might be opportunity for some serious class action lawsuits for breach of contract from Java developers against Oracle using that testimony if Oracle pursue the matter of copyrighting and demanding licences for the APIs. Not to mention massive flight of developers from use of the language and collapse of the Java business as developers decide not to pray that Oracle doesn't alter the deal further.
So there's reasonable hope that we might get a double win: a non-infringement ruling from the jury and a legal ruling against API copyrightability from the judge.
Laissez lire, et laissez danser; ces deux amusements ne feront jamais de mal au monde. - Voltaire
DMCA is an American law. Why would a court decision in EU affect it?
Software licenses or EULA cannot take away rights granted by law. This is in the EU.
Now in the US its a whole other can of worms.
It would be sufficient to legally download and install a single instance of the JRE to obtain a license according to the court. The defendant in the case didn't buy a license to the API either, just installed a single instance of SAS' program which he obtained legally.
Yes, almost like claiming that you have violated the copyrights by copying the words "to be" from the works of Shakespear.
But rounded corners? Still protected?
That has never been a copyright issue.
These "rounded corners" can be protected in very specific situations, notably design patents. You're probably referring to Apple vs Samsung and cases like that. When you create a design (outlook) for a device then you may patent that. This device can be anything: mobile phones, laptops, car, machinery, whatever. It means that while that patent is valid no-one is allowed to make a lookalike device.
So if you make a phone that looks exactly like an iPhone, Apple may prevent you from selling it based on their design patent. Now how same this "looks exactly like" should be, that's up to the courts, and there is definitely no clear borderline. And it's definitely more than just "rounded corners".
Another place where this "rounded corners" issue appears is in trademarks and branding. I'm sure the Coca Cola bottle design with it's narrow waist is well protected, by design patents and/or by trademarking. After all this design is very important for Coca Cola as even from a km distance many people will instantly recognise it's shape, and know the product it belongs to. Now you may be allowed to make a bottle with a narrow waist, but to get away with it you have to make it obviously different.
There's a whole 'other' market out there for mattresses that are...
'the purchaser of a license for a program is entitled, as a rule, to observe, study or test its functioning so as to determine the ideas and principles which underlie that program.'"
Google is not a purchaser of a license for JME, so this ruling is irrelevant to the jury for that case, sorry.
Sure, but I suppose the definition of 'purchaser' in this context needs to be clarified. After all if you download a 'free' piece of software, then are you 'buying' a piece of software for 0€? This is important, since Java can freely be downloaded in compiled or source form, with the latter under GPL.
Jumpstart the tartan drive.
Why would a European court rule on patentability of software when no software in Europe can be patented?
If this is true, then why is libdvdcss still not able to be incorporated in Linux distributions originating from the US?
It is a tool for circumventing access controls to copyrighted materials, thus prohibited. The reverse engineering is allowed, and access controls can be bypassed to perform that step, but you still can't distribute tools that perform the bypass.
And despite what the authoritarians said in their usual spiel of 'the innocent have nothing to fear'...
I agree with you there. While the DMCA definitely brings a chilling effect and I'd support its repeal, it is too often misrepresented in conversation. The actual text of the bill is quite readable, and some "geeky" things are actually exempted or protected.
Actually, it didn't. If you are referring to Apple vs. Microsoft in the 1980s, then that wasn't the reason Apple lost--although it is popular to say so.
Apple granted Microsoft a license to use certain elements of the UI, and Microsoft exploited this license by using such elements in their own GUI system.
Apple lost some of their claims because apparently the license was broad enough to cover most anything. Note that they did win some copyright claims.
-dZ.
Carol vs. Ghost
It would be legal under DMCA because bypassing whatever access controls are theoretically in PSD (AFAIK there aren't any, but let's hypothesize that there were) wouldn't be circumvention. DMCA defines circumvention in a certain way, an important part of that definition being "without the authority of the copyright holder," and the copyright holder it's talking about there, isn't Adobe; it's the copyright holder for whoever created the imagery that is in the PSD.
If PSDs contained DRM (false, but again, let's pretend they did), and you created a PSD containing your hand-drawn picture, you simply need to "authorize" the world to defeat the DRM, and then DMCA will allow anyone to defeat the PSD's DRM, anyone to create and traffic in tools that defeat the PSD's DRM, etc. These DRM-breaking acts wouldn't be exempted; they would simply not be covered in the first place. Authorization by the copyright holder removes DMCA.
Better yet, authorize everyone in the world except Adobe and their customers. Make Adobe use the interoperability clause in their defense when you're suing them over their infringement tool.
As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
It wouldn't. It ruled on copyrightability.
'the purchaser of a license for a program is entitled, as a rule, to observe, study or test its functioning so as to determine the ideas and principles which underlie that program.'"
Google is not a purchaser of a license for JME, so this ruling is irrelevant to the jury for that case, sorry.
Sure, but I suppose the definition of 'purchaser' in this context needs to be clarified. After all if you download a 'free' piece of software, then are you 'buying' a piece of software for 0€? This is important, since Java can freely be downloaded in compiled or source form, with the latter under GPL.
It seems like it should be legal, if I buy you a copy of TurboTax for your birthday and give it to you (effectively transferring the license to you) then YOU own the program even though you didn't pay for it. Maybe buying someone a computer with Windows already installed would be a better example or the software in a car's integrated navigation system.