Gemini version available ♊︎

Who Will Merpel be in 2020? (Now Defending Battistelli’s Attacks on EPO Judges and Serious Violations of the EPC)

Posted in Deception, Europe, Patents at 6:29 am by Dr. Roy Schestowitz

Maximalists (patent, copyright, trademark etc.) and litigation zealots have taken over IP Kat, which has sadly become merely an amplifier of EPO lies (deliberate falsehoods) and propaganda

The old IP Kat
The ‘old’ IP Kat (several more key people have left since)

Summary: The tone of IP Kat has changed to the point where it’s very much part of Team Campinos/Battistelli — i.e. the very opposite of what it was prior to key departures and sanctions from the European Patent Office (EPO)

THE EPO is not an ordinary institution. I probably ought to know this, having covered it very closely since 2014 (I had covered it before that, albeit not as closely and without inside informants). Today’s EPO is bribing and threatening publishers (they tried this on us several times). Sheer corruption, sheer abuse, but these people enjoy immunity…

I’ve often read about practices such as these in Russia or sometimes China as well. Is Europe prone to tolerating the same? The corrupt people who have seized control of the Office are effectively killing every form of journalism (about patents) that dares criticise or even speak about EPO abuses. I spoke to some reporters and they told me stories. Giving the full details would likely reveal identities of publishers and therefore writers too.

“I’ve often read about practices such as these in Russia or sometimes China as well. Is Europe prone to tolerating the same?”The EPO may in fact be Europe’s most corrupt institution. This very much matters because it’s also Europe’s second-largest one. Why don’t more publications speak about it? Well, being Europe’s second-largest institution means a lot of power, connections and even budget (‘slush funds’). Therein lies a very big problem. Publications that used to speak of EPO issues refrain from saying anything at all. It’s not necessarily the case that they all paint a rosy picture; but when there’s a scandal they pretend not to see, they perpetuate the idea that it does not exist. I’ve witnessed similar things when Wikileaks published some bombshell reports/leaks, whereupon there were even (as recently as this month) reports about reporters who resign, having been denied — by the publisher — the permission to cover the story. 4 years ago I saw that at the BBC. They try to keep as ‘marginal’ as possible particular stories/developments, suppressing ‘inconvenient’ facts to guard an incomplete and misleading narrative. JUVE totally embraced that. Yes, JUVE… which used to provide splendid coverage back in the days.

Several years ago people reported to us that IP Kat had begun actively deleting comments — even entire threads — critical of EPO management. Moderators changed. They sought to police the tone, narrative, discussion etc. It was rather astounding given the low standards applied; totally polite comments were deleted as well (we made copies — where possible — before these deletions). Since then IP Kat has been pushing UPC lies every month or so. With AstraZeneca and Bristows in key positions it’s hardly surprising (consider their corporate agenda), which means that IP Kat has become ‘litigation industry’ blog. Also remember Stephen Jones; previously in charge, not just at CIPA, an integral part of Team UPC, he did photo ops with Battistelli. It was as if he chose to make photographic evidence of a complete coup.

“Several years ago people reported to us that IP Kat had begun actively deleting comments — even entire threads — critical of EPO management.”We could go on and on talking about the pro-software patents bias of IP Kat; it hardly deals with 35 U.S.C. § 101 at the U.S. Patent and Trademark Office (USPTO) and a lot of the time it uses misleading propaganda terms that are technically and legally unsound. So what is this blog even useful for? When it comes to patents, it’s not scholarly at all (the scholars have mostly left), it’s a litigation lobby. Ask around the EPO (examiners); they might say the same. The difference is felt. Speak to former ‘Kats’ (if they dare speak out); they too might say the same.

This morning I saw this latest tidbit, preceded by the following introductory paragraph: “It has been a busy year for the Enlarged Board of Appeal. 2019 has seen four referrals from the Boards of Appeal and one decision. The more controversial of this year’s referrals (namely Pepper and Computer simulated inventions) have attracted a large number of third party comments. Other referrals (i.e. “Double-patenting”) seem to have dropped off the radar of even the EBA. Readers may therefore be forgiven for losing track.”

This is far from a balanced overview; we’ll get to that in a moment. Rose Hughes with her typically dismissive remarks about software patents critics (we covered her stance on software patents in Europe in the past; she’s no coder) isn’t quite surprising to us. We’ve become accustomed to it by now. Her outline does not mention at all those who oppose software patents, instead giving the impression that software companies are in favour (citing monopolies and law firms); they try to ‘vanish’ actual coders, letting legal departments of multinationals claim to speak ‘for’ them. She also mentions Campinos with his violation of the European Patent Convention (EPC) — the principle of separation of powers — but seems to see nothing wrong with that!

