creadur-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r1405335 [2/2] - in /creadur/whisker/trunk/src/site: ./ apt/ apt/examples/ fml/
Date Sat, 03 Nov 2012 13:55:40 GMT
Modified: creadur/whisker/trunk/src/site/apt/examples/license-family.apt
URL: http://svn.apache.org/viewvc/creadur/whisker/trunk/src/site/apt/examples/license-family.apt?rev=1405335&r1=1405334&r2=1405335&view=diff
==============================================================================
--- creadur/whisker/trunk/src/site/apt/examples/license-family.apt (original)
+++ creadur/whisker/trunk/src/site/apt/examples/license-family.apt Sat Nov  3 13:55:39 2012
@@ -1,5 +1,5 @@
   ------
-  Parameterising a Template for a License Family  
+  Parameterising a Template for a License Family
   ------
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ~~
@@ -18,7 +18,7 @@
 ~~  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
 ~~  KIND, either express or implied.  See the License for the
 ~~  specific language governing permissions and limitations
-~~  under the License.    
+~~  under the License.
 ~~
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -26,80 +26,80 @@ Parameterising a Template for a License 
 
  {{{http://creadur.apache.org/whisker} Apache Whisker}} is based around
  {{{../meta-data.html}meta-data}} describing the licensing qualities
- of documents included within 
+ of documents included within
  {{{../faq.html#complex-software-applications}complex software distributions}}.
- Whisker just helps to maintain information more efficiently, and is 
+ Whisker just helps to maintain information more efficiently, and is
  {{{../faq.html#what-whisker-is-not}no substitute}}
  for solid legal work.
  Learn about copyright and software licensing {{{../faq.html#more-resources'}here}}.
- 
+
  For this example, we'll add the meta-data for a third party work whose
- license is parameterised using a 
- {{{../faq.html#what-is-license-family}license family}} template, 
- featuring the 
-    {{{http://opensource.org/licenses/BSD-2-Clause}BSD (2 Clause) license}}  
- 
+ license is parameterised using a
+ {{{../faq.html#what-is-license-family}license family}} template,
+ featuring the
+    {{{http://opensource.org/licenses/BSD-2-Clause}BSD (2 Clause) license}}
+
  If this isn't quite what you're looking for, take a look at:
- 
+
    * {{{./in-5-mins.html}Whisker in 5 minutes}}, an MIT licensed project
-   
-   * including a 3rd Party work licensed by 
-   
+
+   * including a 3rd Party work licensed by
+
        * an {{{./3rd-party-individual.html}individual}}
 
-       * a for- or non-profit 
+       * a for- or non-profit
          {{{./3rd-party-corporate.html}corporation}}
-       
+
        * an {{{./3rd-party-group.html}informal group}}
-       
- 
- 
+
+
+
   or dive into sample meta-data:
- 
+
    * {{{./james.xml} Apache James}}
 
    * {{{./public-domain.xml} Public Domain}}
 
-   * {{{./template-license.xml} Template License}} 
-   
+   * {{{./template-license.xml} Template License}}
+
    * {{{./license-family-sample.xml}License Family}}
-   
+
    * Whisker In 5 Minutes featuring the {{{./in-5-mins-sample.xml}MIT License}}
-   
-   * distributing work licensed from 
-      
+
+   * distributing work licensed from
+
       * an {{{./3rd-party-individual-sample.xml} individual maintainer}}
-      
+
       * a for- or non-profit {{{./3rd-party-corporate-sample.xml}corporation}}
 
       * an informal {{{./3rd-party-group-sample.xml}group}}
-  
- 
- If you're using an IDE then see the 
-  {{{../meta-data.html}meta data reference}} for a 
-  {{{../faq.html#why-dtd}DTD}}. 
-  
- If you have 
-  any questions, please try the {{{../faq.html}FAQ}} before asking on the 
+
+
+ If you're using an IDE then see the
+  {{{../meta-data.html}meta data reference}} for a
+  {{{../faq.html#why-dtd}DTD}}.
+
+ If you have
+  any questions, please try the {{{../faq.html}FAQ}} before asking on the
   {{{../mail-lists.html}mail lists}}.
- 
+
 * The Story So Far
 
-  Let's assume <<<foo>>> is a simple project, 
-  with a single original source file: <<<HelloWorld.py>>>.  
+  Let's assume <<<foo>>> is a simple project,
+  with a single original source file: <<<HelloWorld.py>>>.
   The source for <<<foo>>> looks something like:
 
 +---------------------------------------+
-  foo--| 
+  foo--|
        | HelloWorld.py
        | LICENSE
 +---------------------------------------+
 
 ** Starting Definitions
 
-  Whisker describes each {{{../faq.html#what-is-a-license}license}}, 
-  {{{../faq.html#what-notice}notice}} 
-  and {{{../faq.html#what-is-org}organisation}} once 
+  Whisker describes each {{{../faq.html#what-is-a-license}license}},
+  {{{../faq.html#what-notice}notice}}
+  and {{{../faq.html#what-is-org}organisation}} once
   above, and then {{{../faq.html#why-ids}references by id}} below. So, the meta-data for
   project <<<foo>>> is structured along these lines:
 
@@ -115,11 +115,11 @@ Parameterising a Template for a License 
     ...
 +---------------------------------------+
 
-  Let's say that the 
+  Let's say that the
   {{{http://www.apache.org/licenses/LICENSE-2.0.html}Apache License, Version 2}}
-  is the {{{../faq.html#what-is-primary}primary license}} 
-  for the project, but <<<foo>>> opts not to 
-  {{{../faq.html#notice-needed-for-al2}include a primary notice}}. 
+  is the {{{../faq.html#what-is-primary}primary license}}
+  for the project, but <<<foo>>> opts not to
+  {{{../faq.html#notice-needed-for-al2}include a primary notice}}.
   The text for this license is included in <<<licenses>>> above,
   and this data is referenced by <<<id>>> as <<<primary-license>>> below:
 
@@ -127,9 +127,9 @@ Parameterising a Template for a License 
 <manifest>
     <!-- Definitions -->
     <licenses>
-        <license 
-            name='Apache License, Version 2' 
-            id='osi:AL2' 
+        <license
+            name='Apache License, Version 2'
+            id='osi:AL2'
             url='http://www.apache.org/licenses/LICENSE-2.0.txt'>
 <text>
                                  Apache License
@@ -319,21 +319,21 @@ Parameterising a Template for a License 
     ...
 +---------------------------------------+
 
-  Let's assume that our project <<<foo>>> is here at Apache. So the 
+  Let's assume that our project <<<foo>>> is here at Apache. So the
   {{{../faq.html#what-is-primary}primary organisation}} is the
-  {{{http://www.apache.org/foundation}Apache Software Foundation}}. 
-  This organisation is described once in <<<organisations>>> (above) then 
+  {{{http://www.apache.org/foundation}Apache Software Foundation}}.
+  This organisation is described once in <<<organisations>>> (above) then
   referenced by id as the
-  <<<primary-organisation>>> (below). 
+  <<<primary-organisation>>> (below).
 
 +---------------------------------------+
 <manifest>
     ...
     <organisations>
-        <organisation 
-            id='apache.org' 
-            name='The Apache Software Foundation' 
-            url='http://www.apache.org/'/>  
+        <organisation
+            id='apache.org'
+            name='The Apache Software Foundation'
+            url='http://www.apache.org/'/>
     </organisations>
     ...
     <primary-organisation id='apache.org'/>
@@ -341,13 +341,13 @@ Parameterising a Template for a License 
 +---------------------------------------+
 
 ** Starting Contents
-  
+
   Let's assume that the distribution for <<<foo>>> just contains the single
-  source file <<<HelloWorld.py>>> (plus legal documentation generated by Whisker), 
+  source file <<<HelloWorld.py>>> (plus legal documentation generated by Whisker),
   like this:
 
 +---------------------------------------+
-  foo--| 
+  foo--|
        | HelloWorld.py
 +---------------------------------------+
 
@@ -365,90 +365,90 @@ Parameterising a Template for a License 
     </within>
 </manifest>
 +---------------------------------------+
-  
-   It is essential that the <<<id>>> attributes in the <<<with-license>>> 
+
+   It is essential that the <<<id>>> attributes in the <<<with-license>>>
    and <<<by-organisation>>> elements match the ids assigned above. This
    allows the details entered above to be re-used consistently.
-  
+
 * Adding A Third Party Work to the Distribution
 
   Let's add <<<boo.png>>> to the distribution,
   licensed with the
-  {{{http://opensource.org/licenses/BSD-2-Clause}BSD (2 Clause) license}} 
+  {{{http://opensource.org/licenses/BSD-2-Clause}BSD (2 Clause) license}}
   from the (hypothetical) <Example Project>. The license shipped is
-  
+
 +---------------------------------------+
   Copyright (c) 2000-2010 The Example Project. All rights reserved.
 
-Redistribution and use in source and binary forms, with or without modification, 
+Redistribution and use in source and binary forms, with or without modification,
 are permitted provided that the following conditions are met:
 
-    1. Redistributions of source code must retain the above copyright notice, 
+    1. Redistributions of source code must retain the above copyright notice,
        this list of conditions and the following disclaimer.
-    
-    2. Redistributions in binary form must reproduce the above copyright notice, 
-       this list of conditions and the following disclaimer in the documentation 
+
+    2. Redistributions in binary form must reproduce the above copyright notice,
+       this list of conditions and the following disclaimer in the documentation
        and/or other materials provided with the distribution.
 
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND 
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 
-IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, 
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, 
-BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 
-DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY 
-OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING 
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, 
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
+OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
 EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 +---------------------------------------+
 
-  Consulting the 
+  Consulting the
   {{{http://opensource.org/licenses/index.html}open source initiative}},
-  we find this corresponds to the 
+  we find this corresponds to the
   {{{http://opensource.org/licenses/BSD-2-Clause}BSD (2 Clause) license}}
   template
- 
+
 +---------------------------------------+
 Copyright (c) <YEAR>, <OWNER>
 All rights reserved.
 
-Redistribution and use in source and binary forms, with or without modification, 
+Redistribution and use in source and binary forms, with or without modification,
 are permitted provided that the following conditions are met:
 
-    * Redistributions of source code must retain the above copyright notice, 
+    * Redistributions of source code must retain the above copyright notice,
       this list of conditions and the following disclaimer.
-      
-    * Redistributions in binary form must reproduce the above copyright notice, 
-      this list of conditions and the following disclaimer in the documentation 
+
+    * Redistributions in binary form must reproduce the above copyright notice,
+      this list of conditions and the following disclaimer in the documentation
       and/or other materials provided with the distribution.
 
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND 
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 
-IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, 
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, 
-BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 
-DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY 
-OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING 
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, 
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
+OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
 EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 +---------------------------------------+
 
   Yes, the license is indeed part of the BSD (2 Clause) license family.
   Checking <<<licenses>>> verifies that we need to add this as a new
-  template <<<license>>> with two parameters. We have a 
-  {{{../faq.html#parameter-name-freedom}free choice}} 
+  template <<<license>>> with two parameters. We have a
+  {{{../faq.html#parameter-name-freedom}free choice}}
   of <<<parameter-name>>> but it's conventional to reuse (where possible)
   standard names - in this case <<<YEAR>>> and <<<OWNER>>>.
-  Define them within in a <<<template>>> element and then values   
+  Define them within in a <<<template>>> element and then values
   will be substituted for <<<$\{YEAR\}>>> and <<<$\{OWNER\}>>> within
   the text.
-  
+
 +---------------------------------------+
 <manifest>
         ...
-        <license 
-            id='osi:BSD2' 
+        <license
+            id='osi:BSD2'
             name='BSD (2 Clause)'
             url='http://opensource.org/licenses/BSD-2-Clause'
             >
@@ -460,49 +460,49 @@ EVEN IF ADVISED OF THE POSSIBILITY OF SU
 Copyright (c) ${YEAR}, ${OWNER}
 All rights reserved.
 
-Redistribution and use in source and binary forms, with or without modification, 
+Redistribution and use in source and binary forms, with or without modification,
 are permitted provided that the following conditions are met:
 
-    * Redistributions of source code must retain the above copyright notice, 
+    * Redistributions of source code must retain the above copyright notice,
       this list of conditions and the following disclaimer.
-      
-    * Redistributions in binary form must reproduce the above copyright notice, 
-      this list of conditions and the following disclaimer in the documentation 
+
+    * Redistributions in binary form must reproduce the above copyright notice,
+      this list of conditions and the following disclaimer in the documentation
       and/or other materials provided with the distribution.
 
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND 
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 
-IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, 
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, 
-BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 
-DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY 
-OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING 
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, 
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
+OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
 EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
             </text>
         </license>
         ...
 +---------------------------------------+
 
- Comparing the text of the license instance with the template (we just created), 
- we find that <<<YEAR>>> should be <2000-2010> and 
- <<<OWNER>>> should be <The Example Project>. We'll need to 
+ Comparing the text of the license instance with the template (we just created),
+ we find that <<<YEAR>>> should be <2000-2010> and
+ <<<OWNER>>> should be <The Example Project>. We'll need to
  add these later as <<<license-parameters>>>.
- We note the {{{../faq.html#id-freedom}id chosen}} 
- - <<<osi:BSD2>>> - for {{{../faq.html#why-ids}later}}. 
-  
-
-** Add Organisation  
-
-  After verifying that <The Example Project> isn't already 
-  described in the <<<organisations>>>, we add this new 
-  <<<organisation>>>, noting the 
-  {{{../faq.html#id-freedom}id chosen}} for 
-  {{{../faq.html#why-ids}later}}. 
-  (Read more about adding organisations 
+ We note the {{{../faq.html#id-freedom}id chosen}}
+ - <<<osi:BSD2>>> - for {{{../faq.html#why-ids}later}}.
+
+
+** Add Organisation
+
+  After verifying that <The Example Project> isn't already
+  described in the <<<organisations>>>, we add this new
+  <<<organisation>>>, noting the
+  {{{../faq.html#id-freedom}id chosen}} for
+  {{{../faq.html#why-ids}later}}.
+  (Read more about adding organisations
   {{{../faq.html#add-org-example}here}}.)
-  
+
 +---------------------------------------+
 <manifest>
     <organisations>
@@ -522,19 +522,19 @@ EVEN IF ADVISED OF THE POSSIBILITY OF SU
   suppose that the contents of the new distribution are:
 
 +---------------------------------------+
-  foo--| 
+  foo--|
        | HelloWorld.py
        | boo.png         <- Newly added
 +---------------------------------------+
 
-  We need to add <<<boo.png>>> to the 
-  {{{../faq.html#how-contents}contents}}, 
+  We need to add <<<boo.png>>> to the
+  {{{../faq.html#how-contents}contents}},
   into a new group of resources
-  within the {{{../faq.html#how-root-dir}root directory}}. 
-  Within each <<<dir>>>, resources contained within the 
+  within the {{{../faq.html#how-root-dir}root directory}}.
+  Within each <<<dir>>>, resources contained within the
   directory are grouped <<<with-license>>>. The new resource
   - <<<boo.png>>> - is the first with the <BSD (2 Clause) License>,
-  so we need to add a new <<<with-license>>> with <<<id>>> 
+  so we need to add a new <<<with-license>>> with <<<id>>>
   attribute <<<osi:BSD2>>>, the <<<id>>> we chose when we
   added the license earlier.
 
@@ -546,7 +546,7 @@ EVEN IF ADVISED OF THE POSSIBILITY OF SU
         </with-license>
         ...
 +---------------------------------------+
-  
+
   The <<<license>>> we added earlier is a template,
   so we need to include the parameter values
   as <<<license-parameters>>>. These will be substituted
@@ -571,13 +571,13 @@ EVEN IF ADVISED OF THE POSSIBILITY OF SU
         </with-license>
         ...
 +---------------------------------------+
-  
+
   Within each license, resources are grouped by organisation.
   So the <<<by-organisation>>> containing
-  the new resource named <<<boo.png>>> needs to 
-  {{{../faq.html#why-ids}refer}} (by <<<id>>>) 
-  to the <<<organisation>>> we added earlier - <<<example.org>>>. 
-   
+  the new resource named <<<boo.png>>> needs to
+  {{{../faq.html#why-ids}refer}} (by <<<id>>>)
+  to the <<<organisation>>> we added earlier - <<<example.org>>>.
+
 +---------------------------------------+
     ...
     <within dir='.'>
@@ -601,11 +601,11 @@ EVEN IF ADVISED OF THE POSSIBILITY OF SU
 +---------------------------------------+
 
   That's about all there is to adding <<<boo.png>>>,
-  a new BSD (2 Clause) licensed resource. 
+  a new BSD (2 Clause) licensed resource.
 
 * And Finally
 
-  We end up with this meta-data 
+  We end up with this meta-data
   ({{{./license-family-sample.xml}open}}
   as an annotated sample):
 
@@ -614,9 +614,9 @@ EVEN IF ADVISED OF THE POSSIBILITY OF SU
 <manifest>
     <!-- Definitions -->
     <licenses>
-        <license 
-            name='Apache License, Version 2' 
-            id='osi:AL2' 
+        <license
+            name='Apache License, Version 2'
+            id='osi:AL2'
             url='http://www.apache.org/licenses/LICENSE-2.0.txt'>
 <text>
                                  Apache License
@@ -797,8 +797,8 @@ EVEN IF ADVISED OF THE POSSIBILITY OF SU
    END OF TERMS AND CONDITIONS
 </text>
         </license>
-        <license 
-            id='osi:BSD2' 
+        <license
+            id='osi:BSD2'
             name='BSD (2 Clause)'
             url='http://opensource.org/licenses/BSD-2-Clause'
             >
@@ -810,35 +810,35 @@ EVEN IF ADVISED OF THE POSSIBILITY OF SU
 Copyright (c) ${YEAR}, ${OWNER}
 All rights reserved.
 
-Redistribution and use in source and binary forms, with or without modification, 
+Redistribution and use in source and binary forms, with or without modification,
 are permitted provided that the following conditions are met:
 
-    * Redistributions of source code must retain the above copyright notice, 
+    * Redistributions of source code must retain the above copyright notice,
       this list of conditions and the following disclaimer.
-      
-    * Redistributions in binary form must reproduce the above copyright notice, 
-      this list of conditions and the following disclaimer in the documentation 
+
+    * Redistributions in binary form must reproduce the above copyright notice,
+      this list of conditions and the following disclaimer in the documentation
       and/or other materials provided with the distribution.
 
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND 
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 
-IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, 
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, 
-BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 
-DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY 
-OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING 
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, 
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
+OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
 EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
             </text>
         </license>
     </licenses>
     <notices/>
     <organisations>
-        <organisation 
-            id='apache.org' 
-            name='The Apache Software Foundation' 
-            url='http://www.apache.org/'/>  
+        <organisation
+            id='apache.org'
+            name='The Apache Software Foundation'
+            url='http://www.apache.org/'/>
         <organisation
            id='example.org'
            name='The Example Project'
@@ -846,9 +846,9 @@ EVEN IF ADVISED OF THE POSSIBILITY OF SU
         />
     </organisations>
     <primary-license id='osi:AL2'/>
-    <primary-notice/>        
+    <primary-notice/>
     <primary-organisation id='apache.org'/>
-        
+
     <!-- Contents -->
     <within dir='.'>
         <with-license id='osi:AL2'>
@@ -874,11 +874,11 @@ EVEN IF ADVISED OF THE POSSIBILITY OF SU
     </within>
 </manifest>
 +---------------------------------------+
-   
-    From this meta-data, Whisker (either from the 
+
+    From this meta-data, Whisker (either from the
     {{{../apache-whisker-cli/index.html}command line}} or
-    integrated into a 
-    {{{../apache-whisker-plugin4maven/index.html}Maven build}}) 
+    integrated into a
+    {{{../apache-whisker-plugin4maven/index.html}Maven build}})
     generates a <<<LICENSE>>> similar to:
 
 +---------------------------------------+
@@ -1065,34 +1065,33 @@ EVEN IF ADVISED OF THE POSSIBILITY OF SU
 This distribution contains third party resources.
 Within the . directory
     licensed under the BSD (2 Clause) http://opensource.org/licenses/BSD-2-Clause  (as follows)
- 
-            
+
+
             Copyright (c) 2000-2010, The Example Project
             All rights reserved.
-            
-            Redistribution and use in source and binary forms, with or without modification, 
+
+            Redistribution and use in source and binary forms, with or without modification,
             are permitted provided that the following conditions are met:
-            
-                * Redistributions of source code must retain the above copyright notice, 
+
+                * Redistributions of source code must retain the above copyright notice,
                   this list of conditions and the following disclaimer.
-                  
-                * Redistributions in binary form must reproduce the above copyright notice, 
-                  this list of conditions and the following disclaimer in the documentation 
+
+                * Redistributions in binary form must reproduce the above copyright notice,
+                  this list of conditions and the following disclaimer in the documentation
                   and/or other materials provided with the distribution.
-            
-            THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND 
-            ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 
-            WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 
-            IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, 
-            INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, 
-            BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 
-            DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY 
-            OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING 
-            NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, 
+
+            THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+            ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+            WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+            IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
+            INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+            BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+            DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
+            OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+            NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
             EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-                            
-        from The Example Project  http://example.org/ 
+
+        from The Example Project  http://example.org/
             boo.png
 
 +---------------------------------------+
-   
\ No newline at end of file

Modified: creadur/whisker/trunk/src/site/apt/index.apt
URL: http://svn.apache.org/viewvc/creadur/whisker/trunk/src/site/apt/index.apt?rev=1405335&r1=1405334&r2=1405335&view=diff
==============================================================================
--- creadur/whisker/trunk/src/site/apt/index.apt (original)
+++ creadur/whisker/trunk/src/site/apt/index.apt Sat Nov  3 13:55:39 2012
@@ -18,43 +18,43 @@
 ~~  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
 ~~  KIND, either express or implied.  See the License for the
 ~~  specific language governing permissions and limitations
-~~  under the License.    
+~~  under the License.
 ~~
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 What Is Apache Whisker?
 
-  Apache Whisker assists assembled applications maintain correct legal 
-  documentation. 
+  Apache Whisker assists assembled applications maintain correct legal
+  documentation.
 
   Apache Whisker is part of the {{{http://creadur.apache.org}Apache Creadur}}
-  language- and build-agnostic suite of tools for auditing and comprehending 
-  software distributions. Our community develops 
+  language- and build-agnostic suite of tools for auditing and comprehending
+  software distributions. Our community develops
   {{{http://www.opensource.org/} open source software}} the
   {{{http://www.apache.org/foundation/how-it-works.html} Apache Way}}.
-  
-  Whisker just helps to maintain information more efficiently, and is 
-  {{{./faq.html#what-whisker-is-not}no substitute}} 
-  for solid legal work. No part of our documentation is 
-  {{{./faq.html#what-this-documentation-is-not}legal advice}}, 
-  and readers are assumed to have a practical understanding of the relevant laws. 
-  
+
+  Whisker just helps to maintain information more efficiently, and is
+  {{{./faq.html#what-whisker-is-not}no substitute}}
+  for solid legal work. No part of our documentation is
+  {{{./faq.html#what-this-documentation-is-not}legal advice}},
+  and readers are assumed to have a practical understanding of the relevant laws.
+
   Learn about copyright and software licensing {{{../faq.html#more-resources'}here}}.
 
 * How Can Whisker Help?
 
  Whisker can
- 
+
   * verify - checking meta-data quality against a distribution
 
   * generate - legal documents from meta-data
- 
+
  Particular useful for complex assembled applications.
-   
+
 ** What's An Assembled Application?
 
   An assembled application is composed from libraries and frameworks.
-  
+
   Read more {{{./faq.html#complex-software-applications}here}}.
 
 ** What Legal Documentation?
@@ -62,65 +62,65 @@ What Is Apache Whisker?
   NOTICE and LICENSE are supported examples.
 
 ** How Does Whisker Work?
- 
-  Licensing {{{./meta-data.html} meta-data}} describes the legal qualities of the components 
-  assembled.  
- 
+
+  Licensing {{{./meta-data.html} meta-data}} describes the legal qualities of the components
+  assembled.
+
 
 * How Can I Use Whisker?
 
- * From the {{{./apache-whisker-cli/index.html} command line}} 
- 
+ * From the {{{./apache-whisker-cli/index.html} command line}}
+
  * As a {{{./apache-whisker-plugin4maven/index.html} plugin for Maven}}
 
 * Getting Started
 
- Browse the {{{./xref/index.html}source}}, 
+ Browse the {{{./xref/index.html}source}},
  read the {{{./apidocs/index.html}javadocs}},
  take a look
- 
+
    * {{{./examples/in-5-mins.html}Whisker In 5 Minutes}}
- 
- 
+
+
  dive into sample meta-data
- 
+
    * {{{./examples/james.xml} Apache James}}
 
    * {{{./examples/public-domain.xml} Public Domain}}
 
    * {{{./examples/template-license.xml} Template License}}
-   
+
    * {{{./examples/license-family-sample.xml}License Family}}
-   
-   * Whisker In 5 Minutes featuring the 
+
+   * Whisker In 5 Minutes featuring the
      {{{./examples/in-5-mins-sample.xml}MIT License}}
-   
-   * distributing work licensed from 
-      
+
+   * distributing work licensed from
+
       * an {{{./examples/3rd-party-individual-sample.xml} individual maintainer}}
-      
+
       * a for- or non-profit {{{./examples/3rd-party-corporate-sample.xml}corporation}}
 
       * an informal {{{./examples/3rd-party-group-sample.xml}group}}
-      
+
  or browse the {{{./faq.html}FAQ}}.
 
- A warm welcome is guaranteed on our 
+ A warm welcome is guaranteed on our
  {{{../mail-lists.html}mail lists}}.
-      
+
 ** More Examples
- 
- * Including a 3rd Party work licensed by 
-  
+
+ * Including a 3rd Party work licensed by
+
     * an {{{./examples/3rd-party-individual.html}individual}}
- 
+
     * a for- or non-profit {{{./examples/3rd-party-corporate.html}corporation}}
-    
+
     * an {{{./examples/3rd-party-group.html}informal group}}
-    
- * {{{./examples/license-family.html}Parameterising a template}} for a 
-     {{{./faq.html#what-is-license-family}license family}}, 
-     featuring the 
+
+ * {{{./examples/license-family.html}Parameterising a template}} for a
+     {{{./faq.html#what-is-license-family}license family}},
+     featuring the
      {{{http://opensource.org/licenses/BSD-2-Clause}BSD (2 Clause) license}}
- 
- 
+
+

Modified: creadur/whisker/trunk/src/site/fml/faq.fml
URL: http://svn.apache.org/viewvc/creadur/whisker/trunk/src/site/fml/faq.fml?rev=1405335&r1=1405334&r2=1405335&view=diff
==============================================================================
--- creadur/whisker/trunk/src/site/fml/faq.fml (original)
+++ creadur/whisker/trunk/src/site/fml/faq.fml Sat Nov  3 13:55:39 2012
@@ -15,10 +15,10 @@
   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
   KIND, either express or implied.  See the License for the
   specific language governing permissions and limitations
-  under the License.    
+  under the License.
 -->
 <faqs id="FAQ" title="Frequently Asked Questions">
-  <part id="meta-data"> 
+  <part id="meta-data">
     <title>Meta Data</title>
     <faq id="why-ids">
       <question>Why Reference Licenses, Notices and Organisations by ID?</question>
@@ -29,7 +29,7 @@
       <p>
       Each license, notice and organisation should be described once, and then
       referenced by <code>id</code>. For complex projects, this reduces duplication
-      and eases maintenance.   
+      and eases maintenance.
       </p>
       </answer>
     </faq>
@@ -38,7 +38,7 @@
       <answer>
       <p>
 IDs need to be unique (within the document)
-but otherwise you are free. 
+but otherwise you are free.
       </p>
       </answer>
     </faq>
@@ -49,14 +49,14 @@ but otherwise you are free. 
       Yes, but...
       </p>
       <p>
-Whisker adopts the convention that <code>name</code> attributes 
+Whisker adopts the convention that <code>name</code> attributes
 (for example, on <code>license</code> elements) are used
 for presentation, so it is strong recommended that a suitably
-human-readable title is chosen. 
+human-readable title is chosen.
       </p>
       <p>
 Where possibly, pick the standard name for this license: either the
-title within the text, or the name adopted by a standards organisation 
+title within the text, or the name adopted by a standards organisation
 for example  <a href='http://www.opensource.org'>The Open Source Initiative</a>.
       </p>
       </answer>
@@ -68,7 +68,7 @@ for example  <a href='http://www.opensou
 Whisker adopts the convention that <code>url</code> attributes
 (for example, on <code>license</code> elements) are used to present
 a reference location for a reader. It is recommended that a
-standard URL is given, where possible, for example from the 
+standard URL is given, where possible, for example from the
 <a href='http://www.opensource.org'>The Open Source Initiative</a>.
        </p>
       </answer>
@@ -80,7 +80,7 @@ standard URL is given, where possible, f
       Yes
       </p>
       <p>
-Where possible, we recommend reusing the name adopted by a standards organisation, 
+Where possible, we recommend reusing the name adopted by a standards organisation,
 for example  <a href='http://www.opensource.org'>The Open Source Initiative</a>.
       </p>
       </answer>
@@ -97,60 +97,60 @@ for example  <a href='http://www.opensou
         <question>What do you mean by 'primary'?</question>
         <answer>
             <p>
-Whisker documentation often talks about a <em>primary license</em>, 
+Whisker documentation often talks about a <em>primary license</em>,
 a <em>primary organisation</em> and so on.
-The meta-data contains elements like <code>primary-license</code> and 
+The meta-data contains elements like <code>primary-license</code> and
 <code>primary-notice</code>. Though the intended meaning might accord
-with intuition, a more precise description may help to deepen 
+with intuition, a more precise description may help to deepen
 understanding of software licensing.
             </p>
             <p>
-By <em>primary</em>, we mean the 
+By <em>primary</em>, we mean the
 main license, notice or organisation associated with the project.
 Take, for example, a project here at <a href='http://www.apache.org'>Apache</a>.
-In this case, the primary license would be 
+In this case, the primary license would be
 <a href='http://www.apache.org/licenses/LICENSE-2.0.html'>The Apache License, Version 2</a>
-(<abbr title='The Apache License, Version 2'><code>AL2</code></abbr>) 
-and the primary organisation 
+(<abbr title='The Apache License, Version 2'><code>AL2</code></abbr>)
+and the primary organisation
 <a href='http://www.apache.org/foundation/'>The Apache Software Foundation</a>.
             </p>
             <p>
-The <em>primary license</em> should cover most of the original content contributed 
-by the project to the software distributed. Apache, for example, 
-<a href='http://www.apache.org/legal/src-headers.html'>insists</a> that 
-original source is 
+The <em>primary license</em> should cover most of the original content contributed
+by the project to the software distributed. Apache, for example,
+<a href='http://www.apache.org/legal/src-headers.html'>insists</a> that
+original source is
 <abbr title='The Apache License, Version 2'><code>AL2</code></abbr> licensed.
-The <em>primary organisation</em> should be the legal entity 
-issuing the primary license. Apache, for example, uses 
+The <em>primary organisation</em> should be the legal entity
+issuing the primary license. Apache, for example, uses
 <a href='http://www.apache.org/licenses/index.html#clas'>contributor license agreements</a>,
 <a href='http://www.apache.org/licenses/index.html#grants'>grants</a> and
 <code><abbr title='The Apache License, Version 2'>AL2</abbr> Section 5</code>
 to allow the foundation to issue open source licenses.
-            </p>            
+            </p>
         </answer>
     </faq>
     <faq id='primary-license-organisation-relationship'>
         <question>What is the relationship between the Primary License and the Primary Organsation?</question>
         <answer>
             <p>
-The <em>primary license</em> covers most of the original content contributed 
-by the project to the software distributed. Apache, for example, 
-<a href='http://www.apache.org/legal/src-headers.html'>insists</a> that 
-original source is 
+The <em>primary license</em> covers most of the original content contributed
+by the project to the software distributed. Apache, for example,
+<a href='http://www.apache.org/legal/src-headers.html'>insists</a> that
+original source is
 <abbr title='The Apache License, Version 2'><code>AL2</code></abbr> licensed.
             </p>
             <p>
-The <em>primary organisation</em> should be the legal entity 
-issuing the <em>primary license</em>. Apache, for example, uses 
+The <em>primary organisation</em> should be the legal entity
+issuing the <em>primary license</em>. Apache, for example, uses
 <a href='http://www.apache.org/licenses/index.html#clas'>contributor license agreements</a>,
 <a href='http://www.apache.org/licenses/index.html#grants'>grants</a> and
 <code><abbr title='The Apache License, Version 2'>AL2</abbr> Section 5</code>
-to allow the foundation to issue open source licenses. Alternatively 
-(as practiced by 
+to allow the foundation to issue open source licenses. Alternatively
+(as practiced by
 <a href='http://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html#Copyright-Papers'>GNU</a>,
-for example) 
+for example)
 copyright may be assigned to the organisation by its contributions.
-            </p>            
+            </p>
         </answer>
     </faq>
     <faq id='what-is-org'>
@@ -159,12 +159,12 @@ copyright may be assigned to the organis
             <p>
 Whisker uses <em>organisation</em> to identify and describe groups or individuals
 who license the third party works distributed. This includes a wide variety of
-entities, for example 
+entities, for example
             </p>
             <ul>
-<li>non-profit corporations such as 
-<a href='http://www.apache.org/foundation'>The Apache Software Foundation</a>, 
-<a href='http://www.fsf.org/about/'>The Free Software Foundation</a> and 
+<li>non-profit corporations such as
+<a href='http://www.apache.org/foundation'>The Apache Software Foundation</a>,
+<a href='http://www.fsf.org/about/'>The Free Software Foundation</a> and
 <a href='http://www.gnome.org/foundation/'>The GNOME Foundation</a>;
 </li>
 <li>
@@ -172,14 +172,14 @@ for-profit corporations such as
 VMWare Inc., Google Inc. and IBM Corporation;
 </li>
 <li>
-academic institutions such as the 
+academic institutions such as the
 <a href='http://berkeley.edu/'>University of California, Berkeley</a>,
 the
 <a href='http://web.mit.edu/'>Massachusetts Institute of Technology</a> and
-<a href='http://osuosl.org/'>Oregon State University</a>; 
+<a href='http://osuosl.org/'>Oregon State University</a>;
 </li>
 <li>
-groups and collectives such as 
+groups and collectives such as
 <a href='http://www.bouncycastle.org'>The Legion of the Bouncy Castle</a> and
 <a href='http://www.joda.org'>Joda</a>
 </li>
@@ -193,7 +193,7 @@ groups and collectives such as 
             <p>
  See <a href='#add-org-example'>here</a> for examples.
             </p>
-        </answer>    
+        </answer>
     </faq>
     <faq id='where-is-dtd'>
         <question>Does an organisation have to be a formal corporation or company?</question>
@@ -202,13 +202,13 @@ groups and collectives such as 
             No
             </p>
             <p>
-            As far as Whisker is concerned, 
+            As far as Whisker is concerned,
             a wide variety of entities are organisations,
             as well as some individual maintainers.
             </p>
             <p>
-            Read more <a href='#what-is-org'>here</a> and see comments 
-            on <a href='#third-party-ad-hoc'>informal groups</a>. 
+            Read more <a href='#what-is-org'>here</a> and see comments
+            on <a href='#third-party-ad-hoc'>informal groups</a>.
             </p>
         </answer>
     </faq>
@@ -216,15 +216,15 @@ groups and collectives such as 
         <question>What about third party software licensed from an individual?</question>
         <answer>
             <p>
-As far as Whisker is concerned, each individual maintainer is an  
-organisation.  
+As far as Whisker is concerned, each individual maintainer is an
+organisation.
             </p>
             <p>
-            See this 
+            See this
             <a href='./examples/3rd-party-individual.html'>example</a>.
             </p>
             <p>
-            Read more <a href='#what-is-org'>here</a>. 
+            Read more <a href='#what-is-org'>here</a>.
             </p>
         </answer>
     </faq>
@@ -232,15 +232,15 @@ organisation.  
         <question>What about third party software licensed from a corporation?</question>
         <answer>
             <p>
-As far as Whisker is concerned, each corporation (whether non-profit or for-profit) is an  
+As far as Whisker is concerned, each corporation (whether non-profit or for-profit) is an
 organisation.
             </p>
             <p>
-            See this 
+            See this
             <a href='./examples/3rd-party-corporate.html'>example</a>.
             </p>
             <p>
-            Read more <a href='#what-is-org'>here</a>. 
+            Read more <a href='#what-is-org'>here</a>.
             </p>
         </answer>
     </faq>
@@ -249,16 +249,16 @@ organisation.
         <answer>
             <p>
 As far as Whisker is concerned, each group or collective is an organisation.
-You might want to check that the <a href='#licensor'>licensor</a> 
+You might want to check that the <a href='#licensor'>licensor</a>
 has the rights required to issue the license,
-though, before adding it to your distribution. 
+though, before adding it to your distribution.
             </p>
             <p>
-            See this 
+            See this
             <a href='./examples/3rd-party-group.html'>example</a>.
             </p>
             <p>
-            Read more <a href='#what-is-org'>here</a>.  
+            Read more <a href='#what-is-org'>here</a>.
             </p>
         </answer>
     </faq>
@@ -272,7 +272,7 @@ though, before adding it to your distrib
             Apologies to those tripped up by this choice
             </p>
         </answer>
-    </faq>    
+    </faq>
     <faq id='where-is-dtd'>
         <question>Is a DTD available?</question>
         <answer>
@@ -286,13 +286,13 @@ though, before adding it to your distrib
         <question>Why only a DTD?</question>
         <answer>
             <p>
-The <a href='http://www.xml.com/axml/target.html#dt-doctype'>DTD</a> is 
+The <a href='http://www.xml.com/axml/target.html#dt-doctype'>DTD</a> is
 aimed at IDE users and developers,
 and is not prescriptive but descriptive.
             </p>
             <p>
 For the present, schema validation is not enforced.
-If it were, probably a language like 
+If it were, probably a language like
 <a href='http://relaxng.org/'>Relax NG</a> would be chosen.
             </p>
         </answer>
@@ -301,13 +301,13 @@ If it were, probably a language like 
         <question>I prefer to use an IDE. Can it help me write the meta-data?</question>
         <answer>
             <p>
-            A DTD is available in the 
+            A DTD is available in the
             <a href='meta-data.html#Described_By_DTD'>meta data reference</a>,
-            which should be of some use. 
+            which should be of some use.
             </p>
             <p>
 There are currently no known plugins. If you know of a plugin please
-<a href='./mail-lists.html'>let us know</a> or 
+<a href='./mail-lists.html'>let us know</a> or
 <a href='./source-repository.html'>contribute a patch</a> for this documentation.
             </p>
         </answer>
@@ -322,8 +322,8 @@ There are currently no known plugins. If
             As in &lt;within dir='.'&gt;
             </p>
             <p>
-Read how directories are modeled <a href='#how-dir-model'>here</a>           
-            </p>            
+Read how directories are modeled <a href='#how-dir-model'>here</a>
+            </p>
         </answer>
     </faq>
     <faq id='how-dir-model'>
@@ -334,7 +334,7 @@ Read how directories are modeled <a href
  elements.
             </p>
             <p>
-Read why <a href='#why-dir-model'>here</a>           
+Read why <a href='#why-dir-model'>here</a>
             </p>
             <p>
 See how the root directory is modelled <a href='#how-root-dir'>here</a>
@@ -349,40 +349,40 @@ See how the root directory is modelled <
             </p>
             <p>
  Within a file system, the containment relationship between
- directories typically forms a natural tree. Modern file systems 
+ directories typically forms a natural tree. Modern file systems
  typically allow cyclic links only with special links (for example,
-  <code>symbolic links</code> in 
+  <code>symbolic links</code> in
   <a href='http://dbpedia.org/resource/Unix-like'>*nix</a>).
   Including these links would allow directory containment
   to become a graph. XML element containment forms a natural
-  tree structure, but representing a graph in XML requires 
+  tree structure, but representing a graph in XML requires
   links to break this structure.
-  This would introduce more complexity 
-  and more ways to make mistakes but little gain. 
+  This would introduce more complexity
+  and more ways to make mistakes but little gain.
             </p>
             <p>
-Read how directories are modeled <a href='#how-dir-model'>here</a>           
+Read how directories are modeled <a href='#how-dir-model'>here</a>
             </p>
             <p>
 See how the root directory is modelled <a href='#how-root-dir'>here</a>
             </p>
         </answer>
     </faq>
-    
+
     <faq id='how-contents'>
         <question>How are the contents of a distribution represented?</question>
         <answer>
             <p>
-Resources are grouped       
+Resources are grouped
             </p>
             <ul>
                 <li><code>by-organisation</code></li>
                 <li><code>with-license</code></li>
                 <li><code>within</code> a directory.</li>
             </ul>
-            <p> 
-The directory structure is not represented by 
-nesting <code>within</code> elements. These elements are simply listed. 
+            <p>
+The directory structure is not represented by
+nesting <code>within</code> elements. These elements are simply listed.
             </p>
             <p>
 See the <a href='#sample-meta-data'>samples</a> for examples.
@@ -394,7 +394,7 @@ See the <a href='#sample-meta-data'>samp
         <question>Are license families supported?</question>
         <answer>
             <p>
-Yes       
+Yes
             </p>
             <p>
 Add a template <code>license</code> and parameterise.
@@ -421,15 +421,15 @@ Read more about license families <a href
 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. 
+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. 
+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 
+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.
@@ -438,7 +438,7 @@ Using a template for all members of a fa
             <p>
 Read more about license families <a href='#what-is-license-family'>here</a>.
             </p>
-            
+
         </answer>
     </faq>
     <faq id='what-primary-copyright-notice'>
@@ -492,18 +492,18 @@ is positioned above the
         <question>When do I need to add a primary copyright notice?</question>
         <answer>
             <p>
-<a href='#what-is-license-family'>Template licenses</a> 
-(for example the 
+<a href='#what-is-license-family'>Template licenses</a>
+(for example the
 <a href='http://opensource.org/licenses/BSD-2-Clause'>BSD License 2 Clause</a>)
-typically includes a 
-parameterised copyright notice. Licenses 
+typically includes a
+parameterised copyright notice. Licenses
 <a href='#when-notice-needed'>with</a> a <code>NOTICE</code>
-(for example the 
+(for example the
 <a href='http://www.apache.org/licenses/LICENSE-2.0.html'>Apache License, Version 2</a>)
 usually include the copyright notice in the <code>NOTICE</code>.
             </p><p>
-Some other licenses (for example the 
-<a href='http://opensource.org/licenses/mit-license.php/'>MIT License</a>) 
+Some other licenses (for example the
+<a href='http://opensource.org/licenses/mit-license.php/'>MIT License</a>)
 conventionally include a copyright notice above the text:
 to use these licenses with Whisker, add a primary copyright notice
 and use the plain license text.
@@ -522,7 +522,7 @@ and use the plain license text.
         </answer>
     </faq>
 
-    
+
     <faq id='sample-meta-data'>
         <question>Are any samples available?</question>
         <answer>
@@ -533,9 +533,9 @@ and use the plain license text.
             See
             </p>
             <ul>
-                <li> 
-<a href='./examples/james.xml'>Apache James</a>, sample meta-data 
-for a complex open source application; 
+                <li>
+<a href='./examples/james.xml'>Apache James</a>, sample meta-data
+for a complex open source application;
                 </li>
                 <li>
 <a href='./examples/template-license.xml'>Template License</a>, an
@@ -543,56 +543,56 @@ annotated outline useful for new meta-da
                  </li>
                  <li>simple annotated educational samples for
                  <ul>
-                    <li> 
+                    <li>
 <a href='./examples/public-domain.xml'>public domain</a>
                     </li>
                     <li>
 <a href='./examples/license-family-sample.xml'>license family</a> using a template
                     </li>
-                    <li>                    
-Whisker In 5 Minutes featuring the 
+                    <li>
+Whisker In 5 Minutes featuring the
 <a href='./examples/in-5-mins-sample.xml'>MIT License</a>
                     </li>
                     <li>
-distributing work licensed from 
+distributing work licensed from
                         <ul>
-                            <li>                      
+                            <li>
 an <a href='./examples/3rd-party-individual-sample.xml'>individual maintainer</a>
                             </li><li>
 a for- or non-profit <a href='./examples/3rd-party-corporate-sample.xml'>corporation</a>
                             </li><li>
 an informal <a href='./examples/3rd-party-group-sample.xml'>group</a>
                             </li>
-                            
-                        </ul>                            
+
+                        </ul>
                     </li>
                  </ul>
                  </li>
             </ul>
         </answer>
     </faq>
-        
+
   </part>
-  <part id="generation"> 
+  <part id="generation">
     <title>Generating Licensing Documents</title>
     <faq id="when-notice">
       <question>When will a NOTICE be generated?</question>
       <answer>
-      <p>Whisker should generate a <code>NOTICE</code> document only when 
-      <a href='#when-notice-needed'>needed</a>. 
+      <p>Whisker should generate a <code>NOTICE</code> document only when
+      <a href='#when-notice-needed'>needed</a>.
       Examples include:</p>
       <ul>
         <li>when the primary notice is not empty; and</li>
         <li>when at least one distributed artifact requires an attribution.</li>
       </ul>
       <p>If you have a use case where an unnecessary <code>NOTICE</code> is generated,
-      or when a <code>NOTICE</code> isn't generated when it is needed please open an 
-      <a href='./issue-tracking.html'>issue</a> or let us know 
+      or when a <code>NOTICE</code> isn't generated when it is needed please open an
+      <a href='./issue-tracking.html'>issue</a> or let us know
       <a href='./mail-lists.html'>on list</a>.</p>
       </answer>
     </faq>
   </part>
-  <part id="licensing"> 
+  <part id="licensing">
     <title>Licensing</title>
        <faq id="what-whisker-is-not">
         <question>Will Whisker Automagically Solve my Licensing Problems?</question>
@@ -601,8 +601,8 @@ an informal <a href='./examples/3rd-part
             No
             </p>
             <p>
-Whisker is just an efficient way to maintain licensing documentation for 
-<a href='#complex-software-applications'>complex applications</a>. It is no 
+Whisker is just an efficient way to maintain licensing documentation for
+<a href='#complex-software-applications'>complex applications</a>. It is no
 substitute for accurate legal legwork.
             </p>
             <p>
@@ -619,7 +619,7 @@ Learn about copyright and software licen
             <p>
 This documentation guides users assumed to have a practical understanding of the relevant
 laws in appropriate jurisdictions. In order to explain how Whisker can help,
-we need to agree some terms with the reader.       
+we need to agree some terms with the reader.
             </p>
             <p>
 Learn about copyright and software licensing <a href='#more-resources'>here</a>.
@@ -641,25 +641,25 @@ thinking in particular about copyright o
             <p>
 Whisker focuses on tracking explicit licenses, and so almost always
 when we talk about a license, we're thinking about a
-written document conditionally granting some copyright 
-and patents permissions for a work.  
+written document conditionally granting some copyright
+and patents permissions for a work.
             </p>
             <p>
 Learn about copyright and software licensing <a href='#more-resources'>here</a>.
             </p>
             <p>
-We adopt the convention  <code>LICENSE</code> for the principle licensing 
-document. Read more about this convention <a href='#what-license'>here</a>. 
+We adopt the convention  <code>LICENSE</code> for the principle licensing
+document. Read more about this convention <a href='#what-license'>here</a>.
             </p>
         </answer>
     </faq>
-     
+
       <faq id="what-license">
         <question>What do you mean by <code>LICENSE</code>?</question>
         <answer>
             <p>
-We adopt the convention that <code>LICENSE</code> means the principle licensing 
-document for the project. 
+We adopt the convention that <code>LICENSE</code> means the principle licensing
+document for the project.
             </p>
            <p>
 Learn about copyright and software licensing <a href='#more-resources'>here</a>.
@@ -675,12 +675,12 @@ A <code>NOTICE</code> is informational d
 is required by a license condition.
             </p>
             <p>
-Some licenses (for example the 
+Some licenses (for example the
 <a href='http://www.apache.org/licenses/LICENSE-2.0.html'>Apache License, Version 2</a>)
 may require the retention of a document named <code>NOTICE</code> (or at least its contents).
-By <code>NOTICE</code> we mean information that <code>MUST</code> be preserved 
+By <code>NOTICE</code> we mean information that <code>MUST</code> be preserved
 to satisfy some condition of a license. Take care not to confuse <code>NOTICE</code> with
-<a href='#notice-vs-copyright-notice'>copyright notice</a> or 
+<a href='#notice-vs-copyright-notice'>copyright notice</a> or
 <a href='#notice-vs-license'><code>LICENSE</code></a>.
              </p>
         </answer>
@@ -691,7 +691,7 @@ to satisfy some condition of a license. 
             <p>
 A phrase or symbol informing a reader about a underlying claim of copyright ownership.
             </p><p>
-For example <em>"Copyright (c) 2525 Apache Software Foundation"</em>   
+For example <em>"Copyright (c) 2525 Apache Software Foundation"</em>
             </p><p>
 Though copyright laws differ from country to country, copyright notices
 are may well be considered important, and may be governed by statue.
@@ -704,25 +704,25 @@ are may well be considered important, an
 Learn about copyright and software licensing <a href='#more-resources'>here</a>.
            </p>
         </answer>
-     </faq>    
-         
+     </faq>
+
      <faq id="notice-vs-copyright-notice">
         <question>What is the difference between a <code>NOTICE</code> and a copyright notice?</question>
         <answer>
             <p>
-A <code>NOTICE</code> is informational documentation, whereas a copyright notice 
+A <code>NOTICE</code> is informational documentation, whereas a copyright notice
 informs a reader about a legal claim of ownership. A license may be conditional
 on the redistribution of the contents of a <code>NOTICE</code> but typically
 a copyright notice is governed directly by statue.
             </p><p>
 A <code>NOTICE</code> document often contains
-copyright notices, but is not limited to just this sort of content. 
+copyright notices, but is not limited to just this sort of content.
             </p>
             <p>
-Read more on <code>NOTICE</code> documents <a href='#what-notice'>here</a>. 
+Read more on <code>NOTICE</code> documents <a href='#what-notice'>here</a>.
            </p>
            <p>
-Read more on copyright notices <a href='#what-copyright-notice'>here</a>. 
+Read more on copyright notices <a href='#what-copyright-notice'>here</a>.
            </p>
            <p>
 Learn about copyright and software licensing <a href='#more-resources'>here</a>.
@@ -733,19 +733,19 @@ Learn about copyright and software licen
         <question>What is the difference between a <code>NOTICE</code> and a <code>LICENSE</code>?</question>
         <answer>
             <p>
-A <code>NOTICE</code> is informational documentation, whereas a <code>LICENSE</code> 
-is legal documentation. 
+A <code>NOTICE</code> is informational documentation, whereas a <code>LICENSE</code>
+is legal documentation.
 A <code>NOTICE</code> may be subject to a <a href='#when-notice-needed'>retention clause</a>.
             </p>
             <p>
-Read more on <code>NOTICE</code> documents <a href='#what-notice'>here</a>. 
+Read more on <code>NOTICE</code> documents <a href='#what-notice'>here</a>.
             </p>
            <p>
 Learn about copyright and software licensing <a href='#more-resources'>here</a>.
            </p>
         </answer>
     </faq>
-    
+
     <faq id="when-notice-needed">
         <question>When is a <code>NOTICE</code> needed?</question>
         <answer>
@@ -756,12 +756,12 @@ Learn about copyright and software licen
 Some licenses require <code>NOTICE</code> documents to be retained.
 For example, clause 4.4 in the
 <a href='http://www.apache.org/licenses/LICENSE-2.0.html'>Apache License, Version 2</a>
-is a retention clause covering any <code>NOTICE</code> distributed with the original. 
+is a retention clause covering any <code>NOTICE</code> distributed with the original.
 When creating or distributing a modified version of a project licensed with a retention clause,
-you need to ensure that the <code>NOTICE</code> is distributed. 
+you need to ensure that the <code>NOTICE</code> is distributed.
             </p>
             <p>
-Read more on <code>NOTICE</code> documents <a href='#what-notice'>here</a>. 
+Read more on <code>NOTICE</code> documents <a href='#what-notice'>here</a>.
             </p>
             <p>
 Learn about copyright and software licensing <a href='#more-resources'>here</a>.
@@ -772,46 +772,46 @@ Learn about copyright and software licen
         <question>Do I need to add a <code>NOTICE</code> for my Apache Licensed Project?</question>
         <answer>
             <p>
-Not necessarily, though Apache Software Foundation projects 
-MUST include a <code>NOTICE</code> 
-of <a href='http://www.apache.org/legal/src-headers.html#notice'>standard form</a>. 
+Not necessarily, though Apache Software Foundation projects
+MUST include a <code>NOTICE</code>
+of <a href='http://www.apache.org/legal/src-headers.html#notice'>standard form</a>.
             </p>
             <p>
 The <a href='http://www.apache.org/licenses/LICENSE-2.0.html'>Apache License, Version 2</a>
 requires that a <code>NOTICE</code> is retained but if your project contains only
 original files then you could opt not to have a <code>NOTICE</code>. Please read
-<a href='#when-notice-needed'>this</a>.  
+<a href='#when-notice-needed'>this</a>.
             </p>
             <p>
-It is polite to include a minimal <code>NOTICE</code>. Otherwise, 
-<a href='#what-is-downstream'>downstream consumers</a> may need to manually verify that no 
-<code>NOTICE</code> exists 
+It is polite to include a minimal <code>NOTICE</code>. Otherwise,
+<a href='#what-is-downstream'>downstream consumers</a> may need to manually verify that no
+<code>NOTICE</code> exists
 for the release.
             </p>
             <p>
-Read more on <code>NOTICE</code> documents <a href='#what-notice'>here</a>. 
+Read more on <code>NOTICE</code> documents <a href='#what-notice'>here</a>.
            </p>
         </answer>
     </faq>
-    
+
     <faq id='complex-software-applications'>
         <question>When is Whisker needed?</question>
         <answer>
             <p>
 For projects distributing applications containing only a few third party dependencies,
 manually maintaining and verifying the <code>LICENSE</code> and <code>NOTICE</code> documents
-shipped is not a major burden. When releasing complex applications containing scores of 
+shipped is not a major burden. When releasing complex applications containing scores of
 third party dependencies from dozens of sources, producing accurate licensing documentation
 without automation takes a lot of time. This is where Whisker has the biggest value.
             </p>
         </answer>
     </faq>
-    
+
     <faq id="licensor">
         <question>What do you mean by licensor?</question>
         <answer>
             <p>
-The entity issuing the license.            
+The entity issuing the license.
             </p>
         </answer>
     </faq>
@@ -824,7 +824,7 @@ Software flows downstream from the sourc
 Dependencies are <em>upstream</em> of a project, and software
 that relies on a project are <em>downstream consumers</em>.
             </p>
-            
+
         </answer>
     </faq>
 
@@ -832,12 +832,12 @@ that relies on a project are <em>downstr
         <question>What is an Open Source License?</question>
         <answer>
             <p>
-An open-source license complies with the 
+An open-source license complies with the
 <a href='http://opensource.org/docs/osd'>Open Source Definition</a>.
-Open Source Licenses are those on this 
-<a href='http://opensource.org/licenses/index.html'>list</a>. 
-Both are maintained by the 
-<a href='http://www.opensource.org'>Open Source Initiative</a>.   
+Open Source Licenses are those on this
+<a href='http://opensource.org/licenses/index.html'>list</a>.
+Both are maintained by the
+<a href='http://www.opensource.org'>Open Source Initiative</a>.
             </p>
             <p>
  Learn more about Open Source <a href='http://opensource.org/history'>here</a>.
@@ -845,17 +845,17 @@ Both are maintained by the 
         </answer>
     </faq>
 
-    
+
     <faq id="what-is-license-family">
         <question>What do you mean by a license family?</question>
         <answer>
             <p>
-<a href='#what-is-an-open-source-license'>Open source licenses</a> 
-are designed to be re-usable: 
-both you and I can use the same basic text to license our works. 
+<a href='#what-is-an-open-source-license'>Open source licenses</a>
+are designed to be re-usable:
+both you and I can use the same basic text to license our works.
 Many license texts can be reused without modification (for example,
 the <a href='http://www.apache.org/licenses/LICENSE-2.0.html'>Apache License, Version 2</a>).
-Others require that a small number of details are changed.   
+Others require that a small number of details are changed.
             </p>
 <p>For example, to use the
 <a href='http://opensource.org/licenses/BSD-2-Clause'>BSD License (2 Clause)</a>
@@ -864,13 +864,13 @@ licenses of this sort a <em>license fami
 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 
+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>. 
+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>.
@@ -885,7 +885,7 @@ Learn about copyright and software licen
     </faq>
 
   </part>
-  <part id="examples"> 
+  <part id="examples">
     <title>Is there an Example...</title>
     <faq id="mit-example">
     <question>Using the MIT License?</question>
@@ -915,7 +915,7 @@ Learn about copyright and software licen
             Read more about organisations <a href='#what-is-org'>here</a>.
             </p>
         </answer>
-    </faq>    
+    </faq>
 
     <faq id="3rd-party-individual-example">
         <question>Of a Third Party Dependency licensed from an Individual?</question>
@@ -934,9 +934,9 @@ Learn about copyright and software licen
         <answer>
             <p><a href='examples/3rd-party-group.html'>Yes</a></p>
         </answer>
-    </faq>    
+    </faq>
   </part>
-  <part id="learning"> 
+  <part id="learning">
     <title>Learning</title>
     <faq id="more-resources">
       <question>I'm interested in learning more about software licensing. Where should I start?</question>
@@ -946,14 +946,13 @@ Learn about copyright and software licen
       </p>
       <ul>
         <li><a href='http://www.rosenlaw.com/oslbook.htm'>Open Source Licensing</a> by Lawrence Rosen</li>
-        <li><a href='http://www.softwarefreedom.org/'>Software Freedom Law Center</a> 
+        <li><a href='http://www.softwarefreedom.org/'>Software Freedom Law Center</a>
         <a href='http://www.softwarefreedom.org/resources/'>publications</a></li>
         <li><a href='http://www.ifosslr.org/'>International Free and Open Source Software Law Review</a></li>
         <li><a href='http://ifosslawbook.org'>The International Free and Open Source Software Law Book</a></li>
       </ul>
-      
+
       </answer>
     </faq>
   </part>
-  
 </faqs>
\ No newline at end of file

Modified: creadur/whisker/trunk/src/site/site.xml
URL: http://svn.apache.org/viewvc/creadur/whisker/trunk/src/site/site.xml?rev=1405335&r1=1405334&r2=1405335&view=diff
==============================================================================
--- creadur/whisker/trunk/src/site/site.xml (original)
+++ creadur/whisker/trunk/src/site/site.xml Sat Nov  3 13:55:39 2012
@@ -15,7 +15,7 @@
   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
   KIND, either express or implied.  See the License for the
   specific language governing permissions and limitations
-  under the License.    
+  under the License.
 -->
 <project name="Apache Whisker&trade;">
   <bannerRight>
@@ -24,26 +24,26 @@
     <src>http://www.apache.org/images/asf_logo_wide.jpg</src>
     <href>http://www.apache.org/</href>
   </bannerRight>
-  
+
   <poweredBy>
-      <logo name="ApacheCon EU 2012 November 5-8 Sinsheim, Germany" 
+      <logo name="ApacheCon EU 2012 November 5-8 Sinsheim, Germany"
             href="http://www.apachecon.eu/"
             img="http://www.apache.org/events/logos-banners/ApacheCon-2012-Europe/EU_square_20.png"/>
 
-      <logo name="ApacheCon NA 2012 November 26-28 Portland, Oregon" 
+      <logo name="ApacheCon NA 2012 November 26-28 Portland, Oregon"
             href="http://na.apachecon.com/"
             img="http://www.apache.org/events/logos-banners/ApacheCon-2013-NorthAmerica/NA_square_20.png"/>
-      <logo name="Maven" 
+      <logo name="Maven"
             href="http://maven.apache.org/"
             img="http://maven.apache.org/images/logos/maven-feather.png"/>
-            
+
   </poweredBy>
 
   <body>
     <head>
-        <link 
-            href='http://fonts.googleapis.com/css?family=Mate+SC' 
-            rel='stylesheet' 
+        <link
+            href='http://fonts.googleapis.com/css?family=Mate+SC'
+            rel='stylesheet'
             type='text/css'/>
     </head>
     <breadcrumbs>
@@ -51,7 +51,7 @@
       <item name="Creadur" href="http://creadur.apache.org/"/>
       <item name="Whisker" href="http://creadur.apache.org/whisker/"/>
     </breadcrumbs>
-  
+
     <menu name='Apache Whisker&trade;' inherit="bottom">
        <item name='Introducing Whisker' href='index.html'/>
        <item name='Meta Data' href='meta-data.html'/>
@@ -61,7 +61,7 @@
        <item name='Source Cross-ref' href='xref/index.html'/>
        <item name="FAQ" href="faq.html"/>
     </menu>
-    
+
     <menu name='Examples'>
         <item name="In 5 Minutes" href="examples/in-5-mins.html"/>
         <item name="3rd Party (Individual)" href="examples/3rd-party-individual.html"/>
@@ -80,36 +80,36 @@
         <item name="3rd Party (Group)" href="examples/3rd-party-group-sample.xml"/>
         <item name="MIT License" href="examples/in-5-mins-sample.xml"/>
     </menu>
-    
+
     <menu name="Apache Creadur &trade;" inherit="bottom">
 		<item name='Creadur Project Home' href="http://creadur.apache.org"/>
-		<item name='Apache Rat' href="http://creadur.apache.org/rat"/>  
+		<item name='Apache Rat' href="http://creadur.apache.org/rat"/>
 		<item name='Apache Tentacles' href="http://creadur.apache.org/tentacles"/>
 		<item name='Security' href='http://www.apache.org/security/'/>
 		<item name='License' href='http://www.apache.org/licenses/'/>
 		<item name='Sponsorship' href='http://www.apache.org/foundation/sponsorship.html'/>
 		<item name='Thanks' href='http://www.apache.org/foundation/thanks.html'/>
 	</menu>
-    
+
     <menu name="The Apache Software Foundation" inherit="bottom">
-        <item name='About the Foundation' 
+        <item name='About the Foundation'
             href="http://www.apache.org/foundation"/>
-        <item name='The projects' 
+        <item name='The projects'
             href="http://projects.apache.org"/>
-        <item name='The people' 
+        <item name='The people'
             href="http://people.apache.org"/>
-        <item name='How we work' 
+        <item name='How we work'
             href='http://www.apache.org/foundation/how-it-works.html'/>
-        <item name='Our history' 
+        <item name='Our history'
             href='http://www.apache.org/foundation/how-it-works.html#history'/>
-        <item name='News' 
+        <item name='News'
             href='http://blogs.apache.org/foundation/'/>
     </menu>
-   
+
     <menu name="Contribute" inherit="bottom">
       <item name="Get Involved" href='http://www.apache.org/foundation/getinvolved.html'/>
     </menu>
-    
+
     <menu name="Committer Info" inherit="bottom">
       <item name="Committers' FAQ" href='http://www.apache.org/dev/committers.html'/>
       <item name='New Committers Guide' href='http://www.apache.org/dev/new-committers-guide.html'/>
@@ -119,17 +119,17 @@
       <item name='Branding' href='http://www.apache.org/foundation/marks/'/>
       <item name='Media Relations' href='http://www.apache.org/press/'/>
     </menu>
-    
-    
+
+
     <menu ref='reports'/>
-    
+
     <footer>Copyright &#169; 2012 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.
-      Apache Creadur, Creadur, Apache Rat, Apache Tentacles, Apache Whisker, Apache and the Apache feather logo are trademarks 
+      Apache Creadur, Creadur, Apache Rat, Apache Tentacles, Apache Whisker, Apache and the Apache feather logo are trademarks
       of The Apache Software Foundation.
       All other marks mentioned may be trademarks or registered trademarks of their respective owners.
       This is user documentation, not legal advice.
       </footer>
-    
+
   </body>
-    
+
 </project>
\ No newline at end of file



Mime
View raw message