taler-merchant-demos

Python-based Frontends for the Demonstration Web site
Log | Files | Refs | Submodules | README | LICENSE

hague.html (14010B)


      1 <!--#include virtual="/server/header.html" -->
      2 <!-- Parent-Version: 1.96 -->
      3 <!-- This page is derived from /server/standards/boilerplate.html -->
      4 <!--#set var="TAGS" value="essays laws patents" -->
      5 <!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
      6 <title>Harm from the Hague
      7 - GNU Project - Free Software Foundation</title>
      8 <!--#include virtual="/philosophy/po/hague.translist" -->
      9 <!--#include virtual="/server/banner.html" -->
     10 <!--#include virtual="/philosophy/ph-breadcrumb.html" -->
     11 <!--GNUN: OUT-OF-DATE NOTICE-->
     12 <!--#include virtual="/server/top-addendum.html" -->
     13 <div class="article reduced-width">
     14 <h2>Harm from the Hague</h2>
     15 
     16 <address class="byline">by <a href="https://www.stallman.org/">Richard
     17 Stallman</a></address>
     18 
     19 <p><i>June 2001</i></p>
     20 
     21 <p>
     22 Europeans have energetically opposed and thwarted the attempt to
     23 introduce software patents in Europe.  A proposed treaty, now being
     24 negotiated, threatens to subject software developers in Europe and
     25 other countries to U.S. software patents&mdash;and other harmful
     26 laws from around the world.  The problem is not just for programmers;
     27 authors of all kinds will face new dangers.  Even the censorship laws
     28 of various countries could have globalized effect.</p>
     29 
     30 <p>
     31 The Hague treaty is not actually about patents, or about copyrights, or
     32 about censorship, but it affects all of them.  It is a treaty about
     33 jurisdiction, and how one country should treat the court decisions of
     34 another country.  The basic idea is reasonable enough: if someone hits
     35 your car in France or breaks a contract with your French company, you
     36 can sue him in France, then bring the judgment to a court in whichever
     37 country he lives in (or has assets in) for enforcement.</p>
     38 
     39 <p>
     40 The treaty becomes a problem when it is extended to distribution of
     41 information&mdash;because information now travels normally and
     42 predictably to all countries.  (The Internet is one way, but not the
     43 only way.)  The consequence is that you could be sued about the
     44 information you distributed under the laws of <strong>any</strong>
     45 Hague country, and the judgment would probably be enforced by your
     46 country.</p>
     47 
     48 <p>
     49 For instance, if you release a software package (either free or not)
     50 in Germany, and people use it in the U.S., you could be sued for
     51 infringing an absurd U.S. software patent.  That part does not depend
     52 on Hague&mdash;it could happen now.  But right now you could ignore
     53 the U.S. judgment, safe in Germany, and the patent holder knows this.
     54 Under the Hague treaty, any German court would be required to enforce
     55 the U.S. judgment against you.  In effect, the software patents of any
     56 signatory country would apply to all signatory countries.  It isn't
     57 enough to keep software patents out of Europe, if U.S. or Japanese or
     58 Egyptian software patents can reach you there.</p>
     59 
     60 <p>
     61 But patent law is not the only area of law that could wreak havoc if
     62 globalized by the Hague treaty.  Suppose you publish a statement
     63 criticizing a public figure.  If copies are read in England, that public
     64 figure could sue you under the strict U.K. libel law.  The laws of your
     65 country may support the right to criticize a public figure, but with the
     66 Hague treaty, they won't necessarily protect you any more.</p>
     67 
     68 <p>
     69 Or suppose you publish a statement comparing your prices with your
     70 competitors' prices.  If this is read in Germany, where comparative
     71 advertising is illegal, you could be sued in Germany and the judgment
     72 brought back to you wherever you are.  (Subsequent note: I've received
     73 word that this law may have been changed in Germany.  The point is the
     74 same, though&mdash;any country could have such a law, and some other
     75 European countries may still have one.)</p>
     76 
     77 <p>
     78 Or suppose you publish a parody.  If it is read in Korea, you could be
     79 sued there, since Korea does not recognize a right to parody.  (Since
     80 the publication of this article, the Korean Supreme Court affirmed the
     81 right to parody, but the general point remains.)</p>
     82 
     83 <p>
     84 Or suppose you have political views that a certain government prohibits.
     85 You could be sued in that country, and the judgment against you there
     86 would be enforced wherever you live.</p>
     87 
     88 <p>
     89 Not long ago, Yahoo was sued in France for having links to U.S. sites
     90 that auctioned Nazi memorabilia, which is lawful in the U.S.  After a
     91 French court required Yahoo France to block such links, Yahoo went to
     92 court in the U.S., asking for a ruling that the French judgment cannot
     93 be applied to the parent company in the U.S.</p>
     94 
     95 <p>
     96 It may come as a surprise to learn that exiled Chinese dissidents
     97 joined the case in support of Yahoo.  But they knew what they were
     98 doing&mdash;their democracy movement depends on the outcome.</p>
     99 
    100 <p>
    101 You see, Nazism is not the only political view whose expression is
    102 prohibited in certain places.  Criticism of the Chinese government is
    103 also prohibited&mdash;in China.  If a French court ruling against
    104 Nazi statements is enforceable in the US, or in your country, maybe a
    105 Chinese court ruling against anti-Chinese-government statements will
    106 be enforceable there too.  (This might be why China has joined the
    107 Hague treaty negotiations.)  The Chinese government can easily adapt
    108 its censorship law so that the Hague treaty would apply to it; all it
    109 has to do is give private individuals (and government agencies) the
    110 right to sue dissident publications.</p>
    111 
    112 <p>
    113 China is not the only country to ban criticism of the government; as
    114 of this writing, the government of Victoria (Australia) is suing to
    115 suppress a book called Victoria Police Corruption on the grounds that
    116 it &ldquo;scandalizes the courts.&rdquo; This book is available on the
    117 Internet outside Australia.  Australia is a Hague treaty participant;
    118 if the treaty applies to such cases, an Australian court judgment
    119 against the book could be used to suppress it elsewhere.</p>
    120 
    121 <p>
    122 Meanwhile, works that criticize Islam have faced increasing censorship
    123 in Egypt, a Hague treaty participant; this too could be globalized by
    124 the Hague treaty.</p>
    125 
    126 <p>
    127 Americans may turn to the First Amendment to protect them from foreign
    128 judgments against their speech.  The draft treaty permits a court to
    129 ignore a foreign judgment that is &ldquo;manifestly incompatible with
    130 public policy.&rdquo; That is a stringent criterion, so you cannot
    131 count on it to protect you just because your conduct is legal where
    132 you are.  Just what it does cover is up to the particular judge.  It
    133 is unlikely to help you against broad foreign interpretations of
    134 copyright, trademarks or software patents, but U.S. courts might use
    135 it to reject outright censorship judgments.</p>
    136 
    137 <p>
    138 However, even that won't help you if you publish on the Internet,
    139 because your <abbr title="Internet service provider">ISP</abbr> either
    140 has assets in other countries or communicates to the world through
    141 larger ISPs that have them.  A censorship judgment
    142 against your site, or any other kind, could be enforced against
    143 your ISP, or your ISP's
    144 ISP, in any other country where it has assets&mdash;and
    145 where there is no Bill of Rights, and freedom of speech does not enjoy
    146 the same exalted status as in the U.S.  In response, the ISP will shut
    147 off your site.  The Hague treaty would globalize pretexts for
    148 lawsuits, but not the protections for civil liberties, so any local
    149 protection could be bypassed.</p>
    150 
    151 <p>
    152 Does suing your ISP seem far-fetched?  It already
    153 happens.  When the multinational company Danone announced plans to
    154 close factories in France, Olivier Malnuit opened a site,
    155 jeboycottedanone.com, to criticize this.  (The name is French for
    156 &ldquo;I boycott Danone.&rdquo;) Danone sued not only him but his site
    157 hosting company and domain name registrar for &ldquo;counterfeiting of
    158 goods&rdquo;&mdash;and in April 2001 received a ruling prohibiting
    159 Malnuit from mentioning the name &ldquo;Danone&rdquo; either in the
    160 domain name or in the text of the site.  Even more telling, the
    161 registrar removed the domain in fear before the court made a
    162 ruling.</p>
    163 
    164 <p>
    165 The natural response for French dissidents is to publish their
    166 criticism of Danone outside France, just as Chinese dissidents publish
    167 their criticism of China outside China.  But the Hague treaty would
    168 enable Danone to attack them everywhere.  Perhaps even this article
    169 would be suppressed through its ISP or
    170 its ISP's ISP.</p>
    171 
    172 <p>
    173 The potential effects of the treaty are not limited to laws that exist
    174 today.  When 50 countries know that their court judgments could be
    175 enforced throughout North America, Europe and Asia, they would have
    176 plenty of temptation to pass laws just for that purpose.</p>
    177 
    178 <p>
    179 Suppose, for example, that Microsoft would like to be able to impose
    180 copyright on languages and network protocols.  They could approach a
    181 small, poor country and offer to spend $50 million a year there for 20
    182 years, if only that country will pass a law saying that implementing a
    183 Microsoft language or protocol constitutes copyright infringement.  They
    184 can surely find some country which would take the offer.  Then if you
    185 implement a compatible program, Microsoft could sue you in that country,
    186 and win.  When the judge rules in their favor and bans distribution of
    187 your program, the courts in your country will enforce the judgment on
    188 you, obeying the Hague treaty.</p>
    189 
    190 <p>
    191 Does this seem implausible?  In 2000, Cisco pressured Liechtenstein, a
    192 small European country, to legalize software patents.  And IBM's chief
    193 lobbyist threatened many European governments with a termination of
    194 investment if they did not support software patents.  Meanwhile, the
    195 U.S. trade representative pressured Middle Eastern country Jordan to
    196 allow patents on mathematics.</p>
    197 
    198 <p>
    199 <a href="http://tacd.org">A meeting of consumer organizations</a>
    200 recommended in
    201 May 2001 that patents, copyrights and trademarks (&ldquo;intellectual
    202 property&rdquo;) should be excluded from the scope of the Hague
    203 treaty, because these laws vary considerably between countries.</p>
    204 
    205 <p>
    206 That is a good recommendation, but it only solves part of the problem.
    207 Patents and bizarre extensions of copyright are just two of many excuses
    208 used for suppression of publication in certain countries.  To solve the
    209 problem thoroughly, all cases about the legality of distributing or
    210 transmitting particular information should be excluded from
    211 globalization under the treaty, and only the country where the
    212 distributor or transmitter operates should have jurisdiction.</p>
    213 
    214 <p>
    215 In Europe, people opposed to software patents will be active in
    216 working to change the Hague treaty; for more information, see
    217 <a href="http://web.archive.org/web/20061209210148/http://www.noepatents.org/hague/index_html?NO_COOKIE=true">www.noepatents.org</a>.
    218 In the U.S., the Consumer Project for Technology is taking the
    219 lead; for more information, see
    220 <a href="http://www.cptech.org/ecom/jurisdiction/hague.html">www.cptech.org</a>.</p>
    221 
    222 <p>
    223 A diplomatic conference is slated to begin today (June 6, 2001) to work
    224 on the details of the Hague treaty.  We should make ministries and the
    225 public aware of the possible dangers as soon as possible.</p>
    226 
    227 <hr class="column-limit" />
    228 
    229 <p>
    230 There is more information about the problems with the Hague
    231 at <a href="https://web.archive.org/web/20210507012748/http://web.lemuria.org/DeCSS/hague.html">web.lemuria.org</a>.</p>
    232 </div>
    233 
    234 </div><!-- for id="content", starts in the include above -->
    235 <!--#include virtual="/server/footer.html" -->
    236 <div id="footer" role="contentinfo">
    237 <div class="unprintable">
    238 
    239 <p>Please send general FSF &amp; GNU inquiries to <a
    240 href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>.  There are also <a
    241 href="/contact/">other ways to contact</a> the FSF.  Broken links and other
    242 corrections or suggestions can be sent to <a
    243 href="mailto:webmasters@gnu.org">&lt;webmasters@gnu.org&gt;</a>.</p>
    244 
    245 <p><!-- TRANSLATORS: Ignore the original text in this paragraph,
    246         replace it with the translation of these two:
    247 
    248         We work hard and do our best to provide accurate, good quality
    249         translations.  However, we are not exempt from imperfection.
    250         Please send your comments and general suggestions in this regard
    251         to <a href="mailto:web-translators@gnu.org">
    252         &lt;web-translators@gnu.org&gt;</a>.</p>
    253 
    254         <p>For information on coordinating and contributing translations of
    255         our web pages, see <a
    256         href="/server/standards/README.translations.html">Translations
    257         README</a>. -->
    258 Please see the <a
    259 href="/server/standards/README.translations.html">Translations README</a> for
    260 information on coordinating and contributing translations of this article.</p>
    261 </div>
    262 
    263 <!-- Regarding copyright, in general, standalone pages (as opposed to
    264      files generated as part of manuals) on the GNU web server should
    265      be under CC BY-ND 4.0.  Please do NOT change or remove this
    266      without talking with the webmasters or licensing team first.
    267      Please make sure the copyright date is consistent with the
    268      document.  For web pages, it is ok to list just the latest year the
    269      document was modified, or published.
    270      
    271      If you wish to list earlier years, that is ok too.
    272      Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
    273      years, as long as each year in the range is in fact a copyrightable
    274      year, i.e., a year in which the document was published (including
    275      being publicly visible on the web or in a revision control system).
    276      
    277      There is more detail about copyright years in the GNU Maintainers
    278      Information document, www.gnu.org/prep/maintain. -->
    279 
    280 <p>Copyright &copy; 2001, 2022 Richard Stallman</p>
    281 
    282 <p>This page is licensed under a <a rel="license"
    283 href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
    284 Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
    285 
    286 <!--#include virtual="/server/bottom-notes.html" -->
    287 
    288 <p class="unprintable">Updated:
    289 <!-- timestamp start -->
    290 $Date: 2022/04/12 11:15:30 $
    291 <!-- timestamp end -->
    292 </p>
    293 </div>
    294 </div><!-- for class="inner", starts in the banner include -->
    295 </body>
    296 </html>