diff --git a/compliance-guide.tex b/compliance-guide.tex index ecc1817ac354d3a3e47b91990ba234fcbcb07f89..68c50d71e363e5ad6583844b0234f9e6780baba3 100644 --- a/compliance-guide.tex +++ b/compliance-guide.tex @@ -134,7 +134,7 @@ more complex obligations under the license.\footnote{While, there has been much discussion regarding copyleft and derivative works. In practical reality, this issue is not relevant to the vast majority of companies distributing GPL'd software. Those interested in this issue should study - \tutorialpartsplit{\texit{Detailed Analysis of the GNU GPL and Related + \tutorialpartsplit{\textit{Detailed Analysis of the GNU GPL and Related Licenses}'s Section on derivative works}{\S~\ref{derivative-works} of this tutorial}.} @@ -173,7 +173,7 @@ with an attorney.\footnote{If you would like more information on the application of derivative works doctrine to software, a detailed legal discussion is presented in our colleague Dan Ravicher's article, \textit{Software Derivative Work: A Circuit Dependent Determination} and in - \tutorialpartsplit{\texit{Detailed Analysis of the GNU GPL and Related + \tutorialpartsplit{\textit{Detailed Analysis of the GNU GPL and Related Licenses}'s Section on derivative works}{\S~\ref{derivative-works} of this tutorial}.} @@ -184,9 +184,9 @@ to run on a Linux-based operating system) distributed in conjunction with those works are separate works within the meaning of copyright law and the GPL\@. In such a case, the GPL requires you to provide complete corresponding source (CCS)\footnote{For more on CCS, see -\tutorialpartsplit{\texit{Detailed Analysis of the GNU GPL and Related +\tutorialpartsplit{\textit{Detailed Analysis of the GNU GPL and Related Licenses}'s Section on GPLv2~\S2 and GPLv3~\S1.}{\S~\ref{GPLv2s2} and \S~\ref{GPLv3s1} of - this tutorial}. + this tutorial}.} for the GPL'd components and your modifications thereto, but not for independent proprietary applications. The procedures described in this document address this typical scenario. @@ -768,7 +768,7 @@ ultimately secondary to those goals. Second, there are ``for-profit enforcers'' who use the GPL as a either a crippleware license, or sneakily induce infringement merely to gain proprietary licensing revenue. -Note that the latter model \texit{only} works for companies who hold 100\% of +Note that the latter model \textit{only} works for companies who hold 100\% of the copyrights in the infringed work. As such, multi-copyright-held works are fully insulated from these tactics.