Mercurial > thoughts
changeset 18:fe9e92bbafbc
spellcheck.
author | Robert McIntyre <rlm@mit.edu> |
---|---|
date | Mon, 01 Apr 2013 16:06:09 +0000 |
parents | 63a9cd3edcc0 |
children | fcb569c767b6 |
files | org/patents.org |
diffstat | 1 files changed, 15 insertions(+), 15 deletions(-) [+] |
line wrap: on
line diff
1.1 --- a/org/patents.org Mon Apr 01 16:05:13 2013 +0000 1.2 +++ b/org/patents.org Mon Apr 01 16:06:09 2013 +0000 1.3 @@ -14,7 +14,7 @@ 1.4 Copyright is something the you are automatically granted whenever 1.5 you create a work in some permanent form; you don't have to request 1.6 it or anything. It lets you prevent other people from copying your 1.7 - work, reading your work, or creating derivitave works based on your 1.8 + work, reading your work, or creating derivative works based on your 1.9 work. 1.10 1.11 Thus, copyright is what I call a "negative force". It is something 1.12 @@ -29,8 +29,8 @@ 1.13 your information. The GPL essentially reads: 1.14 1.15 #+begin_quote 1.16 - This work is copyrighted, but by recieving this work you gain the 1.17 - rights to distribute, copy, and make derivitave works based on this 1.18 + This work is copyrighted, but by receiving this work you gain the 1.19 + rights to distribute, copy, and make derivative works based on this 1.20 work, but only if you also license such work under this license. 1.21 #+end_quote 1.22 1.23 @@ -51,17 +51,17 @@ 1.24 patent, it gives you the ability to stop anyone else from using your 1.25 idea in any other invention. This is supposed to give you a 1.26 temporary monopoly to help you make money off your invention before 1.27 - anyone else would be legally allowed to do so. In practce, many 1.28 + anyone else would be legally allowed to do so. In practice, many 1.29 patents are given for ideas that are quite obvious to pretty much 1.30 everyone. For example, Amazon has a patent (#[[http://patft.uspto.gov/netacgi/nph-Parser?Sect2=PTO1&Sect2=HITOFF&p=1&u=%2Fnetahtml%2FPTO%2Fsearch-bool.html&r=1&f=G&l=50&d=PALL&RefSrch=yes&Query=PN%2F5715399][5,715,399]]) on the idea 1.31 - of presenting a coustomer with the last four digits of a credit card 1.32 - instead of displaying the entire numbner. Amazon can sue any other 1.33 + of presenting a customer with the last four digits of a credit card 1.34 + instead of displaying the entire number. Amazon can sue any other 1.35 company that displays only the last four digits of a credit card 1.36 number and prevent them from using that method unless they pay 1.37 Amazon a lot of money. Needless to say, there are many patents that 1.38 are very silly. 1.39 1.40 - Now, I choose a particurally silly patent, but the point is that 1.41 + Now, I choose a particularly silly patent, but the point is that 1.42 patents can be a great force for the retardation of progress. Many 1.43 silly patents have been issued, and a patent lasts for 17 years. For 1.44 almost any idea, there will be some patent that will cover your 1.45 @@ -72,8 +72,8 @@ 1.46 program will be covered by a patent, and it can become impossible to 1.47 legally distribute that program as free software. This is why some 1.48 GNU/Linux distributions don't come with an mp3 player. The mp3 1.49 - algorighm is patented, and even if you write an open source mp3 1.50 - player, you will have problems distribuiting that player because of 1.51 + algorithm is patented, and even if you write an open source mp3 1.52 + player, you will have problems distributing that player because of 1.53 the mp3 patents. 1.54 1.55 ** Patents are treated as physical objects 1.56 @@ -97,7 +97,7 @@ 1.57 can actually distribute that invention. Normally, your invention 1.58 will be affected by other patents, which themselves are affected by 1.59 other patents. You can only distribute your invention if you 1.60 - negoitate with the owners of all these dependent patents. 1.61 + negotiate with the owners of all these dependent patents. 1.62 1.63 An example: If I own the patent for table tops and you own the 1.64 patent for table legs, and you and I don't get along too well, then 1.65 @@ -112,14 +112,14 @@ 1.66 1.67 This is an interesting statement to me. With this pledge, Google has 1.68 created "neutral" patents that allow open source software to 1.69 - develop, but do not particurally encourage it to develop. They have 1.70 + develop, but do not particularly encourage it to develop. They have 1.71 done this by attaching legally binding conditions on the enforcement 1.72 of their patents via a pledge. 1.73 1.74 * Positive Patents 1.75 We can create patents that actively encourage openness by emulating 1.76 the GPL. What it would take is a company that issues a more 1.77 - agressive pledge about its patents; Something along the lines of: 1.78 + aggressive pledge about its patents; Something along the lines of: 1.79 1.80 #+begin_quote 1.81 The Positive Patent Pledge, v0.1 1.82 @@ -130,7 +130,7 @@ 1.83 see market, as is our right under patent law. 1.84 1.85 The only exception is if the product is open (all code/methods of 1.86 - construction is made pubically available under an open license), and 1.87 + construction is made publicly available under an open license), and 1.88 the entity makes this same pledge for any patents relating to the 1.89 product." 1.90 #+end_quote 1.91 @@ -165,11 +165,11 @@ 1.92 see market, as is our right under patent law. 1.93 1.94 The only exception is if the product is open (all code/methods of 1.95 - construction is made pubically available under an open license), and 1.96 + construction is made publicly available under an open license), and 1.97 the entity makes this same pledge for any patents relating to the 1.98 product, the entity can take the Google 'neutral patent pledge' 1.99 instead of this pledge if they are a 'special exception'. 1.100 #+end_quote 1.101 1.102 The only way for a company to become a special exception would be 1.103 - for them to contribute monetairly to this hypothetical company. 1.104 + for them to contribute monetarily to this hypothetical company.