<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>OGL &amp;mdash; Valinard&#39;s Tower</title>
    <link>https://valinard.writeas.com/tag:OGL</link>
    <description>“For this my lamp is lit, to the grief of the owls, and often  burns till lark-song.” &lt;br&gt;--Lord Dunsany, *The Charwoman&#39;s Shadow*</description>
    <pubDate>Sat, 16 May 2026 23:13:27 +0000</pubDate>
    <image>
      <url>https://i.snap.as/uT13t3LA.jpg</url>
      <title>OGL &amp;mdash; Valinard&#39;s Tower</title>
      <link>https://valinard.writeas.com/tag:OGL</link>
    </image>
    <item>
      <title>Perpetual and Irrevocable</title>
      <link>https://valinard.writeas.com/perpetual-and-irrevocable?pk_campaign=rss-feed</link>
      <description>&lt;![CDATA[Layman&#39;s legal analysis of the OGL scandal, arguing that a contract can be irrevocable even if it does not explicitly use the word &#39;irrevocable&#39;. We make contracts we cannot revoke every day, without explicitly using that word.&#xA;&#xA;!--more--&#xA;&#xA;These two words have dominated the discussion of WotC’s attempts to eliminate #OGL 1.0a and replace it with something far more draconian.&#xA;&#xA;Many people, including some lawyers, have argued that if a license doesn’t specifically state that it is irrevocable, it can be revoked at will.&#xA;&#xA;But as far as I can tell, from what I’ve read and heard from lawyers and people who have spoken to lawyers in the open source community where they deal with this kind of thing as a matter of routine that simply isn’t true.&#xA;&#xA;Take the MIT License, which has been used since the late 80s and is one of the most popular free software licenses in the world:&#xA;&#xA;  Copyright (c) (year) (copyright holders)&#xA;    Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the &#34;Software&#34;), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:&#xA;    The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.&#xA;    THE SOFTWARE IS PROVIDED &#34;AS IS&#34;, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.&#xA;&#xA;This license is widely considered to be valid, perpetual and non-revocable. Now, reading through it carefully, what two words do you not see?&#xA;&#xA;Contracts are intended to be binding on both parties. That’s what a contract is - a binding agreement with particular terms. If you sign a contract that says “I will do X” you can’t simply get out of it by saying “I promised to do X, but I didn’t specifically promise not to not do X!” &#xA;&#xA;Yet this is the consequence of assuming at-will revocation as the default - in order to really promise something, you have to not only make a promise, but make a separate promise to not renege on that promise.&#xA;&#xA;There are two elements of the OGL that serve to make it irrevocable: One, the term “perpetual”. From what I’ve read, courts will generally tend toward the interpretation that when you specify a term, and don’t specify a termination clause, both parties meant and understood for the contract to last for that term. &#xA;&#xA;Two, consideration. If you paid someone for a license they obviously can’t just cancel it at will unless they specify that they can in the contract - in effect saying “give us some money, and maybe we won’t just keep it in return for nothing.”&#xA;&#xA;The OGL contains consideration, but it isn’t money - the consideration is “agreeing to use this License” - that is, publishing your work as Open Game Content under the OGL.&#xA;&#xA;Some have claimed that there is no consideration in the OGL one one side or the other, but this is false. The license to the SRD and other OGC is valid consideration because the OGC contains copyrightable material, as well as uncopyrightable procedures and rules.&#xA;&#xA;On the other side, the agreement to publish under the license has value too. Jacobsen v. Katzer in 2008 found that open source licenses do have consideration (emphasis mine): &#xA;&#xA;  Traditionally, copyright owners sold their copyrighted material in exchange for money. The lack of money changing hands in open source licensing should not be presumed to mean that there is no economic consideration, however. There are substantial benefits, including economic benefits, to the creation and distribution of copyrighted works under public licenses that range far beyond traditional license royalties. For example, program creators may generate market share for their programs by providing certain components free of charge. Similarly, a programmer or company may increase its national or international reputation by incubating open source projects. Improvement to a product can come rapidly and free of charge from an expert not even known to the copyright holder. The Eleventh Circuit has recognized the economic motives inherent in public licenses, even where profit is not immediate.&#xA;&#xA;Is it perhaps a good idea to specify both terms in future contracts? Absolutely, for the avoidance of doubt and stupid “no backsies” playground style arguments. Indeed, there may even be some uncertainty in certain jurisdictions as to which way the courts might rule. &#xA;&#xA;But is it strictly necessary? &#xA;&#xA;The long experience of the open source community - which seems to be our best source of evidence here - suggests no.&#xA;&#xA;Of course I am not a lawyer, am not giving legal advice here, and I welcome clarification and corrections from actual lawyers if they care to weigh in. &#xA;&#xA;But I have noticed several of the actual lawyers who have_ been weighing in on this issue don’t appear to have done their research. This is perhaps unsurprising. If anti-vaxxers can find doctors willing to claim COVID isn’t real, we must bear in mind that people with idiosyncratic interpretations of contract law are going to be able to find lawyers to swear to those, too.&#xA;&#xA;And the danger here in focusing overly on these two words is that we end up getting hoodwinked with such things as “perpetual, irrevocable” licenses which have clear and draconian termination clauses, or can be updated to change their terms (including the term that makes them irrevocable) at will.&#xA;&#xA;Because the law isn’t a game of Simon Says. The text of the contract in its entirety matters a lot more than whether you said the magic word.]]&gt;</description>
      <content:encoded><![CDATA[<p><em>Layman&#39;s legal analysis of the OGL scandal, arguing that a contract can be irrevocable even if it does not explicitly use the word &#39;irrevocable&#39;. We make contracts we cannot revoke every day, without explicitly using that word.</em></p>



<p>These two words have dominated the discussion of WotC’s attempts to eliminate <a href="https://valinard.writeas.com/tag:OGL" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">OGL</span></a> 1.0a and replace it with something far more draconian.</p>

<p>Many people, including some lawyers, have argued that if a license doesn’t specifically state that it is irrevocable, it can be revoked at will.</p>

<p>But as far as I can tell, from what I’ve read and heard from lawyers and people who have spoken to lawyers in the open source community where they deal with this kind of thing as a matter of routine that <em>simply isn’t true.</em></p>

<p>Take the <a href="https://opensource.org/licenses/MIT" rel="nofollow">MIT License</a>, which has been used since the late 80s and is one of the most popular free software licenses in the world:</p>

<blockquote><p>Copyright © (year) (copyright holders)</p>

<p>Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:</p>

<p>The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.</p>

<p>THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p></blockquote>

<p>This license is widely considered to be valid, perpetual and non-revocable. Now, reading through it carefully, what two words do you not see?</p>

<p>Contracts are intended to be binding on both parties. That’s what a contract <em>is</em> – a binding agreement with particular terms. If you sign a contract that says “I will do X” you can’t simply get out of it by saying “I promised to do X, but I didn’t specifically promise not to not do X!”</p>

<p>Yet this is the consequence of assuming at-will revocation as the default – in order to <em>really</em> promise something, you have to not only make a promise, but make a separate promise to not renege on that promise.</p>

<p>There are two elements of the OGL that serve to make it irrevocable: One, the term “perpetual”. From what I’ve read, courts will generally tend toward the interpretation that when you specify a term, and don’t specify a termination clause, both parties meant and understood for the contract to last for that term.</p>

<p>Two, consideration. If you paid someone for a license they obviously can’t just cancel it at will unless they specify that they can in the contract – in effect saying “give us some money, and maybe we won’t just keep it in return for nothing.”</p>

<p>The OGL contains consideration, but it isn’t money – the consideration is “agreeing to use this License” – that is, publishing your work as Open Game Content under the OGL.</p>

<p><a href="https://doctorow.medium.com/good-riddance-to-the-open-gaming-license-8902f4aa69d2" rel="nofollow">Some have claimed</a> that there is no consideration in the OGL one one side or the other, but this is false. The license to the SRD and other OGC is valid consideration because the OGC contains copyrightable material, <em>as well as</em> uncopyrightable procedures and rules.</p>

<p>On the other side, the agreement to publish under the license has value too. <a href="https://scholar.google.com/scholar_case?case=17776182574171214893&amp;hl=en&amp;as_sdt=6&amp;as_vis=1&amp;oi=scholarr" rel="nofollow">Jacobsen v. Katzer</a> in 2008 found that open source licenses do have consideration (emphasis mine):</p>

<blockquote><p>Traditionally, copyright owners sold their copyrighted material in exchange for money. The lack of money changing hands in open source licensing should not be presumed to mean that there is no economic consideration, however. There are substantial benefits, including economic benefits, to the creation and distribution of copyrighted works under public licenses that range far beyond traditional license royalties. For example, program creators <strong>may generate market share for their programs by providing certain components free of charge</strong>. Similarly, a programmer or company may increase its national or international reputation by incubating open source projects. Improvement to a product can come rapidly and free of charge from an expert not even known to the copyright holder. The Eleventh Circuit has recognized the economic motives inherent in public licenses, even where profit is not immediate.</p></blockquote>

<p>Is it perhaps a good idea to specify both terms in future contracts? Absolutely, for the avoidance of doubt and stupid “no backsies” playground style arguments. Indeed, there may even be some uncertainty in certain jurisdictions as to which way the courts might rule.</p>

<p>But is it strictly necessary?</p>

<p>The long experience of the open source community – which seems to be our best source of evidence here – suggests no.</p>

<p>Of course I am not a lawyer, am not giving legal advice here, and I welcome clarification and corrections from actual lawyers if they care to weigh in.</p>

<p>But I have noticed several of the actual lawyers who <em>have</em> been weighing in on this issue don’t appear to have done their research. This is perhaps unsurprising. If anti-vaxxers can find doctors willing to claim COVID isn’t real, we must bear in mind that people with idiosyncratic interpretations of contract law are going to be able to find lawyers to swear to those, too.</p>

<p>And the danger here in focusing overly on these two words is that we end up getting hoodwinked with such things as “perpetual, irrevocable” licenses which have clear and draconian termination clauses, or can be updated to change their terms (including the term that makes them irrevocable) at will.</p>

<p>Because the law isn’t a game of Simon Says. The text of the contract in its entirety matters a lot more than whether you said the magic word.</p>
]]></content:encoded>
      <guid>https://valinard.writeas.com/perpetual-and-irrevocable</guid>
      <pubDate>Sat, 21 Jan 2023 17:21:00 +0000</pubDate>
    </item>
    <item>
      <title>Burning the Library</title>
      <link>https://valinard.writeas.com/burning-the-library?pk_campaign=rss-feed</link>
      <description>&lt;![CDATA[My layman&#39;s legal analysis of the OGL scandal, and the inadequacy and incoherence of Hasbro&#39;s first response.&#xA;&#xA;!--more--&#xA;&#xA;Incendie Alexandrie by Hermann Goll&#xA;&#xA;In response to the community revolt over changes to the #OGL WotC have released an updated OGL1.2 draft. There are various changes to the terms of the proposed 1.1 but I wish to focus on those that affect the existing body of Open Game Content developed over 20 years.&#xA;&#xA;The OGL1.0 and 1.0a create a contract between “the contributors”, meaning anyone who has contributed to a bucket full of shared resources called “the Open Game Content”, and the publisher making a derivative work using material from the bucket.&#xA;&#xA;It allows anyone to put any part of their work into the bucket, and take whatever they want to use out of the bucket, as long as they otherwise abide by the terms of the license.&#xA;&#xA;With 1.1, WotC tried to steal the bucket. They claimed the right to “de-authorize” earlier versions of the contract - a term as meaningful as “de-publish” or “de-sign” - which effectively meant they could dictate the license terms for all OGC content, regardless of who originally contributed it.&#xA;&#xA;Edit: It also contained conflicting definitions of the content being shared. &#xA;&#xA;  Licensed Content (what used to be called “Open Game Content”)&#xA;&#xA;  i. Usable D&amp;D Content (“Licensed Content”) – This is Dungeons &amp; Dragons content that is included in the SRD v. 5.1, including basic game mechanics and a curated selection of classes, monsters, spells, and items that allow You to make content compatible with Dungeons &amp; Dragons 5th edition. &#xA;&#xA;So it both says that &#39;Licensed Content&#39; includes the content previously defined as OGC, and that it doesn&#39;t.&#xA;&#xA;1.2 removes this ambiguity. It is not an open license, creating a commons to which anyone can contribute. It is purely a third party publishing license for the SRD5.1.&#xA;&#xA;And they still claim it replaces the “de-authorized” 1.0a. So where 1.1 left you to use OGC except under the draconian terms of 1.1, 1.2 leaves you unable to re-use this work at all. There is simply, by their claim, no “authorized” OGL contract capable of licensing it.&#xA;&#xA;Instead of stealing the bucket, they are now simply kicking it over so nobody else can have it.&#xA;&#xA;They also claim that work published previously under 1.0a will still be licensed, but this isn’t in the contract. Instead, they put new terms in a legally dubious “Notice of Deauthorization”:&#xA;&#xA;  NOTICE OF DEAUTHORIZATION OF OGL 1.0a. The Open Game License 1.0a is no longer an authorized license. This means that you may not use that version of the OGL, or any prior version, to publish SRD content after (effective date). It does not mean that any content previously published under that version needs to update to this license. Any previously published content remains licensed under whichever version of the OGL was in effect when you published that content.&#xA;&#xA;Saying they have “de-authorized” the contract is, as I have said, like saying they have “de-signed” an agreement, so it seems very unlikely they actually have the legal power to do this; but let us accept for the sake of argument that they do.&#xA;&#xA;1\.0a is either an authorized agreement or it is not. If it is not, then by its own wording it cannot be used for publication. Here they say that 1.0a is no longer authorized. A “Notice of Deauthorization” is not a legal contract. It cannot apply new terms to the contract it has just invalidated.&#xA;&#xA;So when they say &#xA;&#xA;  It does not mean that any content previously published under that version needs to update to this license.&#xA;&#xA;that is not a legally binding contract clause: It is just ‘a thing they said’, like when they said&#xA;&#xA;  if Wizards made a change you disagreed with, you could continue to use an earlier, acceptable version at your option. In other words, there’s no reason for Wizards to ever make a change that the community of people using the Open Gaming License would object to, because the community would just ignore the change anyway.&#xA;&#xA;and we all know how that turned out.&#xA;&#xA;So the effect of 1.2 along with “de-authorization” of 1.0a, is to make 1.0a content unlicensed and unpublishable, with a non-binding claim that it actually is licensed and publishable, but only for old content.&#xA;&#xA;Even if this is honored, the library of freely usable material represented by the OGC, created by hundreds of contributors over 23 years, will be locked away and unlicensed for use in any further works.&#xA;&#xA;Some of those contributors will re-release their work under Creative Commons or the upcoming ORC license, but for some - who are no longer with us, busy with other things, or whose work relies on WotC material such as the D20 SRD - that work will not be recoverable.&#xA;&#xA;If WotC are allowed to burn the OGC library it will be salvaged, and placed on a firmer footing, but it will never be recovered in its entirety.&#xA;&#xA;And if there’s one thing D&amp;D fans don’t like, it’s book-burners.&#xA;&#xA;]]&gt;</description>
      <content:encoded><![CDATA[<p><em>My layman&#39;s legal analysis of the OGL scandal, and the inadequacy and incoherence of Hasbro&#39;s first response.</em></p>



<p><img src="https://images.saturnian.uk/burning-alexandria.gif" alt="Incendie Alexandrie by Hermann Goll"/></p>

<p>In response to the community revolt over changes to the <a href="https://valinard.writeas.com/tag:OGL" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">OGL</span></a> WotC have released an updated <a href="https://www.dndbeyond.com/posts/1432-starting-the-ogl-playtest" rel="nofollow">OGL1.2 draft</a>. There are various changes to the terms of the proposed 1.1 but I wish to focus on those that affect the existing body of Open Game Content developed over 20 years.</p>

<p>The OGL1.0 and 1.0a create a contract between “the contributors”, meaning anyone who has contributed to a bucket full of shared resources called “the Open Game Content”, and the publisher making a derivative work using material from the bucket.</p>

<p>It allows anyone to put any part of their work into the bucket, and take whatever they want to use out of the bucket, as long as they otherwise abide by the terms of the license.</p>

<p>With 1.1, WotC tried to steal the bucket. They claimed the right to “de-authorize” earlier versions of the contract – a term as meaningful as “de-publish” or “de-sign” – which effectively meant they could dictate the license terms for all OGC content, regardless of who originally contributed it.</p>

<p>Edit: It also contained conflicting definitions of the content being shared.</p>

<blockquote><p>Licensed Content (what used to be called “Open Game Content”)</p>

<p>i. Usable D&amp;D Content (“Licensed Content”) – This is Dungeons &amp; Dragons content that is included in the SRD v. 5.1, including basic game mechanics and a curated selection of classes, monsters, spells, and items that allow You to make content compatible with Dungeons &amp; Dragons 5th edition.</p></blockquote>

<p>So it both says that &#39;Licensed Content&#39; includes the content previously defined as OGC, and that it doesn&#39;t.</p>

<p>1.2 removes this ambiguity. It is not an open license, creating a commons to which anyone can contribute. It is purely a third party publishing license for the SRD5.1.</p>

<p>And they still claim it replaces the “de-authorized” 1.0a. So where 1.1 left you to use OGC except under the draconian terms of 1.1, 1.2 leaves you unable to re-use this work <em>at all</em>. There is simply, by their claim, no “authorized” OGL contract capable of licensing it.</p>

<p>Instead of stealing the bucket, they are now simply kicking it over so nobody else can have it.</p>

<p>They also claim that work published previously under 1.0a will still be licensed, but this isn’t in the contract. Instead, they put new terms in a legally dubious “Notice of Deauthorization”:</p>

<blockquote><p>NOTICE OF DEAUTHORIZATION OF OGL 1.0a. The Open Game License 1.0a is no longer an authorized license. This means that you may not use that version of the OGL, or any prior version, to publish SRD content after (effective date). It does not mean that any content previously published under that version needs to update to this license. Any previously published content remains licensed under whichever version of the OGL was in effect when you published that content.</p></blockquote>

<p>Saying they have “de-authorized” the contract is, as I have said, like saying they have “de-signed” an agreement, so it seems very unlikely they actually have the legal power to do this; but let us accept for the sake of argument that they do.</p>

<p>1.0a is either an authorized agreement or it is not. If it is not, then <em>by its own wording</em> it cannot be used for publication. Here they say that 1.0a is no longer authorized. A “Notice of Deauthorization” is not a legal contract. It cannot apply new terms to the contract it has just invalidated.</p>

<p>So when they say</p>

<blockquote><p>It does not mean that any content previously published under that version needs to update to this license.</p></blockquote>

<p>that is not a legally binding contract clause: It is just ‘a thing they said’, like when they said</p>

<blockquote><p>if Wizards made a change you disagreed with, you could continue to use an earlier, acceptable version at your option. In other words, there’s no reason for Wizards to ever make a change that the community of people using the Open Gaming License would object to, because the community would just ignore the change anyway.</p></blockquote>

<p>and we all know how that turned out.</p>

<p>So the effect of 1.2 along with “de-authorization” of 1.0a, is to make 1.0a content unlicensed and unpublishable, with a non-binding claim that it actually is licensed and publishable, but only for old content.</p>

<p>Even if this is honored, the library of freely usable material represented by the OGC, created by hundreds of contributors over 23 years, will be locked away and unlicensed for use in any further works.</p>

<p>Some of those contributors will re-release their work under Creative Commons or the upcoming ORC license, but for some – who are no longer with us, busy with other things, or whose work relies on WotC material such as the D20 SRD – that work will not be recoverable.</p>

<p>If WotC are allowed to burn the OGC library it will be salvaged, and placed on a firmer footing, but it will never be recovered in its entirety.</p>

<p>And if there’s one thing D&amp;D fans don’t like, it’s book-burners.</p>
]]></content:encoded>
      <guid>https://valinard.writeas.com/burning-the-library</guid>
      <pubDate>Sat, 21 Jan 2023 16:22:11 +0000</pubDate>
    </item>
  </channel>
</rss>