“Remember that Merpel is not an actual person but a pseudonym for several (they told me so themselves).”For those who wish to hear from critics of software patents (people who actually do software) there’s this talk tomorrow by Benjamin Henrion at CCC/36C3 in Hamburg (Germany). They’ve “Moved the Unitary Software Patents discussion to Sunday at 6PM”, he noted. It was supposed to be today. “Unitary Software Patents discussion moved to 6PM on Sunday,” he added later. We know that some of our readers will be there (but won’t name them).

Going back to IP Kat, notice what Hughes added in: “[Merpel: Whilst relocation of the Boards of Appeal was undoubtedly an unpopular move, was it really necessary to expend EBA time on such a question?]“

Remember that Merpel is not an actual person but a pseudonym for several (they told me so themselves). It wasn’t an “unpopular” move but an illegal one. But now they’re changing history and retroactively justifying the abuse. Here’s the full text about software patents and Haar:

Computer simulated inventions (G 1/19)

The patentability of software (which takes the form of computer “simulated” or “implemented” inventions under the EPO’s problem and solution approach) is a controversial topic. In the first of a couple of referrals in February, a Board of Appeal (3.5.07) sought clarity from the EBA on the patentability of computer-implemented simulations (T 0489/14): The patentability of computer simulated methods – another referral to the Enlarged Board of Appeal. The referral was followed by comments from the EPO president: Comments from the EPO President on the patentability of computer-implemented simulations (G 1/19). The President appears broadly in favour of the patentability of computer-simulated inventions. The referral particularly relates to claims having both a technical and non-technical character. The referral asks whether the non-technical features of such an invention and/or the technical purpose of the invention can be considered in the assessment of inventive step.

G 1/19 has received a large number of amicus curiae from third parties. A number of the amicus curiae are from large software companies, who are unsurprisingly in favour of the patentability of this kind of software invention (e.g. Siemens, Philips and IBM). CIPA and EPI have also all given their view, which are in favour of including the technical purpose of a claim in the assessment of inventive step.

Clarity in appeal and is Munich in Haar? (G 2/19)

The second referral in February related to appeals procedure. The referral sought an answer to whether a clarity objection can be discussed in appeal oral proceedings. Clarity can not be raised in opposition (accept in response to a Patentee’s post-grant amendment). A clarity objection may be raised in examination by a third party (Article 115 EPC). In the case in question (T 831/17), in order to pursue a clarity objection after grant, a third party filed an appeal against the decision to grant the patent (EP2378735). The appeal was rejected as inadmissible. However, the Board of Appeal referred the question to the EBA of whether the appellant still has the right to oral proceedings even when an appeal is deemed inadmissible.

In response to the referral, the EBA decided that following an inadmissible appeal, a third party is not entitled to oral proceedings in order to discuss the third party’s clarity objections. The EBA therefore closed the door on the possibility that clarity may be discussed as a ground of opposition in appeal proceedings: Enlarged Board of Appeal releases full reasoning in G2/19. The opposition period for the granted patent has now expired.

The final question in the referral raised a collective sigh from many in the patent community. The question related to whether Haar could really be said to be situated in Munich: Where is Haar and how did it get there? Observations on Geography while Waiting for G2/19. In particular, did the location of oral proceedings in Haar contravene a party’s right to be heard? Rather unsurprisingly, the EBA decided that Haar was in Munich. [Merpel: Whilst relocation of the Boards of Appeal was undoubtedly an unpopular move, was it really necessary to expend EBA time on such a question?]

Wow, what a truly terrible remark, attributed to “Merpel”. In past years Merpel held exactly the opposite position, but the whisperer handle which is “Merpel” is now used to justify what happened to G 2/19. Sorry, “Merpel”, but now you’re contradicting yourself, you’re not even consistent!

Now that the blog’s founder has left — and later those whom he left in charge (entrusted so to speak) — who’s even in charge? We have a rough idea as it’s at the top of all pages in the blog (names but not employers). They try to give the impression that the blog is run by a vast and diverse team.

“Now that the blog’s founder has left — and later those whom he left in charge (entrusted so to speak) — who’s even in charge? We have a rough idea as it’s at the top of all pages in the blog (names but not employers).”Read again that last paragraph (above); to them, it’s almost as if it’s a waste of time to check whether the law is being broken (which isn’t hard to see, but they make it a political question and thwart it altogether). Remember that this decision was released not in English (intentional). As we explained and showed at the time, they googlebombed in every way possible to distract from what was happening. Read the first (and as of now only) comment: “Regarding G4/19, the written decision was handed down on December 20, 10 months after the hearing.”

By that stage will anyone care/notice/bother?

