www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/licenses 200104_seminar.html 210104_seminar...


From: Pavel Kharitonov
Subject: www/licenses 200104_seminar.html 210104_seminar...
Date: Fri, 23 Oct 2015 07:05:50 +0000

CVSROOT:        /web/www
Module name:    www
Changes by:     Pavel Kharitonov <ineiev>       15/10/23 07:05:49

Modified files:
        licenses       : 200104_seminar.html 210104_seminar.html 
                         NYC_Seminars_Jan2004.html 

Log message:
        Update boilerplate to 1.78.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/200104_seminar.html?cvsroot=www&r1=1.14&r2=1.15
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/210104_seminar.html?cvsroot=www&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/NYC_Seminars_Jan2004.html?cvsroot=www&r1=1.17&r2=1.18

Patches:
Index: 200104_seminar.html
===================================================================
RCS file: /web/www/www/licenses/200104_seminar.html,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -b -r1.14 -r1.15
--- 200104_seminar.html 23 Dec 2014 13:57:42 -0000      1.14
+++ 200104_seminar.html 23 Oct 2015 07:05:42 -0000      1.15
@@ -1,22 +1,18 @@
 <!--#include virtual="/server/header.html" -->
-<title>FSF Seminar: Detailed Study and Analysis of GPL and LGPL</title>
+<!-- Parent-Version: 1.78 -->
+<title>FSF Seminar: Detailed Study and Analysis of GPL and LGPL
+- GNU Project - Free Software Foundation</title>
 <meta name="CREATED" content="20031124;15182100" />
-<meta name="CHANGED" content="16010101;0" />
 <!--#include virtual="/licenses/po/200104_seminar.translist" -->
 <!--#include virtual="/server/banner.html" -->
 <h2>FSF Seminar: Detailed Study and Analysis of GPL and LGPL</h2>
-<div style="font-weight: bold; text-align: center;"><big>FSF 
Seminar</big></div>
-<p style="margin-bottom: 0in;"> </p>
-<p style="margin-bottom: 0in; text-align: center;"><big><span
- style="font-weight: bold;">Detailed Study and Analysis of GPL and
- LGPL<br />
-</span></big></p>
-<p style="margin-bottom: 0in; text-align: center;"><b>Columbia Law
-School, Columbia University<br />
-New York, NY<br />
-January 20, 2004 (9:00 am - 6:00 pm)</b><br />
-<br />
-</p>
+<blockquote>
+<p>Columbia Law
+School, Columbia University
+New York, NY
+January 20, 2004 (9:00 am - 6:00 pm)
+</p></blockquote>
+
 <p>This one-day course gives a section-by-section explanation of the
 most popular Free Software copyright license, the GNU General Public
 License (GNU GPL), and teaches lawyers, software developers, managers
@@ -24,13 +20,17 @@
 successfully in a new Free Software business and in existing,
 successful enterprises.
 </p>
-<p style="margin-bottom: 0in; margin-left:
-40px;"><i>Prerequisites:</i> Attendees should have a general
+
+<h3>Prerequisites</h3>
+
+<p>Attendees should have a general
 familiarity with software development processes.  A basic
 understanding of how copyright law typically applies to software is
 also helpful.</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 40px;"><i>Audience:</i> The
+
+<h3>Audience</h3>
+
+<p>The
 course is of most interest to lawyers, software developers and
 managers who run (or have clients who run) software businesses that
 modify and/or redistribute software under terms of the GNU GPL or
@@ -40,8 +40,10 @@
 <p>The course will include the topics listed below, along with ample
 time for questions and discussions.
 </p>
-<p style="margin-bottom: 0in; margin-left: 40px;"><b>Lunchtime
-Speaker: </b><a href="http://emoglen.law.columbia.edu/";>Eben
+
+<h3>Lunchtime Speaker</h3>
+
+<p><a href="http://emoglen.law.columbia.edu/";>Eben
 Moglen</a> will be the lunchtime speaker.  Professor Moglen is
 Professor of Law and Legal History at Columbia Law School and one of
 the nation's foremost scholars on copyright, patents and the proposed
@@ -49,11 +51,12 @@
 Directors and the foundation's General Counsel.  Professor Moglen has
 also written extensively on the SCO vs IBM lawsuit.
 </p>
-<p style="margin-bottom: 0in; margin-left: 40px;"> * Free Software
+<dl>
+<dt>Free Software
 Principles and the Free Software Definition
-</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 80px;">The ethical
+</dt>
+<dd>
+<p>The ethical
 principles that motivated the creation of these licenses are
 presented.  Unlike licenses that seek to lock up software in a
 proprietary fashion, the GPL and LGPL are designed to grant freedom to
@@ -63,41 +66,41 @@
 to copy, share, modify and redistribute the software either gratis or
 for a fee) for for-profit companies.
 </p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 40px;"> * Preamble of the GNU
+</dd>
+<dt>Preamble of the GNU
 General Public License (GPL)
-</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 80px;"> The preamble
+</dt>
+<dd>
+<p> The preamble
 presents the intent of the license.  The preamble puts forth the
 motivations for the detailed terms and conditions that follow in the
 license.  We discuss the language of the preamble in detail to show
 how it frames the legal details that follow.
 </p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 0:
+</dd>
+<dt> GPL, Section 0:
 Definitions, etc.
-</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 80px;"> GPL's Section 0
+</dt>
+<dd>
+<p> GPL's Section 0
 defines and presents the terms that make the basis of this copyright
 license.  We discuss those definitions and the copyright scope of the
 license.</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 1:
+</dd>
+<dt>GPL, Section 1:
 Grant for Verbatim Source Copying
