Property, intangible

a blog about ownership of intellectual property rights and its licensing

What You Can’t Put on a Copyright Registration — UPDATED

Ruh-roh, I think a court went off the rails. I don’t have a good feeling about this.

The case is, in part, about infringement of copyright. As you know, one cannot bring suit for infringement of a U.S. copyright unless the copyright is registered. 17 U.S.C. § 411. But it gets a little confusing with registration of derivative works.

The leading case is Streetwise Maps, Inc. v. VanDam, Inc., 159 F.3d 739 (2d Cir. 1998). All we know about Streetwise’s registration is that “The registration certificate relied upon by the plaintiff stated that the copyrighted work was derivative of a ‘Streetwise Manhattan map carrying a copyright notice date of 1984, 1985.’”

In Streetwise, the defendant argued that the registration for the derivative work covered only the new material added to already-existing maps. The court disagreed; in what later came to be called the “effective registration doctrine,” it held that a registration of a derivative work is sufficient for purposes of alleging infringement of the underlying original work also. Although the case has been distinguished by Oravec v. Sunny Isles Luxury Ventures, L.C., 527 F.3d 1218, 1229 (11th Cir. 2008) (holding that the certificate had to identify the preexisting works) and Morris v. Bus. Concepts, Inc., 283 F.3d 502, 505 (2d Cir. 2002) (holding that it only applies to situations where the copyright plaintiff owns both the preexisting and derivative work), it is well-settled law.

Which brings us to the present case. Plaintiff AFL Telecommunications LLC had a registration for version 1.32b of software that it alleged was infringed. This was a derivative work of a number of earlier versions of the work and the registration stated “Material excluded from this claim: Previous version.”

The court held that, unlike Streetwise, where the registration stated that the registered work was a derivative work, AFL Telecommunications specifically excluded the preexisting work and thus “AFL has failed to satisfy the registration requirement with regard to any previous version of the software.”

While this appears logical on its face, it is wrong. The difference in the wording used by AFL Telecommunications is forced by current copyright registration practice and does not mean that the AFL Telecommunications plaintiff intended any different scope of copyright than the Streetwise plaintiff did.

For an online copyright application for software, Circular 61 describes the “Limitation of Field Claim” — the part of the registration that the court was looking at — this way:

Circular 61 2012 clip
(click through to 2012 Circular 61)

If you can’t read the image, it says:

Limitation of Claim· Complete this part of the application if the computer program contains a substantial amount of previously published, registered, or public domain material such as subroutines or modules, or if the work was developed using an underlying computer program or authoring tool. “Material excluded” may state “previous version.” Typical examples of descriptions of “New material included” are “computer program” and “revised version.” Do not refer to debugging, error corrections, new functions of the revised program, or other elements that cannot be registered.

Note that this is not discretionary; if a copyright applicant fails to provide the information (because, for example, it wants to claim the underlying work also as part of the registration to satisfy a court like AFL Telecommuncations) the registration may be invalidated as fraudulent. See, e.g., One Treasure’s One Treasure Ltd., Inc. v. Richardson, 202 F. App’x 658, 661 (5th Cir. 2006) (challenging registration for failure to identify derivative sources).

This same exact information used to go in a block on the application called “Derivative Work or Compilation”:

circular 61 1999 clip
(click through to 1999 Circular 61)

If you can’t read it, it says:

Space 6. Derivative Work or Compilation. Complete this space if the computer program contains a substantial amount of previously published, registered, or public domain material such as subroutines, modules, textual images, or if the work was developed using an underlying computer program or authoring tool. Space 6a may state “previous version.” Typical examples of descriptions of new material for space 6b include “revised computer program,” “editorial revisions,” “revisions and additional text of computer program,” “new programming text,” etc. Do not refer to debugging, error corrections, new functions of the revised program, or other unregistrable elements.*

You can see that the Copyright Office has merely changed the wording used for the derivative work claim also by comparing the current paper Form TX and the online application. The paper application still calls for a description of the “Derivative Work or Compilation”:

FormTX clip
(click through for original application form)

But an online application puts exactly the same information in a block called “Limitation of Claim,” albeit with a surprising new word that was of such import to the court, “excluded”:

AFL copyright registration clip
(click through for AFL copyright registration)

The copyright applicant has no control over the wording of the registration form. Further, the online application is a checkbox-based filing system where there is no place for an applicant to note that it intends for the application to cover both the preexisting work and the new work, nor to state that the application is for a “derivative work.”

So the Copyright Office, by modernizing its system and changing the wording of a block, has led at least one court astray and caused a substantive change to copyright law. But the Copyright Office cannot create substantive copyright law; it only administers it: “The Register of Copyrights is authorized to establish regulations not inconsistent with law.” 17 U.S.C. § 702. The Copyright Office did not have the authority to, and therefore could not have, changed the law merely by changing the words it chose for the content of the application. The court therefore erred in distinguishing this case from Streetwise on the basis of the uneditable form language of the copyright application.

The plaintiff’s infringement case failed for other reasons too — it didn’t prove that version 1.32 of the software indeed incorporated earlier versions, or what version of the software was being used on the accused hardware devices. But I have a sinking feeling that Streetwise will be mooted by a small change in a Copyright Office form as plaintiffs find they cannot bring a copyright infringement claim simply because they followed Copyright Office rules.

AFL Telecommunications LLC v. Inc., No. CV11-1086 PHX DGC (D. Ariz. May 20, 2013).

*UPDATE: The language of the Circular is probably incomplete. The Compendium II of Copyright Office Practices § 308.01 is fairly clear that the intention is to identify the preexisting work owned by a different author:

306.01 Extent of claim.

The copyright in a derivative work extends only to the material contributed by the author of such work, as distinguished from the preexisting material employed in the work, and does not imply any exclusive right in the preexisting material. The copyright in such work is independent of, and does not affect or enlarge the scope, duration, ownership, or subsistence of, any copyright protection in the preexisting material. 17 U.S.C. 103(b). Where a work contains a substantial amount of previously registered, published, or public domain material, the application should contain a statement of the preexisting material as well as the new copyrightable material.

Nowhere does Circular 61, however, mention that the preexisting work to be identified is only that of a different author.

Creative Commons License
The text of this work is licensed under a Creative Commons Attribution-No Derivative Works 3.0 United States License.

Share Button

One response to “What You Can’t Put on a Copyright Registration — UPDATED”

  1. […] Hey copyright tweeps, this is an important decision on registration practice, please RT… […]

Leave a Reply

Your email address will not be published. Required fields are marked *