<p>
    I have submitted for approval to <a href="http://www.opensource.org">OSI</a> a license on behalf of my good friend and client <a href="http://en.wikipedia.org/wiki/Leonardo_Chiariglione">Mr. Leonardo Chiariglione</a>, convenor of the ISO/IEC JTC1 WG11 (also known as <a href="http://www.chiariglione.org/mpeg/">MPEG</a>).
  </p>
  
  <p>
    <a href="http://www.linuxjournal.com/content/should-open-source-licence-ever-be-patent-agnostic">Linux Journal</a>, followed by many <a href="http://carlodaffara.conecta.it/?p=186">others</a>, has a story:
  </p>
  
  <blockquote>
    <p>
      [&#8230;] are there ever circumstances when software patents that require payment might be permitted by an open source licence? That's the question posed by a new licence that is being submitted to the Open Source Inititative (<a href="http://www.opensource.org/" rel="nofollow">OSI</a>) for review.
    </p>
    
    <p>
      It arises out of work to create a reference implementation of the MPEG eXtensible Middleware (<a href="http://mxm.wg11.sc29.org/" rel="nofollow">MXM</a>) standard. This <a href="http://mxm.wg11.sc29.org/?page_id=2" rel="nofollow">aims</a>
    </p>
    
    <p>
      <cite>to promote the extended use of digital media content through increased interoperability and accelerated development of components, solutions and applications. This is achieved by specifying</cite>
    </p>
    
    <p>
      <cite>1.The MXM architecture<br /> 2.The MXM components (by reference)<br /> 3.The MXM components APIs<br /> 4.The MXM applications API<br /> 5.The inter-MXM communication protocols</cite>
    </p>
    
    <p>
      More details can be found <a href="http://www.chiariglione.org/mpeg/visions/mxm/index.htm" rel="nofollow">here</a>.
    </p>
    
    <p>
      The proposed <a href="http://www.crynwr.com/cgi-bin/ezmlm-cgi?17:mss:717:200904:chenjkbbnllffijebmno" rel="nofollow">licence</a> is closely modelled on the Mozilla Public Licence (MPL). In his submission to the OSI, the well-known free software activist Carlo Piana explains the key difference:
    </p>
    
    <p>
      <cite>As you will notice, we have removed some of the patent conditions that existed in the MPL. This is because none of the contributors would have accepted to encapsulate their patents in a FOSS license without the ability to ask for a license separately from the copyright. This is a basic tenet that is enshrined in the so-called ISO/IEC Directives for the development of International Standards. Some of you might know about my public stance against software patents and my approval to some of the licenses which impose implied licensing to or patent retaliation against all who distribute FOSS software while relying on patent protection. However, the sad truth is that if we did not offer a patent-agnostic license we would have made all efforts to have an open source reference implementation moot.</cite>
    </p>
  </blockquote>
  
  <p>
    What!? Carlo Piana speaks software patents, Carlo Piana speaks &#8220;open source&#8221;? He must be out of his mind, nuts, off the rocker (my English stops here, but surely you can suggest more insult).
  </p>
  
  <p>
    Well, I am not. Let me explain.
  </p>
  
  <p>
    I was asked by Mr. Chiariglione to help out in drafting a license which could accommodate combining an &#8220;open source&#8221; model with the need for the patent holders to retain their patents rights without releasing them freely. I said that this was an impossible task, but I could produce something close enough. Then I was asked to submit it to OSI for approval, and what we had written (some small amendments to the <strong>Mozilla Public License</strong>) was working under copyright and patent laws, but not under the Open Source Definition. However I am not the ultimate expert of OSD, interpreting this as a legal text is within my reach, I reckon, and thus I have asked myself whether it could be possible to comply with the letter of the OSD, by more cleanly separating copyright from patents. From my submission:
  </p>
  
  <blockquote>
    <p>
      <cite> I have asked myself if this could work and if it complied with the OSI definition. My final conclusion is that if the BSD family is considered compliant, so shall be the MXM, as it does not condition the copyright grant to the obtaining of the patents, just as the BSD licenses don't deal with them. And insofar an implementer is confident that the part of the code it uses if free from the patented area, or it decided to later challenge the patent in case an infringement litigation is threatened, the license works just fine.</cite>
    </p>
  </blockquote>
  
  <p>
    Am I saying that having <strong>software patents</strong> attached to a reference implementation is fine? I am not, they should not. My public stance is for <strong>patent free standards</strong>, and I will not stop advocating <a href="http://www.interlex.it/forum10/relazioni/31piana.htm">against software patents</a> and against patent encumbered standards in particular. What I say is MPEG and the other ISO standards <em>are</em> patent encumbered. I say that this is not going to change in the short term, unless we make people aware of the problem. I have invested much of my time to <a href="http://www.piana.eu/is_29500">fight</a> against adoption of the ISO/IEC IS 29500 (AKA <a href="http://www.piana.eu/ooxml">OOXML</a>) and I have learned a lot from seeing things from inside. I have presented and even had a public argument with a representative of Microsoft in Geneva about this, downstairs from the Ballot Resolution Meeting. You can see a picture of mine in the big anti sw-pats flag that was brought before the Europarliament when the CII Directive was being discussed. I don't miss a chance to present against sw-pats.
  </p>
  
  <p>
    So let me be more clear: software patents are <em>patently</em> against Freedom, Digital Liberties, competition, progress, and <strong>detrimental to the software industry</strong> at large, especially SMEs (but the Big Guys have learned how it is detrimental also to them). The sooner they are <strong>abolished</strong>, or possibly replaced with something more sensible, the better.  My fellows from the industry could be in disagreement, and have a less draconian stance. But this is my opinion, even if without software patents a good chunk of my daily work would disappear.
  </p>
  
  <p>
    A final remark. I don't use the words &#8220;open source&#8221; lightly. In this context I could not use another wording because I was asking people to say that the license is&#8230; an &#8220;open source&#8221; license. So the question &#8220;is this 'open source'&#8221; is out of the realm of my concerns, usually; it became relevant only in this case because I was expressly asked to follow the submission procedure. Usually, I don't care much about a license being &#8220;approved&#8221;, and there are simply too many licenses. The <strong>only licenses</strong> that should exist, to me, are the <strong>GNU GPL</strong>, the GNU <strong>LGPL</strong> and the <strong>Affero</strong> GPL, possibly in their <strong>version 3</strong> or any later version. If you ask me if the license is Free Software, I would say &#8220;very likely, no&#8221;. If you ask me &#8220;is your license worth spreading?&#8221; I would say &#8220;of course absolutely not!&#8221;, and to push for another license was never within my instructions. As opposed to open up the ISO bunch to the concepts of <strong>copyelft</strong>, which is something I think can be achieved and beneficial in the long run.
  </p>
  
  <p>
    So, as you see, I am still not entirely mental. And I am not wearing any Napoleon hat, because I am <a href="http://en.wikipedia.org/wiki/Julius_Cesar">Julius Cesar</a>! <em>Alea jacta est</em>!
  </p>
</div>
<div class="field-item odd">
  <a href="/taxonomy/term/36">Interoperability</a>
</div>

<div class="field-item even">
  <a href="/taxonomy/term/53">Free Software</a>
</div>