www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r809847 - in /infrastructure/site/trunk: docs/legal/resolved.html xdocs/legal/resolved.xml
Date Tue, 01 Sep 2009 06:38:31 GMT
Author: rdonkin
Date: Tue Sep  1 06:38:30 2009
New Revision: 809847

URL: http://svn.apache.org/viewvc?rev=809847&view=rev
Log:
Rework markup to use sections. This allows an automatic table of contents to be added at the
top. Hopefully no semantic changes. If there are, please jump in and fix.

Modified:
    infrastructure/site/trunk/docs/legal/resolved.html
    infrastructure/site/trunk/xdocs/legal/resolved.xml

Modified: infrastructure/site/trunk/docs/legal/resolved.html
URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/docs/legal/resolved.html?rev=809847&r1=809846&r2=809847&view=diff
==============================================================================
--- infrastructure/site/trunk/docs/legal/resolved.html [utf-8] (original)
+++ infrastructure/site/trunk/docs/legal/resolved.html [utf-8] Tue Sep  1 06:38:30 2009
@@ -70,15 +70,96 @@
 		<div class="column span-15 colborder">
                             
 <div class="section-content">
+<ul>
+<li>ASF Legal Previously Asked Questions
+ <ul>
+<li><a href='#audience'>
+Purpose and Intended Audience
+ </a>
+</li>
+<li><a href='#criteria'>
+Software License Criteria
+ </a>
+</li>
+<li><a href='#asking-questions'>
+Asking Questions
+ </a>
+</li>
+</ul>
+</li>
+<li><a href='#faq'>
+Previously Asked Questions
+ </a>
+ <ul>
+<li><a href='#category-a'>
+For the purposes of being a dependency to an Apache product, which licenses are considered

+ to be similar in terms to the Apache License 2.0?
+ </a>
+</li>
+<li><a href='#category-x'>
+Which licenses may  be included within Apache products?
+ </a>
+</li>
+<li><a href='#ruby-license'>
+Can Apache projects have external dependencies on Ruby licensed works?
+ </a>
+</li>
+<li><a href='#cc-sa'>
+Can Apache projects include Creative Commons Attribution-Share Alike works?
+ </a>
+</li>
+<li><a href='#category-b'>
+How should so-called "Weak Copyleft" Licenses be handled?
+ </a>
+</li>
+<li><a href='#json'>
+Can Apache products include works licensed under the JSON license?
+ </a>
+</li>
+<li><a href='#concurrent'>
+Doug Lea's concurrent library is public domain, but contains some 
+  Sun files which are not public domain. Can this be included in an Apache product?
+ </a>
+</li>
+<li><a href='#osgi-category-b'>
+Can OSGi metadata be added to weak copyleft binaries - thus modifying the binary jar file?
+ </a>
+</li>
+<li><a href='#cobertura'>
+Can Cobertura reports be included in Apache distributions?
+ </a>
+</li>
+<li><a href='#platform'>
+Does it matter what platform an Apache product is created to work with?
+ </a>
+</li>
+<li><a href='#domainkeys'>
+Does the Yahoo! DomainKeys Patent License Agreement v1.2 raise any concerns?
+ </a>
+</li>
+<li><a href='#library-ip-clearance'>
+Is 
+  IP clearance required for library dependencies?
+ </a>
+</li>
+<li><a href='#no-modification'>
+How should licenses that prevent modification be handled?
+ </a>
+</li>
+</ul>
+</li>
+</ul>
 
-<h4>
+<h4 id="audience">
    Purpose and Intended Audience
 </h4>
 <div class="section-content">
-<p>This page provides a history of the answers to questions asked on the legal-discuss@
mailing list, and the scope of those answers. As each answer is as much dictated by Apache
Software Foundation (ASF) policy as any other interpretation, it is of most value to ASF projects.</p>
+<p>This page provides a history of the answers to questions asked on the legal-discuss@
mailing list, 
+and the scope of those answers. As each answer is as much dictated by Apache Software Foundation
(ASF) 
+policy as any other interpretation, it is of most value to ASF projects.</p>
 </div>
 
-<h4>
+<h4 id="criteria">
    Software License Criteria
 </h4>
 <div class="section-content">
@@ -90,18 +171,24 @@
 </ol>
 </div>
 