-</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-left: 80px;"> Section 1 defines the terms for making
+</dt>
+<dd>
+<p> Section 1 defines the terms for making
 source-only copies of software programs.  We discuss how those rules
 work and the requirements and obligations for distributors of GPL'd
 source, whether they choose to distribute at no charge or for
 fees.</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 40px;"> * Derivative Works:
-Statute and Case Law</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 80px;"> Free Software
+</dd>
+<dt>Derivative Works:
+Statute and Case Law</dt>
+<dd>
+<p> Free Software
 licensing in general, and the GPL and LGPL in particular, relies
 critically on the concept of derivative work since software that is
 independent (i.e., not derivative) of Free Software need not abide by
@@ -111,21 +114,21 @@
 information available to build a working understanding of what is
 generally considered a derivate work in the rapidly changing field of
 software copyright law.</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 2:
-Grants for Source Derivative Works</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 80px;"> Section 2 sets
+</dd>
+<dt> GPL, Section 2:
+Grants for Source Derivative Works</dt>
+<dd>
+<p> Section 2 sets
 forth the rules for creation of derivative works of GPL'd software.
 We discuss the intent of this section of GPL and how it relates to the
 copyright situation discussed in our discussion of derivative works.
 We also explain the details of preparing derivative source in a
 GPL-compliant way.</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 3:
-Grants for Creating Binary Derivative Works</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 80px;"> Source-only
+</dd>
+<dt> GPL, Section 3:
+Grants for Creating Binary Derivative Works</dt>
+<dd>
+<p> Source-only
 distribution works well for technically savvy clients and users, but
 most want runnable binary programs as well.  Section 3 gives
 permission for the creation and distribution of such binary works.  We
@@ -133,11 +136,11 @@
 and detail what distribution options are available to distributors of
 binary GPL'd software.  We explore the benefits and downsides of each
 of those options.</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 40px;"> * The Implied Patent
-Grant in GPL</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 80px;"> Patent rights are
+</dd>
+<dt>The Implied Patent
+Grant in GPL</dt>
+<dd>
+<p> Patent rights are
 most often granted expressly, through detailed language in a license.
 However, express patent grants are not the exclusive way rights in
 patents are granted by patentees.  Even without express language,
@@ -148,82 +151,81 @@
 rights to the licensee greater than what occurs through many other
 Free Software and &ldquo;Open Source&rdquo; licenses?
 </p>
-<div style="margin-left: 40px;"> </div>
-<div style="margin-left: 80px;"> We will consider these questions and
-provide detailed answers to them.
-</div>
-<p style="margin-bottom: 0in; margin-left: 40px;">* GPL, Section 4:
+<p>We will consider these questions and
+provide detailed answers to them.</p>
+</dd>
+<dt>GPL, Section 4:
 Termination of License
-</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 80px;"> Section 4
+</dt>
+<dd>
+<p> Section 4
 terminates rights under the GPL for those who violate it.  We discuss
 how such termination works, what it means for violators, what risks
 one takes in violating, and how rights are typically restored.  We
 briefly mention how Section 4 is used as the central tool in GPL
 enforcement.
 </p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 5:
+</dd>
+<dt>GPL, Section 5:
 Acceptance of License
-</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 80px;"> GPL is not a
+</dt>
+<dd>
+<p> GPL is not a
 contract, so acceptance of the license works differently than it does
 for contracts.  We discuss how this acceptance works under the copyright
 rules that govern the GPL.</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 6:
-Prohibition on Further Restrictions</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 80px;"> Other licensing
+</dd>
+<dt>GPL, Section 6:
+Prohibition on Further Restrictions</dt>
+<dd>
+<p> Other licensing
 terms cannot be placed on GPL'd software that would trump the rights
 granted under GPL.  We discuss how Section 6 is used to ensure that no
 such additional restrictions occur.  We briefly discuss how this leads
 to the concept of GPL-incompatible Free Software licenses.</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 7:
-Conflicts with Other Agreements or Orders</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 80px;"> Just as additional
+</dd>
+<dt>GPL, Section 7:
+Conflicts with Other Agreements or Orders</dt>
+<dd>
+<p> Just as additional
 licensing restrictions cannot trump the GPL, outside agreements,
 patent licenses or court orders cannot do so either.  We discuss how
 Section 7 ensures that other rules outside of the direct software
 license cannot take rights away from users, distributors, and
 modifiers of GPL'd software.
 </p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 8:
-International Licensing Issues</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 80px;"> Section 8 is a
+</dd>
+<dt>GPL, Section 8:
+International Licensing Issues</dt>
+<dd>
+<p> Section 8 is a
 rarely used part of the GPL that helps copyright holders when certain
 technologies are prohibited from full international distribution due
 to draconian rules elsewhere in the world.  We explain how Section 8
 helps such copyright holders.
 </p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 9: FSF
-as GPL's Stewards</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 80px;"> We discuss how the
+</dd>
+<dt>GPL, Section 9: FSF
+as GPL's Stewards</dt>
+<dd>
+<p> We discuss how the
 update process and release of new GPL versions happens.</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 10:
-Copyright Holder's Exceptions to GPL</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 80px;"> Section 10 reminds
+</dd>
+<dt>GPL, Section 10:
+Copyright Holder's Exceptions to GPL</dt>
+<dd>
+<p> Section 10 reminds
 licensees that under copyright law, other relicensing arrangements can
 be made.  We discuss how this can often be used as a business model
 and we explicate that model's benefits and downsides.</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 11:
-Disclaimer of Warranties</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 40px;">* GPL, Section 12:
-Limitation of Liability</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 80px;"> Almost all software
+</dd>
+<dt>GPL, Section 11:
+Disclaimer of Warranties</dt>
+<dd></dd>
+<dt>GPL, Section 12:
+Limitation of Liability</dt>
+<dd>
+<p> Almost all software
 licenses, including Free Software licenses such as the GPL, contain
 sections, typically in all caps, regarding warranties and liability.
 The purposes of these sections are lost on most non-lawyers, but
