EditorsAbout the SiteComes vs. MicrosoftUsing This Web SiteSite ArchivesCredibility IndexOOXMLOpenDocumentPatentsNovellNews DigestSite NewsRSS

05.10.14

The World’s Craziest Patent System (USPTO) Now a Serious Threat to Free Software, But So is Copyright

Posted in Intellectual Monopoly, Patents at 4:35 am by Dr. Roy Schestowitz

Privatising everything, even vague ideas

Author

Summary: Patents on everything that’s conceivable are being granted and even APIs are being monopolised, due to overzealous copyright lawyers

YESTERDAY we wrote about Amazon‘s latest crazy patent, using it as an example of how crazy the USPTO has gone. It’s not even an examination centre, it is approving almost everything that comes through, rendering it just a rubber-stamping pipeline like ISO. Ars Technica says that “Amazon’s latest patent is sillier than the peanut butter sandwich patent”, or to put it another way: “Thought the peanut butter sandwich patent was a joke? That one doesn’t even register a chuckle compared to a patent recently granted to Amazon.com. The e-commerce giant now can claim a legal monopoly on the process of photographing people and things against a white backdrop.”

The USPTO is starting to look more like a hoax. Sun employees, whose patents got passed to Oracle, said they had joked about how silly a patent they could get past the USPTO. They even competed over how ridiculous a patent they could slide through. And watch what Oracle is doing with such patents right now. Copyright may be essential for copyleft licences such as the GPL, but what happens when patent attacks on Android are coupled with copyright on APIs? To quote the EFF: “We’re still digesting today’s lengthy decision in the Oracle v. Google appeal, but we’re disappointed—and worried. The heart of the appeal was whether Oracle can claim a copyright on Java APIs and, if so, whether Google infringed that copyright. According to the Federal Circuit today, the answer to both questions was a qualified yes—with the qualification being that Google may have a fair use defense.

“Quick background: When it implemented the Android OS, Google wrote its own version of Java. But in order to allow developers to write their own programs for Android, Google relied on Java APIs. Application Programming Interfaces are, generally speaking, specifications that allow programs to communicate with each other. So when you type a letter in a word processor, and hit the print command, you are using an API that lets the word processor talk to the printer driver, even though they were written by different people.”

Copyright, patents and even trademarks in the US need revisiting. There are many examples where each of those three get misused to censor, to crush competition, to impede innovation, and ban sharing where it’s clearly beneficial, collectively. The waning dominance of the West may, in some awkward way, one day weaken all those artificial barriers that ACTA, SOPA, TPP etc. are trying to prop up. Right now it’s too damn clear that progress is not the goal; protectionism for the top 1% of wealth holder is the goal.

Share this post: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • Reddit
  • co.mments
  • DZone
  • email
  • Google Bookmarks
  • LinkedIn
  • NewsVine
  • Print
  • Technorati
  • TwitThis
  • Facebook

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