-<h4>
+<h4 id="asking-questions">
    Asking Questions
 </h4>
 <div class="section-content">
 <p>Please submit questions to the Legal Affair Committee <a href="https://issues.apache.org/jira/browse/LEGAL">JIRA
space</a>.</p>
 </div>
-
-<h4>
+</div>
+                 
+<h4 id="faq">
    Previously Asked Questions
 </h4>
 <div class="section-content">
-<p><b>* For the purposes of being a dependency to an Apache product, which licenses
are considered to be similar in terms to the Apache License 2.0?</b></p>
+
+<h5 id="category-a">
+   For the purposes of being a dependency to an Apache product, which licenses are considered

+ to be similar in terms to the Apache License 2.0?
+</h5>
+<div class="section-content">
 <p>Works under the following licenses may be included within Apache products:</p>
 <ul>
    <li><a href="http://apache.org/licenses/LICENSE-2.0">Apache License 2.0</a></li>
@@ -134,7 +221,12 @@
 <p>Many of these licenses have specific attribution terms that need to be adhered to,
for example CC-A, often by adding 
     them to the NOTICE file. Ensure you are doing this when including these works. Note,
this list is colloquially known 
     as the <i>Category A</i> list. </p>
-<p><b>* Which licenses may <b>NOT</b> be included within Apache products?</b></p>
+</div>
+
+<h5 id="category-x">
+   Which licenses may  be included within Apache products?
+</h5>
+<div class="section-content">
 <ul>
    <li>Binary Code License (BCL)</li>
    <li>Binary Code License (BCL)</li>
@@ -187,17 +279,32 @@
       the software in particular environments (air traffic control, nuclear facilities etc).

   </dd>
   </dl>
-<p>* <b>Can Apache projects have external dependencies on Ruby licensed works?</b></p>
+</div>
+
+<h5 id="ruby-license">
+   Can Apache projects have external dependencies on Ruby licensed works?
+</h5>
+<div class="section-content">
 <p>A project written primarily and obviously in Ruby can have a dependency either on
Matz's Ruby Interpreter (MRI), 
      or on any Gem which is licensed under the <a href="http://www.ruby-lang.org/en/LICENSE.txt">Ruby
license</a>.  
      Of course Gems written under other licenses (such as MIT) may also be OK, depending
on the license. </p>
-<p>* <b>Can Apache projects include Creative Commons Attribution-Share Alike
works?</b></p>
+</div>
+
+<h5 id="cc-sa">
+   Can Apache projects include Creative Commons Attribution-Share Alike works?
+</h5>
+<div class="section-content">
 <p>Unmodified media under the 
      <a href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-Share
Alike 2.5</a> and 
      <a href="http://creativecommons.org/licenses/by-sa/3.0/">Creative Commons Attribution-Share
Alike 3.0</a> 
      licenses may be included in Apache products, subject to the licenses attribution clauses
which may require 
      LICENSE/NOTICE/README changes. For any other type of CC-SA licensed work, please contact
the Legal PMC. </p>
-<p><b>* How should so-called "Weak Copyleft" Licenses be handled?</b></p>
+</div>
+
+<h5 id="category-b">
+   How should so-called "Weak Copyleft" Licenses be handled?
+</h5>
+<div class="section-content">
 <p>Each license in this category requires some degree of reciprocity;
      this may mean that additional action is warranted in order to
      minimize the chance that a user of an Apache product will create a
@@ -231,19 +338,49 @@
      permitted. An example of this is the web-facesconfig_1_0.dtd, whose
      inclusion is mandated by the JSR 127: JavaServer Faces specification. </p>
 <p>This is colloquially known as the <i>Category B</i> list. </p>
-<p>* <b>Can Apache products include works licensed under the JSON license?</b></p>
+</div>
+
+<h5 id="json">
+   Can Apache products include works licensed under the JSON license?
+</h5>
+<div class="section-content">
 <p>The <a href="http://www.json.org/java/">JSON Java library</a> may be
included. Please contact 
      legal-discuss@ for other products under this license. </p>
