« Play the Punctuation Game | Main | Avoid over-using adverbs »

Copyright and the new year

Here’s a question that came up on a technical writing list I subscribe to: If you have a copyright statement in a document that you distribute regularly, do you update the copyright date for the new year?

If the document is unchanged, then no. For example, if you publish a recipe for eggnog in December of 2006, the copyright statement should say “Copyright © 2006 Alphonse Q. Murgatroyd.” According to the American Bar Association’s guide to copyright, your copyright begins “from the time the work is created in fixed form.” You might distribute that recipe for many years, but as long as you don’t make any changes to it, you don’t change the copyright.

However, assume that in 2007 you add some information about how to avoid salmonella poisoning (in an effort to avoid lawsuits) and republish your recipe, then you would update the copyright date.

If you have a website (like a blog) that you claim copyright for, and the information on that website is updated regularly, then as soon as a change is made on that website, you should update the copyright statement for the new year. 

Disclaimer: I am not a lawyer. I’m basing this on an interested layman’s understanding of U.S. copyright law.

Posted on Wednesday, December 20, 2006 at 06:58AM by Registered CommenterRoy Jacobsen in | CommentsPost a Comment | References1 Reference

PrintView Printer Friendly Version

EmailEmail Article to Friend

References (1)

References allow you to track sources for this article, as well as articles that were written in response to this article.

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>