2 Comments

  1. NotZed said,

    May 10, 2014 at 8:31 pm

    Gravatar

    So I read through the google/oracle decision and I see nothing in there that would affect free software developers.

    In this specific case all the code in question is available under GNU GPL (version 2 + classpath exception), meaning that at least in part this is a GNU GPL violation by google – which oracle is defending. i.e. if google used the GNU GNPLv2+classpath exception version of the openjdk, Oracle could not sue them.

    Secondly the interface was simply copied – akin to taking a good chunk of the header files in /usr/include and stripping out the comments and license headers (and if you don’t think that is copyrighted material, why do they all have copyright headers?). This was not a clean-room re-implementation.

    And lastly although the question of fair use was not decided it was discussed. The defence of using it for interoperability has some pretty glaring problems as google clearly did not create an interoperable implementation – and have said as much. The intention was instead to to leverage the language’s familiarity with external developers for the commercial benefit of google. Basically google pulled an embrace/extend/extinguish move, and somehow gets lauded for it by those who should be most aware of them.

    But the most alarming revelation comes in the last 3 pages. Google was apparently arguing that copyrights shouldn’t even apply to computer software and it should only be covered by patents. Quite rightly the court rejected this wholesale but this line of thinking is about as ‘evil’ as you can imagine. It would essentially end all commercial software development by individuals and SMBs too small to employ eye-pee lawyers, and greatly affect non-commercial software development – free software or otherwise.

    I recommend reading it, it’s not that long and much of it is well written and shows a good understanding of the technical issues involved and explains each decision clearly and succinctly.

    The basic gist seems to be that google could have created another programming language runtime (possibly with the same language syntax) to perform the same function, but instead intentionally created a direct copy of an existing one. This is the source of the copyright infringement.

    It also seems to hint that the fair use defence of ‘interoperability’ should fall flat because google explicitly stated android was intended not to be java. They were simply utilising it’s popularity and familiarity and the existing tools in order to accelerate their own commercial interests.

    Dr. Roy Schestowitz Reply:

    I don’t share these views and in a post later today I will explain why. For now, here’s another interpretation:

    Appeals Court Doesn’t Understand The Difference Between Software And An API; Declares APIs Copyrightable

    [...]

    We sort of expected this to happen after the appeals court for the Federal Circuit (CAFC) held its oral arguments back in December, but CAFC has now spit at basic common sense and has declared that you can copyright an API. As we noted, back when Judge William Alsup (who learned to code Java to better understand the issues in the case) ruled that APIs were not subject to copyright protection, his ruling was somewhat unique in that it was clearly directed as much at an appeals court panel who would be hearing the appeal as it was at the parties. Alsup rightly suspected that the judges on the appeal wouldn’t actually understand the issues as well as he did, and tried to break it down clearly for them. Unfortunately, the three judge CAFC panel did not pay attention. The ruling is so bad that legal scholars are suggesting that it may be as bad as the horrific ruling in the Garcia case.

    [...]

    As for the ruling itself… well… it’s bad. The court seems to not understand what an API is, confusing it with software functionality. It also appears to misread Judge Alsup’s ruling, thinking that he’s mistakenly using a fair use analysis to determine whether or not something is copyrightable. But that was not the basis of Judge Alsup’s ruling. He very specifically noted that the “command structure is a system or method of operation under Section 102(b) of the Copyright Act and, therefore, cannot be copyrighted.” The CAFC panel doesn’t seem to understand this at all.

    [...]

    It seems fairly clear that the CAFC judges don’t understand the difference between an API and software. And thus they make a decision that makes no sense. There is no distinction recognized when it comes to the functionality of an API and how it’s entirely different than the purpose of the software itself. This is especially clear towards the end, in which the CAFC ruling misrepresents some discussions on whether certain functionality is best protected by patents or copyright. But the problem is that they misinterpret statements people are making about APIs, thinking that those statements were made about software as a whole. This is just a flat-out fundamental misunderstanding of what an API is, assuming that it’s just software.

    [...]

    Note that “[software]” thrown in before interfaces? Google is talking about whether APIs — “application programming interfaces” — are copyrightable. Not whether or not software is copyrightable. And yet the CAFC doesn’t even seem to realize this. Ridiculously, CAFC then uses its own misunderstanding and misquote, and points to some of the (many) arguments where people argue that patents are inappropriate for software to dismiss Google’s argument about APIs. It honestly doesn’t realize that it’s comparing two totally different things. What lots of people agree on: software shouldn’t be patentable and APIs shouldn’t be copyrightable, but software can be copyrightable and API functionality may be patentable. But by confusing APIs and software, CAFC totally misreads both arguments.