-<p>* <b>Doug Lea's concurrent library is public domain, but contains some Sun
files which are not public domain. Can this be included in an Apache product?</b> </p>
-<p>Yes, treat it much as you currently would the Category B licenses above - "it may
be included in binary form within an Apache product if the inclusion is appropriately labeled".
If using the source, remove the files Sun licensed to Doug and treat as Category A (or get
it from <a href="http://svn.apache.org/repos/asf/harmony/standard/classlib/trunk/modules/concurrent/src/main/java/java/util/concurrent/">Harmony</a>).
</p>
-<p>* <b>Can OSGi metadata be added to weak copyleft binaries - thus modifying
the binary jar file?</b></p>
+</div>
+
+<h5 id="concurrent">
+   Doug Lea's concurrent library is public domain, but contains some 
+  Sun files which are not public domain. Can this be included in an Apache product?
+</h5>
+<div class="section-content">
+<p>Yes, treat it much as you currently would the Category B licenses above 
+  - "it may be included in binary form within an Apache product if the inclusion
+   is appropriately labeled". If using the source, remove the files Sun licensed to Doug
and 
+   treat as Category A (or get it from 
+   <a href="http://svn.apache.org/repos/asf/harmony/standard/classlib/trunk/modules/concurrent/src/main/java/java/util/concurrent/">Harmony</a>).
</p>
+</div>
+
+<h5 id="osgi-category-b">
+   Can OSGi metadata be added to weak copyleft binaries - thus modifying the binary jar file?
+</h5>
+<div class="section-content">
 <p>Insertion of OSGi metadata into 'Category B' licensed jars is
   permitted; even though that metadata becomes licensed under the 3rd
   party license when it is put in the jar, assuming that a note that this has occurred is
included in the 
   prominent labeling that the Category B language calls for. </p>
-<p>* <b>Can Cobertura reports be included in Apache distributions?</b></p>
+</div>
+
+<h5 id="cobertura">
+   Can Cobertura reports be included in Apache distributions?
+</h5>
+<div class="section-content">
 <p>Yes. </p>
-<p>* <b>Does it matter what platform an Apache product is created to work with?</b></p>
+</div>
+
+<h5 id="platform">
+   Does it matter what platform an Apache product is created to work with?
+</h5>
+<div class="section-content">
 <p>It does not matter, unless the terms for that platform affect
   the Apache product's licensing. For example, creating a product that
   runs on Windows or Java, uses a web service such as Google Services or
@@ -254,14 +391,29 @@
   depend on the licensing of said code. Also, if you have any doubts as to whether the licensing
   of the platform would affect the Apache code, we recommend that you check the legal-discuss@
   archives to see if it has come up before, and if not email legal-discuss@ to find out.
</p>
-<p>* <b>Does the Yahoo! DomainKeys Patent License Agreement v1.2 raise any concerns?</b></p>
+</div>
+
+<h5 id="domainkeys">
+   Does the Yahoo! DomainKeys Patent License Agreement v1.2 raise any concerns?
+</h5>
+<div class="section-content">
 <p>No. </p>
-<p>* <b>Is <a href="http://incubator.apache.org/ip-clearance/index.html">IP
clearance</a> 
-required for library dependencies?</b></p>
+</div>
+
+<h5 id="library-ip-clearance">
+   Is 
+  IP clearance required for library dependencies?
+</h5>
+<div class="section-content">
 <p>No. </p>
-<p>IP clearance is used to import code bases from outside Apache for future development
here.</p>
+<p><a href="http://incubator.apache.org/ip-clearance/index.html">IP clearance</a>

+  is used to import code bases from outside Apache for future development here.</p>
 </div>
-<p>* <b>How should licenses that prevent modification be handled?</b></p>
+
+<h5 id="no-modification">
+   How should licenses that prevent modification be handled?
+</h5>
+<div class="section-content">
 <p>
     There are licenses that give broad rights for redistribution of
     <em>unmodified</em> copies. Such licenses are not open source, but they
@@ -283,6 +435,7 @@
     <li><a href="http://www.adobe.com/devnet/opentype/archives/glyphlist.txt">Adobe
Glyph List</a></li>
   </ul>
 </div>
+</div>
          </div>
     <div class="column span-8 last">
       <div class="block">

Modified: infrastructure/site/trunk/xdocs/legal/resolved.xml
URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/xdocs/legal/resolved.xml?rev=809847&r1=809846&r2=809847&view=diff
==============================================================================
--- infrastructure/site/trunk/xdocs/legal/resolved.xml [utf-8] (original)
+++ infrastructure/site/trunk/xdocs/legal/resolved.xml [utf-8] Tue Sep  1 06:38:30 2009
@@ -25,10 +25,13 @@
 <body>
 <section>
 <title>ASF Legal Previously Asked Questions</title>
