Those of us in the US should not just dismiss this as not affecting them. Multinationals have long understood and used the strategy of trying to get whatever countries they can to pass legislation, getting a treaty signed codifying the standard, and then forcing legislation in the rest based on "international standards". The goal being to fight all of the difficult battles out of sight in the easiest place to fight them, then be able to fight them in the hard jurisdictions with the "weight of international opinion" on their side.

In this case I believe that the pattern is that software algorithms first were justified in the US based on patenting machines that implemented said algorithms. They then moved on to algorithms in general. Then there was pressure to have patents on software in Europe obstensibly to create a uniform environment since the US already had them. Strangely enough, though, in Europe the standard is aiming substnatially lower than the (already absurd) US limit. Finally the goal would be to have the lower standard pushed on the US as well.

This type of strategy has been pursued successfully in many areas. For instance it is why in the US the terms of copyrights well beyond anything dreamed of in the US Constitution...

In reply to Re (tilly) 1: European Software Patents vs. Perl? by tilly
in thread European Software Patents vs. Perl? by neophyte

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.