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 27.
The nuts and bolts of patent documents are explained in Chapter 2, and the process of writing and prosecuting (obtaining) a patent is examined in Chapter 3. This chapter also examines patent-specific issues such as priority, prior art, ...
... enable a person having ordinary skill in the art to actually make the invention without extensive research or experimentation. ... I stated earlier that the conception is complete when the inventor can make an enabling disclosure.
If a patent claims priority to some document that was filed earlier than the utility patent application, however, and there is support ... The priority date matters because this is the magic date that divides prior art from new ideas.
As described earlier, although the priority date is frequently the same as the application date, ... Remember, the priority date is the dividing line between prior art (which can be used to challenge a patent) and ideas that are not ...
The examiner puts forth prior art and can make rejections based on the prior art, after which the applicant points out the distinguishing features included in the claims that are not taught by the prior art references.
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