-<section><title>Purpose and Intended Audience</title>
-<p>This page provides a history of the answers to questions asked on the legal-discuss@
mailing list, and the scope of those answers. As each answer is as much dictated by Apache
Software Foundation (ASF) policy as any other interpretation, it is of most value to ASF projects.</p>
+<toc/>
+<section id='audience'><title>Purpose and Intended Audience</title>
+<p>This page provides a history of the answers to questions asked on the legal-discuss@
mailing list, 
+and the scope of those answers. As each answer is as much dictated by Apache Software Foundation
(ASF) 
+policy as any other interpretation, it is of most value to ASF projects.</p>
 </section>
-<section><title>Software License Criteria</title>
+<section id='criteria'><title>Software License Criteria</title>
 
 <p>The following criteria serve as guidelines for the answers on this page. </p>
 
@@ -40,12 +43,14 @@
 
 </section>
 
-<section><title>Asking Questions</title>
+<section id='asking-questions'><title>Asking Questions</title>
 <p>Please submit questions to the Legal Affair Committee <a href="https://issues.apache.org/jira/browse/LEGAL">JIRA
space</a>.</p>
 </section>
+</section>
 
-<section><title>Previously Asked Questions</title>
- <p><b>* For the purposes of being a dependency to an Apache product, which licenses
are considered to be similar in terms to the Apache License 2.0?</b></p>
+<section id='faq'><title>Previously Asked Questions</title>
+ <section id='category-a'><title>For the purposes of being a dependency to an
Apache product, which licenses are considered 
+ to be similar in terms to the Apache License 2.0?</title>
  <p>Works under the following licenses may be included within Apache products:</p>
 
  <ul>
@@ -80,8 +85,9 @@
  <p>Many of these licenses have specific attribution terms that need to be adhered
to, for example CC-A, often by adding 
     them to the NOTICE file. Ensure you are doing this when including these works. Note,
this list is colloquially known 
     as the <i>Category A</i> list. </p>
-
- <p><b>* Which licenses may <b>NOT</b> be included within Apache
products?</b></p>
+ </section>
+ 
+ <section id='category-x'><title>Which licenses may <b>NOT</b> be
included within Apache products?</title>
  <ul>
    <li>Binary Code License (BCL)</li>
    <li>Binary Code License (BCL)</li>
@@ -135,23 +141,23 @@
       the software in particular environments (air traffic control, nuclear facilities etc).

   </dd>
   </dl>
-
-  <p>* <b>Can Apache projects have external dependencies on Ruby licensed works?</b></p>
+  </section>
+  <section id='ruby-license'><title>Can Apache projects have external dependencies
on Ruby licensed works?</title>
 
   <p>A project written primarily and obviously in Ruby can have a dependency either
on Matz's Ruby Interpreter (MRI), 
      or on any Gem which is licensed under the <a href="http://www.ruby-lang.org/en/LICENSE.txt">Ruby
license</a>.  
      Of course Gems written under other licenses (such as MIT) may also be OK, depending
on the license. </p>
-
-  <p>* <b>Can Apache projects include Creative Commons Attribution-Share Alike
works?</b></p>
+  </section>
+  
+  <section id='cc-sa'><title>Can Apache projects include Creative Commons Attribution-Share
Alike works?</title>
 
   <p>Unmodified media under the 
      <a href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-Share
Alike 2.5</a> and 
      <a href="http://creativecommons.org/licenses/by-sa/3.0/">Creative Commons Attribution-Share
Alike 3.0</a> 
      licenses may be included in Apache products, subject to the licenses attribution clauses
which may require 
      LICENSE/NOTICE/README changes. For any other type of CC-SA licensed work, please contact
the Legal PMC. </p>
-
-
-  <p><b>* How should so-called "Weak Copyleft" Licenses be handled?</b></p>
+  </section>
+  <section id='category-b'><title>How should so-called "Weak Copyleft" Licenses
be handled?</title>
 
   <p>Each license in this category requires some degree of reciprocity;
      this may mean that additional action is warranted in order to
@@ -191,27 +197,37 @@
      inclusion is mandated by the JSR 127: JavaServer Faces specification. </p>
 
   <p>This is colloquially known as the <i>Category B</i> list. </p>
