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. New Optimism in the Age of Doubt Over Software Patents

    As the tide turns against software patents, even in their country of origin, their opponents come out of the woodwork to celebrate



  2. Links 28/7/2014: New Linux RC, Plasma 5 Live in Kubuntu

    Links for the day



  3. Links 27/7/2014: KDE 4.14 Beta 3, KDE 4.14 Beta 3 Released

    Links for the day



  4. Apple and Microsoft Are Proprietary Software Companies and the Media Should Stop Openwashing Them

    New examples where proprietary software giants are characterised as FOSS-embracing and FOSS-friendly by gullible or dishonest 'journalists'



  5. Bloomberg's Microsoft Propaganda

    Bloomberg delivers 'damage control' and PR ahead of the layoffs announcement; Microsoft uses Nokia to hide it and Bloomberg helps Microsoft by radically modifying headlines



  6. Frequency of Browser Back Doors in Microsoft Windows is Doubling

    The vulnerabilities which Microsoft tells the NSA about (before these are patched) are significantly growing in terms of their numbers



  7. FUD Entities Entering the FOSS World

    Symantec enters the AllSeen Alliance and Sonatype is once again trying to claim great insecurity in FOSS due to software licensing



  8. Groklaw Back in the Wake of ODF in the UK?





  9. Links 26/7/2014: New Wine, Chromebooks Strong Sales

    Links for the day



  10. Links 25/7/2014: GOG With GNU/Linux, Ubuntu 14.04.1 LTS

    Links for the day



  11. Links 24/7/2014: Oracle Linux 7; Fedora Delays

    Links for the day



  12. Valerie Strauss Explains Why Gates Foundation's Lobbying for 'Common Core' (Privatisation) is a Swindle That Makes Microsoft Richer

    Continued criticism of the Gates Foundation's lobbying and masquerading, with more journalists brave enough to highlight the corruption



  13. USPTO Officially Sets New Guidelines to Limit Scope of Software Patents in the United States

    Even patent lawyers finally acknowledge that the incentive to file software patent applications has been reduced, as the scope of patents on software has been noticeably narrowed and they are harder to acquire, let alone enforce in a courtroom



  14. UK Government Adopts OpenDocument Format (ODF) and Microsoft Already Attacks the Government Over It, Showing Absolutely No Commitment to Open Standards

    Only "Microsoft as the standard" is the 'standard' Microsoft is willing to accept, as its response to the Cabinet Office's judgment reveals



  15. Microsoft Layoffs of 2014

    Another quick look at Microsoft's horrible state of affairs and why it has virtually nothing to do with Nokia



  16. Links 22/7/2014: Linux 3.16 RC 6, New UberStudent

    Links for the day



  17. Links 20/7/2014: Jolla in India, Mega Censored in Italy

    Links for the day



  18. Longtime Mono Booster Joins Microsoft-linked Xamarin

    Jo Shields almost joins Microsoft, settling instead for its proxy, Xamarin



  19. Linux Foundation Welcomes Patent Aggressor Red Bend Software

    The Linux Foundation's AllSeen Alliance welcomes as a member a company that uses software patents to sue Free/Open Source software



  20. Matt Levy From Patent Progress (and CCIA) Does Not Really Want Patent Progress

    Matthew ('Matt') Levy moved into a foe of patent progress last year, but he still runs a site calls Patent Progress, in which he diverts all attention to patent trolls (as large corporations such as Microsoft like to do)



  21. Attacking FOSS by Ignoring/Overlooking Issues With Proprietary Software

    The biasing strategy which continues to be used to demonise Free/Open Source software (FOSS) along with some new examples



  22. Links 19/7/2014: CRUX 3.1 is Out, CyanogenMod Competes With Google Now

    Links for the day



  23. Microsoft's Massive Layoffs Go Far Beyond Nokia; Nokia's Android Phones Axed by Microsoft's Elop

    Microsoft's rapid demise and permanent exit from Nokia's last remaining Linux platform (after Microsoft had killed two more)



  24. Patents on Software Already Being Invalidated in Courts Owing to SCOTUS Ruling on 'Abstract' Patents

    The Federal Circuit Appeals Court has just "invalidated a software patent for being overly abstract," says a patents expert



  25. OpenSUSE 'Community' is Crumbling, AttachMSFT Killed SUSE's Potential (Except as Microsoft Tax)

    Not much too see in the land of SUSE and Attachmate, or formerly the company known as Novell



  26. Links 18/7/2014: Slackware Turns 21, Spotify Switches to Ubuntu

    Links for the day



  27. Links 16/7/2014: Manjaro 0.8.10 Third Update, SIA Migrates to Red Hat

    Links for the day



  28. Microsoft's Latest Round of Massive/Bulk/Large-scale Layoffs

    Microsoft boosters are preparing 'damage control' pieces ahead of massive layoffs at Microsoft



  29. Secrecy Allows British Government to be Manipulated by Microsoft for Spyware Behind Closed Doors

    Dependence on malicious software from NSA ally Microsoft is highly dependent, at least in Britain, on government secrecy and vain refusal to comply with Freedom of Information (FOI) requests



  30. Software Patent Applications Already Being Rejected in the US Owing to SCOTUS Ruling, Some Patent Lawyers Are Fuming

    Good news on the software patents front as the USPTO starts rejecting software patent applications, based on patent lawyers' words


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