@@ -233,18 +235,17 @@
 whether that is true, and present the likely interpretation and
 implementation of the GPL's Warranty Disclaimer and Liability
 Limitation provisions.</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 40px;"> * Lesser General
-Public License (LGPL)</p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 80px;"> The LGPL is a
+</dd>
+<dt>Lesser General
+Public License (LGPL)</dt>
+<dd>
+<p> The LGPL is a
 &ldquo;scaled back&rdquo; version of GPL, designed specifically to
 allow creation of a very well-defined class of proprietary derivative
 works.  However, it does prohibit turning the LGPL'd software itself
 directly into proprietary software.
 </p>
-<div style="margin-left: 40px;"> </div>
-<p style="margin-bottom: 0in; margin-left: 80px;"> We discuss the
+<p> We discuss the
 basic design of LGPL and how it compares and contrasts with GPL.  We
 introduce the two classes of derivative works covered by LGPL,
 &ldquo;works that use the library&rdquo; and &ldquo;works based on the
@@ -252,31 +253,31 @@
 derivative works are prohibited and permitted when basing the software
 on an LGPL'd work.
 </p>
-<p><b>Pricing (Book by December 24, 2003 for early registration
-discount):</b>
-</p>
-<div style="margin-left: 40px;">$495 for registrations on or before
-December 24, 2003 and $595 after December 24<br />
-<br />
-<span style="font-family: Nimbus Roman No9 L,
-serif"><span style="text-decoration: underline;">Financial Aid
-Policy:</span> Applicants with annual incomes of up to $15,000 are
+</dd>
+</dl>
+<h3>Pricing (Book by December 24, 2003 for early registration
+discount)</h3>
+<p>$495 for registrations on or before
+December 24, 2003 and $595 after December 24</p>
+<p>
+<b>Financial Aid
+Policy:</b> Applicants with annual incomes of up to $15,000 are
 entitled to a 75% discount.  People with incomes between $15,000 and
 $30,000 receive a 50% discount.  Any member of the judiciary,
 academics or attorneys from non-profit organizations receive a 10%
 discount.  If you fall within one of these categories, please contact
 John at <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a> or
 Ravi at <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a> or by
-phone at 617.620.9640.</span><br />  <br /> To register for the
+phone at 617.620.9640.</p>
+<p>To register for the
 seminar, please download
 the registration form,
-fill it in and fax it to FSF.<br />  <br />
-</div>
-<p style="font-family: Nimbus Roman No9 L, serif"><b>CLE
+fill it in and fax it to FSF.</p>
+<p><b>CLE
 Credits: </b>Attorneys who successfully complete the day long course
 will be entitled to 7 New York Transitional CLE credits toward the
 area of Professional Practice.</p>
-<p style="font-family: Nimbus Roman No9 L, serif">Companies that have
+<p>Companies that have
 signed up as Corporate Patrons of FSF receive two complimentary seats
 per year at FSF seminars and reduced rates for additional
 participants.  Please
@@ -284,52 +285,75 @@
 more details.  You can find out more about the Corporate Patron
 Program at <a href="http://patron.fsf.org/";>
 http://patron.fsf.org</a></p>
-<p style="font-family: Nimbus Roman No9 L, serif">The seminar will be
+<p>The seminar will be
 held at Columbia Law School in New York.  Directions will be sent
 following registration.  For more information, please contact Ravi
 Khanna, FSF's Director of Communication
 at <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a> or by
 calling 1+617-620-9640.</p>
 
-</div>
+</div><!-- for id="content", starts in the include above -->
 <!--#include virtual="/server/footer.html" -->
 <div id="footer">
+<div class="unprintable">
 
-<p>
-Please send FSF &amp; GNU inquiries to 
-<a href="mailto:address@hidden";><em>address@hidden</em></a>.
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
 There are also <a href="/contact/">other ways to contact</a> 
-the FSF.
-<br />
-Please send broken links and other corrections or suggestions to
-<a href="mailto:address@hidden";><em>address@hidden</em></a>.
-</p>
+the FSF.  Broken links and other corrections or suggestions can be sent
+to <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
 
-<p>
-Please see the 
-<a href="/server/standards/README.translations.html">Translations
-README</a> for information on coordinating and submitting
-translations of this article.
-</p>
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 4.0.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright &copy; 2003, 2004, 2007, 2008, 2009, 2014, 2015 Free Software
+Foundation, Inc.</p>
 
-<p>
-Copyright &copy; 2003, 2004, 2007, 2008, 2009, 2014 Free Software
-Foundation, Inc.
-</p>
 <p>This page is licensed under a <a rel="license"
-href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
-Commons Attribution-NoDerivs 3.0 United States License</a>.
-</p>
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
+Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
 
 <!--#include virtual="/server/bottom-notes.html" -->
 
-<p>Updated:
+<p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2014/12/23 13:57:42 $
+$Date: 2015/10/23 07:05:42 $
 <!-- timestamp end -->
 </p>
 </div>
-
 </div>
 </body>
 </html>

Index: 210104_seminar.html
===================================================================
RCS file: /web/www/www/licenses/210104_seminar.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- 210104_seminar.html 12 Jun 2014 06:21:45 -0000      1.15
+++ 210104_seminar.html 23 Oct 2015 07:05:44 -0000      1.16
@@ -1,21 +1,20 @@
 <!--#include virtual="/server/header.html" -->
-<title>FSF Seminar: Case Study and Legal Ethics</title>
+<!-- Parent-Version: 1.78 -->
+<title>FSF Seminar: Case Study and Legal Ethics
+- GNU Project - Free Software Foundation</title>
 <meta name="CREATED" content="20031124;15183300" />