What Else is New


  1. Microsoft Windows Unsafe at Any Speed, by Design

    More timely reminders that Windows is simply not designed to be secure, irrespective of version, status of patching, etc.



  2. After Moonlight Dies and Even Microsoft Abandons Silverlight, the Abusive Monopolist Keeps Pushing for Other Microsoft Lock-in, Injecting OOXML Traps Into Free Software (Moodle)

    Despite a long history of Microsoft formats being proven guarantee of digital obsolescence, Moodle allows itself to become Microsoft prey and a Trojan horse for OOXML in classrooms (for children)



  3. Links 4/7/2015: Mostly (Geo)Political Catchup

    Links for the day



  4. Links 3/7/2015: KDE Applications 15.04.3, Ubuntu-Flavored Compute Stick

    Links for the day



  5. Patent Lawyers and Their Firms, Still Desperate to Protect the Status Quo, Manipulate the Media

    Patent lawyers are besieged by gradual tightening of patent scope and recklessly fight back (e.g. by saturating the media) to secure their revenue sources, derived from (and at the expense of) actual scientists and true market producers



  6. Amid Controversy, Political Scrutiny and Increased Media Pressure Željko Topić and Benoît Battistelli Allegedly Cancel Today's Trip to Zagreb (Croatia) Where Topić Faces Many Criminal Charges

    The Croatian press comments on the recent declaration from the Council of Europe and Topić's not-so-sterling status in his home country, where he is wanted for alleged crimes



  7. Microsoft Gradually Embraces, Extends, Extinguishes Linux Foundation as a Foundation of GNU/Linux

    By liaising with (or hijacking) existing members of the Linux Foundation, as well as by paying the Linux Foundation, Microsoft turns the Linux Foundation into somewhat of a Windows advocacy group



  8. Microsoft India Still Lobbies and Lies About Free Software in Order to Knock Down Policy That Favours Free Software

    Microsoft continues to bully Indian politicians who merely 'dare' to prefer software that India can modify, maintain, extend, audit, etc.



  9. Patent Lawyers and Corporate Media Nervous About New Patents Barrier/Reality (Less Patents on Software and Business Methods)

    The rich and the powerful, as well as their lawyers (whose job is to protect their money and power by means of government-enforced monopoly), carry on whining after the Alice case, in which many abstract patents were essentially ruled -- by extension -- invalid



  10. Translation of Pierre-Yves Le Borgn' Speech Against EPO Management and New Parliamentarian Interventions

    More political fire targeting the EPO's management, adding up to over 100 parliamentarians by now



  11. Links 2/7/2015: KDE Plasma 5.3.2, antiX 15

    Links for the day



  12. Links 1/7/2015: OpenDaylight Lithium, OpenMandriva Lx 2014.2

    Links for the day



  13. Munich Press, Münchner Merkur, Slams the Munich-based EPO

    Pressure on Benoît Battistelli to leave (or be fired) grows as the cronies whom he filled his office with have become a huge public embarrassment to the decades-old European Patent Office



  14. The Shameless Campaign to Paint/Portray Free Software as Inherently Insecure, Using Brands, Logos, and Excessive, Selective Press Coverage

    Some more FUD from firms such as Sonatype, which hope to make money by making people scared of Free/libre software



  15. National Insecurity and Blackmail, Courtesy of Microsoft

    British members of parliament (MPs) outsourced their communication to the number one PRISM company and they are paying the price for it; The US Navy's systems continue to be unbelievably insecure (Windows XP), despite access to the world's biggest nuclear arsenal



  16. Microsoft Keeps Shrinking

    As the era of shrink-wrapped software comes to an end so does Microsoft, whose effort to become a 'cloud' company with online operations has been miserable at best



  17. They 'R' Coming: More Microsoft Money for the Linux Foundation

    The problem with having Microsoft in a Linux Foundation initiative, the R Consortium



  18. Speculations About the EPO's Possible Role in DDOS Attacks

    Readers' views on who might be behind the attacks on this site amid confirmation that it's on the 'targets' list of the EPO



  19. Links 30/6/2015: Linux Mint 17.2, OpenMandriva

    Links for the day



  20. Techrights Confirmed as a Target of EPO Surveillance, With Help From Control Risks Group (CRG)

    Unveiling the cloak of secrecy from long-term surveillance by the European Patent Office (EPO) and a London-based mercenary it hired, bypassing the law



  21. Google's Fight to Keep APIs Free is Lost, Let's Hope Google Continues Fighting

    SCOTUS refuses to rule that APIs cannot be considered copyright-'protected', despite common sense and despite Java (which the case is about) being Free/libre software



  22. Patent Trolls in the Post-Alice World

    A round-up of news about patent trolls in the United States, some of whom are are doing well and some of them not as well



  23. DDOS Attacks Against Techrights

    Information about some of the most recent DDOS attacks against this Web site and the steps to be taken next



  24. The Patent System Not What it Used to be, Large Corporations and Patent Lawyers the Principal Beneficiaries

    A look at some recent patent stories and what can be deduced from them, based on statistics and trends



  25. After Intervention by the Council of Europe Comes a Detailed Summary of the Situation in the European Patent Office (EPO)





  26. IRC Proceedings: May 31st - June 27th, 2015

    Many IRC logs



  27. Links 28/6/2015: Manjaro Linux Cinnamon 0.8.13, VectorLinux 7.1

    Links for the day



  28. Williamson v. Citrix Online (at CAFC) Reinforces Alice v. CLS Bank (at SCOTUS) in Crushing Software Patents

    More patent news from the United States, again serving to indicate that software patents over there are getting weak (harder to defend in court or acquire from the patent office)



  29. Proskauer Rose LLP is Cherry-Picking Cases to Make Software Patents Seem Eligible Despite Alice v. CLS Bank

    Naming and shaming those who are trying to reshape the consensus despite a rather consistent pattern of software patents being rejected



  30. IAM Biased: How IAM 'Magazine' Glorifies Patent Stockpiling

    A look at the bias of one of the most overzealous sites for and by patent lawyers


CoPilotCo

RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

CoPilotCo

Recent Posts