Literary Law Guide for Authors 85
| Literary Law Guide for Authors: Copyright, Trademark, and Contracts in Plain Language | |
| author | Tonya Marie Evans and Susan Borden Evans |
| pages | 190 |
| publisher | FYOS Entertainment |
| rating | Excellent |
| reviewer | Logic Bomb |
| ISBN | 0967457963 |
| summary | A practical guide to copyright and trademark law |
The content of the book really is as the title claims. It is a practical explanation of legal concepts, written by practicing lawyers. It is not a theoretical exploration, it is not a detailed history, and it is most definitely not criticism. The primary audience is writers who want a good understanding of the law before getting involved with the publishing industry or attempting to self-publish. The writing itself is beautifully concise and precise. Given the topic, there are passages that require long lists of examples and distinctions to maintain accuracy. If you have never encountered thorough legal writing before, it can be a bit daunting.
Literary Law Guide begins by explaining copyright in great depth. In this book, that only means 10 pages. But the table of contents for that section alone lists the following:
- Protecting Ideas
- When Copyright Ownership Begins
- Showing the World That You Own Your Work
- What a Copyright Owner Has the Right to Do
- Scope of Copyright Protection
- The Elements of Copyrightable Works
- Copyright Registration
- How to Investigate the Copyright Status of a Work
- Where to Search for Information about Registered Copyrights
- Transfer of Copyright
- Reclaiming Your Copyright After Transfer
That's only the first half of the book's text. Trademark gets the next 30 pages. Once again the authors provide thorough explanations of concepts and actual legal procedures. The final section is on contracts. Given the book's nature, it's really about publishing contracts for writers, but the information is still useful.
The book includes a CD with a handful of Copyright and Trademark Office forms in PDF and Word files of sample publishing contracts. These materials are also printed over 90 pages in the book itself. With the exception of the contracts, this is fairly superfluous. The forms are all readily available online.
Overall, Literary Law Guide has value for several segments of the Slashdot readership. Programmers, especially those working independently, can gain invaluable information on the available means for protecting or profiting from their work. Those interested in Free content (not just software) can better understand issues surrounding licensing and the public domain. Everyone who reads the book will have a better understanding of the issues we spend so much time discussing.
Perhaps because it is targeted towards the world of traditional writing, Literary Law Guide may leave a Slashdot reader unsatisfied at the coverage of digital-age issues. However, I think the fault for that really lies with a legal structure that is, as we all know, far behind the times. A book on the law can only cover what law there is. As the authors put it, in what may be the greatest understatement on this issue I've seen:
In light of this twenty-first century reality, some scholars believe that the law lags far behind in closing the gap between yesterday's statutes and tomorrow's technology.
The final recommendation: if you want to know more about copyright and trademark than you'll easily discover using Google, this book is for you.
You can purchase Literary Law Guide for Authors: Copyright, Trademark, and Contracts in Plain Language from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
Copyright (Score:5, Funny)
Literary Law Guide begins by explaining copyright in great depth.
I agree. I downloaded the book off of Kazaa and thought the whole discussion concerning copyrights was well done.
Where's the fun in that? (Score:4, Funny)
- If you make something into an MP3, it automatically receives 1st Amendment protection against any copyright, trademark, contract or national security classification you would otherwise be violating.
- Everything is parody of something, and is therefore invariably legal.
- Don't ask us! Get a lawyer!
It seems to be that readership armed with actual facts and knowledge could only diminish this wellspring of creativity we've built here...A slight error by the author (Score:1, Funny)
Actually, the favorite way to begin a post on Slashdot is "I ANAL"
I'm afraid to hazard a guess as to what they mean.
Re:what it means (FOF REAL) (Score:1, Funny)
I Am Not A Lawer
You mis-spelled Lawnmower. Don't use abbrev. on
The answer to the question (Score:2, Funny)
This means I Am Not A Lawyer (IANAL).
It does not mean "IANAL - I am Near Alabama, so Yankees can filter posts easier." as some have suggested bcolflesh (710514)
Neither does it mean I Abuse Non-informative Acronyms Liberally
New question, Is there any way of filtering out posts from those near Alabama (or any states like IOWA, Ohio etc)?
re: IAAL. if you want to learn about the law... (Score:4, Funny)
OK, sorry; i'm sure this'll get modded redundant in 0.3 nanoseconds but i just couldn't help it.
ed
Re:IAAL. If you want to learn about the law... (Score:1, Funny)
Well to be honest, I've tried just what you said some time ago and to be honest, reading legal texts is insanely frustrating for programmers, because the level of chaos that comes about when non-programmers try to write a listing, in human language no less, it very quickly becomes a mess.
It's like one long list of if/then/else causes, sometimes a switch/case, but all in all very little genericity, little functional decomposition or abstrahation of recurring issues, and when they finally wrote themselve into a hole they can't get out of anymore, they throw an exception : "this situation is left to the interpretation of the judge".
I know the above sounds a bit like I'm mostly joking
(AC 'cause my login is on the fritz)
-bpe