-<meta name="CHANGED" content="20031124;15494100" />
 <!--#include virtual="/licenses/po/210104_seminar.translist" -->
 <!--#include virtual="/server/banner.html" -->
-<h2>FSF Seminar: Case Study and Legal Ethics</h2>
+<h2>FSF Seminar: GPL
+Compliance Case Studies and Legal Ethics in Free Software Licensing</h2>
+
+<blockquote>
+<p>Columbia
+Law School, Columbia University
+New York, NY
+January 21, 2004 (9:00 am - 6:00 pm)</p>
+</blockquote>
 
-<div style="font-weight: bold; text-align: center;"><big>FSF 
Seminar</big></div>
-<b></b>
-<p style="margin-bottom: 0in;"> </p>
-<p style="margin-bottom: 0in; text-align: center; font-weight: bold;"><big>GPL
-Compliance Case Studies and Legal Ethics in Free Software Licensing</big></p>
-<p style="margin-bottom: 0in; text-align: center; font-weight: 
bold;"><big>Columbia
-Law School, Columbia University<br />
-New York, NY<br />
-January 21, 2004 (9:00 am - 6:00 pm)<br />
-</big></p>
 <p>
 This one-day course presents the details of five different GPL
 compliance cases handled by FSF's GPL Compliance Laboratory.  Each case
@@ -28,13 +27,18 @@
 attorneys who want to represent clients that make use of or sell Free
 Software products.</p>
 
-<p style="margin-left: 40px;"><i>Prerequisites:</i> Attendees should
+<h3>Prerequisites</h3>
+
+<p>Attendees should
 have successfully completed the course, a <i>Detailed Study and
 Analysis of GPL and LGPL</i>, as the material from that course forms
 the building blocks for this material, or have attended a
 previous <i>Free Software Licensing and the GNU GPL Seminar</i>.
 </p>
-<p style="margin-bottom: 0in; margin-left: 40px;"><i>Audience:</i> The
+
+<h3>Audience</h3> 
+
+<p>The
 course is of most interest to lawyers who have clients or employers
 that deal with Free Software on a regular basis.  However, technical
 managers and executives whose businesses use or distribute Free
@@ -43,8 +47,9 @@
 <p>The course will include the topics listed below, along with ample
 time for questions and discussions.
 </p>
-<p style="margin-bottom: 0in; margin-left: 40px;"><b>Lunchtime
-Speaker: </b><a href="http://emoglen.law.columbia.edu/";>Eben
+<h3>Lunchtime Speaker</h3>
+
+<p><a href="http://emoglen.law.columbia.edu/";>Eben
 Moglen</a> will be the lunchtime speaker.  Professor Moglen is
 Professor of Law and Legal History at Columbia Law School and one of
 the nation's foremost scholars on copyright, patents and the proposed
@@ -52,15 +57,19 @@
 Directors and the foundation's General Counsel.  Professor Moglen has
 also written extensively on the SCO vs IBM lawsuit.
 </p>
-<p><b>GPL Compliance Case Studies:</b></p>
-<p style="margin-left: 40px;">* Overview of FSF's GPL Compliance
-Lab</p>
-<p style="margin-left: 80px;">We present a brief
+<h3>GPL Compliance Case Studies</h3>
+<dl>
+<dt>Overview of FSF's GPL Compliance
+Lab</dt>
+<dd>
+<p>We present a brief
 introduction to the work that FSF does to enforce the GPL and defend the
 freedoms granted by Free Software.</p>
-<p style="margin-left: 40px;">* GPL Violation Case Study A
-</p>
-<p style="margin-left: 80px;">In this case study, we consider one of
+</dd>
+<dt>GPL Violation Case Study A
+</dt>
+<dd>
+<p>In this case study, we consider one of
 the most complex and longest-running violations that FSF has handled.
 Company A distributed a derivative work of the GNU Complier Collection
 (GCC) without complete corresponding source, and refused to distribute
@@ -68,48 +77,60 @@
 follow the slow movement toward compliance and explain how FSF deals
 with sometimes belligerent violators.
 </p>
-<p style="margin-left: 40px;">* GPL Violation Case Study B</p>
-<p style="margin-left: 80px;">In this case study, we consider a
+</dd>
+<dt>GPL Violation Case Study B</dt>
+<dd>
+<p>In this case study, we consider a
 contrasting violation to Case A.  Company B, who sold a complete
 GNU/Linux distribution, had worked hard to be in compliance, but we
 had nevertheless found an infraction in their compliance efforts.  We
 explain how smoothly violations of this type can be resolved and the
 process that an otherwise friendly violator can expect.
 </p>
-<p style="margin-left: 40px;">* GPL Violation Case Study C</p>
-<p style="margin-left: 80px;">In this case study, we present a
+</dd>
+<dt>GPL Violation Case Study C</dt>
+<dd>
+<p>In this case study, we present a
 violation where an entire embedded GNU/Linux distribution was included
 in a consumer electronic device.  We consider the problems faced
 regarding kernel modules for device drivers for government-regulated
 hardware, and cases where both an upstream provider and a downstream
 distributor are in violation on separate matters.
 </p>
-<p style="margin-left: 40px;">* GPL Violation Case Study D</p>
-<p style="margin-left: 80px;">In this case study, we consider how to
+</dd>
+<dt>GPL Violation Case Study D</dt>
+<dd>
+<p>In this case study, we consider how to
 handle the inevitable violations that can occur from a company that is
 generally committed to doing Free Software as a regular part of its
 business, but &mdash; due to experimentation with new cutting edge
 business models, or because of mere oversights &mdash; has occasional
 GPL violations or near-violations.</p>
