Slight wording changes, increased sunset clause to 15 years, added more notes in rationale on length and warranties

2 files changed, 21 insertions, 12 deletions

diff --git a/license.txt b/license.txt
index 8dc18fe..e17f36a 100644
--- a/license.txt
+++ b/license.txt
@@ -1,7 +1,7 @@
 
 
 SUNSET LICENSE
-Version 1.0 Draft Revision 4, June 2017
+Version 1.0 Draft Revision 5, June 2017
 
 
 1. You may copy, modify, use, sell, or distribute this work, verbatim or
@@ -13,13 +13,13 @@ no extra charge.
 
 3. A modified version of this work must be clearly labeled as such.
 
-4. Derivative works must also be licensed under this license or a license with
+4. Derivative works must also be licensed under this license or a license of
 equivalent terms. As an exception, linking this work with another, whether
 statically or dynamically, does not impose any license requirements on the
 other work.
 
-5. If a minimum of 10 years have passed since the date of first publishing for
+5. If a minimum of 15 years have passed since the date of first publishing for
 a part of this work, then that part is placed into the public domain and you
-can do whatever you want with it, regardless of all other clauses.
+may do whatever you want with it, regardless of all other clauses.
 
 
diff --git a/rationale.txt b/rationale.txt
index 8d517df..87af121 100644
--- a/rationale.txt
+++ b/rationale.txt
@@ -30,11 +30,15 @@ date, or the work itself has stagnated to the point where nobody cares anyway.
 But the time that it takes for those parts of a work to be allowed under the
 rules of public domain will remain reasonable, relatively short, and finite.
 
+The length of 15 years was chosen after reviewing the timelines of multiple
+major software projects, the policy of Pirate Party Australia, and a paper on
+optimal copyright term lengths by Rufus Pollock published in August 2007.
+
 Combining this idea with minimalistic copyleft clauses should fill another
 hole in available licenses, as all current ones are exceedingly verbose.
 
 The copyleft clauses have to be weak however, as otherwise works using this
-license would not be able to link against LGPL/BSD/MIT licensed works, which
+license would not be able to be linked with LGPL/BSD/MIT licensed works, which
 would be less than ideal. Both static and dynamic linking have to be allowed
 as otherwise there would be too many language specific details required in the
 license.
@@ -47,14 +51,19 @@ Scope
 This is primarily conceived of as a software license. While the result may be
 applicable to other works, it may not be optimal for them.
 
-Software patents are not something that will be mentioned or considered. The
-position taken is that if software patents are a problem in your country, you
-should reform the law.
+Software patents are not something that will be mentioned. The position taken
+is that if software patents are a problem in your country, you should reform
+the law.
+
+Warranty disclaimers will also not be mentioned. The position taken is that
+your software should do what you say it does, and that you should be
+responsible for what you release to the public. Again, if this is a problem in
+your country, you should reform the law.
 
-Warranty disclaimers will also neither be mentioned nor considered. The
-position taken is that your software should do what you say it does, and that
-you should be responsible for what you release to the public. Again, if this
-is a problem in your country, you should reform the law.
+(An interesting note about warranties is that, as buggy software is common, an
+occasional software bug fits the standard of "passes ordinarily in the trade"
+and thus would not violate a typical implied warranty of merchantability. You
+are encouraged to check your local consumer law yourself to verify this.)
 
 The focus is on the work actually released, not on spreading the license
 itself.