1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
|
<!--#include virtual="/server/header.html" -->
<!-- Parent-Version: 1.96 -->
<!-- This page is derived from /server/standards/boilerplate.html -->
<!--#set var="TAGS" value="essays laws patents" -->
<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
<title>FSF's Position on W3 Consortium “Royalty-Free” Patent
Policy - GNU Project - Free Software Foundation</title>
<meta http-equiv="Keywords"
content="GNU, FSF, Free Software Foundation, Linux, patent, general, public, license, gpl, general public license, policy, freedom, software, Eben, Moglen, Eben Moglen" />
<meta http-equiv="Description"
content="The W3C RF patent policy seems on its surface to be helpful to Free Software, but in fact it is not. FSF encourages the public to say so in response to the last call." />
<!--#include virtual="/philosophy/po/w3c-patent.translist" -->
<!--#include virtual="/server/banner.html" -->
<!--#include virtual="/philosophy/ph-breadcrumb.html" -->
<!--GNUN: OUT-OF-DATE NOTICE-->
<!--#include virtual="/server/top-addendum.html" -->
<div class="article reduced-width">
<h2>FSF's Position on W3 Consortium “Royalty-Free” Patent Policy</h2>
<p>
<i>Rewritten 1 June 2003</i>
</p>
<h3>Our Position</h3>
<p>
The Free Software Foundation, represented by Professor Moglen of
Columbia University Law School, has participated in the W3 Consortium
Patent Policy Working Group from November 2001 through the present.
The current W3C patent policy, which in most cases requires
“royalty-free” or “RF” patent licenses, is a
significant step in the direction of protecting the World Wide Web
from patent-encumbered standards. But it falls short because a
loophole allows conditions on these patent licenses that would
prohibit free software implementations of the standards.</p>
<p>
The problem comes from the “field of use” restrictions
that patent holders are allowed to put in their royalty-free patent
licenses. Such restrictions say that you are allowed to practice the
patented idea, but only for implementing the standard precisely as
specified—not in any other way. Thus, if you change the code
to depart from the spec even slightly, the patent license no longer
protects you from against being sued for infringing the patent.</p>
<p>
The W3C has policies to reject some kinds of “field of
use” restrictions. For instance, it won't allow a patent
license to be limited to a certain kind of software or a certain kind
of platform. (We were informed of this in 2012.) However, that still
allows other kinds of restrictions that can cause a problem.</p>
<p>
One requirement for Free Software is that users have the freedom to
modify and redistribute it. But we can hardly consider that users
have freedom to publish modified versions of the program if, for a
part of the program's behavior, modification is prohibited. Thus,
these “field of use” restrictions would prevent
implementation of W3C standards as <a href="/philosophy/free-sw.html">
Free Software</a>.</p>
<p>
“Field of use” restrictions are also legally incompatible
with section 7 of the <a href="/licenses/old-licenses/gpl-2.0.html">GNU
General Public License (version 2)</a>, since it does not allow the user's
freedom to modify to be shrunk to zero in this way.</p>
<p>
Many other Free Software licenses have no provisions equivalent to the
GPL's Section 7, but you can't solve the problem merely by using one
of those licenses. Section 7 is intended to prevent the imposition of
side restrictions (for instance, by patent licenses) which would deny
the freedoms that the GPL itself gives you. If the software license
does nothing to prevent this, you can find yourself in a situation
where the program's license appears to give you freedom, but this
freedom has been taken away by restrictions not stated there.</p>
<p>
Freedom to modify software can always be limited by third-party
patents in ways that the software copyright license doesn't disclose.
This is why software patents are <a href="https://ffii.org/">so
dangerous to software freedom</a>.</p>
<p>The FSF plans to continue to participate in the implementation
process. We will try to convince patent-holders not to impose
“field of use” restrictions, and we encourage all those
who care about the right of Free Software developers to implement all
future web standards to do the same.</p>
</div>
</div><!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.html" -->
<div id="footer" role="contentinfo">
<div class="unprintable">
<p>Please send general FSF & GNU inquiries to
<a href="mailto:gnu@gnu.org"><gnu@gnu.org></a>.
There are also <a href="/contact/">other ways to contact</a>
the FSF. Broken links and other corrections or suggestions can be sent
to <a href="mailto:webmasters@gnu.org"><webmasters@gnu.org></a>.</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:web-translators@gnu.org">
<web-translators@gnu.org></a>.</p>
<p>For information on coordinating and contributing 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 contributing 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 © 2002, 2003, 2012, 2021 Free Software Foundation, Inc.</p>
<p>This page is licensed under a <a rel="license"
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 class="unprintable">Updated:
<!-- timestamp start -->
$Date: 2021/09/22 09:19:58 $
<!-- timestamp end -->
</p>
</div>
</div><!-- for class="inner", starts in the banner include -->
</body>
</html>
|
