Commentary

Serdar Yegulalp
 

Copyright And Open Licensing: Not Mutually Exclusive

Yesterday the open source world got handed a major victory in the courts -- or, rather, given another brick for its growing wall of legal defense. The Federal Circuit Court of Appeals has ruled that the use of content under a properly worded open license is still protected by copyright law.

Yesterday the open source world got handed a major victory in the courts -- or, rather, given another brick for its growing wall of legal defense. The Federal Circuit Court of Appeals has ruled that the use of content under a properly worded open license is still protected by copyright law.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The case in question, Jacobsen v. Katzer, involves just such an issue. Jacobsen created an open source software package to control model trains; Katzer allegedly created a derivative product that used Jacobsen's work but didn't hew to the attributive licensing clauses that came with it. Jacobsen then took Katzer to court for copyright infringement, and further claimed that his licensing terms were unambiguous enough that it should have been clear he wasn't surrendering copyright on the material in question by offering it under the terms of such a license. (Jacobsen could, in theory, have sued for breach of contract a lot more easily, but the copyright terms of this type of case have, as far as I know, generally gone untested.)

The courts agreed on that point, and so did the appeals court. In the text of the judgment, the court noted:

The clear language of the Artistic License creates conditions to protect the economic rights at issue in the granting of a public license. These conditions govern the rights to modify and distribute the computer programs and files included in the downloadable software package. The attribution and modification transparency requirements directly serve to drive traffic to the open source incubation page and to inform downstream users of the project, which is a significant economic goal of the copyright holder that the law will enforce. Through this controlled spread of information, the copyright holder gains creative collaborators to the open source project; by requiring that changes made by downstream users be visible to the copyright holder and others, the copyright holder learns about the uses for his software and gains others' knowledge that can be used to advance future software releases.

It's striking, and rather reassuring, that the court not only took the time to educate itself about the subject but understands the deeper implications of what's going on. Making something available free of charge does not necessarily dilute its value; in fact, it may augment it, especially if the people who acquire it are building on it and returning those changes to the world at large.

What's still up in the air is whether or not Jacobsen is owed damages. I suspect such a thing would be established on a case-by-case basis, as fits the event in question. But open licensing in general just took a massive and well-deserved step forward.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links