-<p style="margin-left: 40px;"> * Good Practices for GPL Compliance
-</p>
-<p style="margin-left: 80px;">After discussing the details of the
+</dd>
+<dt>Good Practices for GPL Compliance</dt>
+<dd>
+<p>After discussing the details of the
 various archetypes of GPL compliance efforts undertaken by FSF, we
 generalize what we have learned to advise on good practices to build a
 product from start to finish in compliance with GPL, and how to build
 internal policies to assure that your client or company is never faced
 with a violation report.</p>
-<p><b>Ethical Considerations for the Attorney Practicing Free
-Software</b></p>
-<p style="margin-left: 40px;">This portion of the course will focus on
+</dd>
+</dl>
+
+<h3>Ethical Considerations for the Attorney Practicing Free
+Software</h3>
+
+<p>This portion of the course will focus on
 ethical issues that may arise for attorneys counseling clients with
 respect to free software issues.  Many of these topics have more
 general application, but specific discussion of the ways in which
 these issues may arise for free software clients will be
 presented.</p>
-<p style="margin-left: 40px;"> * Part I: Representing Free Software
-Clients</p>
-<p style="margin-left: 80px;">An attorney's ethical duties run to not
+<dl>
+<dt>Part I: Representing Free Software Clients</dt>
+<dd>
+<p>An attorney's ethical duties run to not
 just their clients, but to potential clients and the general public as
 well.  Pro bono representation of free software clients not only
 conforms with the principles set forth by most Bar Associations, but
@@ -117,9 +138,10 @@
 retained, the duty of loyalty attaches and conflicts, be they direct,
 indirect, or political, should be identified and handled.
 </p>
-<p style="margin-left: 40px;"> * Part II: Practicing Free Software
-</p>
-<p style="margin-bottom: 0in; margin-left: 80px;">Differing ethical
+</dd>
+<dt>Part II: Practicing Free Software</dt>
+<dd>
+<p>Differing ethical
 issues arise in the context of counseling a client who is a free
 software licensor as opposed to one who is a free software licensee.
 Further still, representing a client who is both licensor and licensee
@@ -131,10 +153,12 @@
 relationship.  The ethical considerations relevant to each of these
 situations will be presented and discussed.
 </p>
-<p style="margin-left: 40px;">* Part III: More General Ethical
+</dd>
+<dt>Part III: More General Ethical
 Considerations Relevant to Free Software
-</p>
-<p style="margin-left: 80px;">Free software counseling is but one
+</dt>
+<dd>
+<p>Free software counseling is but one
 specialty within the realm of intellectual property counseling in
 general.  A review of various topics of more general application, but
 with special relevance to free software counseling, will be given
@@ -142,30 +166,30 @@
 issues arise when representing free software clients.  Patent
 prosecution and governing rules considerations are two such topics.
 </p>
+</dd>
+</dl>
+
+<h3>Pricing (Book by December 24, 2003 for early registration
+discount)</h3>
 
-<p><b>Pricing (Book by December 24, 2003 for early registration
-discount):</b></p>
-<div style="margin-left: 40px;">$495 for registrations on or before
-December 24, 2003 and $595 after December 24 <br />
-<br />
-<span style="font-family: Nimbus Roman No9 L,
-serif"><span style="text-decoration: underline;">Financial Aid
-Policy:</span> Applicants with annual incomes of up to $15,000 are
+<p>$495 for registrations on or before
+December 24, 2003 and $595 after December 24 </p>
+<p><b>Financial Aid
+Policy:</b> Applicants with annual incomes of up to $15,000 are
 entitled to a 75% discount.  People with incomes between $15,000 and
 $30,000 receive a 50% discount.  Any member of the judiciary,
 academics or attorneys from non-profit organizations receive a 10%
 discount.  If you fall within one of these categories, please contact
 John at <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a> or
 Ravi at <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a> or by
-phone at 617.620.9640.</span> <br /> <br />
-</div>
+phone at 617.620.9640.</p>
 
-<p style="font-family: Nimbus Roman No9 L, serif"><b>CLE Credits:</b>
+<p><b>CLE Credits:</b>
 Attorneys who successfully complete the day long course will be
 entitled to a total of 7.5 New York Transitional CLE credits, 3 in the
 area of Professional Practice and 4.5 toward the Ethics and
 Professionalism requirments.</p>
-<p style="font-family: Nimbus Roman No9 L, serif">Companies that have
+<p>Companies that have
 signed up as Corporate Patrons of FSF receive two complimentary seats
 per year at FSF seminars and reduced rates for additional
 participants.  Please
@@ -173,50 +197,75 @@
 more details.  You can find out more about the Corporate Patron
 Program at <a href="http://patron.fsf.org/";>
 http://patron.fsf.org</a></p>
-<p style="font-family: Nimbus Roman No9 L, serif">The seminar will be
+<p>The seminar will be
 held at Columbia Law School in New York.  Directions will be sent
 following registration.  For more information, please contact Ravi
 Khanna, FSF's Director of Communication
 at <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a> or by
 calling 1+617-620-9640.</p>
 
-</div>
+</div><!-- for id="content", starts in the include above -->
 <!--#include virtual="/server/footer.html" -->
 <div id="footer">
+<div class="unprintable">
 
-<p>
-Please send FSF &amp; GNU inquiries to 
-<a href="mailto:address@hidden";><em>address@hidden</em></a>.
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
 There are also <a href="/contact/">other ways to contact</a> 
-the FSF.
-<br />
-Please send broken links and other corrections or suggestions to
-<a href="mailto:address@hidden";><em>address@hidden</em></a>.
-</p>
+the FSF.  Broken links and other corrections or suggestions can be sent
+to <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
 
-<p>
-Please see the 
-<a href="/server/standards/README.translations.html">Translations
-README</a> for information on coordinating and submitting
-translations of this article.
-</p>
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 4.0.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
 
