A California Jury Finds Copyright Infringement In an Interface (deepchip.com)
whoever57 writes: A California jury in one of the cases between Synopsys and Atoptech found copyright infringement in Atoptech's use of the "Primetime commands". These companies compete in the field of EDA ("Electronic Design Automation") software: software that is used by semiconductor companies to design ICs. The Primetime commands are merely an interface. Atoptech has their own implementation of the functionality that these commands [provide]. This can be seen as similar to the Oracle vs. Google lawsuit, in which an appeals court has found that providing a similar interface (via header files) can constitute copyright infringement. Naturally, there will be appeals in this case.
How many people believe in owning imaginary things.
Let's eliminate copyrights and patents here in the EU. Let the rest of the world fight and sue each other while we'll have freedom. The EU is smart enough to do something like this, unlike the US. The boost to EU economies will be enough to render the US even more irrelevant than it already is.
The whole idea that a jury can decide one way or another on a technical matter is pretty idiotic, and a misapplication of jury process as it enshrines decision making on the basis of ignorance.
In fact the whole legal system is back to front on this issue, since having specialist domain knowledge in an area often precludes you from serving on a jury in a relevant case. That's severely illogical.
Not even judges should have the power to make such decisions, because they are experts in law. not in technical topics. Making a good decision based on pro/con arguments presented by technical experts does not mean that the decision will be a good one, because a judge's second-hand understanding will always be superficial at best.
There are two good sources for informed decision making on technical topics: the professional institutions in a technical domain (such as IEEE, IEE/IET, BCS, ACM), and vocational academic bodies created for this purpose and barred from commercial influence. No human-based decision making can be perfect, but this would at least eliminate the ill-informed harm being done by judges and the general public working outside of their competency.
I wonder when someone is going to write a free-form written-language parser that will read in a carefully worded english description and spit out a header file. Then you can have your own description as a paragraph of poetry, which generates headers internally as part of the compilation process. This would make the whole problem of "illegal to have compatible interface" problem go away.
I'm a minority race. Save your vitriol for white people.
The script commands are eerily similar to Modelsim (now owned by Mentor Graphics)
Well... Socket/plug connections are patentable so I'm not bothered that APIs can be copyrighted.
That a copyrighted API lasts 5 times as long as the hardware patent bothers me.
(Legislator: "That's a good point we'll increase the length of the patents to match!
Me: "no no No!!!!")
A copyright infringement case is up before in East Texas alleging that parrots infringe on the human copyright of speech. The defense wanted to bring in specialists to discuss convergent evolution, but the judge said, "I don't see what a bunch of biologists has to do with copyright law."
If you beleive anything you might have learned in computer science surely it is that spending time to get the API right is the most important thing. populating the implementation of the sub sections defined by the API is the work you give to the C-students. You let the A-students come define the interface. The API is the most valuable part of the whole
Some drink at the fountain of knowledge. Others just gargle.
I patent hydrogen. Now it's your turn
But don't you dare to patent elementary particles! This would ruin the fun of patenting atoms, and I can't have my hydrogen.
And don't complain that you wanted to patent molecules before I had the idea of patenting atoms! That's not how the game's supposed to be played
there was an amicus brief signed by nearly a hundred software libre supporters: i read it, and they missed some really, really important very dangerous examples of how copyrighting interfaces destroys both proprietary and libre software *and hardware* business models.
* assembly instructions. assembly instructions *are* the "interface" between the hardware and the software. if assembly instructions themselves become copyrighted - a restricted form of of free speech if you will - then we are hopelessly screwed. software distributors - any software - presently being sold (or given away as libre binaries) WORLDWIDE - would need all of a sudden to contact the *PROCESSOR* designers to gain their permission in order to continue distribution of what was previously recognised as legal and covered under free speech laws.
* the GPL, LGPL, AGPL, and all other software licenses whether they be proprietary or libre, would need to be updated in order to explicitly grant permission to use the APIs that were previously recognised as "free speech" [code, under precedent, is recognised as being "speech"]. in cases where changing the license is *NOT POSSIBLE* such as with the GPLv2 on the linux kernel, the problem becomes extremely serious. for those people not familiar with the problem of the GPLv2 license on the linux kernel: it's GPLv2 not GPLv2+, and, given that there are several thousand individual copyright holders - each and every one of whom needs to be contacted and EXPLICITLY asked if they agree to the license change, you start to understand how flat-out impossible that is. especially given that some of those people will have died, or changed name, or will have been working for companies at the time and so on. so all of a sudden, given that it would not be possible to update the license, and given that the license would no longer cover APIs within the copyrighted work of the linux kernel, the burden is on the END-USER to request permission of the copyright-holders - all of them - for the requisite permission... and thus we are completely fucked because the exact same problem occurs, in contacting and tracking down thousands of people. remember: if you can't *get* permission, you must cease and desist from use of the software, otherwise you are acting in a criminal capacity.
* RPC mechanisms. (remote procedure calls). all and any RPC interfaces - by virtue of *being* interfaces - would become copyrighted. this would entirely defeat the extremely protracted and lengthy ground-breaking work by which the samba team members managed - over many years - to persuade the EU to compel microsoft to release their IDL files for interoperability purposes. if it now becomes necessary for each and every end-user as well as developer to contact microsoft and ask their permission to use their suddenly-copyrighted interfaces.... what do you think is going to happen?
* Silicon Chips - even just *buying* a chip would be problematic as its "interfaces" would be copyrighted. we have enough problems as it is with NDAs and being unable to get hold of datasheets: what do you think would happen if the sellers of ICs suddenly started enforcing license agreements and copyright enforcement agreements because the pins of the chip were considered to be "interfaces" and thus "controlled"? supply via distributors - especially smaller ones - would be sent into absolute chaos.
the most amazing thing is that i was actually contacted by someone who claimed that there were *supporters* in the software libre community of copyrighting of interfaces, because it would somehow strengthen the effects of the GPL. as such copyrighting is in effect an extremely dangerous restriction of "freedom of speech" (because it effectively terminates your free unrestricted right to "talk" in the "language" of the "interface"), any such perceived "benefits" are utterly smashed by the total chaos that the entire world - with its now heavy-dependence on software and hardware - would be thrown into.
i just... i'm completely blown away that there are intelligent people out there who do not understand how utterly insane the concept of API copyrighting really is.
And watch developers and publishers of free software get sued for patent infringement or copyright infringement for having reimplemented elements essential to interoperating with instances of the incumbent proprietary product or service operated by users who have not yet embraced free software. Though Replicant OS is free software, Google (developer of the Android Open Source Project that forms the basis of Replicant OS) still lost to Oracle.
So then lets spread the word. Juries are there to impose, to the best of their ability, justice, not law. They are the final safeguard against a legal system run amok. Yes, they are commonly informed that they must only consider the evidence and the law, but that's a lie - if that was all that was needed we could just appoint a few more judges and do away with the jury entirely. But jury nullification has a long history with many proud moments that helped make this country what it is. Also some dark ones, admittedly, but in those cases I really doubt the jury was pursuing justice anyway.
--- Most topics have many sides worth arguing, allow me to take one opposite you.
Remember way back when at the dawn of the PC era? When Tandy clean-room reversed engineered IBM's BIOS? That led directly, directly, to the PC as an open-platform. If the PC wasn't open, and therefore became the de-facto standard, then very arguably we would be stuck with crappy machines right now because innovation would have been dead. IBM would have had a strangle-hold on their implementation and if you didn't like their MicroBUS then you could build your own complete architecture. Copyrighting API's sounds good to non-technical people but people in the know know that it is the death-knell for advancement. The specific implementation deserves copyright but API's, and various implementations of them, are what foster competition and therefore better stuff, faster.
Shh.
Yes, an interface is covered by copyright, but it is also covered by the fair use and implied license doctrines. The fair use doctrine is (in the U.S.) a statutory right of the public to use a copyrighted work that is "fair". If you bought a movie on VHS (years ago), for example, you can convert it to DVD format for your own use without paying the publisher a second time. You don't get to redistribute the movie to others, because that would impair the publisher's ability to obtain payment in the market and is not "fair".
The implied license doctrine creates a legal (judicially-created) right and comes about from the way in which a work is distributed. The web code delivered to your browser to read this page is a good example. When you submit an HTTP query for this page, the server delivers a copy of my words and a copy of the web code your browser interprets to display them. By submitting a comment, I have given the world an implied license to have those words copied to your computer, and Slashdot has given an implied license for the web code to your browser.
The interface here is used to operate either a machine or a software package, which machine or package was purchased for a particular purpose. The interface must be used to operate it, and therefore the supplier gave an implied license to copy those parts of it needed to make it operable. Using the interface would probably also be considered fair, if the machine or package was not copied.
These are old issues in the legal system ... move along.
An interface is very akin to a language. It defines a set of rules by which two entities (two programs in this case) can communicate. It's the same with natural languages. Then ask yourself: Is it possible to copyright Esperanto? If so, what happens when someone copyrights English ?
Interfaces define the way we can express ourselves.
Write boring code, not shiny code!
Nothing at *all* like Lotus 1-2-3 vs. Borland, in the eighties....
mark
I dont know the specifics of this particular case but didn't they already decide that user interfaces aren't protected by copyright in the Lotus vs Borland case?
Or is there more to this case than just menu options and stuff?
Technically, juries are there only to decide on the facts. For instance, the jury can't find someone guilty of murder if the charges were for breaking and entering, the jury is there to decide that matter before them (guilty or not guilty of the stated charges). The judge is allowed to decide if evidence is admissible or not, and other issues of whether something is lawful or not. This is for *criminal* trials as per the sixth amendment to the constitution. The juries in nullification don't actually overturn a law but they do make the law moot if enough juries refuse to convict on a particular law.
Unfortunately there's not a lot of legal framework regarding civil trials in the constitution, and this particular case is a civil matter. Jury nullification in civil trials are very rare because the framework is different. For instance there's no constitutional requirement for a jury trial in civil cases.
In any event, intellectual property law is so byzantine that the average jury is baffled by it all. Whereas any set of professional judges well versed in intellectual property laws are biased.