Create, Consult, Control
News & commentary on intellectual property issues.
Jan192010 | Steve O'Donnell
What should your copyright notice say?
As I mentioned before, copyright has a lot of urban legends attached to it. Another one of these is the attachment most people have to the little copyright notice on the bottom of their websites.
You don’t need it.
Copyright is automatic as soon as something is “fixed in any tangible medium of expression.” Under US law, a copyright notice is not required for anything first published after March 1, 1989.
There may be reasons why you’d want to use a copyright notice. There is a chance of the notice scaring away a potential infringer that doesn’t know much about copyrights. I don’t think it’s much of a watchdog, maybe a small chihuahua--one of those shaky, teacup, apple-headed chihuahuas.
Another reason is that a notice will defeat a challenge that an infringement was not willful. If an infringement is willful, the infringer could be liable for enhanced statutory damages as high as $150,000 plus costs and legal fees. I know, sounds good doesn’t it? However statutory damages are only available to registered works and precious few people register the work on their websites with the copyright office. Notice may also have benefits under the laws of other countries.
On the other hand, having a copyright notice doesn’t hurt anything. Whether you want to use one or not is your call, but don’t feel like you’re putting your work in danger if you don’t have one.
Image published in 1906 found on cyberlawcentre.org and is from the Library of Congress' Bob Hope Vaudeville and American Variety Archive.
Jan042010 | Steve O'Donnell
How many copyrights does your blog infringe?
If you are a blogger you’re probably familiar with blog scrapers (sites that take other people’s content and republish somewhere else). Bloggers have a good reason to be upset about scrapers; after all, it is someone else taking your work. However, most bloggers don’t give a second thought about snatching a picture online and using it for a post.
If you find a picture on Flickr, another blog, or somewhere else online and upload it to your own blog (or worse yet, inline link to it from your blog) without permission, you’re committing a copyright violation.
By grabbing whatever picture you find that fits with your post you’re risking damages up to $150,000 for a registered work. Admittedly, that number is an extreme possibility, and probably one that would never be levied against a blogger, but it is technically possible. A more likely damages award would be $750 for a registered work, plus lots more in attorney fees.
Most graphic files you encounter online are not going to be registered with the copyright office, in that case damages would likely be limited to actual damages and an injunction to take down the picture, plus whatever you have to pay your attorney.
More likely than someone suing you for scraping their .jpg is them sending your ISP a takedown notice, which is probably going to result in them taking your site down until you remove the picture. It’s less onerous that taking a $150k hit, but still not good.
If you want to be a good internet citizen, and have the moral authority to complain if your blog gets scrapped, don’t take from others. There are plenty of sources for Creative Commons images, Google Image Search’s Advanced tab will pull such images, as will the Creative Commons' own home. Just make sure you comply with the license.
Image published in 1906 found on cyberlawcentre.org and is from the Library of Congress' Bob Hope Vaudeville and American Variety Archive.
1
Recent Posts
- A City Authentic
- Does downloading really hurt DVD sales?
- What happens to patents when a company closes.
- Bilski didn’t change much except my dinner plans
- When the "little guy's" copyright is infringed
- Is there a better way to police a trademark?
- Chick-Fil-A only wants you to eat more chicken.
- What I learned at the 2010 Launch Music Conference
- You probably don't want a provisional patent application
- Avoiding Trademark issues when naming your band




Comments