svn commit: r1368163 - /creadur/whisker/trunk/src/site/fml/faq.fml

[rd...@apache.org]

Author: rdonkin
Date: Wed Aug  1 18:27:18 2012
New Revision: 1368163

URL: http://svn.apache.org/viewvc?rev=1368163&view=rev
Log:
Explain more about templating and licensing families

Modified:
    creadur/whisker/trunk/src/site/fml/faq.fml

Modified: creadur/whisker/trunk/src/site/fml/faq.fml
URL: http://svn.apache.org/viewvc/creadur/whisker/trunk/src/site/fml/faq.fml?rev=1368163&r1=1368162&r2=1368163&view=diff
==============================================================================
--- creadur/whisker/trunk/src/site/fml/faq.fml (original)
+++ creadur/whisker/trunk/src/site/fml/faq.fml Wed Aug  1 18:27:18 2012
@@ -331,6 +331,9 @@ Add a template <code>license</code> and 
 Read how <a href='meta-data.html#Templates_For_License_Families'>here</a>.
             </p>
             <p>
+Read the rational for templates <a href='#why-license-family'>here</a>.
+            </p>
+            <p>
 See this <a href='examples/license-family.html'>example</a>.
             </p>
             <p>
@@ -339,6 +342,34 @@ Read more about license families <a href
         </answer>
     </faq>
 
+    <faq id='why-license-family'>
+        <question>Why use templates for license families?</question>
+        <answer>
+            <p>
+Templates are not strictly necessary.
+            </p><p>
+Just pasting every complete license into the <code>text</code> would work,
+though the meta-data would be less concise than using templates. 
+There is some additional work involved with drawing up each template,
+so you might think that this is not a worthwhile tradeoff. 
+            </p><p>
+But there are reasons why using templates today may benefit a project
+tomorrow.
+            </p>
+            <p>
+License families share important legal qualities. In the future, it should 
+be possible to
+automate some licensing policy checks but only if licenses are
+categorised in a form which enables automated reasoning.
+Using a template for all members of a family is likely to help.
+            </p>
+            <p>
+Read more about license families <a href='#what-is-license-family'>here</a>.
+            </p>
+            
+        </answer>
+    </faq>
+
     
     <faq id='sample-meta-data'>
         <question>Are any samples available?</question>
@@ -673,6 +704,15 @@ your name, organisation and the year of 
 licenses of this sort a <em>license family</em> to emphasis that the text is
 a template from which instances of the licenses are created by parameterisation.
 </p>
+<p>
+Each family shares the share legal qualities, typically differing only in details 
+related
+to the act of publication. Knowing that a license belongs to a family allows
+knowledge about that family to be applied without extensive analysis of the text.
+So, for example, even though BSD License (2 Clause) texts differ we can confidently
+state that each is an 
+<a href='#what-is-an-open-source-license'>Open Source License</a>. 
+</p>
             <p>
 Learn how Whisker supports license families <a href='#how-license-family'>here</a>.
             </p>