-<p>Copyright &copy; 2003, 2004, 2007, 2008, 2009, 2014 Free Software
+<p>Copyright &copy; 2003, 2004, 2007, 2008, 2009, 2014, 2015 Free Software
 Foundation, Inc.</p>
+
 <p>This page is licensed under a <a rel="license"
-href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
-Commons Attribution-NoDerivs 3.0 United States License</a>.
-</p>
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
+Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
 
 <!--#include virtual="/server/bottom-notes.html" -->
 
-<p>Updated:
+<p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2014/06/12 06:21:45 $
+$Date: 2015/10/23 07:05:44 $
 <!-- timestamp end -->
 </p>
 </div>
-
 </div>
 </body>
 </html>

Index: NYC_Seminars_Jan2004.html
===================================================================
RCS file: /web/www/www/licenses/NYC_Seminars_Jan2004.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
--- NYC_Seminars_Jan2004.html   12 Jun 2014 06:35:58 -0000      1.17
+++ NYC_Seminars_Jan2004.html   23 Oct 2015 07:05:46 -0000      1.18
@@ -1,26 +1,26 @@
 <!--#include virtual="/server/header.html" -->
-<title>FSF Seminars in 2004</title>
+<!-- Parent-Version: 1.78 -->
+<title>FSF Seminars in 2004
+- GNU Project - Free Software Foundation</title>
 <!--#include virtual="/licenses/po/NYC_Seminars_Jan2004.translist" -->
 <!--#include virtual="/server/banner.html" -->
 <h2>FSF Seminars in 2004</h2>
 
-<div style="text-align: center;"><big><span style="font-weight:
- bold;">FSF Offers Seminars </span></big><b>on<br /> Study and
+<blockquote><p>FSF Offers Seminars on Study and
  Analysis of the GPL and Legal Ethics in Free Software
- Licensing</b><br /><br /><br />
-</div>
+ Licensing</p></blockquote>
 
-<p><span style="font-family: Nimbus Roman No9 L, serif;">On January 20
+<p>On January 20
  and 21, 2004, the Free Software Foundation (FSF) will offer two
  day-long seminars on Free Software Licensing and the GNU GPL at
  Columbia Law School in New York.  The two days will provide a
- detailed </span>study and analysis of the GPL, review a few case
+ detailed study and analysis of the GPL, review a few case
  studies and look at legal ethics in Free Software
- Licensing<span style="font-family: Nimbus Roman No9 L, serif">. The
+ Licensing.  The
  seminars will be co-led by Daniel Ravicher, Senior Counsel to FSF and
- Bradley M. Kuhn, Executive Director of FSF. </span></p>
+ Bradley M. Kuhn, Executive Director of FSF.</p>
 
-<p><b>&ldquo;Detailed Study and Analysis of GPL and LGPL&rdquo;</b>,
+<p><i>Detailed Study and Analysis of GPL and LGPL</i>,
  the seminar on January 20, will give a section-by-section explanation
  of the most popular Free Software copyright license, the GNU General
  Public License (GNU GPL), and will educate lawyers, software
@@ -29,8 +29,8 @@
  existing, successful enterprises.
 </p>
 
-<p>On January 21, FSF will offer <b>&ldquo;GPL Compliance Case Studies
- and Legal Ethics in Free Software Licensing&rdquo;</b>.  Also a
+<p>On January 21, FSF will offer <i>GPL Compliance Case Studies
+ and Legal Ethics in Free Software Licensing</i>.  Also a
  day-long seminar, which will present the details of five different
  GPL compliance cases handled by FSF's GPL Compliance Laboratory.
  Each case offers unique insights into problems that can arise when
@@ -41,30 +41,32 @@
  clients that make use of or sell Free Software products.
 </p>
 
-<p><b>Lunchtime
-Speaker: </b><a href="http://emoglen.law.columbia.edu/";>Eben
+<h3>Lunchtime Speaker</h3>
+
+<p><a href="http://emoglen.law.columbia.edu/";>Eben
 Moglen</a> will be the lunchtime speaker.  Professor Moglen is
 Professor of Law and Legal History at Columbia Law School and one of
 the nation's foremost scholars on copyright, patents and the proposed
 &ldquo;Broadcast Flag&rdquo;.  He is also a member of FSF's Board of
 Directors and the foundation's General Counsel.  Professor Moglen has
-also written extensively on the SCO vs IBM lawsuit.  <br /> <br />
+also written extensively on the SCO vs IBM lawsuit.
 </p>
 
-<p><span style="font-weight: bold;">&ldquo;Detailed Study and Analysis
- of GPL and LGPL&rdquo;<br />
-</span><span style="font-family: Nimbus Roman No9 L,
- serif">January 20, 9 am to 6 pm<br />
-</span></p>
+<h3>Detailed Study and Analysis of GPL and LGPL</h3>
+
+<blockquote><p>January 20, 9 am to 6 pm</p></blockquote>
 
-<p style="margin-bottom: 0in; margin-left:
- 40px;"><i>Prerequisites:</i> Attendees should have a general
+<h4>Prerequisites</h4>
+
+<p>Attendees should have a general
  familiarity with software development processes.  A basic
  understanding of how copyright law typically applies to software is
  also helpful.
 </p>
 
-<p style="margin-bottom: 0in; margin-left: 40px;"><i>Audience: </i>The
+<h4>Audience</h4>
+
+<p>The
 course is of most interest to lawyers, software developers and
 managers who run (or have clients who run) software businesses that
 modify and/or redistribute software under terms of the GNU GPL or
@@ -74,48 +76,49 @@
 <p>The course will include the topics listed below, along with ample
 time for questions and discussions.
 </p>