Days ago we also saw Sterne, Kessler, Goldstein & Fox P.L.L.C. wrongly assuming that the EPO respects the EPC (it does not, it's a rubber-stamping machine) when writing about bioinformatics patent claims. To quote:

This article discusses challenges in prosecuting bioinformatics patent applications before the European Patent Office (EPO). The EPO determines the subject-matter eligibility of bioinformatics patent applications under Articles 52 and 56 of the European Patent Convention. Article 52 governs what is considered patent eligible subject matter.[1] Article 56 governs whether a bioinformatics patent claim involves an inventive step.[2] While Article 56 is not directly related to eligible subject matter determinations, the EPO uses this Article to screen bioinformatics patent application for eligible subject matter issues. Four points of concern and consideration related to the subject-matter eligibility of bioinformatics patent applications in Europe are discussed below.

First, under Article 52, the EPO may incorrectly reject a bioinformatics patent claim as being directed to (1) discoveries, scientific theories, and mathematical methods, or (2) schemes, rules and methods for performing mental acts, playing games or doing business, and programs for computers.[3] One way patent applicants can argue that a bioinformatics patent claim is not directed to either category is to explicitly recite a computer or physical step (e.g., tying bioinformatics method claim to specific technical equipment) to support technical character in the claim.

Second, under Article 56, the EPO may overlook a technical purpose of a bioinformatics patent claim. In response, patent applicants can argue that the technical purpose is the biological rationale for performing the bioinformatics analysis. For example, the biological rationale can be related to diagnosing a disease or assessing a particular physical property. Patent applicants should be cognizant that issues may arise when arguing that the features fundamental to solving the biological problem (e.g., aligning gene sequences) are the biological rationale. This is because such features may not be considered by the EPO to sufficiently provide the requisite biological rationale.

Articles 52 and 56 of the European Patent Convention won’t matter to today’s EPO management; because it routinely violates many other articles and it gloats about that mass violation having no consequences!

Last but not least, Kluwer Patent Blog is the latest of several to speak of “inventive step” (the EPO’s bizarre terminology, which includes “technical problem”) in the context of “hope” — as pertaining to T/83. Arianna Bartolini, Charlotte Richards-Taylor and Thorsten Bausch (published by the last of the bunch) say this:

As was rightly noted on this blog, the skilled person’s “hope” of solving the objective technical problem using the means that led to the (later claimed) invention, has disappeared from the Guidelines for Examination. What we are left with is the (perhaps) more objective “expectation of some improvement or advantage (see T/83)”. Interestingly, this expectation of “some improvement or advantage” no longer appears to be so closely linked to the objective technical problem than the language previously used in the Guidelines. Whether this will in the future give rise to more problems for applicants or patentees remains to be seen. In any case, it may be a good point in time to remind ourselves that even recognizing a problem and its roots can (at least sometimes) be an invention of itself.



Decision T 2321/15 thus came to the interesting conclusion that the discovery of a yet unrecognized problem may give rise to patentable subject-matter in spite of the fact that the claimed solution may be, once the root of a problem has been identified, retrospectively trivial and in itself obvious. As such, T 2321/15 is not the first decision of its kind, but rather follows a long tradition starting with T 2/83 itself, which was confirmed in T 764/12. It may thus be prudent for parties applying the problem-solution-approach to include the recognizability of the objective problem and its cause into their considerations.

Nothing is said about the lack of independence of the Board; this has, apparently, become the new ‘normal’; the EPO has managed to silence or ‘tame’ its critics and now everyone is supposed to accept that Haar is the permanent home of ‘justice’ — where judges are actively lobbied/pressured by Campinos himself to allow illegal patents.

“Articles 52 and 56 of the European Patent Convention won’t matter to today’s EPO management; because it routinely violates many other articles and it gloats about that mass violation having no consequences!”We certainly hope that more blogs will appear that the EPO won’t bribe or censor (or threaten). As it stands, however, even IPPro Magazine no longer covers EPO affairs (it did for a while and Barney did a decent job). Based on their site, they stopped publication about a month ago (prior to that they had significantly slowed down and only Becky Bellamy composed new articles, mostly PR and ‘puff pieces’ that resemble advertisements).

Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

Decor ᶃ Gemini Space

Below is a Web proxy. We recommend getting a Gemini client/browser.

Black/white/grey bullet button This post is also available in Gemini over at this address (requires a Gemini client/browser to open).

Decor ✐ Cross-references

Black/white/grey bullet button Pages that cross-reference this one, if any exist, are listed below or will be listed below over time.

Decor ▢ Respond and Discuss

Black/white/grey bullet button If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

DecorWhat Else is New

  1. Peak Code — Part II: Lost Source

    "Debian and Mozilla played along. They were made “Yeoman Freeholders” in return for rewriting their charters to “work closely with the new Ministry in the interests of all stakeholders” – or some-such vacuous spout… because no one remembers… after that it started."

  2. Links 22/1/2022: Ubuntu MATE 21.10 for GPD Pocket 3, MINISFORUM Preloads GNU/Linux

    Links for the day

  3. Computer Users Should be Operators, But Instead They're Being Operated by Vendors and Governments

    Computers have been turned into hostile black boxes (unlike Blackbox) that distrust the person who purchased them; moreover, from a legislative point of view, encryption (i.e. computer security) is perceived and treated by governments like a threat instead of something imperative — a necessity for society’s empowerment (privacy is about control and people in positions of unjust power want total and complete control)

  4. Peak Code — Part I: Before the Wars

    Article/series by Dr. Andy Farnell: "in the period between 1960 and 2060 people had mistaken what they called "The Internet" for a communications system, when it had in fact been an Ideal and a Battleground all along - the site of the 100 years info-war."

  5. Links 21/1/2022: RISC-V Development Board and Rust 1.58.1

    Links for the day

  6. IRC Proceedings: Thursday, January 20, 2022

    IRC logs for Thursday, January 20, 2022

  7. Gemini Lets You Control the Presentation Layer to Suit Your Own Needs

    In Gemini (or the Web as seen through Gemini clients such as Kristall) the user comes first; it's not sites/capsules that tell the user how pages are presented/rendered, as they decide only on structural/semantic aspects

  8. The Future of Techrights

    Futures are difficult to predict, but our general vision for the years ahead revolves around more community involvement and less (none or decreased) reliance on third parties, especially monopolistic corporations, mostly because they oppress the population via the network and via electronic devices

  9. [Meme] UPC for CJEU

    When you do illegal things and knowingly break the law to get started with a “legal” system you know it’ll end up in tears… or the CJEU

  10. Links 20/1/2022: 'Pluton' Pushback and Red Hat Satellite 6.10.2

    Links for the day

  11. The Web is a Corporate Misinformation/Disinformation Platform, Biased Against Communities, Facts, and Science

    Misinformation/disinformation in so-called 'news' sites is a pandemic which spreads; in the process, the founder of GNU/Linux gets defamed and GNU/Linux itself is described as the problem, not the solution to the actual problems

  12. Links 20/1/2022: McKinsey Openwashing and Stable Kernels

    Links for the day

  13. IRC Proceedings: Wednesday, January 19, 2022

    IRC logs for Wednesday, January 19, 2022

  14. Links 20/1/2022: Linuxfx 11.1 WxDesktop 11.0.3 and FreeIPMI 1.6.9 Released

    Links for the day

  15. Links 19/1/2022: XWayland 22.1 RC1 and OnlyOffice 7.0 Release

    Links for the day

  16. Links 19/1/2022: ArchLabs 2022.01.18 and KDE's 15-Minute Bug Initiative

    Links for the day

  17. When Twitter Protects Abusers and Abuse (and Twitter's Sponsors)

    Twitter is an out-of-control censorship machine and it should be treated accordingly even by those who merely "read" or "follow" Twitter accounts; Twitter is a filter, not a news/media platform or even means of communication

  18. IRC Proceedings: Tuesday, January 18, 2022

    IRC logs for Tuesday, January 18, 2022

  19. Links 19/1/2022: Wine 7.x Era Begins and Istio 1.12.2 is Out

    Links for the day

  20. Another Video IBM Does Not Want You to Watch

    It seems very much possible that IBM (or someone close to IBM) is trying to purge me from Twitter, so let’s examine what they may be trying to distract from. As we put it 2 years ago, "Watson" is a lot more offensive than those supposedly offensive words IBM is working to purge; think about those hundreds of Red Hat workers who are black and were never told about ethnic purges of blacks facilitated by IBM (their new boss).

  21. What IBM Does Not Want You to Watch

    Let's 'Streisand it'...

  22. Good News, Bad News (and Back to Normal)

    When many services are reliant on the integrity of a single, very tiny MicroSD card you're only moments away from 2 days of intensive labour (recovery, investigation, migration, and further coding); we've learned our lessons and took advantage of this incident to upgrade the operating system, double the storage space, even improve the code slightly (for compatibility with newer systems)

  23. Someone Is Very Desperate to Knock My Account Off Twitter

    Many reports against me — some successful — are putting my free speech (and factual statements) at risk

  24. Links 18/1/2022: Deepin 20.4 and Qubes OS 4.1.0 RC4

    Links for the day

  25. Links 18/1/2022: GNOME 42 Alpha and KStars 3.5.7

    Links for the day

  26. IRC Proceedings: Monday, January 17, 2022

    IRC logs for Monday, January 17, 2022

  27. Links 17/1/2022: More Microsoft-Connected FUD Against Linux as Its Share Continues to Fall

    Links for the day

  28. The GUI Challenge

    The latest article from Andy concerns the Command Line Challenge

  29. Links 17/1/2022: digiKam 7.5.0 and GhostBSD 22.01.12 Released

    Links for the day

  30. IRC Proceedings: Sunday, January 16, 2022

    IRC logs for Sunday, January 16, 2022

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

Recent Posts