Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

2013-03-14: EUPL reviewed

  • Loading branch information...
commit be7e4c25a4885deed0d670c1f9e8bd5b9fdb55ca 1 parent b563416
Karsten Reincke authored
View
3  btexmat/oscHyphenationEnInc.tex
@@ -21,6 +21,9 @@
\hyphenation{rein-cke}
+\hyphenation{Rein-cke}
\hyphenation{OS-LiC}
\hyphenation{ori-gi-nal}
\hyphenation{bi-na-ry}
+\hyphenation{Li-cen-ce}
+\hyphenation{li-cen-ce}
View
2  rel-number.tex
@@ -1 +1 @@
-0.91.3
+0.91.4
View
20 snippets/en/06C-osFulfillmentByToDoLists/0602-apacheFulfillToDoList.tex
@@ -28,7 +28,7 @@ \section{Apache licensed software}
Today, the current release of the Apache open source license is version 2.0,
elder versions are depricated\footnote{For details $\rightarrow$ OSLiC, pp.\
\pageref{sec:ProtectPowerOfApL}}. Because it focusses primarily on the
-\enquote{redistribution}\footcite[cf.][\nopage wp\ §4]{ApL20OsiLicense2004a},
+\enquote{redistribution}\footcite[cf.][\nopage wp\ §4]{Apl20OsiLicense2004a},
the following simplified Apache specific open source use case
finder\footnote{For details of the general OSUC finder $\rightarrow$ OSLiC, pp.\
\pageref{OsucTokens} and \pageref{OsucDefinitionTree}} can be used:
@@ -146,8 +146,8 @@ \subsection{ApL-1: Using the software only for yourself}
license with respect to this use case:
\begin{itemize}
\item You are allowed to use any kind of Apache software in any sense and in
- any context without any obligations as long as you do not give the software
- to 3rd parties.
+ any context without being obligied to do something as long as you do not
+ give the software to 3rd parties.
\end{itemize}
\item[prohibits] \ldots
@@ -575,8 +575,8 @@ \subsection{ApL-9: Passing a modified library as embedded binary}
\item \textbf{[voluntary:]} Arrange your binary distribution so that the
integrated Apache license and the \emph{notice text file} clearly refer only
to the embedded library and do not disturb the licensing of your own
- overarching work. It's a good tradition to keep the librabries, modules,
- snippet, or plugins in specific directiers which contain also all licensing
+ overarching work. It's a good tradition to keep the libraries, modules,
+ snippet, or plugins in specific directories which contain also all licensing
elements.
\end{itemize}
@@ -599,20 +599,20 @@ \subsection{Discussions and Explanations}
\enquote{[\ldots] to use the trade names, trademarks, service marks, or
product names of the Licensor, except as required for reasonable and customary
use in describing the origin of the Work and reproducing the content of the
- NOTICE file}\footcite[cf.][\nopage wp\ §6]{ApL20OsiLicense2004a}. On the other
+ NOTICE file}\footcite[cf.][\nopage wp\ §6]{Apl20OsiLicense2004a}. On the other
hand, this license alerts that all the patent licenses – granted to those who
\enquote{[\ldots] institute a patent litigation} – will terminate
- automatically\footcite[cf.][\nopage wp\ §3]{ApL20OsiLicense2004a}. Hence, the
+ automatically\footcite[cf.][\nopage wp\ §3]{Apl20OsiLicense2004a}. Hence, the
OSLiC generally (ApL-1 - ApL-9) interdicts to promote products or services by
these elements and to legally fight against patents linked to the software.
\item The ApL also requires to \enquote{[\ldots] give any other recipients of
the Work or Derivative Works a copy of this License}\footcite[cf.][\nopage wp\
- §4.1]{ApL20OsiLicense2004a}. Therefore, all \emph{4others} use cases contain
+ §4.1]{Apl20OsiLicense2004a}. Therefore, all \emph{4others} use cases contain
the respective mandatory condition (ApL-2 - ApL-9).
\item Additionally, the ApL requires, that modifications must be
- marked\footcite[cf.][\nopage wp\ §4.2]{ApL20OsiLicense2004a}. Thus, in all
+ marked\footcite[cf.][\nopage wp\ §4.2]{Apl20OsiLicense2004a}. Thus, in all
cases of passing the modified software in the form of source code the OSLiC
requires to mark the modifications and to integrate a hint into the notice
file – while in all the cases of passing the modified software in the form of
@@ -633,7 +633,7 @@ \subsection{Discussions and Explanations}
integrated as readable copy to each package distributed in the form of source
code, or – in case of binary distibutions – must be displayed
\enquote{[\ldots] if and wherever such third-party notices normally
- appear}\footcite[cf.][\nopage wp\ §4.4]{ApL20OsiLicense2004a}. Thus, the OSLiC
+ appear}\footcite[cf.][\nopage wp\ §4.4]{Apl20OsiLicense2004a}. Thus, the OSLiC
requires mandatorily that all source code distributions must include the
notice text file (ApL-2, ApL-4, ApL-6, ApL-8) and that all distributions of
binary applications which normally show such a copyrigth screen must integrate
View
4 snippets/en/06C-osFulfillmentByToDoLists/0603-bsdFulfillToDoList.tex
@@ -448,8 +448,8 @@ \subsection{BSD-9: Passing a modified library as embedded binary}
licensing elements -- esp.\ the BSD license text, the specific copyright
notice of the original author(s), and the BSD disclaimer -- clearly refer
only to the embedded library and do not disturb the licensing of your own
- overarching work. It's a good tradition to keep the librabries, modules,
- snippet, or plugins in specific directiers which contain also all licensing
+ overarching work. It's a good tradition to keep the libraries, modules,
+ snippet, or plugins in specific directories which contain also all licensing
elements.
\end{itemize}
View
549 snippets/en/06C-osFulfillmentByToDoLists/0605-euplFulfillToDoList-a.tex
@@ -1,549 +0,0 @@
-% Telekom osCompendium 'for being included' snippet template
-%
-% (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
-%
-% This LaTeX-File is licensed under the Creative Commons Attribution-ShareAlike
-% 3.0 Germany License (http://creativecommons.org/licenses/by-sa/3.0/de/): Feel
-% free 'to share (to copy, distribute and transmit)' or 'to remix (to adapt)'
-% it, if you '... distribute the resulting work under the same or similar
-% license to this one' and if you respect how 'you must attribute the work in
-% the manner specified by the author ...':
-%
-% In an internet based reuse please link the reused parts to www.telekom.com and
-% mention the original authors and Deutsche Telekom AG in a suitable manner. In
-% a paper-like reuse please insert a short hint to www.telekom.com and to the
-% original authors and Deutsche Telekom AG into your preface. For normal
-% quotations please use the scientific standard to cite.
-%
-% [ Framework derived from 'mind your Scholar Research Framework'
-% mycsrf (c) K. Reincke 2012 CC BY 3.0 http://mycsrf.fodina.de/ ]
-%
-
-
-%% use all entries of the bibliography
-%\nocite{*}
-
-\section{EUPL licensed software}
-
-Explictly, the European Union Public License does not distinguish the
-distribution of the source code from that of the binaries on a finely graduated
-level: first and foremost, the \enquote{Obligations of the Licensee} refer to
-both forms\footcite[cf.][\nopage wp\ §5]{EuplLicense2007en}. Implicitly, there
-nevertheless arises an important difference by the requirement that a
-\enquote{Licensee}, while he \enquote{[\ldots] (distributes) copies of the Work
-[\ldots]} -- which must be read as the \enquote{Original Work and/or its
-Derivative Work} -- has to \enquote{[\ldots] provide a machine-readable copy of
-the Source Code or indicate a repository where this Source (is) easily and
-freely available for as long as the Licensee continues to distribute [\ldots]
-the Work}\footnote{\cite[cf.][\nopage wp\ §5]{EuplLicense2007en} The term
-\enquote{Work} is resolved if §1.}: This requirement is of course already
-fulfilled in the moment the licensee distributes the source code. Thus, for
-getting simply processable task list, the following EUPL specific open source
-use case structure\footnote{For details of the general OSUC finder $\rightarrow$
-OSLiC, pp.\ \pageref{OsucTokens} and \pageref{OsucDefinitionTree}} can be used:
-
-\tikzstyle{nodv} = [font=\small, ellipse, draw, fill=gray!10,
- text width=2cm, text centered, minimum height=2em]
-
-\tikzstyle{nods} = [font=\footnotesize, rectangle, draw, fill=gray!20,
- text width=1.2cm, text centered, rounded corners, minimum height=3em]
-
-\tikzstyle{nodb} = [font=\footnotesize, rectangle, draw, fill=gray!20,
- text width=2.2cm, text centered, rounded corners, minimum height=3em]
-
-\tikzstyle{leaf} = [font=\tiny, rectangle, draw, fill=gray!30,
- text width=1.2cm, text centered, minimum height=6em]
-
-\tikzstyle{edge} = [draw, -latex']
-
-\begin{tikzpicture}[]
-
-\node[nodv] (l71) at (4,10) {EUPL};
-
-\node[nodb] (l61) at (0,8.6) {\textit{recipient:} \\ \textbf{4yourself}};
-\node[nodb] (l62) at (6.5,8.6) {\textit{recipient:} \\ \textbf{4others}};
-
-\node[nodb] (l51) at (2.5,7) {\textit{state:} \\ \textbf{unmodified}};
-\node[nodb] (l52) at (9.3,7) {\textit{state:} \\ \textbf{modified}};
-
-\node[nods] (l41) at (1.8,5.4) {\textit{form:} \textbf{source}};
-\node[nods] (l42) at (3.6,5.4) {\textit{form:} \textbf{binary}};
-\node[nodb] (l43) at (6.5,5.4) {\textit{type:} \\ \textbf{proapse}};
-\node[nodb] (l44) at (12,5.4) {\textit{type:} \\ \textbf{snimoli}};
-
-
-\node[nods] (l31) at (5.4,3.8) {\textit{form:} \textbf{source}};
-\node[nods] (l32) at (7.2,3.8) {\textit{form:} \textbf{binary}};
-\node[nodb] (l33) at (10,3.8) {\textit{context:} \\ \textbf{independent}};
-\node[nodb] (l34) at (13.5,3.8) {\textit{context:} \\ \textbf{embedded}};
-
-\node[nods] (l21) at (9,2.2) {\textit{form:} \textbf{source}};
-\node[nods] (l22) at (10.8,2.2) {\textit{form:} \textbf{binary}};
-\node[nods] (l23) at (12.6,2.2) {\textit{form:} \textbf{source}};
-\node[nods] (l24) at (14.4,2.2) {\textit{form:} \textbf{binary}};
-
-\node[leaf] (l11) at (0,0) {\textbf{EUPL-1} \textit{using software only
-for yourself}};
-
-\node[leaf] (l12) at (1.8,0) { \textbf{EUPL-2} \textit{ distributing unmodified
-software as sources}};
-
-\node[leaf] (l13) at (3.6,0) { \textbf{EUPL-3} \textit{ distributing unmodified
-software as binaries}};
-
-\node[leaf] (l14) at (5.4,0) { \textbf{EUPL-4} \textit{ distributing modified
-program as sources}};
-
-\node[leaf] (l15) at (7.2,0) { \textbf{EUPL-5} \textit{ distributing modified
-program as binaries}};
-
-\node[leaf] (l16) at (9,0) { \textbf{EUPL-6} \textit{ distributing modified
-library as independent sources}};
-
-\node[leaf] (l17) at (10.8,0) { \textbf{EUPL-7} \textit{distributing modified
-library as independent binaries}};
-
-\node[leaf] (l18) at (12.6,0) { \textbf{EUPL-8} \textit{distributing
-modified library as embedded sources}};
-
-\node[leaf] (l19) at (14.4,0) { \textbf{EUPL-9} \textit{ distributing modified
-library as embedded binaries}};
-
-
-\path [edge] (l71) -- (l61);
-\path [edge] (l71) -- (l62);
-\path [edge] (l61) -- (l11);
-\path [edge] (l62) -- (l51);
-\path [edge] (l62) -- (l52);
-\path [edge] (l51) -- (l41);
-\path [edge] (l51) -- (l42);
-\path [edge] (l52) -- (l43);
-\path [edge] (l52) -- (l44);
-\path [edge] (l41) -- (l12);
-\path [edge] (l42) -- (l13);
-\path [edge] (l43) -- (l31);
-\path [edge] (l43) -- (l32);
-\path [edge] (l44) -- (l33);
-\path [edge] (l44) -- (l34);
-\path [edge] (l31) -- (l14);
-\path [edge] (l32) -- (l15);
-\path [edge] (l33) -- (l21);
-\path [edge] (l33) -- (l22);
-\path [edge] (l34) -- (l23);
-\path [edge] (l34) -- (l24);
-\path [edge] (l21) -- (l16);
-\path [edge] (l22) -- (l17);
-\path [edge] (l23) -- (l18);
-\path [edge] (l24) -- (l19);
-
-\end{tikzpicture}
-
-
-\subsection{EUPL-1: Using the software only for yourself}
-\label{OSUC-01-EUPL} \label{OSUC-03-EUPL}
-\label{OSUC-06-EUPL} \label{OSUC-09-EUPL}
-
-\begin{description}
-\item[means] that you are going to use a received EUPL licensed software only
-for yourself and that you do not hand it over to any 3rd party in any sense.
-\item[covers] OSUC-01, OSUC-03, OSUC-06, and OSUC-09\footnote{For details
-$\rightarrow$ OSLiC, pp.\ \pageref{OSUC-01-DEF} - \pageref{OSUC-09-DEF}}
-\item[requires] no tasks in order to fulfill the conditions of the EUPL 2.0
-license with respect to this use case:
- \begin{itemize}
- \item You are allowed to use any kind of EUPL software in any sense and in
- any context without any obligations as long as you do not give the software
- to 3rd parties.
- \end{itemize}
-\item[prohibits] to promote any service you establish on the base of this
-privately used software by trade names, trademarks, service marks, or names of
-licensor
-\end{description}
-
-\subsection{EUPL-2: Passing the unmodified software as source code}
-\label{OSUC-02-EUPL} \label{OSUC-05-EUPL} \label{OSUC-07-EUPL}
-
-\begin{description}
-\item[means] that you are going to distribute an unmodified version of the
-received EUPL software to 3rd parties in the form of a set of source code files or
-an integrated source code package\footnote{In this case it doesn't matter
-whether you distribute a program, an application, a server, a snippet, a
-module, a library, or a plugin as an independent or an embedded unit}
-
-\item[covers] OSUC-02, OSUC-05, OSUC-07\footnote{For details $\rightarrow$ OSLiC, pp.\
-\pageref{OSUC-02-DEF} - \pageref{OSUC-07-DEF}}
-
-\item[requires] the following tasks in order to fulfill the license conditions:
-\begin{itemize}
- \item \textbf{[mandatory:]} Give the recipient a copy of the EUPL 2.0
- license. If it is not already present in the software package, add
- it\footnote{For implementing the handover of files correctly $\rightarrow$
- OSLiC, p. \pageref{DistributingFilesHint}}.
- \item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ the
- specific copyright notice of the original author(s) -- are retained in your
- package in the form you have received them.
- \item \textbf{[mandatory:]} Ensure that a \emph{notice text file}\footnote{
- The EUPL license seems purposely to be a bit ambiguous: it uses the term
- \enquote{``Notice'' text file}. In its strict sense, the term refers to a file
- named 'NOTICE.[txt\textbar{}pdf\textbar{}\ldots]'. In a weaker sense, it may
- denote any (text) file containing (licensing) notices. For being sure to act
- according to this requirement you should also read this term in the broader
- sense if there is no text file named 'NOTICE'} is retained in your package in
- the form you have received it.
-
- \item \textbf{[voluntary:]} Let the documentation of your distribution and/or
- your additional material also reproduce the content of the \emph{notice text
- file}, a hint to the software name, a link to its homepage, and a link to the
- EUPL 2.0 license.
-\end{itemize}
-
-\item[prohibits] to institute any patent litigation against anyone alleging that
-the software constitutes patent infringement.
-
-\end{description}
-
-
-\subsection{EUPL-3: Passing the unmodified software as binaries}
-
-\begin{description}
-\item[means] that you are going to distribute an unmodified version of the
-received EUPL software to 3rd parties in the form of a set of binary files or an
-integrated bi\-na\-ry package\footnote{In this case it doesn't matter
-whether you distribute a program, an application, a server, a snippet, a
-module, a library, or a plugin as an independent or an embedded unit}
-
-\item[covers] OSUC-02, OSUC-05, OSUC-07\footnote{For details $\rightarrow$ OSLiC, pp.\
-\pageref{OSUC-02-DEF} - \pageref{OSUC-07-DEF}}
-
-\item[requires] the following tasks in order to fulfill the license conditions:
-\begin{itemize}
- \item \textbf{[mandatory:]} Give the recipient a copy of the EUPL 2.0
- license. If it is not already present in the binary package, add
- it\footnote{For implementing the handover of files correctly $\rightarrow$
- OSLiC, p. \pageref{DistributingFilesHint}}.
-
- \item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ the
- specific copyright notice of the original author(s) -- are retained in your
- package in the form you have received them. If you compile the binary from the
- sources, ensure that all the licensing elements are also incorporated into the
- package.
- \item \textbf{[mandatory:]} Ensure that the \emph{notice text file} is
- retained or integrated into your binary package in the form you have initially
- received
- it.
- \item \textbf{[mandatory:]} Ensure that the \emph{notice text file} is also
- reproduced if and whereever such third-party notices normally appear --
- especially, if you are distributing an unmodified EUPL licensed library as
- embedded component of your own work which displays its own copyright notice.
-
- \item \textbf{[voluntary:]} Let the documentation of your distribution and/or
- your additional material also reproduce the content of the \emph{notice text
- file}, a hint to the software name, a link to its homepage, and a link to the
- EUPL 2.0 license -- especially as subsection of your own copyright notice.
-\end{itemize}
-
-\item[prohibits] to institute any patent litigation against anyone alleging that
-the software constitutes patent infringement.
-
-\end{description}
-
-\subsection{EUPL-4: Passing a modified program as source code}
-\label{OSUC-04-EUPL}
-
-\begin{description}
-\item[means] that you are going to distribute a modified version of the received
-EUPL licensed program, application, or server (proapse) to 3rd parties in form
-of a set of source code files or an integrated source code package.
-\item[covers] OSUC-04\footnote{For details $\rightarrow$ OSLiC, pp.\ \pageref{OSUC-04-DEF}}
-\item[requires] the tasks in order to fulfill the license conditions:
-\begin{itemize}
-
- \item \textbf{[mandatory:]} Give the recipient a copy of the EUPL 2.0
- license. If it is not already present in the software package, add
- it\footnote{For implementing the handover of files correctly $\rightarrow$
- OSLiC, p. \pageref{DistributingFilesHint}}.
-
- \item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ the
- specific copyright notice of the original author(s) -- are retained in your
- package in the form you have received them.
-
- \item \textbf{[mandatory:]} Ensure that the \emph{notice text file} contains at least
- all the information of that \emph{notice text file} you have received.
-
- \item \textbf{[mandatory:]} Ensure that the \emph{notice text file} is also
- reproduced if and whereever such third-party notices normally appear. If the
- program already displays a copyright dialog, update it in an appropriate
- manner.
-
- \item \textbf{[voluntary:]} Inside of the source code, mark all your
- modifications thoroughly. Generate a \emph{notice text file}, if it still does not
- exist. Add (sic!) a description of your modifications into the \emph{notice text file}.
-
- \item \textbf{[voluntary:]} Let the documentation of your distribution and/or
- your additional material also reproduce the content of the \emph{notice text
- file}, a hint to the software name, a link to its homepage, and a link to the
- EUPL 2.0 license.
-
- \end{itemize}
-
-\item[prohibits] to institute any patent litigation against anyone alleging that
-the software constitutes patent infringement.
-
-\end{description}
-
-\subsection{EUPL-5: Passing a modified program as binary}
-
-\begin{description}
-\item[means] that you are going to distribute a modified version of the received
-EUPL licensed pro\-gram, application, or server (proapse) to 3rd parties in
-the form of a set of binary files or an integrated binary package.
-\item[covers] OSUC-04\footnote{For details $\rightarrow$ OSLiC, pp.\ \pageref{OSUC-04-DEF}}
-\item[requires] the tasks in order to fulfill the license conditions:
-\begin{itemize}
-
- \item \textbf{[mandatory:]} Give the recipient a copy of the EUPL 2.0
- license. If it is not already present in the binary package, add
- it\footnote{For implementing the handover of files correctly $\rightarrow$
- OSLiC, p. \pageref{DistributingFilesHint}}.
-
- \item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ the
- specific copyright notice of the original author(s) -- are retained in your
- package in the form you have received them. If you compile the binary from the
- sources, ensure that all the licensing elements are also incorporated into the
- package.
-
- \item \textbf{[mandatory:]} Ensure that the \emph{notice text file} contains at least
- all the information of that \emph{notice text file} you have received.
-
- \item \textbf{[mandatory:]} Ensure that the \emph{notice text file} is also
- reproduced if and whereever such third-party notices normally appear. If the
- program already displays a copyright dialog, update it in an appropriate
- manner.
-
- \item \textbf{[voluntary:]} Inside of the source code, mark all your
- modifications thoroughly. Generate a \emph{notice text file}, if it still does not
- exist. Expand (sic!) the \emph{notice text file} by a description of your
- modifications.
-
- \item \textbf{[voluntary:]} Let the documentation of your distribution and/or
- your additional material also reproduce the content of the \emph{notice text
- file}, a hint to the software name, a link to its homepage, and a link to the
- EUPL 2.0 license -- especially as a subsection of your own copyright notice.
-
-\end{itemize}
-
-\item[prohibits] to institute any patent litigation against anyone alleging that
-the software constitutes patent infringement.
-
-\end{description}
-
-\subsection{EUPL-6: Passing a modified library as independent source code}
-\label{OSUC-08-EUPL}
-
-\begin{description}
-\item[means] that you are going to distribute a modified version of the received
-EUPL licensed code snippet, module, library, or plugin (snimoli) to 3rd
-parties in the form of a set of source code files or an integrated source code
-package, but without embedding it into another larger software unit.
-\item[covers] OSUC-08\footnote{For details $\rightarrow$ OSLiC, pp.\ \pageref{OSUC-08-DEF}}
-\item[requires] the tasks in order to fulfill the license conditions:
-\begin{itemize}
-
- \item \textbf{[mandatory:]} Give the recipient a copy of the EUPL 2.0
- license. If it is not already present in the software package, add
- it\footnote{For implementing the handover of files correctly $\rightarrow$
- OSLiC, p. \pageref{DistributingFilesHint}}.
-
- \item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ the
- specific copyright notice of the original author(s) -- are retained in your
- package in the form you have received them.
-
- \item \textbf{[mandatory:]} Ensure that the \emph{notice text file} contains at least
- all the information of that \emph{notice text file} you have received.
-
- \item \textbf{[voluntary:]} Inside of the source code, mark all your
- modifications thoroughly. Generate a \emph{notice text file}, if it still does not
- exist. Expand (sic!) the \emph{notice text file} by a description of your
- modifications.
-
- \item \textbf{[voluntary:]} Let the documentation of your distribution and/or
- your additional material also reproduce the content of the \emph{notice text
- file}, a hint to the software name, a link to its homepage, and a link to the
- EUPL 2.0 license.
-
-\end{itemize}
-
-\item[prohibits] to institute any patent litigation against anyone alleging that
-the software constitutes patent infringement.
-
-\end{description}
-
-
-\subsection{EUPL-7: Passing a modified library as independent binary}
-
-\begin{description}
-\item[means] that you are going to distribute a modified version of the received
-Appache licensed code snippet, module, library, or plugin (snimoli) to 3rd
-parties in the form of a set of binary files or an integrated binary package but
-without embedding it into another larger software unit.
-\item[covers] OSUC-08\footnote{For details $\rightarrow$ OSLiC, pp.\ \pageref{OSUC-08-DEF}}
-\item[requires] the tasks in order to fulfill the license conditions:
-\begin{itemize}
-
- \item \textbf{[mandatory:]} Give the recipient a copy of the EUPL 2.0
- license. If it is not already present in the binary package, add
- it\footnote{For implementing the handover of files correctly $\rightarrow$
- OSLiC, p. \pageref{DistributingFilesHint}}.
-
- \item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ the
- specific copyright notice of the original author(s) -- are retained in your
- package in the form you have received them. If you compile the binary from the
- sources, ensure that all the licensing elements are also incorporated into the
- package.
-
- \item \textbf{[mandatory:]} Ensure that the \emph{notice text file} contains at least
- all the information of that \emph{notice text file} you have received.
-
- \item \textbf{[voluntary:]} Inside of the source code, mark all your
- modifications thoroughly. Generate a \emph{notice text file}, if it still does not
- exist. Expand (sic!) the \emph{notice text file} by a description of your
- modifications.
-
- \item \textbf{[voluntary:]} Let the documentation of your distribution and/or
- your additional material also reproduce the content of the \emph{notice text
- file}, a hint to the software name, a link to its homepage, and a link to the
- EUPL 2.0 license -- especially as a subsection of your own copyright notice.
-
-\end{itemize}
-
-\item[prohibits] to institute any patent litigation against anyone alleging that
-the software constitutes patent infringement.
-
-\end{description}
-
-\subsection{EUPL-8: Passing a modified library as embedded source code}
-\label{OSUC-10-EUPL}
-
-\begin{description}
-\item[means] that you are going to distribute a modified version of the received
-EUPL licensed code snippet, module, library, or plugin (snimoli) to 3rd
-parties in the form of a set of source code files or an integrated source code
-package together with another larger software unit which contains this code
-snippet, module, library, or plugin as an embedded component.
-\item[covers] OSUC-10\footnote{For details $\rightarrow$ OSLiC, pp.\ \pageref{OSUC-10-DEF}}
-\item[requires] the tasks in order to fulfill the license conditions:
-\begin{itemize}
-
- \item \textbf{[mandatory:]} Give the recipient a copy of the EUPL 2.0
- license. If it is not already present in the software package, add
- it\footnote{For implementing the handover of files correctly $\rightarrow$
- OSLiC, p. \pageref{DistributingFilesHint}}.
-
- \item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ the
- specific copyright notice of the original author(s) -- are retained in your
- package in the form you have received them.
-
- \item \textbf{[mandatory:]} Ensure that the \emph{notice text file} contains at least
- all the information of that \emph{notice text file} you have received.
-
- \item \textbf{[mandatory:]} Ensure that the \emph{notice text file} is also
- reproduced if and whereever such third-party notices normally appear. If your
- overarching program displays its own copyright dialog, insert this information
- there.
-
- \item \textbf{[voluntary:]} Inside of the source code, mark all your
- modifications thoroughly. Generate a \emph{notice text file}, if it still does not
- exist. Expand (sic!) the \emph{notice text file} by a description of your
- modifications.
-
- \item \textbf{[voluntary:]} Let the documentation of your distribution and/or
- your additional material also reproduce the content of the \emph{notice text
- file}, a hint to the software name, a link to its homepage, and a link to the
- EUPL 2.0 license.
-
- \item \textbf{[voluntary:]} Arrange your source code distribution so that the
- integrated EUPL license and the \emph{notice text file} clearly refer only
- to the embedded library and do not disturb the licensing of your own
- overarching work. It's a good tradition to keep the embedded components like
- libraries, modules, snippets, or plugins in specific directory which contains
- also all additional licensing elements.
-
-\end{itemize}
-
-\item[prohibits] to institute any patent litigation against anyone alleging that
-the software constitutes patent infringement.
-
-\end{description}
-
-
-\subsection{EUPL-9: Passing a modified library as embedded binary}
-
-\begin{description}
-\item[means] that you are going to distribute a modified version of the received
-EUPL licensed code snippet, module, library, or plugin to 3rd parties in form
-of a set of binary files or an integrated binary package together with another
-larger software unit which contains this code snippet, module, library, or
-plugin as an embedded component.
-\item[covers] OSUC-10\footnote{For details $\rightarrow$ OSLiC, pp.\ \pageref{OSUC-10-DEF}}
-\item[requires] the tasks in order to fulfill the license conditions:
-\begin{itemize}
-
- \item \textbf{[mandatory:]} Give the recipient a copy of the EUPL 2.0
- license. If it is not already present in the binary package, add
- it\footnote{For implementing the handover of files correctly $\rightarrow$
- OSLiC, p. \pageref{DistributingFilesHint}}.
-
- \item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ the
- specific copyright notice of the original author(s) -- are retained in your
- package in the form you have received them. If you compile the binary from the
- sources, ensure that all the licensing elements are also incorporated into the
- package.
-
- \item \textbf{[mandatory:]} Ensure that the \emph{notice text file} contains at least
- all the information of that \emph{notice text file} you have received.
-
- \item \textbf{[mandatory:]} Ensure that the \emph{notice text file} is also
- reproduced if and whereever such third-party notices normally appear. If your
- overarching program displays its own copyright dialog, insert this information
- there.
-
- \item \textbf{[voluntary:]} Inside of the source code, mark all your
- modifications thoroughly. Generate a \emph{notice text file}, if it still does not
- exist. Expand (sic!) the \emph{notice text file} by a description of your
- modifications.
-
- \item \textbf{[voluntary:]} Let the documentation of your distribution and/or
- your additional material also reproduce the content of the \emph{notice text
- file}, a hint to the software name, a link to its homepage, and a link to the
- EUPL 2.0 license -- especially as subsection of your own copyright notice.
-
-
- \item \textbf{[voluntary:]} Arrange your binary distribution so that the
- integrated EUPL license and the \emph{notice text file} clearly refer only
- to the embedded library and do not disturb the licensing of your own
- overarching work. It's a good tradition to keep the librabries, modules,
- snippet, or plugins in specific directiers which contain also all licensing
- elements.
-
-\end{itemize}
-
-\item[prohibits] to institute any patent litigation against anyone alleging that
-the software constitutes patent infringement.
-
-\end{description}
-
-\subsection{Discussions and Explanations [tbd]}
-
-
-
-
-\begin{itemize}
- \item The EUPL explicitly \enquote{[\ldots] does not grant permission to use
- the trade na\-mes, trademarks, service marks, or names of the Licensor
- [\ldots]}\footcite[cf.][\nopage wp\ §5, Section \enquote{Legal
- Protection}]{EuplLicense2007en}. Thus, we inserted the corresponding
- interdiction into each 'prohibits'-section of all the fulfilling to-do lists.
-\end{itemize}
-
-
-%\bibliography{../../../bibfiles/oscResourcesEn}
View
183 snippets/en/06C-osFulfillmentByToDoLists/0605-euplFulfillToDoList.tex
@@ -29,20 +29,20 @@ \section{EUPL licensed software}
of the source code from that of the binaries: In the chapter
\enquote{Communication of the Source Code}, it allows to \enquote{provide the
Work either in its Source Code form, or as Executable
-Code}\footcite[cf.][\nopage wp\ §3]{EuplLicense2007en}. But if any pieces of
-EUPL licensed software is distributed as binary package, then the license
+Code}\footcite[cf.][\nopage wp\ §3]{EuplLicense2007en}. But if a piece of EUPL
+licensed software is distributed as binary package, then the license
additionally requires that the distributor either \enquote{[\ldots] provides a
machine-readable copy of the Source Code [\ldots]} directly together with the
binaries\footcite[cf.][\nopage wp\ §5]{EuplLicense2007en} or that he
\enquote{[\ldots] indicates [\ldots] a repository where the Source Code is
easily and freely accessible for as long as the Licensor continues to distribute
-[\ldots] the Work}\footnote{\cite[cf.][\nopage wp\ §3.]{EuplLicense2007en}} --
-namely regardless whether the software has been modified or not. The other
-\enquote{obligations of the licensee} refer to both forms\footcite[cf.][\nopage
-wp\ §5]{EuplLicense2007en}. Thus, for getting simply processable task list, the
-following EUPL specific open source use case structure\footnote{For details of
-the general OSUC finder $\rightarrow$ OSLiC, pp.\ \pageref{OsucTokens} and
-\pageref{OsucDefinitionTree}} can be used:
+[\ldots] the Work}\footnote{\cite[cf.][\nopage wp\ §3.]{EuplLicense2007en}}. For
+respecting this conditions it is irrelevant whether the software has been
+modified or not; and all the other \enquote{obligations of the licensee} refer
+to both forms\footcite[cf.][\nopage wp\ §5]{EuplLicense2007en}. Thus, for
+getting simply processable task list, the following EUPL specific open source
+use case structure\footnote{For details of the general OSUC finder $\rightarrow$
+OSLiC, pp.\ \pageref{OsucTokens} and \pageref{OsucDefinitionTree}} can be used:
\tikzstyle{nodv} = [font=\small, ellipse, draw, fill=gray!10,
text width=2cm, text centered, minimum height=2em]
@@ -157,8 +157,8 @@ \subsection{EUPL-1: Using the software only for yourself}
license with respect to this use case:
\begin{itemize}
\item You are allowed to use any kind of EUPL software in any sense and in
- any context without any obligations as long as you do not give the software
- to 3rd parties.
+ any context without being obligied to do something as long as you do not
+ give the software to 3rd parties.
\end{itemize}
\item[prohibits] \ldots
@@ -190,7 +190,7 @@ \subsection{EUPL-2: Passing the unmodified software as source code}
\item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ the
copyright, patent or trademarks notices and all notices that refer to the
- Licence and to the disclaimer of warranties -- are retained in your package in
+ license and to the disclaimer of warranties -- are retained in your package in
the form you have received them. If you compile the binary from the sources,
ensure that all the licensing elements are also incorporated into the package.
@@ -200,9 +200,9 @@ \subsection{EUPL-2: Passing the unmodified software as source code}
OSLiC, p. \pageref{DistributingFilesHint}}.
\item \textbf{[voluntary:]} Let the documentation of your distribution and/or
- your additional material also reproduce the content of the \emph{notice text
- file}, a hint to the software name, a link to its homepage, and a link to the
- EUPL 1.1 license.
+ your additional material also reproduce the content of the existing
+ \emph{copyright notice text files}, a hint to the software name, a link to its
+ homepage, and a link to the EUPL 1.1 license.
\end{itemize}
\item[prohibits] \ldots
@@ -233,7 +233,7 @@ \subsection{EUPL-3: Passing the unmodified software as binaries}
\item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ the
copyright, patent or trademarks notices and all notices that refer to the
- Licence and to the disclaimer of warranties -- are retained in your package in
+ license and to the disclaimer of warranties -- are retained in your package in
the form you have received them. If you compile the binary from the sources,
ensure that all the licensing elements are also incorporated into the package.
@@ -244,15 +244,15 @@ \subsection{EUPL-3: Passing the unmodified software as binaries}
\item \textbf{[mandatory:]} Make the source code of the distributed software
accessible via a repository (even if you do not modified it): Push the source
- code package into the repository, make it downloadable via the internet, and
- integrate easily to find descriptions into the distribution package how to the
- code can be received from where. Ensure, that this repository is online for as
- long as you continue to distribute the software.
+ code package into a repository, make it downloadable via the internet, and
+ integrate an easily to find descriptions into the distribution package which
+ explains how to the code can be received from where. Ensure, that this
+ repository is online for as long as you continue to distribute the software.
\item \textbf{[voluntary:]} Let the documentation of your distribution and/or
- your additional material also reproduce the content of the \emph{notice text
- file}, a hint to the software name, a link to its homepage, and a link to the
- EUPL 1.1 license -- especially as subsection of your own copyright notice.
+ your additional material also reproduce the content of the existing
+ \emph{copyright notice text files}, a hint to the software name, a link to its
+ homepage, and a link to the EUPL 1.1 license.
\end{itemize}
\item[prohibits] \ldots
@@ -278,7 +278,7 @@ \subsection{EUPL-4: Passing a modified program as source code}
\item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ the
copyright, patent or trademarks notices and all notices that refer to the
- Licence and to the disclaimer of warranties -- are retained in your package in
+ license and to the disclaimer of warranties -- are retained in your package in
the form you have received them.
\item \textbf{[mandatory:]} Give the recipient a copy of the EUPL 1.1
@@ -294,9 +294,9 @@ \subsection{EUPL-4: Passing a modified program as source code}
embedded libary\footnote{or snippet, or module, or plugin} thoroughly.
\item \textbf{[voluntary:]} Let the documentation of your distribution and/or
- your additional material also reproduce the content of the \emph{notice text
- file}, a hint to the software name, a link to its homepage, and a link to the
- EUPL 1.1 license.
+ your additional material also reproduce the content of the existing
+ \emph{copyright notice text files}, a hint to the software name, a link to its
+ homepage, and a link to the EUPL 1.1 license.
\end{itemize}
@@ -322,7 +322,7 @@ \subsection{EUPL-5: Passing a modified program as binary}
\item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ the
copyright, patent or trademarks notices and all notices that refer to the
- Licence and to the disclaimer of warranties -- are retained in your package in
+ license and to the disclaimer of warranties -- are retained in your package in
the form you have received them. If you compile the binary from the sources,
ensure that all the licensing elements are also incorporated into the package.
@@ -336,19 +336,21 @@ \subsection{EUPL-5: Passing a modified program as binary}
file} by a description of your modifications.
\item \textbf{[mandatory:]} Make the source code of the distributed software
- accessible via a repository (although you modified it): Push the source code
- package into the repository, make it downloadable via the internet, and
- integrate easily to find descriptions into the distribution package how to the
- code can be received from where. Ensure, that this repository is online for as
- long as you continue to distribute the software.
+ accessible via a repository (although you modified it): Push the source
+ code package into a repository, make it downloadable via the internet, and
+ integrate an easily to find descriptions into the distribution package which
+ explains how to the code can be received from where. Ensure, that this
+ repository is online for as long as you continue to distribute the software.
\item \textbf{[voluntary:]} Mark all modifications of source code of the
embedded libary\footnote{or snippet, or module, or plugin} thoroughly.
\item \textbf{[voluntary:]} Let the documentation of your distribution and/or
- your additional material also reproduce the content of the \emph{notice text
- file}, a hint to the software name, a link to its homepage, and a link to the
- EUPL 1.1 license -- especially as a subsection of your own copyright notice.
+ your additional material also reproduce the content of the existing
+ \emph{copyright notice text files}, a hint to the software name, a link to its
+ homepage, and a link to the EUPL 1.1 license -- especially as a subsection of
+ your own copyright notice.
+
\end{itemize}
@@ -376,7 +378,7 @@ \subsection{EUPL-6: Passing a modified library as independent source code}
\item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ the
copyright, patent or trademarks notices and all notices that refer to the
- Licence and to the disclaimer of warranties -- are retained in your package in
+ license and to the disclaimer of warranties -- are retained in your package in
the form you have received them.
\item \textbf{[mandatory:]} Give the recipient a copy of the EUPL 1.1
@@ -392,9 +394,9 @@ \subsection{EUPL-6: Passing a modified library as independent source code}
embedded libary\footnote{or snippet, or module, or plugin} thoroughly.
\item \textbf{[voluntary:]} Let the documentation of your distribution and/or
- your additional material also reproduce the content of the \emph{notice text
- file}, a hint to the software name, a link to its homepage, and a link to the
- EUPL 1.1 license.
+ your additional material also reproduce the content of the existing
+ \emph{copyright notice text files}, a hint to the software name, a link to its
+ homepage, and a link to the EUPL 1.1 license.
\end{itemize}
@@ -422,7 +424,7 @@ \subsection{EUPL-7: Passing a modified library as independent binary}
\item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ the
copyright, patent or trademarks notices and all notices that refer to the
- Licence and to the disclaimer of warranties -- are retained in your package in
+ license and to the disclaimer of warranties -- are retained in your package in
the form you have received them. If you compile the binary from the sources,
ensure that all the licensing elements are also incorporated into the package.
@@ -436,19 +438,20 @@ \subsection{EUPL-7: Passing a modified library as independent binary}
file} by a description of your modifications.
\item \textbf{[mandatory:]} Make the source code of the distributed software
- accessible via a repository (although you modified it): Push the source code
- package into the repository, make it downloadable via the internet, and
- integrate easily to find descriptions into the distribution package how to the
- code can be received from where. Ensure, that this repository is online for as
- long as you continue to distribute the software.
+ accessible via a repository (although you modified it): Push the source
+ code package into a repository, make it downloadable via the internet, and
+ integrate an easily to find descriptions into the distribution package which
+ explains how to the code can be received from where. Ensure, that this
+ repository is online for as long as you continue to distribute the software.
\item \textbf{[voluntary:]} Mark all modifications of source code of the
embedded libary\footnote{or snippet, or module, or plugin} thoroughly.
\item \textbf{[voluntary:]} Let the documentation of your distribution and/or
- your additional material also reproduce the content of the \emph{notice text
- file}, a hint to the software name, a link to its homepage, and a link to the
- EUPL 1.1 license -- especially as a subsection of your own copyright notice.
+ your additional material also reproduce the content of the existing
+ \emph{copyright notice text files}, a hint to the software name, a link to its
+ homepage, and a link to the EUPL 1.1 license -- especially as a subsection of
+ your own copyright notice.
\end{itemize}
@@ -477,7 +480,7 @@ \subsection{EUPL-8: Passing a modified library as embedded source code}
\item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ the
copyright, patent or trademarks notices and all notices that refer to the
- Licence and to the disclaimer of warranties -- are retained in your package in
+ license and to the disclaimer of warranties -- are retained in your package in
the form you have received them.
\item \textbf{[mandatory:]} Give the recipient a copy of the EUPL 1.1
@@ -489,21 +492,17 @@ \subsection{EUPL-8: Passing a modified library as embedded source code}
notice file still does not exist. \emph{Expand} the \emph{modification text
file} by a description of your modifications.
+ \item \textbf{[mandatory:]} License your overarching program also under the
+ EUPL 1.1.
+
\item \textbf{[voluntary:]} Mark all modifications of source code of the
embedded libary\footnote{or snippet, or module, or plugin} thoroughly.
-
+
\item \textbf{[voluntary:]} Let the documentation of your distribution and/or
- your additional material also reproduce the content of the \emph{notice text
- file}, a hint to the name of the used EUPL licensed component, a link to its
- homepage, and a link to the EUPL 1.1 license -- especially as subsection of
- your own copyright notice.
-
- \item \textbf{[voluntary:]} Arrange your source code distribution so that the
- integrated EUPL license and the \emph{notice text file} clearly refer only
- to the embedded library and do not disturb the licensing of your own
- overarching work. It's a good tradition to keep the embedded components like
- libraries, modules, snippets, or plugins in specific directory which contains
- also all additional licensing elements.
+ your additional material also reproduce the content of the existing
+ \emph{copyright notice text files}, a hint to the name of the used EUPL
+ licensed component, a link to its homepage, and a link to the EUPL 1.1 license
+ -- especially as subsection of your own copyright notice.
\end{itemize}
@@ -533,7 +532,7 @@ \subsection{EUPL-9: Passing a modified library as embedded binary}
\item \textbf{[mandatory:]} Ensure that the licensing elements -- esp.\ the
copyright, patent or trademarks notices and all notices that refer to the
- Licence and to the disclaimer of warranties -- are retained in your package in
+ license and to the disclaimer of warranties -- are retained in your package in
the form you have received them. If you compile the binary from the sources,
ensure that all the licensing elements are also incorporated into the package.
@@ -546,41 +545,31 @@ \subsection{EUPL-9: Passing a modified library as embedded binary}
notice file still does not exist. \emph{Expand} the \emph{modification text
file} by a description of your modifications.
- \item \textbf{[mandatory:]} Make the source code of the distributed software
- accessible via a repository: Push the source code package into the repository,
- make it downloadable via the internet, and integrate easily to find
- descriptions into the distribution package how to the code can be received
- from where.
-
\item \textbf{[mandatory:]} Make the source code of the embedded library and
- th source code of your overarching program accessible via a
+ the source code of your overarching program accessible via a
repository\footnote{Formally, the EUPL-1.1 is only a license with weak
copyleft. But this is only a result of the allowance to relicense the software
($\rightarrow$ OSLiC, p.\ \pageref{sec:ProtectingPowerOfEupl}). So, as long as
you do not relicense the embedded library with respect to the list of
\enquote{compatible licenses accodring to article 5 EUPL} (\cite[cf.][\nopage
wp §5 and Appendix]{EuplLicense2007en}), you also have to publish the code of
- your overarching work.}: Push the source code package into the repository,
- make it downloadable via the internet, and integrate easily to find
- descriptions into the distribution package how to the code can be received
+ your overarching work.}: Push the source code package into a repository, make
+ it downloadable via the internet, and integrate an easily to find descriptions
+ into the distribution package which explains how to the code can be received
from where. Ensure, that this repository is online for as long as you continue
to distribute the software.
+ \item \textbf{[mandatory:]} License your overarching program also under the
+ EUPL 1.1.
+
\item \textbf{[voluntary:]} Mark all modifications of source code of the
embedded libary\footnote{or snippet, or module, or plugin} thoroughly.
\item \textbf{[voluntary:]} Let the documentation of your distribution and/or
- your additional material also reproduce the content of the \emph{notice text
- file}, a hint to the name of the used EUPL licensed component, a link to its
- homepage, and a link to the EUPL 1.1 license -- especially as subsection of
- your own copyright notice.
-
- \item \textbf{[voluntary:]} Arrange your binary distribution so that the
- integrated EUPL license and the \emph{notice text file} clearly refer only
- to the embedded library and do not disturb the licensing of your own
- overarching work. It's a good tradition to keep the librabries, modules,
- snippet, or plugins in specific directiers which contain also all licensing
- elements.
+ your additional material also reproduce the content of the existing
+ \emph{copyright notice text files}, a hint to the name of the used EUPL
+ licensed component, a link to its homepage, and a link to the EUPL 1.1 license
+ -- especially as subsection of your own copyright notice.
\end{itemize}
@@ -599,7 +588,7 @@ \subsection{Discussions and Explanations}
\item The EUPL generally \enquote{[\ldots] does not grant permission to use
the trade names, trademarks, service marks, or names of the Licensor , except
- as required for reasonable and customary use in describing the orig in of the
+ as required for reasonable and customary use in describing the origin of the
Work and reproducing the content of the copyright
notice}\footcite[cf.][\nopage wp\ §5]{EuplLicense2007en}. Therefore, the OSLiC
genreally interdicts (EUPL-1 - EUPL-9) to promote any service or product --
@@ -613,8 +602,8 @@ \subsection{Discussions and Explanations}
'distributing' the software (\emph{4others}). But -- in the cases of not
distributing the software -- the control of a license compliant fulfillment
could be difficult without automatically switching into the use case class
- 'distributing'. Therefore the OSLiC inserts this requirement as a mandatory
- clause for the 4others use cases (EUPL-2 - EUPL-9).
+ 'distributing'. Therefore the OSLiC only inserts this requirement as a
+ mandatory clause for the \emph{4others} use cases (EUPL-2 - EUPL-9).
\item The EUPL also requires to \enquote{[\ldots] include [\ldots] a copy of
the (EUPL) Licence with every (distributed) copy of the Work
@@ -646,26 +635,24 @@ \subsection{Discussions and Explanations}
\item Finally, the EUPL contains a \enquote{copyleft clause} stating that if a
\enquote{[\ldots] Licensee distributes [\ldots] copies of the Original Works
or Derivative Works based upon the Original Work, this Distribution [...] will
- be done under the terms of this (EUPL) Licence [\ldots]}. In all use cases
+ be done under the terms of this (EUPL) Licence [\ldots]}. In all the use cases
which do not concern the use of an embedded component (EUPL-2 - EUPL-7) this
copyleft clause is already fulfilled by either distributing the modified
- sources themselves of by making them accissble via a repository. In those
+ sources themselves of by making them accessible via a repository. In those
cases where the licensee distributes an overarching program which uses an EUPL
licensed component (EUPL-8 - EUPL-9) normally also the code of the overarching
- work must be distributed. In case of distributing the source code of the
- embedded component and the overarching work (EUPL-8) this is already
- implicitly fulfilled. So, the OSLiC only mentions this default view in the
- case EUPL-9 and therefore evokes a strong copyleft effect of the
+ work must be distributed. Thus, with respect to the use case (EUPL-8) this is
+ already fulfilled by definition. So, the OSLiC only mentions this default view
+ in the case EUPL-9 and therefore evokes a strong copyleft effect of the
EUPL\footnote{Formally, the EUPL-1.1 is a license with weak copyleft. But this
is only a result of the allowance to relicense the software ($\rightarrow$
OSLiC, p.\ \pageref{sec:ProtectingPowerOfEupl}). So, as long as you do not
relicense the embedded library with respect to the list of \enquote{compatible
- licenses accoring to article 5 EUPL}, you also have to publish the code of
+ licenses according to article 5 EUPL}, you also have to publish the code of
your overarching work. Therefore, you can only avoid this consequence by
- relicensing the embedded component by one of the compatible licenses with weak
- copyleft protection listed in the EUPL appendix and its list of
- \enquote{compatible licenses according to article 5 EUPL} (\cite[cf.][\nopage
- wp §5 and Appendix]{EuplLicense2007en})}.
+ relicensing the embedded component by one of the compatible licenses with a
+ weak copyleft listed in the EUPL appendix (\cite[cf.][\nopage wp §5 and
+ Appendix]{EuplLicense2007en})}.
\end{itemize}
View
2  snippets/en/06C-osFulfillmentByToDoLists/0608-mitFulfillToDoList.tex
@@ -231,7 +231,7 @@ \subsection{MIT-5: Passing a modified library as embedded component}
copyright notices of the original author(s), the permission notices and the
MIT disclaimer -- clearly refer only to the embedded library and do not
disturb the licensing of your own overarching work. It's a good tradition to
- keep the libraries, modules, snippet, or plugins in specific directiers which
+ keep the libraries, modules, snippet, or plugins in specific directories which
contain also all licensing elements.
\end{itemize}
View
2  snippets/en/06C-osFulfillmentByToDoLists/0611-pglFulfillToDoList.tex
@@ -246,7 +246,7 @@ \subsection{PGL-5: Passing a modified library as embedded component}
copyright notices of the original author(s), the permission notices and the
PGL disclaimer -- clearly refer only to the embedded library and do not
disturb the licensing of your own overarching work. It's a good tradition to
- keep the libraries, modules, snippet, or plugins in specific directiers which
+ keep the libraries, modules, snippet, or plugins in specific directories which
contain also all licensing elements.
\end{itemize}
View
4 snippets/en/06C-osFulfillmentByToDoLists/0612-phpFulfillToDoList.tex
@@ -475,8 +475,8 @@ \subsection{PHP-9: Passing a modified library as embedded binary}
licensing elements -- esp.\ the PHP license text, the specific copyright
notice of the original author(s), and the PHP disclaimer -- clearly refer
only to the embedded library and do not disturb the licensing of your own
- overarching work. It's a good tradition to keep the librabries, modules,
- snippet, or plugins in specific directiers which contain also all licensing
+ overarching work. It's a good tradition to keep the libraries, modules,
+ snippet, or plugins in specific directories which contain also all licensing
elements.
\end{itemize}
Please sign in to comment.
Something went wrong with that request. Please try again.