-
-<p style="margin-bottom: 0in; margin-left: 40px;">* Free Software
-Principles and the Free Software Definition<br />
-* Preamble of the GNU General Public License (GPL)<br />
-* GPL, Section 0: Definitions, etc.<br />
-* GPL, Section 1: Grant for Verbatim Source Copying<br />
-* Derivative Works: Statute and Case Law<br />
-* GPL, Section 2: Grants for Source Derivative Works<br />
-* GPL, Section 3: Grants for Creating Binary Derivative Works<br />
-* The Implied Patent Grant in GPL<br />
-* GPL, Section 4: Termination of License<br />
-* GPL, Section 5: Acceptance of License<br />
-* GPL, Section 6: Prohibition on Further Restrictions<br />
-* GPL, Section 7: Conflicts with other Agreements or Orders<br />
-* GPL, Section 8: International Licensing Issues<br />
-* GPL, Section 9: FSF as GPL's Stewards<br />
-* GPL, Section 10: Copyright Holder's Exceptions to GPL<br />
-* GPL, Section 11: Disclaimer of Warranties<br />
-* GPL, Section 12: Limitation of Liability<br />
-* Lesser General Public License (LGPL)<br />
-</p>
+<dl>
+<dt>Free Software
+Principles and the Free Software Definition</dt>
+<dt>Preamble of the GNU General Public License (GPL)</dt>
+<dt>GPL, Section 0: Definitions, etc.</dt>
+<dt>GPL, Section 1: Grant for Verbatim Source Copying</dt>
+<dt>Derivative Works: Statute and Case Law</dt>
+<dt>GPL, Section 2: Grants for Source Derivative Works</dt>
+<dt>GPL, Section 3: Grants for Creating Binary Derivative Works</dt>
+<dt>The Implied Patent Grant in GPL</dt>
+<dt>GPL, Section 4: Termination of License</dt>
+<dt>GPL, Section 5: Acceptance of License</dt>
+<dt>GPL, Section 6: Prohibition on Further Restrictions</dt>
+<dt>GPL, Section 7: Conflicts with other Agreements or Orders</dt>
+<dt>GPL, Section 8: International Licensing Issues</dt>
+<dt>GPL, Section 9: FSF as GPL's Stewards</dt>
+<dt>GPL, Section 10: Copyright Holder's Exceptions to GPL</dt>
+<dt>GPL, Section 11: Disclaimer of Warranties</dt>
+<dt>GPL, Section 12: Limitation of Liability</dt>
+<dt>Lesser General Public License (LGPL)</dt>
+</dl>
 
 <p>For more details, please
  visit <a href="/licenses/200104_seminar.html">
  http://www.gnu.org/licenses/200104_seminar.html.</a>
-<br />
 </p>
 
-<p><b>&ldquo;GPL Compliance Case Studies
-and Legal Ethics in Free Software Licensing&rdquo;<br />
-</b><span style="font-family: Nimbus Roman No9 L, serif">January 21, 9
-am to 6 pm<br />
-</span></p>
+<h3>GPL Compliance Case Studies
+and Legal Ethics in Free Software Licensing</h3>
+
+<blockquote><p>January 21, 9 am to 6 pm</p></blockquote>
+
+<h4>Prerequisites</h4>
 
-<p style="margin-bottom: 0in; margin-left:
- 40px;"><i>Prerequisites:</i> Attendees should have successfully
+<p> Attendees should have successfully
  completed the course, a <i>Detailed Study and Analysis of GPL and
  LGPL</i>, as the material from that course forms the building blocks
  for this material, or have attended a previous <i>Free Software
  Licensing and the GNU GPL Seminar</i>.</p>
 
-<p style="margin-bottom: 0in; margin-left: 40px;"><i>Audience:</i> The
+<h4>Audience</h4>
+
+<p> The
 course is of most interest to lawyers who have clients or employers
 that deal with Free Software on a regular basis.  However, technical
 managers and executives whose businesses use or distribute Free
@@ -125,134 +128,154 @@
 time for questions and discussions.</p>
 
 <p>GPL Compliance Case Studies:</p>
-<p style="margin-bottom: 0in; margin-left: 40px;">* Overview of FSF's
-GPL Compliance Lab</p>
-<div style="margin-left: 40px;">* GPL Violation Case Study A<br />
-<div style="margin-left: 40px;">- Explains how FSF deals with sometimes
-belligerent violators.</div></div>
-<div style="margin-left: 40px;"> </div>
-<div style="margin-left: 40px;">* GPL Violation Case Study B<br />
-<div style="margin-left: 40px;">- Explains how smoothly violations can
+<dl>
+<dt>Overview of FSF's
+GPL Compliance Lab</dt>
+<dt>GPL Violation Case Study A</dt>
+<dd>
+<p>Explains how FSF deals with sometimes
+belligerent violators.</p>
+</dd>
+<dt>GPL Violation Case Study B</dt>
+<dd>
+<p>Explains how smoothly violations can
 be resolved and the process that an otherwise friendly violator can
-expect.<br />
-</div>
-* GPL Violation Case Study C<br />
-<div style="margin-left: 40px;">- Problems faced regarding kernel
+expect.</p></dd>
+<dt>GPL Violation Case Study C</dt>
+<dd><p>Problems faced regarding kernel
 modules for device drivers for government-regulated hardware, and cases
 where both an upstream provider and a downstream distributor are in
-violation on separate matters.<br />
-</div>
-* GPL Violation Case Study D<br />
-<div style="margin-left: 40px;">- Violations from a company committed
+violation on separate matters.</p></dd>
+<dt>GPL Violation Case Study D</dt>
+<dd><p>Violations from a company committed
 to doing Free Software but has occasional GPL violations or
-near-violations.<br />
-</div>
-* Good Practices for GPL Compliance<br /><br /></div>
+near-violations.</p>
+</dd>
+<dt>Good Practices for GPL Compliance</dt>
+</dl>
 
 <p>Ethical Considerations for the Attorney Practicing Free
 Software</p>
