<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>softwarepatents &amp;mdash; Webmink In Draft</title>
    <link>https://the.webm.ink/tag:softwarepatents</link>
    <description>Things cooking in the Minkiverse. They move elsewhere when the oven pings.</description>
    <pubDate>Fri, 17 Apr 2026 11:09:01 +0100</pubDate>
    <item>
      <title>Open CODECs Are Not Anti-Competitive</title>
      <link>https://the.webm.ink/open-codecs-are-not-anti-competitive</link>
      <description>&lt;![CDATA[Update: Graduated to the OSI Blog.&#xA;!--more--&#xA;The news that the European Commission’s competition directorate (DG COMP) has decided not to conduct a full antitrust investigation into the Alliance for Open Media’s (AOM) licensing policy is to be welcomed, especially for the AV1 CODEC specification (successor to the VP9 CODEC and intended to allow royalty-free high-quality video streaming). It seems that whispering voices had falsely suggested the reciprocal licensing of standard-essential patents (SEPs) in AOM’s policy is somehow anti-competitive. &#xA;&#xA;A magpie perched on the side of a skip (dumpster) trying to persaude the world he is not in fact a thieving magpie&#xA;&#xA;But reciprocal patent licensing is very common in the software industry generally and open source in particular - it’s part of the terms of the Apache License for example - so the accusation seemed far more likely to be projection by the SEP-dependent legacy industries of Europe. One useful insight into the whispers to which DG COMP responded can be seen in the extra information AOM has added to its legal page in response to the matter. The questions they address have such obvious and innocuous answers that only express sophistry could have been behind such questions, given the sophistication of the actors involved.&#xA;&#xA;This is all crucially important to open source software, and not just as an endorsement of reciprocal terms. While there are edge cases, generally open source projects avoid standards which embed royalty-due patents, not primarily because of the royalties but because of the need to submit to the control implied by privately negotiating terms with the patent holders - an obviously anti-competitive aspect for any market entrant, about which Europeans complain when others do it. &#xA;&#xA;It only takes one patent aggressor to rob everyone of viable open source video, so it seems entirely reasonable to scrupulously maintain hygiene by requiring any beneficiary of AV1 to commit to waiving royalties (and thus their negotiation). AOM is creating standards expressly intended to allow implementation by open source projects, so their terms are both rational and reasonable … unless you want to keep open source out of your cozy market.&#xA;&#xA;The clouds have not all dispersed. AOM’s licensing is unfortunately based on a non-OSI-approved license (for excellent reasons but still an issue). Hopefully this will become more and more unfashionable as open source expands its reach. Also significantly there are hostile patent pools which, unfathomably and without evidence their mountain of claims are actually essential, assert that the AV1 standards infringe patents in the pools. &#xA;&#xA;But this is good progress and underlines that the &#34;reciprocal&#34; mechanisms so common in open source licenses are generally pro-competitive.  Perhaps the Commission will now move on to ask why such an obviously anti-competitive arrangement as standards bodies permitting royalty-due patents in their specifications is still tolerated?&#xA;&#xA;---&#xA;Notes, Tags &amp; Mentions&#xA;&#xA;#OpenSource #FOSS #FLOSS #Patents #SoftwarePatents #SEPs #CODECs #AV1&#xA;&#xA;Follow @webmink@the.webm.ink to be informed of new posts. To discuss this post please reply from Mastodon etc. (search for the URL) &amp; include @webmink@meshed.cloud as WriteFreely still doesn&#39;t display replies. a href=&#34;/About&#34;More/a.]]&gt;</description>
      <content:encoded><![CDATA[<p><em>Update:</em> Graduated to the <a href="https://blog.opensource.org/why-open-video-is-vital-for-open-source/">OSI Blog</a>.

The <a href="https://aomedia.org/press%20releases/preliminary-aom-royalty-free-licensing-policy-investigation/">news</a> that the European Commission’s competition directorate (DG COMP) has decided not to conduct a full antitrust investigation into the Alliance for Open Media’s (AOM) licensing policy is to be welcomed, especially for the <a href="https://en.wikipedia.org/wiki/AV1">AV1 CODEC specification</a> (successor to the VP9 CODEC and intended to allow royalty-free high-quality video streaming). It seems that whispering voices had falsely suggested the reciprocal licensing of standard-essential patents (SEPs) in AOM’s policy is somehow anti-competitive.</p>

<p><a href="https://www.flickr.com/photos/webmink/51296452914/"><img src="https://live.staticflickr.com/65535/51296452914_3027748602_h.jpg" alt="A magpie perched on the side of a skip (dumpster) trying to persaude the world he is not in fact a thieving magpie" title="Rossini Will Be Hearing From My Lawyers"></a></p>

<p>But reciprocal patent licensing is very common in the software industry generally and open source in particular – it’s part of the terms of the Apache License for example – so the accusation seemed far more likely to be projection by the SEP-dependent legacy industries of Europe. One useful insight into the whispers to which DG COMP responded can be seen in the <a href="https://aomedia.org/docs/AOM_W3C_Mode_and_the_AOM_Patent_License_1.0.pdf">extra information</a> AOM has added to its <a href="https://aomedia.org/license/">legal page</a> in response to the matter. The questions they address have such obvious and innocuous answers that only express sophistry could have been behind such questions, given the sophistication of the actors involved.</p>

<p>This is all crucially important to open source software, and not just as an endorsement of reciprocal terms. While there are edge cases, generally <a href="https://blog.opensource.org/why-open-source-should-be-exempt-from-standard-essential-patents/">open source projects avoid standards which embed royalty-due patents</a>, not primarily because of the royalties but because of the need to submit to the control implied by privately negotiating terms with the patent holders – an obviously anti-competitive aspect for any market entrant, <a href="https://the.webm.ink/seps-cut-both-ways">about which Europeans complain when others do it</a>.</p>

<p>It only takes one patent aggressor to rob everyone of viable open source video, so it seems entirely reasonable to scrupulously maintain hygiene by requiring any beneficiary of AV1 to commit to waiving royalties (and thus their negotiation). AOM is creating standards expressly intended to allow implementation by open source projects, so their terms are both rational and reasonable … unless you want to keep open source out of your cozy market.</p>

<p>The clouds have not all dispersed. AOM’s licensing is unfortunately based on a non-OSI-approved license (for excellent reasons but still an issue). Hopefully this will become more and more unfashionable as open source expands its reach. Also significantly there are hostile patent pools which, unfathomably and without evidence their mountain of claims are actually essential, assert that the AV1 standards infringe patents in the pools.</p>

<p>But this is good progress and underlines that the “reciprocal” mechanisms so common in open source licenses are generally pro-competitive.  Perhaps the Commission will now move on to ask why such an obviously anti-competitive arrangement as standards bodies permitting royalty-due patents in their specifications is still tolerated?</p>

<hr>

<h3 id="notes-tags-mentions">Notes, Tags &amp; Mentions</h3>
<ul><li><a href="https://the.webm.ink/tag:OpenSource" class="hashtag"><span>#</span><span class="p-category">OpenSource</span></a> <a href="https://the.webm.ink/tag:FOSS" class="hashtag"><span>#</span><span class="p-category">FOSS</span></a> <a href="https://the.webm.ink/tag:FLOSS" class="hashtag"><span>#</span><span class="p-category">FLOSS</span></a> <a href="https://the.webm.ink/tag:Patents" class="hashtag"><span>#</span><span class="p-category">Patents</span></a> <a href="https://the.webm.ink/tag:SoftwarePatents" class="hashtag"><span>#</span><span class="p-category">SoftwarePatents</span></a> <a href="https://the.webm.ink/tag:SEPs" class="hashtag"><span>#</span><span class="p-category">SEPs</span></a> <a href="https://the.webm.ink/tag:CODECs" class="hashtag"><span>#</span><span class="p-category">CODECs</span></a> <a href="https://the.webm.ink/tag:AV1" class="hashtag"><span>#</span><span class="p-category">AV1</span></a></li></ul>

<p><em>Follow <code><a href="https://the.webm.ink/@/webmink@the.webm.ink" class="u-url mention">@<span>webmink@the.webm.ink</span></a></code> to be informed of new posts. To discuss this post please reply from Mastodon etc. (search for the URL) &amp; include <code><a href="https://the.webm.ink/@/webmink@meshed.cloud" class="u-url mention">@<span>webmink@meshed.cloud</span></a></code> as WriteFreely still doesn&#39;t display replies. <a href="/About">More</a>.</em></p>
]]></content:encoded>
      <guid>https://the.webm.ink/open-codecs-are-not-anti-competitive</guid>
      <pubDate>Tue, 23 May 2023 16:23:34 +0100</pubDate>
    </item>
    <item>
      <title>SEPs Cut Both Ways</title>
      <link>https://the.webm.ink/seps-cut-both-ways</link>
      <description>&lt;![CDATA[I just read a news story about how Chinese tech companies are threatening Europe by registering so many patents. Turns out it&#39;s in the context of &#34;open standards&#34; and is actually Chinese companies copying what European multinationals have done for years with patents embedded in standards. That Sword of Damocles cuts both ways.&#xA;&#xA;The handles of three gigantic sword statues seen against a blue sky&#xA;!--more--&#xA;I still meet people who think that implementing an &#34;open standard&#34; is something anyone can do freely. But it&#39;s unfortunately not so - the word &#34;open&#34; in standards is not used the same way as &#34;open&#34; in software. This difference exists for a reason, resisting even clarification by the European Interoperability Framework (EIF) v1 where pro-patent lobbyists managed to get the clarification removed in the subsequent version. Even if you can get the specification without having to pay a significant sum for the privilege, chances are a standard from a body like ETSI will have a high aggregate patent royalty associated with any implementation. &#xA;&#xA;Why? For years, cartel-like behaviour by technology companies has used patents they have embedded in formal standards to control the markets they monetise. They do this not just legally but with the encouragement of market authorities, who regard it as a reasonable compromise despite the obviously anti-competitive nature of the practice (which they freely admit). So they describe as &#34;open&#34; any standard created under a standards-body process that is theoretically equally open to all, which thus circumvents the anti-trust rules. &#xA;&#xA;Once embedded in the specification, &#34;standard-essential patents&#34; (SEPs) must then be licensed in order to implement technologies the companies include in core standards for mobile phones, media playback, consumer device functions and more. The terms are almost always based on per-unit royalties. This has proved extremely profitable, allowing companies to continue to harvest revenues from markets they may have been unable to monetise fairly via superior products. They are supposed to license on &#34;Fair, Reasonable and Non-Discriminatory&#34; (FRAND) terms, but recent research shows securing licenses can be extremely difficult, if not impossible. The European Commission is now legislating to partially address that in the upcoming SEP Directive, which is also perhaps motivated by a desire to address the use of the same system by China.&#xA;&#xA;But in some ways the royalties are the least issue. By creating SEPs, the corporations also gain market control, again in a way that amazingly does not break any anti-trust laws. The presence of SEPs ensures that all newcomers who are attempting to enter or disrupt a market are forced into NDA-secret negotiations with their incumbent competitors to get licenses. Controlling who can compete is just as valuable to the incumbents.&#xA;&#xA; It is not unknown for incumbents to use the covert control point of terms negotiation to disrupt market access by offering unreasonable terms regardless of commitments to FRAND licensing. This raises the barrier to entry in their markets and keeps costs -- and thus consumer prices -- high, while the market controllers are able to privately cross-license to each other to keep their own costs controlled and their margins high. The power asymmetry is also a valuable asset; courts start out assuming the supplicant is evading their responsibilities and may well intervene for the plaintiff while the case is running. Even without these extremes, it&#39;s common for patent owners to drag their feet to disadvantage licensees.&#xA;&#xA;But what if vendors in China behaved in a similar cartel-like manner and then gained control of a critical mass of SEPs needed to implement critical technologies? What if they also used their patents to block foreign companies from the Chinese market and to tax their products when they are finally allowed? Seemingly with little sense of irony, representatives of the incumbents interviewed by the Financial Times complained of just those scenarios starting to appear because of the single-minded intensity of patenting activities by Chinese companies. &#xA;&#xA;There&#39;s no doubt this is a threat to the livelihood of the incumbent companies. But perhaps the problem is not China but the practice of tolerating patents in standards itself? The lesson here is to carefully consider the privileges you exploit, lest others do the same. Live by the SEP, die by the SEP.&#xA;&#xA;---&#xA;Notes, Tags and Mentions&#xA;&#xA;#FRAND #RAND #SEP #Patents #SoftwarePatents #Standards #SEPD #OpenSource &#xA;If the story is paywalled try a longer ladder for fair use.&#xA;The two papers linked above are worth reading independently of the story as they document the creeping regulatory capture of &#34;FRAND&#34; and the near-impossibility securing licenses for a SEP-encumbered standard:&#xA;   Pocknell, Robert &amp; Djavaherian, Dave, The History of the ETSI IPR Policy: Using the Historical Record to Inform Application of the ETSI FRAND Obligation (September 27, 2022). http://dx.doi.org/10.2139/ssrn.4231645&#xA;   Lundell, Björn; Gamalielsson, Jonas &amp; Katz, Andrew, Implementing the HEVC standard in software: Challenges and Recommendations for organisations planning development and deployment of software (February 3, 2023). https://doi.org/10.18757/jos.2022.6695&#xA;&#xA;Follow @webmink@the.webm.ink to be informed of new posts. To discuss this post please reply from Mastodon etc. (search for the URL) &amp; include @webmink@meshed.cloud as WriteFreely still doesn&#39;t display replies. a href=&#34;/About&#34;More/a.]]&gt;</description>
      <content:encoded><![CDATA[<p>I just read a <a href="https://www.ft.com/content/57c16db1-023a-4c81-8507-7ccec851232e">news story</a> about how Chinese tech companies are threatening Europe by registering so many patents. Turns out it&#39;s in the context of “open standards” and is actually Chinese companies copying what European multinationals have done for years with patents embedded in standards. That Sword of Damocles cuts both ways.</p>

<p><a href="https://www.flickr.com/photos/webmink/4574073617/"><img src="https://live.staticflickr.com/4002/4574073617_b79e8e6dc7_h.jpg" alt="The handles of three gigantic sword statues seen against a blue sky" title="Scandinavian Swords"></a>

I still meet people who think that implementing an “open standard” is something anyone can do freely. But it&#39;s unfortunately not so – the word <a href="https://meshedinsights.com/2021/02/11/chalk-and-cheese/">“open” in standards is not used the same way as “open” in software</a>. This difference exists for a reason, resisting even clarification by the <a href="http://web.archive.org/web/20120710134922/https://ec.europa.eu/idabc/servlets/Docd552.pdf">European Interoperability Framework (EIF) v1</a> where pro-patent lobbyists managed to <a href="https://arstechnica.com/information-technology/2009/11/eu-waffles-on-open-standards-in-interoperability-guideline/">get the clarification removed</a> in the subsequent version. Even if you can get the specification without having to pay a significant sum for the privilege, chances are a standard from a body like <a href="https://etsi.org">ETSI</a> will have a high aggregate patent royalty associated with any implementation.</p>

<p>Why? For years, cartel-like behaviour by technology companies has <a href="https://dx.doi.org/10.2139/ssrn.4231645">used patents</a> they have embedded in formal standards to control the markets they monetise. They do this not just legally but with the encouragement of market authorities, who regard it as a reasonable compromise despite the obviously anti-competitive nature of the practice (which they freely admit). So they describe as “open” any standard created under a standards-body process that is theoretically equally open to all, which thus circumvents the anti-trust rules.</p>

<p>Once embedded in the specification, “standard-essential patents” (SEPs) must then be licensed in order to implement technologies the companies include in core standards for mobile phones, media playback, consumer device functions and more. The terms are almost always based on per-unit royalties. This has proved extremely profitable, allowing companies to continue to harvest revenues from markets they may have been unable to monetise fairly via superior products. They are supposed to license on “Fair, Reasonable and Non-Discriminatory” (FRAND) terms, but <a href="https://doi.org/10.18757/jos.2022.6695">recent research</a> shows securing licenses can be extremely difficult, if not impossible. The European Commission is now legislating to partially address that in the upcoming SEP Directive, which is also perhaps motivated by a desire to address the use of the same system by China.</p>

<p>But in some ways the royalties are the least issue. By creating SEPs, the corporations also gain market control, again in a way that amazingly does not break any anti-trust laws. The presence of SEPs ensures that all newcomers who are attempting to enter or disrupt a market are forced into NDA-secret negotiations with their incumbent competitors to get licenses. Controlling who can compete is just as valuable to the incumbents.</p>

<p> It is not unknown for incumbents to use the covert control point of terms negotiation to disrupt market access by offering unreasonable terms regardless of commitments to FRAND licensing. This raises the barrier to entry in their markets and keeps costs — and thus consumer prices — high, while the market controllers are able to privately cross-license to each other to keep their own costs controlled and their margins high. The power asymmetry is also a valuable asset; courts start out assuming the supplicant is evading their responsibilities and may well intervene for the plaintiff while the case is running. Even without these extremes, it&#39;s common for patent owners to drag their feet to disadvantage licensees.</p>

<p>But what if vendors in China behaved in a similar cartel-like manner and then gained control of a critical mass of SEPs needed to implement critical technologies? What if they also used their patents to block foreign companies from the Chinese market and to tax their products when they are finally allowed? Seemingly with little sense of irony, representatives of the incumbents interviewed by <a href="https://www.ft.com/content/57c16db1-023a-4c81-8507-7ccec851232e">the Financial Times</a> complained of just those scenarios starting to appear because of the single-minded intensity of patenting activities by Chinese companies.</p>

<p>There&#39;s no doubt this is a threat to the livelihood of the incumbent companies. But perhaps the problem is not China but the practice of tolerating patents in standards itself? The lesson here is to carefully consider the privileges you exploit, lest others do the same. Live by the SEP, die by the SEP.</p>

<hr>

<h3 id="notes-tags-and-mentions">Notes, Tags and Mentions</h3>
<ul><li><a href="https://the.webm.ink/tag:FRAND" class="hashtag"><span>#</span><span class="p-category">FRAND</span></a> <a href="https://the.webm.ink/tag:RAND" class="hashtag"><span>#</span><span class="p-category">RAND</span></a> <a href="https://the.webm.ink/tag:SEP" class="hashtag"><span>#</span><span class="p-category">SEP</span></a> <a href="https://the.webm.ink/tag:Patents" class="hashtag"><span>#</span><span class="p-category">Patents</span></a> <a href="https://the.webm.ink/tag:SoftwarePatents" class="hashtag"><span>#</span><span class="p-category">SoftwarePatents</span></a> <a href="https://the.webm.ink/tag:Standards" class="hashtag"><span>#</span><span class="p-category">Standards</span></a> <a href="https://the.webm.ink/tag:SEPD" class="hashtag"><span>#</span><span class="p-category">SEPD</span></a> <a href="https://the.webm.ink/tag:OpenSource" class="hashtag"><span>#</span><span class="p-category">OpenSource</span></a></li>
<li>If the story is paywalled try <a href="https://12ft.io/">a longer ladder</a> for fair use.</li>
<li>The two papers linked above are worth reading independently of the story as they document the creeping regulatory capture of “FRAND” and the near-impossibility securing licenses for a SEP-encumbered standard:
<ul><li>Pocknell, Robert &amp; Djavaherian, Dave, The History of the ETSI IPR Policy: Using the Historical Record to Inform Application of the ETSI FRAND Obligation (September 27, 2022). <a href="http://dx.doi.org/10.2139/ssrn.4231645">http://dx.doi.org/10.2139/ssrn.4231645</a></li>
<li>Lundell, Björn; Gamalielsson, Jonas &amp; Katz, Andrew, Implementing the HEVC standard in software: Challenges and Recommendations for organisations planning development and deployment of software (February 3, 2023). <a href="https://doi.org/10.18757/jos.2022.6695">https://doi.org/10.18757/jos.2022.6695</a></li></ul></li></ul>

<p><em>Follow <code><a href="https://the.webm.ink/@/webmink@the.webm.ink" class="u-url mention">@<span>webmink@the.webm.ink</span></a></code> to be informed of new posts. To discuss this post please reply from Mastodon etc. (search for the URL) &amp; include <code><a href="https://the.webm.ink/@/webmink@meshed.cloud" class="u-url mention">@<span>webmink@meshed.cloud</span></a></code> as WriteFreely still doesn&#39;t display replies. <a href="/About">More</a>.</em></p>
]]></content:encoded>
      <guid>https://the.webm.ink/seps-cut-both-ways</guid>
      <pubDate>Wed, 03 May 2023 10:28:46 +0100</pubDate>
    </item>
  </channel>
</rss>