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. Links 27/5/2016: Android for Raspberry Pi, Google Beats Oracle in Court

    Links for the day



  2. Warning: EPO Surveillance May Have Just Gotten Even More Intrusive

    BlueCoat, which the EPO uses to enable oppression inside its European premises, has just gotten even nastier and staff may be at risk



  3. Victim Card Ends up in Another Blunder for Battistelli and His Six Bodyguards

    Battistelli is wrecking what's left of the EPO's reputation (after decades it took the Office to earn it) as the media continues to scrutinise his appalling regime



  4. Italian Report About EPO Now Available in English

    An English translation of a TV program which earlier this month documented some of the glaring problems at the EPO



  5. The EPO is Doing Great, Says EPO-Connected 'News' Site

    IAM 'magazine', a longtime ally of the EPO, gives people the impression that all is fine and dandy at the EPO even though that's clearly not the case



  6. Microsoft Has Killed Nokia (and Its Own Mobile Ambitions), But Watch What it Does With Patents

    Microsoft announces many more layoffs, having already caused tremendous damage to the Finnish economy, and patents are left astray for Microsoft's favourite patent trolls to pick



  7. EPO Management Under Growing Stress From Croatian Law Enforcement Authorities, German Politicians, Italian Media

    Things are not as rosy as the relative calm may suggest, and in the coming weeks we expect some major events other than the protest at all EPO sites across Europe



  8. Microsoft, a Dead Company Walking, Resorts to Malware Tactics, Now Truly Indistinguishable From Crackers

    Microsoft is essentially taking over people's PCs and installing on them a large piece of malware, complete with keyloggers, against the will of these PCs' owners



  9. Links 26/5/2016: CentOS Linux 6.8, Ansible 2.1

    Links for the day



  10. The Latest EPO Victim Card (Played by Željko Topić) Should be Treated as Seriously as Those Bogus Claims of Violence by a Judge (Updatedx3)

    In its desperate pursuit of a narrative wherein the staff of the EPO is violent and aggressive the management of the EPO, renowned for institutional aggression, finds (or claims to have found) a little tampering with a bicycle



  11. Links 25/5/2016: Nginx 1.11, F1 2015 Coming to GNU/Linux Tomorrow

    Links for the day



  12. The Media Starts Informing the European Public About the Downsides of UPC While EPO Accelerates Its Lobbying for Ratification

    The EPO's shameless UPC promotion takes another step forward as the European press outlets (even television channels) begin to explore the secret deal that's negotiated by patent lawyers (with corporate clients) and patent offices, not the public or any public interest groups



  13. Some Details About How the EPO's President is Rumoured to be 'Buying' Votes and Why It's Grounds/Basis for “Immediate Dismissal”

    Some background information and a detailed explanation of the systemic financial dependency, created by Battistelli at the cost of €13 million or more, which prevents effective oversight of Battistelli



  14. How the Patent Lawyers' Microcosm Continues to Boost Software Patents Filth by Misdirecting Readers, Relying on Highly Selective Coverage

    Under the guise of reporting/analysis/advice the community of patent lawyers is effectively lobbying to make software patents popular and widely-accepted again, based on one single case which they wish to make 'the' precedent



  15. Documents Show Zagreb Police Department in Investigation of Vice-President of the European Patent Office

    Željko Topić's troubles in Croatia, where he faces many criminal charges, may soon become an extraordinary burden for the EPO, which distances itself from it all mostly by attacking staff that 'dares' to bring up the subject



  16. [ES] Interrumpiendo la Propagánda Distractante de Battistelli: los Empleados de la EPO Protestará de Nuevo en una Quincena

    La exágerada extravagancia (desperdicio de dinero) en la Ceremonia de Premiación al Inventor Europeo de la EPO tendrá que competir por atención de los medios con miles de empleados de la EPO (en todaslas sedes de la EPO) marchándo en las calles para protestar por los abusos de la EPO



  17. Windows and Microsoft's Other 'Burning Platforms'

    It's not just Windows for phones that's reaching minuscule market share levels but also Windows, but Microsoft is skilled at hiding this (cannibalising Windows using something people do not even want, then counting that cannibal, Vista 10)



  18. Links 24/5/2016: CRYENGINE Source Code is Out on GitHub, Jono Bacon Leaves GitHub

    Links for the day



  19. Links 23/5/2016: GNOME 3.22, Calculate Linux 15.17

    Links for the day



  20. 'Celebrity' Patent Trolls and the Elusive Battle Against Patent Trolls (or Eastern District of Texas Courts) Rather Than Software Patents

    Some of last week's more important reports, which serve to demonstrate how the system is attempting to tackle a side-effect of software patents rather than the patents themselves (their irrational scope)



  21. The Circus of Patent 'Reporting' (by Omission) on the Subject of Software Patents in the US and USPTO Bias

    look at some of the latest oddities in the US patent system and much of the reporting about software patenting (more or less monopolised by those who profit from it, not harmed by it)



  22. IP3 Demonstrates That Today's Patent Systems Devolve Into a Conglomerates' Game, Won't Protect the Mythical Small Inventor

    Multinational corporations bring together their shared interests and steer the increasingly-inseparable patent systems according to their needs and goals, but has anyone even noticed?



  23. Disrupting Battistelli's Distracting Propaganda: EPO Staff to Protest Again in About a Fortnight

    The overly extravagant (waste of money) EPO European Inventor Award will have to compete for media attention with thousands of EPO staff (in all EPO sites) marching in the streets to protest against the EPO's abuses



  24. Corrupting Democracy? Growing Frequency of Rumours That the EPO's President Battistelli is 'Buying' Votes of Small Member States

    Several sources suggest that rather than appease the Administrative Council by taking corrective action Battistelli and his notorious 'circle' now work hard to remove opposition from the Administrative Council, especially where this is easier a task to accomplish (politically or economically)



  25. [ES] Los Mitos de la EPO ‘Calidad’ de Patentes y de ‘Creación’ de Patentes: Basados en Ventas de Cafe y Trauma

    La carrera hacia el fondo, o la ridícula asumpción de Battistelli de que otorgar más y más patentenes más rápidamente (e.g. usando PACE) sería beneficióso a largo término, puede guíar al final colapse del valor de la EPO y la pérdida de su lárgamente ganada reputación a nivel mundial



  26. Links 22/5/2016: Systemd 230, Debian Installer Alpha 6

    Links for the day



  27. EPO Patent 'Quality' and 'Patent Creation' Myth: Capsule-Based Coffee Sales and Trauma

    The race to the bottom, or Battistelli's ludicrous assumption that granting more and more patents faster (e.g. using PACE) would be beneficial in the long run, may lead to the ultimate collapse of the EPO's value and demise of its long-earned reputation worldwide



  28. Guest Post: How Vista 10 Imposes Itself on Users of Windows

    A reader's experience being nagged by Microsoft, as documented and explained by this reader



  29. [ES] El Notorio Tirano de la EPO, Benoît Battistelli, Se Reune Con Otros Tiranos, Reportes de Que ‘Limpia’ el Consejo Administrativo

    El régimen de Battistelli, talvez la fuente de verguénza más grande, alegadamente está “cortejándo países pequeños/corruptos para asegurárse de que los delegados que votarón contra él serán remplazados”



  30. [ES] Comentadores Anónimos Debaten Si la EPO de Battistelli Puede Revocar las Pensiones de Empleados Que Se Atreveen — GASP — a Buscar Empleo Alternativo

    Una mirada a las causas de desesperación e imensa presión en la EPO, donde las pensiónes pueden ser cortadas como medio de represália y la gente puede ser negada empleo aún después de dejar la Oficina Europea de Patentes (EPO)


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