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 is Attacking Android Like Never Before, Qisda the Latest to Sign Patent Extortion Deal

    More blackmail and propaganda against Android, courtesy of the gentler, kinder, 'new' Microsoft



  2. Caution Needed When Microsoft Copywriters Flood the Media With Microsoft Propaganda

    Media actively subverted by Microsoft-sponsored agents of deception, whose goal is to change what people think of Microsoft and its software, even if by lying (they call it 'marketing')



  3. Gartner Staff That Worked for Microsoft and the Latest Nonsense from Gartner or 'Former' Staff

    Gartner waited until 2015 to declare FOSS fit for databases; another example spotted where Gartner staff comes from Microsoft or vice versa



  4. Links 27/4/2015: Debian 9 Named, Linux 4.1 Reaches RC

    Links for the day



  5. Microsoft is Interjecting Itself Into GNU/Linux and Free Software News, Even Events and Foundations

    Microsoft's entryism strategy is proving effective as Microsoft successfully embeds itself inside the idealogical competition, subverting the competition's overall message and diluting the competition's focus on Free software



  6. The Unethical Business of Selling Fear of Free/Libre Software Bugs (Black Duck, Sonatype, and Symantec)

    The spreading of fear of Free/Open Source software (FOSS) is now a growth industry, so proprietary opportunists are eager to capitalise on it, even if by distorting the truth



  7. Patients' Data at Risk as NHS Reinforces Its Microsoft/Accenture Stockholm Syndrome

    The worst privacy violator in the world and the firm behind LSE failures are pocketing as much as £0.35 billion of British taxpayers' money to acquire access to very sensitive data of British people



  8. Links 26/4/2015: Debian 8, OpenMandriva Lx 3 Alpha, Mageia 5 RC

    Links for the day



  9. Links 25/4/2015: Debian LTS Plans, Turing Phone Runs Linux

    Links for the day



  10. Who Kills Yahoo? It's Microsoft, Not Yahoo!

    The media should blame Microsoft, not Marissa Mayer, for what's going on (and has been going on for 7 years) at Yahoo!



  11. EPO Management is Trying Hard to Appease Its Critics While Pushing Forth Unitary Patent Agenda

    The European Patent Office and European Commission promote the agenda of large multinational corporations (at the expense or European citizens) and critics are being kept at bay



  12. Real Patent Reform Will Not Come From Biggest Backers of GNU/Linux, Not Even Google

    A look at the 'new' Google, the company which is hoarding patents (2,566 last year alone) instead of fighting for reform



  13. Microsoft's Troll Intellectual Ventures Loses Software Patents

    Intellectual Ventures is bluffing with software patents, but this time around it doesn't get its way



  14. Links 24/4/2015: Ubuntu and Variants in the News, Red Hat Developer Toolset 3.1

    Links for the day



  15. Links 23/4/2015: Ubuntu 15.04 is Out, Debian 8.0 Out Very Soon

    Links for the day



  16. Links 22/4/2015: Fedora 22 Beta, Atlassian Acquires BlueJimp

    Links for the day



  17. The Dying Debate Over Patent Scope (Including Software Patents) Replaced by 'Trolls' (But Not the Biggest Ones)

    The corporate media and Web sites or people who are funded by large corporations have essentially suppressed any debate about issues in the patent granting process, thereby guarding software patents and preventing criticism of large corporations' power grab



  18. The Patents Gold Rush Continues

    The morbid obsession with monopolising mere ideas still dominates the media, even increasingly in China



  19. 9 Millionth US Patent Tells a Story of Failure and USPTO Misconduct

    The USPTO, much like FISA (notorious court for surveillance/espionage authorisation), has become a rubber-stamping operation rather than a patents examination centre, as new evidence and old evidence serve to show



  20. HBO Helps Shift Debate Over Patents to 'Trolls' (Scale), Not Scope

    More of that awkward shifting of the patent debate towards small actors who are misusing patents, not large conglomerates like Apple and Microsoft which use patents to destroy competitors, crush startups, drive up prices, and so on



  21. Software Patents Are Still Menacing to Free Software: OIN Expands Scope, HEVC Adds to MPEG-LA Burden/Tax, Google and Facebook Give in on Patents

    A look at recent news about software patents and especially Free/libre software, which is inherently incompatible with them



  22. The Latest Developments Around Microsoft's Clever Attack on Android/Linux

    Microsoft's campaign of destruction, extortion, etc. against the most widely used Linux-powered operating system is revisited in light of new reports



  23. The Microsoft 'Community' is Maligning the Free Software Community

    Dishonest generalisations and baseless deductions portray the Free/Open Source software communities as a nasty place that leads to poverty and despair



  24. Googlebombing 'Microsoft Open Source' Even When Microsoft Shuts Down Its 'Open Source' Proxy

    A massive failure by the press to cover the most basic news, which is Microsoft putting an end to a supposedly 'Open Source' effort



  25. Links 22/4/2015: Calculate Linux 14.16, SparkyLinux 4.0 RC KDE

    Links for the day



  26. Links 21/4/2015: Project Photon, Ubuntu Touch Buzz

    Links for the day



  27. Embrace, Extend, Extinguish: How Microsoft Plans to Get Rid of Linux/Android

    Microsoft's sheer abuse against Android is laying bare for everyone to see now that Microsoft has paralysed Google's legal department with potential antitrust action in Europe



  28. Yahoo's Current CEO (Mayer, Formerly of Google) is Trying to End Yahoo! Status as Microsoft Proxy

    There are signs of relinquishing Microsoft's control over Yahoo! after Marissa Mayer worked to end the company's suicidal/abusive relationship with Steve Ballmer's Microsoft



  29. Repeating Microsoft's Lies Without Any Journalistic Assessment

    Poor fact-checking by relatively large media/news sites results in Microsoft's patently false claims being repeated uncritically



  30. Links 19/4/2015: New KaOS (2015.04), Manjaro Linux 0.8.13 Pre1

    Links for the day


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