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. |
No grāmatas satura
1.–5. rezultāts no 27.
... 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, obviousness, and the ...
... art to actually make the invention without extensive research or ... earlier that the conception is complete when the inventor can make an ... patent applications, there is an incentive to include or not to include Conception of the ...
... prior art from new ideas. Prior art is the patent law term for everything known to the public before you conceived your idea. Your priority date is, in effect, your “place in line” on the inventor's timeline. As described earlier ...
... prior art (which can be used to challenge a patent) and ideas that are not prior art (which rarely help challenge a patent, and might infringe the patent). For example, competitors trying to work around or challenge this particular ...
... 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. This patent history can be seen in ...
Saturs
1 | |
21 | |
49 | |
Chapter 4 Copyright | 71 |
Chapter 5 Trademarks | 103 |
Chapter 6 Trade Secrets | 119 |
Chapter 7 Contracts and Licenses | 133 |
Chapter 8 The Economic and Legal Foundations of Open Source Software | 153 |
Appendix B Open Source License List | 281 |
Appendix C Free Software License List | 285 |
Appendix D Fedora License List and GPL Compatibility | 289 |
Appendix E Public Domain Declaration | 299 |
Appendix F The Simplified BSD License | 301 |
Appendix G The Apache License Version 20 | 303 |
Appendix H The Mozilla Public License Version 11 | 309 |
Appendix I The GNU Lesser General Public License Version 21 | 319 |
Chapter 9 So I Have an Idea | 179 |
Chapter 10 Choosing a License | 197 |
Chapter 11 Accepting Patches and Contributions | 215 |
Chapter 12 Working with the GPL | 223 |
Chapter 13 Reverse Engineering | 239 |
Chapter 14 Incorporating As a NonProfit | 253 |
Appendix A Sample Proprietary Information Agreement PIA | 271 |
Appendix J The GNU Lesser General Public License Version 3 | 329 |
Appendix K The GNU General Public License Version 2 June 1991 | 333 |
Appendix L The GNU General Public License Version 3 June 2007 | 341 |
Appendix M The Open Software License Version 30 | 355 |
Index | 359 |
Citi izdevumi - Skatīt visu
Intellectual Property and Open Source: A Practical Guide to Protecting Code Van Lindberg Ierobežota priekšskatīšana - 2008 |