Intellectual Property and Open Source: A Practical Guide to Protecting Code
"O'Reilly Media, Inc.", 2008. gada 15. jūl. - 386 lappuses
"Clear, correct, and deep, this is a welcome addition to discussions of law and computing for anyone -- even lawyers!"-- Lawrence Lessig, Professor of Law at Stanford Law School and founder of the Stanford Center for Internet and Society
If you work in information technology, intellectual property is central to your job -- but dealing with the complexities of the legal system can be mind-boggling. This book is for anyone who wants to understand how the legal system deals with intellectual property rights for code and other content. You'll get a clear look at intellectual property issues from a developer's point of view, including practical advice about situations you're likely to encounter.
Written by an intellectual property attorney who is also a programmer, Intellectual Property and Open Source helps you understand patents, copyrights, trademarks, trade secrets, and licenses, with special focus on the issues surrounding open source development and the GPL. This book answers questions such as:
Most legal sources are too scattered, too arcane, and too hard to read. Intellectual Property and Open Source is a friendly, easy-to-follow overview of the law that programmers, system administrators, graphic designers, and many others will find essential.
1.5. rezultāts no 34.
In return for full disclosure of your idea, you are granted the ability to prevent anyone else from making, using, selling, offering for sale, or importing the invention. Patents last for a maximum of about 20 years, after which the ...
The point of the disclosure, as its name suggests, is to teach people how to recreate the invention (even though some inventors do better than others with that requirement). But just as the code segments in an ELF file will vary between ...
I stated earlier that the conception is complete when the inventor can make an enabling disclosure. Constructive reduction to practice is complete when the inventor actually makes that disclosure.
The official purpose of the abstract is to enable the United States Patent and Trademark Office and the public generally to determine quickly from a cursory inspection the nature and gist of the technical disclosure.
To return to an earlier phrase, the detailed description and drawings must together provide an enabling disclosure of the invention. One item of relevance to computer-related patents is that no code listings have to be provided to the ...
Lietotāju komentāri - Rakstīt atsauksmi
LibraryThing ReviewLietotāja recenzija - mwirkk - LibraryThing
Excellent. Probably the best introduction I have read to the issues of intellectual property rights and and their expression as software. It is a very good and clear introduction to anyone who wants ... Lasīt pilnu pārskatu
Chapter 5 Trademarks
Chapter 6 Trade Secrets
Chapter 7 Contracts and Licenses
Chapter 8 The Economic and Legal Foundations of Open Source Software
Appendix B Open Source License List
Appendix C Free Software License List
Appendix D Fedora License List and GPL Compatibility
Appendix E Public Domain Declaration
Appendix F The Simplified BSD License
Appendix G The Apache License Version 20
Appendix H The Mozilla Public License Version 11
Appendix I The GNU Lesser General Public License Version 21
Chapter 9 So I Have an Idea
Chapter 10 Choosing a License
Chapter 11 Accepting Patches and Contributions
Chapter 12 Working with the GPL
Chapter 13 Reverse Engineering
Chapter 14 Incorporating As a NonProfit
Appendix A Sample Proprietary Information Agreement PIA
Appendix J The GNU Lesser General Public License Version 3
Appendix K The GNU General Public License Version 2 June 1991
Appendix L The GNU General Public License Version 3 June 2007
Appendix M The Open Software License Version 30