-<p style="margin-bottom: 0in; margin-left: 40px;"> * Part I:
-Representing Free Software Clients<br />
-* Part II: Practicing Free Software<br />
-* Part III: More General Ethical Considerations Relevant to Free
-Software<br />
-</p>
+<dl>
+<dt>Part I:
+Representing Free Software Clients</dt>
+<dt>Part II: Practicing Free Software</dt>
+<dt>Part III: More General Ethical Considerations Relevant to Free
+Software</dt>
+</dl>
 
 <p>For more details, please
  visit <a href="/licenses/210104_seminar.html">
  http://www.gnu.org/licenses/210104_seminar.html</a>.</p>
 
-<div style="text-align: left;"><br />
-<b>Pricing (Book by December 24, 2003 for registration
- discount):</b><br /> <br />
-<div style="margin-left: 40px;">Both Courses: $875 for registrations on
-or before December 24, 2003 and $975 after December 24<br />
-</div>
-<div style="margin-left: 40px;">First Course Only: $495 for
+<h3>Pricing (Book by December 24, 2003 for registration
+ discount)</h3>
+<p>Both Courses: $875 for registrations on
+or before December 24, 2003 and $975 after December 24
+</p>
+<p>First Course Only: $495 for
 registrations on or before December 24, 2003 and $595 after December
-24<br />
-<br />
-<span style="font-family: Nimbus Roman No9 L,
-serif"><span style="text-decoration: underline;">Financial Aid
-Policy:</span> Applicants with annual incomes of up to $15,000 are
+24</p>
+
+<p><b>Financial Aid
+Policy:</b> Applicants with annual incomes of up to $15,000 are
 entitled to a 75% discount.  People with incomes between $15,000 and
 $30,000 receive a 50% discount.  Any member of the judiciary,
 academics or attorneys from non-profit organizations receive a 10%
 discount.  If you fall within one of these categories, please contact
 John at <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a> or
 Ravi at <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a> or by
-phone at 617.620.9640.</span><br />  <br /> 
-</div>
-</div>
+phone at 617.620.9640.</p>
 
-<p><span style="font-family: Nimbus Roman No9 L, serif"><b>CLE
- Credits: </b>Attorneys who successfully
- complete </span><b>&ldquo;Detailed Study and Analysis of GPL and
- LGPL&rdquo; </b>on <span style="font-family: Nimbus Roman No9 L,
- serif">January 20, will be entitled to 7 New York Transitional CLE
- credits.  Those who complete </span><b>&ldquo;GPL Compliance Case
+<p><b>CLE
+ Credits:</b> Attorneys who successfully
+ complete <i>Detailed Study and Analysis of GPL and
+ LGPL </i> on January 20, will be entitled to 7 New York Transitional CLE
+ credits.  Those who complete <i>GPL Compliance Case
  Studies and Legal Ethics in Free Software
- Licensing&rdquo; </b>on <span style="font-family: Nimbus Roman No9 L,
- serif">January 21, will be entitled to a total of 7.5 New York
+ Licensing </i>on January 21, will be entitled to a total of 7.5 New York
  Transitional CLE credits, 3 in the area of Professional Practice and
- 4.5 toward the Ethics and Professionalism requirments.<br />
-</span></p>
+ 4.5 toward the Ethics and Professionalism requirments.
+</p>
 
-<p><span style="font-family: Nimbus Roman No9 L, serif">Companies that
+<p>Companies that
  have signed up as Corporate Patrons of FSF receive two complimentary
  seats at the seminar and reduced rates for additional participants.
  Please contact address@hidden for more details. You can find out more
  about the Corporate Patron Program
  at <a href="http://patron.fsf.org/";>
- http://patron.fsf.org.</a><br />
-</span></p>
+ http://patron.fsf.org.</a>
+</p>
 
-<p><span style="font-family: Nimbus Roman No9 L, serif">Both days of
+<p>Both days of
  the seminar will be held at Columbia Law School in New York.
  Directions will be sent following registration. For more information,
  please contact Ravi Khanna, FSF's Director of Communication
  at <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a> or by
- calling 1+617-620-9640.</span></p>
+ calling 1+617-620-9640.</p>
 
-</div>
+</div><!-- for id="content", starts in the include above -->
 <!--#include virtual="/server/footer.html" -->
 <div id="footer">
+<div class="unprintable">
 
-<p>
-Please send FSF &amp; GNU inquiries to 
-<a href="mailto:address@hidden";><em>address@hidden</em></a>.
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
 There are also <a href="/contact/">other ways to contact</a> 
-the FSF.
-<br />
-Please send broken links and other corrections or suggestions to
-<a href="mailto:address@hidden";><em>address@hidden</em></a>.
-</p>
+the FSF.  Broken links and other corrections or suggestions can be sent
+to <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
 
-<p>
-Please see the 
-<a href="/server/standards/README.translations.html">Translations
-README</a> for information on coordinating and submitting
-translations of this article.
-</p>
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 4.0.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright &copy; 2004, 2007, 2008, 2009, 2014, 2015 Free Software
+Foundation, Inc.</p>
 
-<p>
-Copyright &copy; 2004, 2007, 2008, 2009, 2014 Free Software Foundation, Inc.
-</p>
 <p>This page is licensed under a <a rel="license"
-href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
-Commons Attribution-NoDerivs 3.0 United States License</a>.
-</p>
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
+Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
 
 <!--#include virtual="/server/bottom-notes.html" -->
 
-<p>Updated:
+<p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2014/06/12 06:35:58 $
+$Date: 2015/10/23 07:05:46 $
 <!-- timestamp end -->
 </p>
 </div>
-
 </div>
 </body>
 </html>
-



reply via email to

[Prev in Thread] Current Thread [Next in Thread]