-
-  <p>* <b>Can Apache products include works licensed under the JSON license?</b></p>
+  </section>
+  <section id='json'><title>Can Apache products include works licensed under
the JSON license?</title>
 
   <p>The <a href="http://www.json.org/java/">JSON Java library</a> may
be included. Please contact 
      legal-discuss@ for other products under this license. </p>
-
-  <p>* <b>Doug Lea's concurrent library is public domain, but contains some Sun
files which are not public domain. Can this be included in an Apache product?</b> </p>
-  <p>Yes, treat it much as you currently would the Category B licenses above - &quot;it
may be included in binary form within an Apache product if the inclusion is appropriately
labeled&quot;. If using the source, remove the files Sun licensed to Doug and treat as
Category A (or get it from <a href="http://svn.apache.org/repos/asf/harmony/standard/classlib/trunk/modules/concurrent/src/main/java/java/util/concurrent/">Harmony</a>).
</p>
-
-  <p>* <b>Can OSGi metadata be added to weak copyleft binaries - thus modifying
the binary jar file?</b></p>
+  </section>
+  
+  <section id='concurrent'><title>Doug Lea's concurrent library is public domain,
but contains some 
+  Sun files which are not public domain. Can this be included in an Apache product?</title>
+  
+  <p>Yes, treat it much as you currently would the Category B licenses above 
+  - &quot;it may be included in binary form within an Apache product if the inclusion
+   is appropriately labeled&quot;. If using the source, remove the files Sun licensed
to Doug and 
+   treat as Category A (or get it from 
+   <a href="http://svn.apache.org/repos/asf/harmony/standard/classlib/trunk/modules/concurrent/src/main/java/java/util/concurrent/">Harmony</a>).
</p>
+  </section>
+  
+  <section id='osgi-category-b'><title>Can OSGi metadata be added to weak copyleft
binaries - thus modifying the binary jar file?</title>
 
   <p>Insertion of OSGi metadata into 'Category B' licensed jars is
   permitted; even though that metadata becomes licensed under the 3rd
   party license when it is put in the jar, assuming that a note that this has occurred is
included in the 
   prominent labeling that the Category B language calls for. </p>
-
-  <p>* <b>Can Cobertura reports be included in Apache distributions?</b></p>
-
+  </section>
+  
+  <section id='cobertura'><title>Can Cobertura reports be included in Apache
distributions?</title>
+  
   <p>Yes. </p>
-
-  <p>* <b>Does it matter what platform an Apache product is created to work with?</b></p>
+  </section>
+  
+  <section id='platform'><title>Does it matter what platform an Apache product
is created to work with?</title>
 
   <p>It does not matter, unless the terms for that platform affect
   the Apache product's licensing. For example, creating a product that
@@ -225,18 +241,24 @@
   of the platform would affect the Apache code, we recommend that you check the legal-discuss@
   archives to see if it has come up before, and if not email legal-discuss@ to find out.
</p>
 
-  <p>* <b>Does the Yahoo! DomainKeys Patent License Agreement v1.2 raise any
concerns?</b></p>
+  </section>
 
-  <p>No. </p>
+  <section id='domainkeys'>
+  <title>Does the Yahoo! DomainKeys Patent License Agreement v1.2 raise any concerns?</title>
 
-  <p>* <b>Is <a href='http://incubator.apache.org/ip-clearance/index.html'>IP
clearance</a> 
-required for library dependencies?</b></p>
   <p>No. </p>
-  <p>IP clearance is used to import code bases from outside Apache for future development
here.</p>
-</section>
-
-  <p>* <b>How should licenses that prevent modification be handled?</b></p>
+  </section>
 
+  <section id='library-ip-clearance'><title>Is 
+  IP clearance required for library dependencies?</title>
+  <p>No. </p>
+  <p><a href='http://incubator.apache.org/ip-clearance/index.html'>IP clearance</a>

+  is used to import code bases from outside Apache for future development here.</p>
+  </section>
+  
+  <section id='no-modification'>
+  <title>How should licenses that prevent modification be handled?</title>
+  
   <p>
     There are licenses that give broad rights for redistribution of
     <em>unmodified</em> copies. Such licenses are not open source, but they
@@ -262,7 +284,7 @@
     <li><a href="http://www.adobe.com/devnet/opentype/archives/glyphlist.txt"
           >Adobe Glyph List</a></li>
   </ul>
-
+  </section>
 </section>
 </body>
 </document>



---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message