copyright software
Under US copyright, when licensing software what is &quot;publicly display&quot; and &quot;publicly perform&quot;
<p>Section 106 of the USA copyright law lists the exclusive rights of copyrighted works.  These are the rights that a software developer may grant for software they have developed.  Unfortunately the exclusive rights were drafted long before software was invented and it's hard to understand how they directly relate to software.</p>

<p>Two of the exclusive rights are the right to <code>publicly perform</code> the work and the right to <code>publicly display</code> the work.</p>

<p>In the context of a source code and binary code software license what do each of these two rights convey and how are they different from each other? </p>

<p>Citations to third party sources that address this would also be greatly appreciated.</p>

<p>Under <a href="https://www.law.cornell.edu/uscode/text/17/101" rel="nofollow">17 USC 101</a>, "perform" is defined as:</p>

<blockquote>
  <p>To “perform” a work means to recite, render, play, dance, or act it,
  either directly or by means of any device or process or, in the case
  of a motion picture or other audiovisual work, to show its images in
  any sequence or to make the sounds accompanying it audible.</p>
</blockquote>

<p>To display is:</p>

<blockquote>
  <p>To “display” a work means to show a copy of it, either directly or by
  means of a film, slide, television image, or any other device or
  process or, in the case of a motion picture or other audiovis­ual
  work, to show individual images nonsequentially.</p>
</blockquote>

<p>The terms "display" and "perform" do not apply to what one ordinarily does with software. Software isn't an audiovisual work so the second half of the definition of "perform" is inapplicable. You also can't recite, render, play, dance, or act software -- you can run / execute it, and that isn't part of what "perform" means. Likewise you don't display software when you execute it – you might display a thing created by software, but you don't (usually) display the software itself.</p>

<p>There are competing legal theories (held by judges) about how to interpret laws. One approach pays attention to the literal meaning of words, and in that approach one cannot say that running software constitutes "performance" or "display". Another approach is to decide what the outcome is supposed to be in a given case, and then stretch the meaning of words (or not) to fit that end. You might guess I don't like the latter approach: I mention this because it's not inconceivable that the meaning of "perform" could be stretched to mean "execute", given a bit more shift in judicial philosophy.</p>

<p>But notice that <a href="https://www.law.cornell.edu/uscode/text/17/106" rel="nofollow">section 106</a> (4)-(6) specifically ties "performance" to literary, musical, dramatic, and choreographic works, pantomimes, and motion pictures and other audiovisual works" as well as sound recordings, and ties "display" to "literary, musical, dramatic, and choreographic works, pantomimes, and pictorial, graphic, or sculptural works, including the individual images of a motion picture or other audiovisual work". In other words, we don't need to care about "perform" and "display" because performing softward and displaying software is not a protected right anyhow, at least by the letter of the law.</p>

<p>Using software at all without permission is prohibited, even in the privacy of your own home. To use software, it has to be copied (which you can't legally do without permission). Copyright law is mostly irrelevant to questions of software, and what really controls what you can and cannot do is the license agreement. Because of copyright law, you can't say "But this was an unlicensed usage so I'm not bound by those terms", so copyright law provides the Scylla and the license provides the Charybdis.</p>

<p><a href="https://www.law.cornell.edu/uscode/text/17/117" rel="nofollow">17 USC 117</a> says:</p>

<blockquote>
  <p>it is not an infringement for the owner of a copy of a computer
  program to make or authorize the making of another copy or adaptation
  of that computer program provided:</p>
  
  <p>(1) that <em>such a new copy or adaptation is created as an essential step
  in the utilization of the computer program in conjunction with a
  machine and that it is used in no other manner</em></p>
</blockquote>

<p>Installing (copying) sure enough is an essential step in utilization. This slice of code suggests that you can use the software, given copyright law. But that would be so only if you are the <em>owner</em> of a copy of the program, and one often does not buy a copy of the program, one buys a license, if you are to believe what the license says.</p>

<p>In <a href="http://www.citizen.org/documents/Vernor_Autodesk_Ninth_Circuit_Opinion.pdf" rel="nofollow">Vernor v. Autodesk</a>, the court held that customers are "licensees of their copies of the software rather than owners" (so Vernor did not buy his copy from an owner). One reason why Autodesk ultimately prevailed is that they asserted in the license that they retain title (they lost in the lower court, <a href="https://www.courtlistener.com/opinion/1457201/vernor-v-autodesk-inc/" rel="nofollow">Vernor v.  Autodesk, 555 F. Supp. 2d 1164</a>). Similarly, the Office 2007 license says "The software is licensed, not sold", thus closing any arguments that you can do things not permitted by the license. The point being, if you don't own the software, you can't execute it in public, unless the license allows it.</p>

<p>If you do own the software, then we can turn to questions of what copyright law might allow. In order to prevent you from publicly running software, the act would have to be something prohibited by copyright law -- like making a copy. the degree of copying involved in installing / executing software would be allowed by section 107, and there is no statutory restriction on public "use" except that which is limited to literary, musical etc. works. At present, software is not considered to be a "literary work" or similar, therefore there is no statutory basis for prohibiting the public execution of a piece of software. Any such limitations must derive from the license agreement.</p>
