[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/patent-examp patent-examples.html
|
From: |
Pavel Kharitonov |
|
Subject: |
www/patent-examp patent-examples.html |
|
Date: |
Sat, 15 Feb 2014 15:37:17 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: Pavel Kharitonov <ineiev> 14/02/15 15:37:17
Modified files:
patent-examp : patent-examples.html
Log message:
Regenerate.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/patent-examp/patent-examples.html?cvsroot=www&r1=1.10&r2=1.11
Patches:
Index: patent-examples.html
===================================================================
RCS file: /web/www/www/patent-examp/patent-examples.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- patent-examples.html 25 Jan 2013 20:31:53 -0000 1.10
+++ patent-examples.html 15 Feb 2014 15:37:17 -0000 1.11
@@ -1,274 +1,301 @@
-<html lang="en">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Created by GNU Texinfo 5.2, http://www.gnu.org/software/texinfo/ -->
<head>
<title>Software patents that hurt free software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Software patents that hurt free software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="top" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
-</head>
-<body>
-<div class="node">
-<a name="Top"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Original-Announcement">Original
Announcement</a>,
-Previous: <a rel="previous" accesskey="p" href="#dir">(dir)</a>,
-Up: <a rel="up" accesskey="u" href="#dir">(dir)</a>
-
-</div>
-
-<!-- node-name, next, previous, up -->
-<h2 class="unnumbered">Examples of Software Patents that hurt Free
Software</h2>
-
-<ul class="menu">
-<li><a accesskey="1" href="#Original-Announcement">Original Announcement</a>
-<li><a accesskey="2" href="#Audio_002fVideo">Audio/Video</a>
-<li><a accesskey="3" href="#Graphics">Graphics</a>
-<li><a accesskey="4" href="#Speech-Synthesis">Speech Synthesis</a>
-<li><a accesskey="5" href="#Fonts">Fonts</a>
-<li><a accesskey="6" href="#Text-Processor">Text Processor</a>
-<li><a accesskey="7" href="#Compression">Compression</a>
-<li><a accesskey="8" href="#Web-server">Web server</a>
-<li><a accesskey="9" href="#Compilers">Compilers</a>
-<li><a href="#Programming">Programming</a>
-<li><a href="#Drivers">Drivers</a>
-<li><a href="#Communication-Protocols">Communication Protocols</a>
-
-</li></ul>
-<p>--- The Detailed Node Listing ---
-
-<p>Audio/Video
-
-</p>
-<ul class="menu">
-<li><a href="#RealNetworks">RealNetworks</a>
-<li><a href="#BladeEnc">BladeEnc</a>
-<li><a href="#Ogg-Vorbis">Ogg Vorbis</a>
-<li><a href="#Virtual-Dub">Virtual Dub</a>
-<li><a href="#Broadcast-2000">Broadcast 2000</a>
-<li><a href="#MPEGII">MPEGII</a>
-
-</li></ul>
-<p>Graphics
-
-</p>
-<ul class="menu">
-<li><a href="#GIF">GIF</a>
-<li><a href="#GD-Library">GD Library</a>
-<li><a href="#GNUstep">GNUstep</a>
-<li><a href="#XOR-graphics">XOR graphics</a>
-<li><a href="#GIMP">GIMP</a>
-
-</li></ul>
-<p>Speech Synthesis
-
-</p>
-<ul class="menu">
-<li><a href="#MBROLA">MBROLA</a>
-
-</li></ul>
-<p>Fonts
-
-</p>
-<ul class="menu">
-<li><a href="#FreeType">FreeType</a>
-
-</li></ul>
-<p>Text Processor
-
-</p>
-<ul class="menu">
-<li><a href="#Ted">Ted</a>
-
-</li></ul>
-<p>Compression
-
-</p>
-<ul class="menu">
-<li><a href="#ncompress">ncompress</a>
-<li><a href="#bzip">bzip</a>
-<li><a href="#zlib">zlib</a>
-
-</li></ul>
-<p>Web server
-
-</p>
-<ul class="menu">
-<li><a href="#Roxen">Roxen</a>
-
-</li></ul>
-<p>Compilers
-</p>
-<ul class="menu">
-<li><a href="#GCC">GCC</a>
-
-</li></ul>
-<p>Programming
-
-</p>
-<ul class="menu">
-<li><a href="#HyperProf">HyperProf</a>
-<li><a href="#OpenIPO">OpenIPO</a>
-<li><a href="#Virtual-functions-in-C_002b_002b">Virtual functions in C++</a>
-<li><a href="#CDDB_002fFreeDB">CDDB/FreeDB</a>
-<li><a href="#ElectricFence">ElectricFence</a>
-
-</li></ul>
-<p>Drivers
+<meta name="description" content="Software patents that hurt free software">
+<meta name="keywords" content="Software patents that hurt free software">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="makeinfo">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="#Top" rel="start" title="Top">
+<link href="dir.html#Top" rel="up" title="(dir)">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
-</p>
-<ul class="menu">
-<li><a href="#CueCat">CueCat</a>
-</li></ul>
+</head>
-<p>Communication Protocols</p>
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+<h1 class="settitle" align="center">Software patents that hurt free
software</h1>
-<ul class="menu">
-<li><a href="#WAP">WAP</a>
-</ul>
+<a name="Top"></a>
+<div class="header">
+<p>
+Next: <a href="#Original-Announcement" accesskey="n" rel="next">Original
Announcement</a>, Previous: <a href="dir.html#Top" accesskey="p"
rel="prev">(dir)</a>, Up: <a href="dir.html#Top" accesskey="u"
rel="up">(dir)</a> </p>
+</div>
+<a name="Examples-of-Software-Patents-that-hurt-Free-Software"></a>
+<h1 class="top">Examples of Software Patents that hurt Free Software</h1>
+
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#Original-Announcement"
accesskey="1">Original Announcement</a>:</td><td> </td><td
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Audio_002fVideo"
accesskey="2">Audio/Video</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Graphics"
accesskey="3">Graphics</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Speech-Synthesis"
accesskey="4">Speech Synthesis</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Fonts"
accesskey="5">Fonts</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Text-Processor"
accesskey="6">Text Processor</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Compression"
accesskey="7">Compression</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Web-server"
accesskey="8">Web server</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Compilers"
accesskey="9">Compilers</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#Programming">Programming</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#Drivers">Drivers</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#Communication-Protocols">Communication
Protocols</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+</pre></th></tr><tr><th colspan="3" align="left" valign="top"><pre
class="menu-comment"> — The Detailed Node Listing —
+
+Audio/Video
+
+</pre></th></tr><tr><td align="left" valign="top">• <a
href="#RealNetworks">RealNetworks</a>:</td><td> </td><td
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#BladeEnc">BladeEnc</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Ogg-Vorbis">Ogg
Vorbis</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Virtual-Dub">Virtual
Dub</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Broadcast-2000">Broadcast
2000</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#MPEGII">MPEGII</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+Graphics
+
+</pre></th></tr><tr><td align="left" valign="top">• <a
href="#GIF">GIF</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#GD-Library">GD
Library</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#GNUstep">GNUstep</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#XOR-graphics">XOR
graphics</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#GIMP">GIMP</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+Speech Synthesis
+
+</pre></th></tr><tr><td align="left" valign="top">• <a
href="#MBROLA">MBROLA</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+Fonts
+
+</pre></th></tr><tr><td align="left" valign="top">• <a
href="#FreeType">FreeType</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+Text Processor
+
+</pre></th></tr><tr><td align="left" valign="top">• <a
href="#Ted">Ted</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+Compression
+
+</pre></th></tr><tr><td align="left" valign="top">• <a
href="#ncompress">ncompress</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#bzip">bzip</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#zlib">zlib</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+Web server
+
+</pre></th></tr><tr><td align="left" valign="top">• <a
href="#Roxen">Roxen</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+Compilers
+
+</pre></th></tr><tr><td align="left" valign="top">• <a
href="#GCC">GCC</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+Programming
+
+</pre></th></tr><tr><td align="left" valign="top">• <a
href="#HyperProf">HyperProf</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#OpenIPO">OpenIPO</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#Virtual-functions-in-C_002b_002b">Virtual functions in
C++</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#CDDB_002fFreeDB">CDDB/FreeDB</a>:</td><td> </td><td
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#ElectricFence">ElectricFence</a>:</td><td> </td><td
align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+Drivers
+
+</pre></th></tr><tr><td align="left" valign="top">• <a
href="#CueCat">CueCat</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+Communication Protocols
+
+</pre></th></tr><tr><td align="left" valign="top">• <a
href="#WAP">WAP</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+</pre></th></tr></table>
-<div class="node">
+<hr>
<a name="Original-Announcement"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Audio_002fVideo">Audio/Video</a>,
-Previous: <a rel="previous" accesskey="p" href="#Top">Top</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</a></p>
-
+<div class="header">
+<p>
+Next: <a href="#Audio_002fVideo" accesskey="n" rel="next">Audio/Video</a>,
Previous: <a href="#Top" accesskey="p" rel="prev">Top</a>, Up: <a href="#Top"
accesskey="u" rel="up">Top</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="Original-Announcement-1"></a>
<h2 class="chapter">1 Original Announcement</h2>
-<p>Richard Stallman <address@hidden></p>
-
- <p>Date: Mon, 11 Dec 2000 10:00:08 -0700 (MST)</p>
-
- <blockquote>
-[Please repost this widely wherever appropriate]
-
- <p>We would like to collect information about cases where free software
+<p>Richard Stallman <address@hidden>
+</p>
+<p>Date: Mon, 11 Dec 2000 10:00:08 -0700 (MST)
+</p>
+<blockquote>
+<p>[Please repost this widely wherever appropriate]
+</p>
+<p>We would like to collect information about cases where free software
has been harmed by software patents–that is, cases where a free
program has been withdrawn from use or interfered with, or where a
feature was taken out or never written in the first place, because of
-the danger of a patent.</p>
-
- <p>We hope to use this information to argue against the system of
+the danger of a patent.
+</p>
+<p>We hope to use this information to argue against the system of
software patents, especially in Europe where the question has become
-a live political issue (on late www.freepatents.org).</p>
-
- <p>If you know of such a case, please write to <a
href="mailto:address@hidden";>address@hidden</a>
+a live political issue (on late www.freepatents.org).
+</p>
+<p>If you know of such a case, please write to <a
href="mailto:address@hidden";>address@hidden</a>
and tell us what happened.
-
- <p>Ideally we would like to know the name of the program, its developer's
+</p>
+<p>Ideally we would like to know the name of the program, its developer’s
name and email address or other coordinates, what happened to the
program, and the patent number. If you know those things, please
-include them in your report. But if you don't have all of that
+include them in your report. But if you don’t have all of that
information, please write anyway and tell us whatever you know. For
-instance, if you can tell us how to contact the program's developer,
+instance, if you can tell us how to contact the program’s developer,
we can probably get the rest of the information from the developer.
-If you can tell us just the program's name, we may be able to find the
+If you can tell us just the program’s name, we may be able to find the
developer. We may write back to you to try to get more details; even
leads for getting more details may be useful.
-
- <p>Please send your information to <a
href="mailto:address@hidden";>address@hidden</a> rather
+</p>
+<p>Please send your information to <a
href="mailto:address@hidden";>address@hidden</a> rather
than to me personally, so that we can collect the responses efficiently.
-</blockquote>
+</p></blockquote>
-<div class="node">
-<a name="Audio%2fVideo"></a>
+<hr>
<a name="Audio_002fVideo"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Graphics">Graphics</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Original-Announcement">Original Announcement</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</a>
-
+<div class="header">
+<p>
+Next: <a href="#Graphics" accesskey="n" rel="next">Graphics</a>, Previous: <a
href="#Original-Announcement" accesskey="p" rel="prev">Original
Announcement</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="Audio_002fVideo-1"></a>
<h2 class="chapter">2 Audio/Video</h2>
<p>Thomas Hudson <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-Another area of constant problems is in audio development for
+</p>
+<blockquote>
+<p>Another area of constant problems is in audio development for
Linux. The relevant homepage is at:
-
- <p>http://www.linuxdj.com/audio/lad/index.php3
-
- <p>Check the archives of the mailing list. Almost every development runs
+</p>
+<p>http://www.linuxdj.com/audio/lad/index.php3
+</p>
+<p>Check the archives of the mailing list. Almost every development runs
into another patent. For audio development it is literally getting to
the point of programmers having to do a patent search and find ways to
program around it. Paul Barton-Davis <a
href="mailto:address@hidden";>address@hidden</a> would be a good
contact for more info.
-</blockquote>
+</p></blockquote>
-<ul class="menu">
-<li><a accesskey="1" href="#RealNetworks">RealNetworks</a>
-<li><a accesskey="2" href="#BladeEnc">BladeEnc</a>
-<li><a accesskey="3" href="#Ogg-Vorbis">Ogg Vorbis</a>
-<li><a accesskey="4" href="#Virtual-Dub">Virtual Dub</a>
-<li><a accesskey="5" href="#Broadcast-2000">Broadcast 2000</a>
-<li><a accesskey="7" href="#MPEGII">MPEGII</a>
-</ul>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#RealNetworks"
accesskey="1">RealNetworks</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#BladeEnc"
accesskey="2">BladeEnc</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Ogg-Vorbis"
accesskey="3">Ogg Vorbis</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Virtual-Dub"
accesskey="4">Virtual Dub</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#Broadcast-2000"
accesskey="5">Broadcast 2000</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#MPEGII"
accesskey="6">MPEGII</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+</table>
-<div class="node">
+<hr>
<a name="RealNetworks"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#BladeEnc">BladeEnc</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Audio_002fVideo">Audio/Video</a>,
-Up: <a rel="up" accesskey="u" href="#Audio_002fVideo">Audio/Video</a>
-
+<div class="header">
+<p>
+Next: <a href="#BladeEnc" accesskey="n" rel="next">BladeEnc</a>, Previous: <a
href="#Audio_002fVideo" accesskey="p" rel="prev">Audio/Video</a>, Up: <a
href="#Audio_002fVideo" accesskey="u" rel="up">Audio/Video</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="RealNetworks-1"></a>
<h3 class="section">2.1 RealNetworks</h3>
<p>Pam Dixon <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-- –I sent a message Sunday with the info; just in case it got jumbled in
=
-the ether, I'll repeat some of it here. I find the RealNetworks patent =
+</p>
+<blockquote>
+<p>- –I sent a message Sunday with the info; just in case it got jumbled
in =
+the ether, I’ll repeat some of it here. I find the RealNetworks patent =
worse than most, given the factors involved. The patent is too broad, =
-the language too loose, and coupled with Real's attitude and approach, =
+the language too loose, and coupled with Real’s attitude and approach, =
the whole thing stinks.=20
-
- <p>The patent abstract is below – unfortunately, the core patent
documents =
-don't get any better. You'll see right through the smoke screen they put =
+</p>
+<p>The patent abstract is below – unfortunately, the core patent
documents =
+don’t get any better. You’ll see right through the smoke screen
they put =
up in the complete description of the so-called invention. Clearly, some =
-attorney who didn't know much let this one through. ( =
+attorney who didn’t know much let this one through. ( =
http://www.uspto.gov/patft/index.html to get to the full patent text.)=20
-
- <p>You are probably already aware of this –some important patents =
+</p>
+<p>You are probably already aware of this –some important patents =
regarding video compression are coming up, particularly relating to =
-MPEG4; I've talked to the attorney who is the primary examiner on this =
+MPEG4; I’ve talked to the attorney who is the primary examiner on this =
patent cluster, and he actually rejected some of them last September =
-(from major multinationals) based on over-breadth. It's wait-and-see. =
+(from major multinationals) based on over-breadth. It’s wait-and-see. =
PacketVideo has just gotten an important patent on an error reduction =
algorithm relating to video compression in low-bandwidth situations that =
could have been applied very usefully, had it been freely distributed. =20
+</p>
- <p>Snipped patent text:=20
-- ——————————–
+<p>Snipped patent text:=20
+- ———————-
United States Patent 6,151,634 =20
Glaser , et al. November 21, 2000 =20
+</p>
+<p>Audio-on-demand communication system=20
+</p>
- <p>Audio-on-demand communication system=20
-
- <p>Abstract
+<p>Abstract
An audio-on-demand communication system provides real-time playback of =
audio data transferred via telephone lines or other communication links. =
One or more audio servers include memory banks which store compressed =
@@ -289,28 +316,29 @@
present invention, servers and subscriber PCs are dynamically allocated =
based upon geographic location to provide the highest possible quality =
in the communication link.=20
-
- <p>Inventors: Glaser; Robert D. (Seattle, WA); O'Brien; Mark =
+</p>
+<p>Inventors: Glaser; Robert D. (Seattle, WA); O’Brien; Mark =
(Cambridge, MA); Boutell; Thomas B. (Seattle, WA); Goldberg; Randy Glen =
(Princeton, NJ) =20
Assignee: RealNetworks, Inc. (Seattle, WA) =20
Appl. No.: 042172=20
Filed: March 13, 1998=20
-
- <p>Current U.S. Class: 709/236; 370/476; 709/219; 709/231 =20
- Intern'l Class: G06F 013/38; G06F 015/17=20
+</p>
+<p>Current U.S. Class: 709/236; 370/476; 709/219; 709/231 =20
+ Intern’l Class: G06F 013/38; G06F 015/17=20
Field of Search: 709/236,231,219,248 348/474 700/94 =
370/503,509,512,476 =20
+</p>
- <p>-
————————————————————————————————————=
-- ———
-
- <p>References Cited [Referenced By]
-
- <p>-
————————————————————————————————————=
-- ———
-
- <p>U.S. Patent Documents
+<p>-
————————————————————————-=
+- ——-
+</p>
+<p>References Cited [Referenced By]
+</p>
+<p>-
————————————————————————-=
+- ——-
+</p>
+<p>U.S. Patent Documents
4827256 May., 1989 Yokoyama. =20
5132992 Jul., 1992 Yurt et al.. =20
5237322 Aug., 1993 Heberle. =20
@@ -320,74 +348,76 @@
5793980 Aug., 1998 Glaser et al. 709/231. =20
5915094 Jun., 1999 Kouloheris et al. 709/219. =20
5917835 Jun., 1999 Barret et al.. =20
+</p>
- <p>Other References=20
- Govindan R; "Operating Systems Mechanisms for Continuous Media"; =
+
+<p>Other References=20
+ Govindan R; "Operating Systems Mechanisms for Continuous
Media"; =
Thesis, University of California, Berkeley CA, 1992.=20
- Topolcic C et al.; "Experimental Internet Stream Protocol, Version =
-2 (ST-II)"; RFC-1190; IETF Request for Comments, Oct. 1990.=20
- Schulzrinne H et al.; "Real Time Streaming Protocol (RTSP)"; =
+ Topolcic C et al.; "Experimental Internet Stream Protocol, Version =
+2 (ST-II)"; RFC-1190; IETF Request for Comments, Oct. 1990.=20
+ Schulzrinne H et al.; "Real Time Streaming Protocol (RTSP)"; =
RFC-2326; IETF Request for Comments, Apr. 1998.=20
- Bigelow S J; "Modem Communications Standards"; Electronics Now; =
+ Bigelow S J; "Modem Communications Standards"; Electronics
Now; =
pp. 35-42, Sep. 1994. =20
-
- <p>Primary Examiner: Rinehart; Mark H.=20
+</p>
+<p>Primary Examiner: Rinehart; Mark H.=20
Attorney, Agent or Firm: Knobbe, Martens, Olson & Bear, LLP=20
-</blockquote>
+</p></blockquote>
-<div class="node">
+<hr>
<a name="BladeEnc"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Ogg-Vorbis">Ogg Vorbis</a>,
-Previous: <a rel="previous" accesskey="p"
href="#RealNetworks">RealNetworks</a>,
-Up: <a rel="up" accesskey="u" href="#Audio_002fVideo">Audio/Video</a>
-
+<div class="header">
+<p>
+Next: <a href="#Ogg-Vorbis" accesskey="n" rel="next">Ogg Vorbis</a>, Previous:
<a href="#RealNetworks" accesskey="p" rel="prev">RealNetworks</a>, Up: <a
href="#Audio_002fVideo" accesskey="u" rel="up">Audio/Video</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="BladeEnc-1"></a>
<h3 class="section">2.2 BladeEnc</h3>
<p>Erkki Ruohtula <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-One free program with patent troubles is the BladeEnc MP3 encoder. (The
original website was lost) See its homepage at http://bladeenc.mp3.no for the
story, especially
+</p>
+<blockquote>
+<p>One free program with patent troubles is the BladeEnc MP3 encoder.
+(The original website was lost) See
+its homepage at http://bladeenc.mp3.no for the story, especially
the news section. Althought theoretically the author (a Swede) should
be safe, he avoids distributing binaries himself due to complaints from
the Fraunhofer institute and the Thomson company.
-</blockquote>
+</p></blockquote>
- <p>Kyle Sparger <a href="mailto:address@hidden";>address@hidden</a>
- <blockquote>
-Although the sourcecode for BladeEnc is distributed under the LGPL, it
+<p>Kyle Sparger <a href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
+<p>Although the sourcecode for BladeEnc is distributed under the LGPL, it
includes algorithms and solutions that some of the
creators of the MPEG Layer 3 standard claims to have patents on.
-
- <p>This makes portions of the BladeEnc sourcecode quite unsuitable for
+</p>
+<p>This makes portions of the BladeEnc sourcecode quite unsuitable for
inclusion into other software projects. It might even
be a breach of the GPL / LGPL license of another product if you add patent
-covered parts of BladeEnc to its sourcecode."
-</blockquote>
-
- <p>Tord Jansson <a href="mailto:address@hidden";>address@hidden</a>
+covered parts of BladeEnc to its sourcecode."
+</p></blockquote>
- <blockquote>
-(Tord sent an email explaining with details how he was approached by
+<p>Tord Jansson <a href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
+<p>(Tord sent an email explaining with details how he was approached by
Fraunhofer/Thomson in regards of a violation of the MP3 related
technology)
-
- <p>European Patent numbers from the first round:
-
- <p>0378609
+</p>
+<p>European Patent numbers from the first round:
+</p>
+<p>0378609
0277613
0309974
0193143
0414838
0251028
-
- <p>European Patent numbers from the second round:
-
- <p>0287578
+</p>
+<p>European Patent numbers from the second round:
+</p>
+<p>0287578
0340301
0393526
0612156
@@ -404,119 +434,115 @@
0485390
0494990
0464534
+</p>
+</blockquote>
- </blockquote>
-
-<div class="node">
+<hr>
<a name="Ogg-Vorbis"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Virtual-Dub">Virtual Dub</a>,
-Previous: <a rel="previous" accesskey="p" href="#BladeEnc">BladeEnc</a>,
-Up: <a rel="up" accesskey="u" href="#Audio_002fVideo">Audio/Video</a>
-
+<div class="header">
+<p>
+Next: <a href="#Virtual-Dub" accesskey="n" rel="next">Virtual Dub</a>,
Previous: <a href="#BladeEnc" accesskey="p" rel="prev">BladeEnc</a>, Up: <a
href="#Audio_002fVideo" accesskey="u" rel="up">Audio/Video</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="Ogg-Vorbis-1"></a>
<h3 class="section">2.3 Ogg Vorbis</h3>
<p>Mike Coleman <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-The Ogg Vorbis sound format (a competitor to Fraunhofer's mp3) is
+</p>
+<blockquote>
+<p>The Ogg Vorbis sound format (a competitor to Fraunhofer’s mp3) is
probably about to become an example. Fraunhofer is already publicly
-claiming that vorbis "probably" infringes on their patents, and since
-they're sending cease-and-desist orders to everyone else, it looks like
-it'll only be a matter of time.
-</blockquote>
+claiming that vorbis "probably" infringes on their patents, and since
+they’re sending cease-and-desist orders to everyone else, it looks like
+it’ll only be a matter of time.
+</p></blockquote>
- <p>"Terry Dube" <a href="mailto:address@hidden";>address@hidden</a>
+<p>"Terry Dube" <a href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
+<p><a
href="http://mp3licensing.com/patents/index.html";>http://mp3licensing.com/patents/index.html</a>
bragging about there
+software patents.
+</p></blockquote>
- <blockquote>
-<a
href="http://mp3licensing.com/patents/index.html";>http://mp3licensing.com/patents/index.html</a>
-bragging about there software
-patents.
-</blockquote>
-<div class="node">
+<hr>
<a name="Virtual-Dub"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Broadcast-2000">Broadcast
2000</a>,
-Previous: <a rel="previous" accesskey="p" href="#Ogg-Vorbis">Ogg
Vorbis</a>,
-Up: <a rel="up" accesskey="u" href="#Audio_002fVideo">Audio/Video</a>
-
+<div class="header">
+<p>
+Next: <a href="#Broadcast-2000" accesskey="n" rel="next">Broadcast 2000</a>,
Previous: <a href="#Ogg-Vorbis" accesskey="p" rel="prev">Ogg Vorbis</a>, Up: <a
href="#Audio_002fVideo" accesskey="u" rel="up">Audio/Video</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="Virtual-Dub-1"></a>
<h3 class="section">2.4 Virtual Dub</h3>
<p>MPEG-4 V3 format: Microsoft informed the author they held patents that
covered its use, and they wanted this format to only be used in their
ASF files, and also not to allow the format to be converted to other
formats.
+</p>
- <p>"Ram'on Garc'ia Fern'andez" <a
href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-Virtual Dub is a free (GPL) program for video edition and conversion.
+<p>"Ram’on Garc’ia Fern’andez" <a
href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
+<p>Virtual Dub is a free (GPL) program for video edition and conversion.
The author had to remove support of ASF file format because Microsoft
threatened him of patent litigation.
-
- <p>Virtual Dub home page:
-
- <p><a href="http://www186.pair.com/vdub/";>http://www186.pair.com/vdub/</a>
-
- <p>The story:
+</p>
+<p>Virtual Dub home page:
+</p>
+<p><a href="http://www186.pair.com/vdub/";>http://www186.pair.com/vdub/</a>
+</p>
+<p>The story:
<a
href="http://www.advogato.org/article/101.html";>http://www.advogato.org/article/101.html</a>
-</blockquote>
+</p></blockquote>
- <p>Derrick Moser <a href="mailto:address@hidden";>address@hidden</a>
- <blockquote>
+<p>Derrick Moser <a href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
- <p>I not sure about the details of what happened to Avery Lee but the
+<p>I not sure about the details of what happened to Avery Lee but the
README.TXT for ASFRecorder says this:
-
- <p>Microsoft does claim a patent on the ASF file format in the United States
+</p>
+<p>Microsoft does claim a patent on the ASF file format in the United States
and possibly in other countries as well. There has been at least one
succesful attempt to reverse engineer the ASF format by a GNU software
author. The program I am talking about is VirtualDub 1.3 by Avery Lee.
By threatening him with legal action, Microsoft has forced the author to
remove support for loading ASF media files because of the programs
ability to transcode these media files to AVI format.
-</blockquote>
+</p></blockquote>
- <p>David Berglund <a href="mailto:address@hidden";>address@hidden</a>
- <blockquote>
-Use of the MPEG-4 format would seem to be potentially a problem with
+<p>David Berglund <a href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
+<p>Use of the MPEG-4 format would seem to be potentially a problem with
getting locked in, and unable to edit your own movies. This would seem
to be even more of a problem with the introduction of digital cameras or
camcorders which record directly to the MPEG-4 format, such as the Sharp
-VN-EZ1, billed as the World's First Internet Viewcam MPEG-4 Digital
+VN-EZ1, billed as the World’s First Internet Viewcam MPEG-4 Digital
Recorder. There would appear to be no legitimate way to use such a
device with any free software operating system, since Microsoft controls
-the format. They do not give any "buyer beware" notices.
+the format. They do not give any "buyer beware" notices.
+</p>
+<p>Information about the Sharp VN-EZ1:
+<a
href="http://web.archive.org/web/20020623133118/http://www.sharp.co.jp/sc/gaiyou/news-e/990317.html";>http://web.archive.org/web/20020623133118/http://www.sharp.co.jp/sc/gaiyou/news-e/990317.html</a>
+(archived)
+</p></blockquote>
- <p>Information about the Sharp VN-EZ1:
-<a
href="http://web.archive.org/web/20020623133118/http://www.sharp.co.jp/sc/gaiyou/news-e/990317.html";>http://www.sharp.co.jp/sc/gaiyou/news-e/990317.html</a>
(archived)
-</blockquote>
-<div class="node">
+<hr>
<a name="Broadcast-2000"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#MPEGII">MPEGII</a>,
-Previous: <a rel="previous" accesskey="p" href="#Virtual-Dub">Virtual
Dub</a>,
-Up: <a rel="up" accesskey="u" href="#Audio_002fVideo">Audio/Video</a>
-
+<div class="header">
+<p>
+Next: <a href="#MPEGII" accesskey="n" rel="next">MPEGII</a>, Previous: <a
href="#Virtual-Dub" accesskey="p" rel="prev">Virtual Dub</a>, Up: <a
href="#Audio_002fVideo" accesskey="u" rel="up">Audio/Video</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="Broadcast-2000-1"></a>
<h3 class="section">2.5 Broadcast 2000</h3>
<p>David Berglund <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-The program Broadcast 2000, a non linear audio and video editor for
+</p>
+<blockquote>
+<p>The program Broadcast 2000, a non linear audio and video editor for
Linux, apparently initially had some support for use of files from
DVD. However, there previously was a note on the web page asking for
input on whether DVD support should be dropped, if it were to only be
@@ -524,171 +550,161 @@
this, but the earlier request for input is no longer present. Similar
issues related to other proprietary codec formats also would be of
importance here, such as the MPEG-4 format, and also MP3 audio.
-
- <p>The web address is:
+</p>
+<p>The web address is:
<a
href="http://heroine.linuxave.net/bcast2000.html";>http://heroine.linuxave.net/bcast2000.html</a>
-
- <p>and the e-mail is:
+</p>
+<p>and the e-mail is:
<a href="mailto:address@hidden";>address@hidden</a>
-</blockquote>
+</p></blockquote>
-<!-- node-name, next, previous, up -->
-
-<div class="node">
+<hr>
<a name="MPEGII"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#Broadcast-2000">
-Broadcast 2000</a>,
-Up: <a rel="up" accesskey="u" href="#Audio_002fVideo">Audio/Video</a>
-
+<div class="header">
+<p>
+Previous: <a href="#Broadcast-2000" accesskey="p" rel="prev">Broadcast
2000</a>, Up: <a href="#Audio_002fVideo" accesskey="u" rel="up">Audio/Video</a>
</p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="MPEGII-1"></a>
<h3 class="section">2.6 MPEGII</h3>
<p>Sengan <a href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
+<p><a
href="http://www.mpegla.com/main/programs/M2/Pages/Agreement.aspx";>http://www.mpegla.com/main/programs/M2/Pages/Agreement.aspx</a>
+</p>
+<p>"There can’t be any Free Software that encodes MPEG II without
violating
+this patent"
+</p></blockquote>
- <blockquote>
-<span style="strike-trough">http://www.mpegla.com/lic_agreement.html</span>
-<a
href="http://www.mpegla.com/main/programs/M2/Pages/Agreement.aspx";>http://www.mpegla.com/main/programs/M2/Pages/Agreement.aspx</a>
-
- <p>"There can't be any Free Software that encodes MPEG II without violating
-this patent"
-</blockquote>
-<div class="node">
+<hr>
<a name="Graphics"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Speech-Synthesis">Speech
Synthesis</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Audio_002fVideo">Audio/Video</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</a>
-
+<div class="header">
+<p>
+Next: <a href="#Speech-Synthesis" accesskey="n" rel="next">Speech
Synthesis</a>, Previous: <a href="#Audio_002fVideo" accesskey="p"
rel="prev">Audio/Video</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a>
</p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="Graphics-1"></a>
<h2 class="chapter">3 Graphics</h2>
-<ul class="menu">
-<li><a accesskey="1" href="#GIF">GIF</a>
-<li><a accesskey="2" href="#GD-Library">GD Library</a>
-<li><a accesskey="3" href="#GNUstep">GNUstep</a>
-<li><a accesskey="4" href="#XOR-graphics">XOR graphics</a>
-<li><a accesskey="5" href="#GIMP">GIMP</a>
-</ul>
-<div class="node">
-<a name="GIF"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#GD-Library">GD Library</a>,
-Previous: <a rel="previous" accesskey="p" href="#Graphics">Graphics</a>,
-Up: <a rel="up" accesskey="u" href="#Graphics">Graphics</a>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#GIF"
accesskey="1">GIF</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#GD-Library"
accesskey="2">GD Library</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#GNUstep"
accesskey="3">GNUstep</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#XOR-graphics"
accesskey="4">XOR graphics</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#GIMP"
accesskey="5">GIMP</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+</table>
+<hr>
+<a name="GIF"></a>
+<div class="header">
+<p>
+Next: <a href="#GD-Library" accesskey="n" rel="next">GD Library</a>, Previous:
<a href="#Graphics" accesskey="p" rel="prev">Graphics</a>, Up: <a
href="#Graphics" accesskey="u" rel="up">Graphics</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="GIF-1"></a>
<h3 class="section">3.1 GIF</h3>
<p>Patents (Unisys and IBM) covering the LZW compression algorithm which is
used in making GIF files.
+</p>
-<div class="node">
+<hr>
<a name="GD-Library"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#GNUstep">GNUstep</a>,
-Previous: <a rel="previous" accesskey="p" href="#GIF">GIF</a>,
-Up: <a rel="up" accesskey="u" href="#Graphics">Graphics</a>
-
+<div class="header">
+<p>
+Next: <a href="#GNUstep" accesskey="n" rel="next">GNUstep</a>, Previous: <a
href="#GIF" accesskey="p" rel="prev">GIF</a>, Up: <a href="#Graphics"
accesskey="u" rel="up">Graphics</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="GD-Library-1"></a>
<h3 class="section">3.2 GD Library</h3>
<p>Moshe Zadka <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-I'm sure this tops the list, but the GD library does not support
+</p>
+<blockquote>
+<p>I’m sure this tops the list, but the GD library does not support
GIF output any longer do to patent program (LZW).
-</blockquote>
+</p></blockquote>
- <p>pavlicek <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-
- <p>The homepage of the project is at:
-
- <p><a href="http://www.boutell.com/gd/";>http://www.boutell.com/gd/</a>
-
- </blockquote>
-
- <p>Don Marti <a href="mailto:address@hidden";>address@hidden</a>
+<p>pavlicek <a href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
- <blockquote>
-Patent number: 4,558,302
+<p>The homepage of the project is at:
+</p>
+<p><a href="http://www.boutell.com/gd/";>http://www.boutell.com/gd/</a>
+</p>
</blockquote>
-<div class="node">
-<a name="GNUstep"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#XOR-graphics">XOR graphics</a>,
-Previous: <a rel="previous" accesskey="p" href="#GD-Library">GD
Library</a>,
-Up: <a rel="up" accesskey="u" href="#Graphics">Graphics</a>
+<p>Don Marti <a href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
+<p>Patent number: 4,558,302
+</p></blockquote>
+<hr>
+<a name="GNUstep"></a>
+<div class="header">
+<p>
+Next: <a href="#XOR-graphics" accesskey="n" rel="next">XOR graphics</a>,
Previous: <a href="#GD-Library" accesskey="p" rel="prev">GD Library</a>, Up: <a
href="#Graphics" accesskey="u" rel="up">Graphics</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="GNUstep-1"></a>
<h3 class="section">3.3 GNUstep</h3>
<p>Adam Fedor <a href="mailto:address@hidden";>address@hidden</a>
Adam Fedor <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-Attached is some text I wrote a few months ago that explains our
+</p>
+<blockquote>
+<p>Attached is some text I wrote a few months ago that explains our
position. The only change is that recently Apple has changed their
interface somewhat which in effect makes parts of the entire GNUstep
-system open to patent 'violation' (not just the EOF and WO parts).
-
- <p>GNUstep, The Basics:
-————–
-
- <p>GNUstep, with regards to the current discussion, consists of three
+system open to patent ’violation’ (not just the EOF and WO parts).
+</p>
+<p>GNUstep, The Basics:
+———-
+</p>
+<p>GNUstep, with regards to the current discussion, consists of three
major parts: The OpenStep system, Enterprise Objects Frameworks (EOF),
and WebObjects (WO). All three parts try to emulate interfaces
originally designed by Next Computer, Inc (Now Apple Computer,
Inc). All three parts use an Object-Oriented design and are primarily
written in the Objective-C language.
-
- <p>The OpenStep system consists of basic foundation classes
+</p>
+<p>The OpenStep system consists of basic foundation classes
(dictionaries, arrays, etc) as well as GUI elements. While Apple
claims it has a copyright over this API, there are no
patents that we know of that affect the basic operation of this system
-(In fact, large parts of the system were released as an "Open"
+(In fact, large parts of the system were released as an "Open"
standard by Apple several years ago).
-
- <p>The EOF is designed to be an Object-Oriented interface to a
+</p>
+<p>The EOF is designed to be an Object-Oriented interface to a
database. This is the interface that Apple has significant patent
claims on that we cannot work around without changing the interface in
-a fundamental way (thereby making it incompatibile with Apple's EOF,
+a fundamental way (thereby making it incompatibile with Apple’s EOF,
which ruins the stated goal of the GNUstep project). EOF depends
somewhat on the OpenStep system.
-
- <p>WO is designed to be an Object-Oriented method of creating and
+</p>
+<p>WO is designed to be an Object-Oriented method of creating and
maintaining dynamic web pages. WO depends on EOF.
-
- <p>EOF:
-—–
-
- <p>Here is a basic description of EOF taken from the Apple
-documentation. This discription actually alludes to Apple's patent
+</p>
+<p>EOF:
+—-
+</p>
+<p>Here is a basic description of EOF taken from the Apple
+documentation. This discription actually alludes to Apple’s patent
that is a key part of the EOF system.
-
- <p>"Enterprise Objects Framework brings the benefits of
+</p>
+<p>"Enterprise Objects Framework brings the benefits of
object-oriented programming to database application
development. You can use the Framework to build feature-rich,
database applications with reusable software components that
tightly couple business information with the business processes
managing that information.
-
- <p>One of the most significant problems developers face when using
+</p>
+<p>One of the most significant problems developers face when using
object-oriented programming languages with SQL databases is the
difficulty of matching static, two-dimensional data structures
with the extensive flexibility afforded by objects. The features
@@ -697,448 +713,424 @@
greater code reusability-are often negated by the programming
restrictions that come with accessing SQL databases within an
object-oriented application.
-
- <p>Enterprise Objects Framework solves this problem by providing
+</p>
+<p>Enterprise Objects Framework solves this problem by providing
tools for defining an object model and mapping it to a data
model. This allows you to create objects that encapsulate both
data and the methods for operating on that data, while taking
advantage of the data access services provided by the Framework
that make it possible for these objects to persist in a relational
- database."
-
- <p>Patents:
-———–
-
- <p>The key patents that cover the implementation of EOF are:
-
- <p>US6085197 07/04/2000 Object graph editing context and methods of use
+ database."
+</p>
+<p>Patents:
+——–
+</p>
+<p>The key patents that cover the implementation of EOF are:
+</p>
+<p>US6085197 07/04/2000 Object graph editing context and methods of use
US5956728 09/21/1999 Object graph editing context and methods of use
US5873093 02/16/1999 Method and apparatus for mapping objects to a data source
US5898871 04/27/1999 Dynamic object communication protocol
-
- <p>URL: <a
href="http://www.patents.ibm.com/patlist?&like_assc=726196&issuedate_selected=CHECKED&title_selected=CHECKED&query=Assignee+=+NEXT%20SOFTWARE";>%20INC.+(726196)&minisd=</a>
-
- <p>US5873093 involves the concept of Key-Value coding (i.e. storing
+</p>
+<p>URL: <a
href="http://www.patents.ibm.com/patlist?&like_assc=726196&issuedate_selected=CHECKED&title_selected=CHECKED&query=Assignee+=+NEXT%20SOFTWARE";>%20INC.+(726196)&minisd=</a>
+</p>
+<p>US5873093 involves the concept of Key-Value coding (i.e. storing
relationships between two entities via a dictionary-like listing of
keys and associated values). In EOF, that is how (dynamic) object models
are associated with (static) database tables.
-
- <p>US5898871 also involves Key-Value coding, but deals more specifically
with
+</p>
+<p>US5898871 also involves Key-Value coding, but deals more specifically with
how to get information out of a database and present it in a uniform,
context-free way to an Object-Oriented program. For example, one
-associates a database property ("FirstName") with an actual
-value ("Joe") in the database and presents it in a dictionary as a
+associates a database property ("FirstName") with an actual
+value ("Joe") in the database and presents it in a dictionary as a
Key-Value pair. This applies to both EOF and WO.
-
- <p>US6085197 and US5956728 covers a system for managing changes to an
+</p>
+<p>US6085197 and US5956728 covers a system for managing changes to an
object-graph that includes also an undo stack.
+</p>
- <p>Possible Prior Art:
-—————————
-
- <p>Rumbaugh, et al. "Object-Oriented Modeling and Design" published 1991,
+<p>Possible Prior Art:
+——————-
+</p>
+<p>Rumbaugh, et al. "Object-Oriented Modeling and Design" published
1991,
chapter 17 deals with mapping object-oriented models to relational
databases. The book stems from actual research and someone should be
able to turn up something like a lab note that even predates any
-patent that contains the word "object".
-
- <p>Objectpeople's product TOPLink for Java and Smalltalk, introduced in
1991.
-
- <p>Relational Object Framework (company bought by IONA). There are
+patent that contains the word "object".
+</p>
+<p>Objectpeople’s product TOPLink for Java and Smalltalk, introduced in
1991.
+</p>
+<p>Relational Object Framework (company bought by IONA). There are
others, at www.object-relational.org, I believe.
-
- <p>A More Detail Analysis (from Stephen MacDougall):
-————————————————————————
-
- <p>"From what I have read of the patent, my impression is that it
+</p>
+<p>A More Detail Analysis (from Stephen MacDougall):
+————————————————-
+</p>
+<p>"From what I have read of the patent, my impression is that it
only covers the creating of the EOModel, as evidenced by the first
- line in the abstract. This states that, "The present invention
+ line in the abstract. This states that, "The present invention
creates a model that maps object classes in an object-oriented
- environment to a data source." Thus, by interpreting the 20
+ environment to a data source." Thus, by interpreting the 20
claims with this in mind, it becomes apparent that the patent is
for the creation of the model itself.
-
- <p>One can conclude from this that we can do every part of EOF except
+</p>
+<p>One can conclude from this that we can do every part of EOF except
the EOModel, which creates the model in the first place. We
can even read a pre-existing EOModel and use it, as far as I can
determine. This would be similar to the LZW patent, in which you
can freely create an LZW decoder, but creating an encoder would
involve licensing to Unisys, as they hold the patent for the LZW
encoding process.
-
- <p>So, if we can find a way to create a completely separate and
+</p>
+<p>So, if we can find a way to create a completely separate and
distinctively unique method to perform a *similar* function,
without violating the patent, then we could go forward, and then
just create a conversion program that would convert from an
EOModel to a GDFMap type of construct. (GDF = GNU Database
Framework, the current working name unless someone comes up with
- something better. "
-
- </blockquote>
+ something better. "
+</p>
+</blockquote>
-<div class="node">
+<hr>
<a name="XOR-graphics"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#GIMP">GIMP</a>,
-Previous: <a rel="previous" accesskey="p" href="#GNUstep">GNUstep</a>,
-Up: <a rel="up" accesskey="u" href="#Graphics">Graphics</a>
-
+<div class="header">
+<p>
+Next: <a href="#GIMP" accesskey="n" rel="next">GIMP</a>, Previous: <a
href="#GNUstep" accesskey="p" rel="prev">GNUstep</a>, Up: <a href="#Graphics"
accesskey="u" rel="up">Graphics</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="XOR-graphics-1"></a>
<h3 class="section">3.4 XOR graphics</h3>
<p>Ingo Marks <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-someone holds a patent on XOR on graphics.
-
- <p>So you couldn't draw a selection frame with your mouse in Gimp
-without violating this patent. You would have to "enjoy" flickering like
+</p>
+<blockquote>
+<p>someone holds a patent on XOR on graphics.
+</p>
+<p>So you couldn’t draw a selection frame with your mouse in Gimp
+without violating this patent. You would have to "enjoy" flickering
like
Sinclar ZX81 or enter the corner coordinates via keyboard.
-</blockquote>
+</p></blockquote>
-<div class="node">
+<hr>
<a name="GIMP"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#XOR-graphics">XOR
graphics</a>,
-Up: <a rel="up" accesskey="u" href="#Graphics">Graphics</a>
-
+<div class="header">
+<p>
+Previous: <a href="#XOR-graphics" accesskey="p" rel="prev">XOR graphics</a>,
Up: <a href="#Graphics" accesskey="u" rel="up">Graphics</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="GIMP-1"></a>
<h3 class="section">3.5 GIMP</h3>
<p>Richard Stallman <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-The GIMP and other free software cannot support Pantone color
+</p>
+<blockquote>
+<p>The GIMP and other free software cannot support Pantone color
matching. This makes it much harder for free software to do a good
job of generating images for printing.
+</p>
+<p>The GIMP developers may be able to tell you what the patent number is.
+</p></blockquote>
- <p>The GIMP developers may be able to tell you what the patent number is.
-</blockquote>
-
-<div class="node">
+<hr>
<a name="Speech-Synthesis"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Fonts">Fonts</a>,
-Previous: <a rel="previous" accesskey="p" href="#Graphics">Graphics</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</a>
-
+<div class="header">
+<p>
+Next: <a href="#Fonts" accesskey="n" rel="next">Fonts</a>, Previous: <a
href="#Graphics" accesskey="p" rel="prev">Graphics</a>, Up: <a href="#Top"
accesskey="u" rel="up">Top</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="Speech-Synthesis-1"></a>
<h2 class="chapter">4 Speech Synthesis</h2>
-<ul class="menu">
-<li><a accesskey="1" href="#MBROLA">MBROLA</a>
-</ul>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#MBROLA"
accesskey="1">MBROLA</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+</table>
-<div class="node">
+<hr>
<a name="MBROLA"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#Speech-Synthesis">Speech
Synthesis</a>,
-Up: <a rel="up" accesskey="u" href="#Speech-Synthesis">Speech
Synthesis</a>
-
+<div class="header">
+<p>
+Previous: <a href="#Speech-Synthesis" accesskey="p" rel="prev">Speech
Synthesis</a>, Up: <a href="#Speech-Synthesis" accesskey="u" rel="up">Speech
Synthesis</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="MBROLA-1"></a>
<h3 class="section">4.1 MBROLA</h3>
<p>The France Telecom patent was used to threaten MBROLA,
with the result that it was made non-free.
+</p>
- <p>"Thierry Dutoit" <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-France Telecom's patent on PSOLA (a well-known speech synthesis technique) :
US 005327498
-
- <p>Our own patent on MBROLA : US 005987413
+<p>"Thierry Dutoit" <a
href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
+<p>France Telecom’s patent on PSOLA (a well-known speech synthesis
technique) : US 005327498
+</p>
+<p>Our own patent on MBROLA : US 005987413
+</p>
+<p>There is a third patent on similar thechniques, owned by Philips : EP
0527527 A2
+</p>
- <p>There is a third patent on similar thechniques, owned by Philips : EP
0527527 A2
+<p>This is the European version of the France Telecom patent: EP 363 233 (B1)
+</p>
+<p>This is the Canadian patent: C 1 324 670
+</p></blockquote>
- <p>This is the European version of the France Telecom patent: EP 363 233
(B1)
- <p>This is the Canadian patent: C 1 324 670
-</blockquote>
-<div class="node">
+<hr>
<a name="Fonts"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Text-Processor">Text
Processor</a>,
-Previous: <a rel="previous" accesskey="p" href="#Speech-Synthesis">Speech
Synthesis</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</a>
-
+<div class="header">
+<p>
+Next: <a href="#Text-Processor" accesskey="n" rel="next">Text Processor</a>,
Previous: <a href="#Speech-Synthesis" accesskey="p" rel="prev">Speech
Synthesis</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="Fonts-1"></a>
<h2 class="chapter">5 Fonts</h2>
-<ul class="menu">
-<li><a accesskey="1" href="#FreeType">FreeType</a>
-</ul>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#FreeType"
accesskey="1">FreeType</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+</table>
-<div class="node">
+<hr>
<a name="FreeType"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#Fonts">Fonts</a>,
-Up: <a rel="up" accesskey="u" href="#Fonts">Fonts</a>
-
+<div class="header">
+<p>
+Previous: <a href="#Fonts" accesskey="p" rel="prev">Fonts</a>, Up: <a
href="#Fonts" accesskey="u" rel="up">Fonts</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="FreeType-1"></a>
<h3 class="section">5.1 FreeType</h3>
<p>Thomas Hudson <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-One such example is the FreeType Project (http://www.freetype.org).
+</p>
+<blockquote>
+<p>One such example is the FreeType Project (http://www.freetype.org).
Apple has several patents on the hinting mechanism of TrueType fonts.
Thus the freetype project had to implement a different mechanism.
+</p>
+<p>More information can be found here:
+</p>
+<p>http://freetype.sourceforge.net/patents.html
+</p></blockquote>
- <p>More information can be found here:
-
- <p>http://freetype.sourceforge.net/patents.html
-</blockquote>
-
- <p>"Alexander Weber" <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-The Freetype font-rendering library is affected by a patent hold by
+<p>"Alexander Weber" <a
href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
+<p>The Freetype font-rendering library is affected by a patent hold by
Apple describing an algorithm to speed up rendering
-
- <p>http://www.freetype.org/
+</p>
+<p>http://www.freetype.org/
http://www.freetype.org/patents.html
-</blockquote>
+</p></blockquote>
-<div class="node">
+<hr>
<a name="Text-Processor"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Compression">Compression</a>,
-Previous: <a rel="previous" accesskey="p" href="#Fonts">Fonts</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</a>
-
+<div class="header">
+<p>
+Next: <a href="#Compression" accesskey="n" rel="next">Compression</a>,
Previous: <a href="#Fonts" accesskey="p" rel="prev">Fonts</a>, Up: <a
href="#Top" accesskey="u" rel="up">Top</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="Text-Processor-1"></a>
<h2 class="chapter">6 Text Processor</h2>
-<ul class="menu">
-<li><a accesskey="1" href="#Ted">Ted</a>
-</ul>
-<div class="node">
-<a name="Ted"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#Text-Processor">Text
Processor</a>,
-Up: <a rel="up" accesskey="u" href="#Text-Processor">Text Processor</a>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#Ted"
accesskey="1">Ted</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+</table>
+<hr>
+<a name="Ted"></a>
+<div class="header">
+<p>
+Previous: <a href="#Text-Processor" accesskey="p" rel="prev">Text
Processor</a>, Up: <a href="#Text-Processor" accesskey="u" rel="up">Text
Processor</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="Ted-1"></a>
<h3 class="section">6.1 Ted</h3>
<p>Mark de Does <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-Not only the HTML/GIF writing part of my easy rich text processor
-'Ted', but many of the graphics projects I do suffer from the fact
+</p>
+<blockquote>
+<p>Not only the HTML/GIF writing part of my easy rich text processor
+’Ted’, but many of the graphics projects I do suffer from the fact
that writing GIF files is a problem.
-
- <p>I probably suffer more from the cowardice of Linux distributors
+</p>
+<p>I probably suffer more from the cowardice of Linux distributors
that ship libungif under the name of libgif, than from the actual
patent. As A European I prefer to ignore the LZW patent. The cowardly
misrepresentation causes me headaches because the patent invites
distributors to distribute a library that writes GIF files that only
are GIF files formally.
-</blockquote>
+</p></blockquote>
-<div class="node">
-<a name="Compression"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Web-server">Web server</a>,
-Previous: <a rel="previous" accesskey="p" href="#Text-Processor">Text
Processor</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</a>
+<hr>
+<a name="Compression"></a>
+<div class="header">
+<p>
+Next: <a href="#Web-server" accesskey="n" rel="next">Web server</a>, Previous:
<a href="#Text-Processor" accesskey="p" rel="prev">Text Processor</a>, Up: <a
href="#Top" accesskey="u" rel="up">Top</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="Compression-1"></a>
<h2 class="chapter">7 Compression</h2>
-<ul class="menu">
-<li><a accesskey="1" href="#ncompress">ncompress</a>
-<li><a accesskey="2" href="#bzip">bzip</a>
-<li><a accesskey="3" href="#zlib">zlib</a>
-</ul>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#ncompress"
accesskey="1">ncompress</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#bzip"
accesskey="2">bzip</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#zlib"
accesskey="3">zlib</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+</table>
-<div class="node">
+<hr>
<a name="ncompress"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#bzip">bzip</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Compression">Compression</a>,
-Up: <a rel="up" accesskey="u" href="#Compression">Compression</a>
-
+<div class="header">
+<p>
+Next: <a href="#bzip" accesskey="n" rel="next">bzip</a>, Previous: <a
href="#Compression" accesskey="p" rel="prev">Compression</a>, Up: <a
href="#Compression" accesskey="u" rel="up">Compression</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="ncompress-1"></a>
<h3 class="section">7.1 ncompress</h3>
<p>Moshe Zadka <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-The "ncompress" program is very hard to find, and is not distributed in
+</p>
+<blockquote>
+<p>The "ncompress" program is very hard to find, and is not
distributed in
many GNU/Linux distributions because it uses the patented LZW.
-</blockquote>
+</p></blockquote>
-<div class="node">
+<hr>
<a name="bzip"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#zlib">zlib</a>,
-Previous: <a rel="previous" accesskey="p" href="#ncompress">ncompress</a>,
-Up: <a rel="up" accesskey="u" href="#Compression">Compression</a>
-
+<div class="header">
+<p>
+Next: <a href="#zlib" accesskey="n" rel="next">zlib</a>, Previous: <a
href="#ncompress" accesskey="p" rel="prev">ncompress</a>, Up: <a
href="#Compression" accesskey="u" rel="up">Compression</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="bzip-1"></a>
<h3 class="section">7.2 bzip</h3>
<p>Sengan <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-I think the original version of bzip was impeded in that the arithmetic
+</p>
+<blockquote>
+<p>I think the original version of bzip was impeded in that the arithmetic
compression section was taken out.
-</blockquote>
+</p></blockquote>
- <p>Kyle Sparger <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-"It also used arithmetic coding as the entropy encoder, but
+<p>Kyle Sparger <a href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
+<p>"It also used arithmetic coding as the entropy encoder, but
this had to be changed to Huffman coding in bzip2 for patent reasons, it
-seems." – <span
class="strike-through">>http://www.kyz.uklinux.net/packers.php3#bzip2</span>
-</blockquote>
+seems." – http://www.kyz.uklinux.net/packers.php3#bzip2
+</p></blockquote>
-<div class="node">
+<hr>
<a name="zlib"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#bzip">bzip</a>,
-Up: <a rel="up" accesskey="u" href="#Compression">Compression</a>
-
+<div class="header">
+<p>
+Previous: <a href="#bzip" accesskey="p" rel="prev">bzip</a>, Up: <a
href="#Compression" accesskey="u" rel="up">Compression</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="zlib-1"></a>
<h3 class="section">7.3 zlib</h3>
<p>Patrick Goltzsch <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-I'll point you to Jean-loup Gailly <address@hidden> who
+</p>
+<blockquote>
+<p>I’ll point you to Jean-loup Gailly <address@hidden> who
wrote zlib. During my journalistic investigations on
software patents I came across his home page
(http://gailly.net/), where he describes his difficulties
with patents. Actually a never published version of zlib
did violate a patent. He found out about it before
publication and changed it accordingly.
+</p>
+<p>If he did not already answer himself, you should write him,
+I’m sure he’s very cooperative.
+</p>
+</blockquote>
- <p>If he did not already answer himself, you should write him,
-I'm sure he's very cooperative.
-
- </blockquote>
-
-<div class="node">
+<hr>
<a name="Web-server"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Compilers">Compilers</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Compression">Compression</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</a>
-
+<div class="header">
+<p>
+Next: <a href="#Compilers" accesskey="n" rel="next">Compilers</a>, Previous:
<a href="#Compression" accesskey="p" rel="prev">Compression</a>, Up: <a
href="#Top" accesskey="u" rel="up">Top</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="Web-server-1"></a>
<h2 class="chapter">8 Web server</h2>
-<ul class="menu">
-<li><a accesskey="1" href="#Roxen">Roxen</a>
-</ul>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#Roxen"
accesskey="1">Roxen</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+</table>
-<div class="node">
+<hr>
<a name="Roxen"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#Web-server">Web
server</a>,
-Up: <a rel="up" accesskey="u" href="#Web-server">Web server</a>
-
+<div class="header">
+<p>
+Previous: <a href="#Web-server" accesskey="p" rel="prev">Web server</a>, Up:
<a href="#Web-server" accesskey="u" rel="up">Web server</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="Roxen-1"></a>
<h3 class="section">8.1 Roxen</h3>
-<p>Niels Möller <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-With the Roxen web-server, there were two well-known patents that
-caused some trouble: The RSA patent (now expired) and the lzw "gif"
+<p>Niels Möller <a href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
+<p>With the Roxen web-server, there were two well-known patents that
+caused some trouble: The RSA patent (now expired) and the lzw "gif"
patents.
+</p>
+<p>The consequences (that I know of) were limited distribution to the US.
+</p>
+<p>I’m no longer working with Roxen, so for more information it is
+probably better to mail <a href="mailto:address@hidden";>address@hidden</a>
than me.
+</p></blockquote>
- <p>The consequences (that I know of) were limited distribution to the US.
- <p>I'm no longer working with Roxen, so for more information it is
-probably better to mail <a href="mailto:address@hidden";>address@hidden</a>
than me.
-</blockquote>
-<div class="node">
+<hr>
<a name="Compilers"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Programming">Programming</a>,
-Previous: <a rel="previous" accesskey="p" href="#Web-server">Web
server</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</a>
-
+<div class="header">
+<p>
+Next: <a href="#Programming" accesskey="n" rel="next">Programming</a>,
Previous: <a href="#Web-server" accesskey="p" rel="prev">Web server</a>, Up: <a
href="#Top" accesskey="u" rel="up">Top</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="Compilers-1"></a>
<h2 class="chapter">9 Compilers</h2>
-<ul class="menu">
-<li><a accesskey="1" href="#GCC">GCC</a>
-</ul>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#GCC"
accesskey="1">GCC</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+</table>
-<div class="node">
+<hr>
<a name="GCC"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#Compilers">Compilers</a>,
-Up: <a rel="up" accesskey="u" href="#Compilers">Compilers</a>
-
+<div class="header">
+<p>
+Previous: <a href="#Compilers" accesskey="p" rel="prev">Compilers</a>, Up: <a
href="#Compilers" accesskey="u" rel="up">Compilers</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="GCC-1"></a>
<h3 class="section">9.1 GCC</h3>
<p>Stefan Rieken <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-I heard telling that GCC suffers because there are a whole bunch of
+</p>
+<blockquote>
+<p>I heard telling that GCC suffers because there are a whole bunch of
optimization algorithms with patents. To find out more about that,
-you'll have to check with GCC.
-</blockquote>
-
- <p>Sengan <a href="mailto:address@hidden";>address@hidden</a>
+you’ll have to check with GCC.
+</p></blockquote>
- <blockquote>
-There's the graph colouring algorithm used in register allocation in gcc
+<p>Sengan <a href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
+<p>There’s the graph colouring algorithm used in register allocation in
gcc
that had to be replaced by a multi-pass algorithm IIRC.
-</blockquote>
-
- <p>Francois PELLEGRINI <a href="mailto:address@hidden";>address@hidden</a>
+</p></blockquote>
- <blockquote>
-I have been told that register coloring, although the best available
+<p>Francois PELLEGRINI <a href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
+<p>I have been told that register coloring, although the best available
algorithm for register allocation in compilers, is not implemented in
GCC because of an IBM patent...
-</blockquote>
+</p></blockquote>
- <p>Ian Lance Taylor <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-In early 1996, when I was employed by Cygnus Solutions, I spent about
+<p>Ian Lance Taylor <a href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
+<p>In early 1996, when I was employed by Cygnus Solutions, I spent about
a month working on gcc patches to do memory bounds checking. I
patched gcc to generate a call to a bounds checker around every memory
access. Array references to arrays of known size were handled by
@@ -1148,382 +1140,370 @@
(I implemented the linker –wrap option to make this easily
controllable at link time). It was possible to link code compiled
with checking with code compiled without checking.
-
- <p>The idea was to permit easy detection of memory access errors. This
+</p>
+<p>The idea was to permit easy detection of memory access errors. This
was based on the Purify product from Pure Software (now part of
Rational). Their product was linker based. This had the advantage of
not requiring recompilation, but the significant disadvantage of only
working on a few platforms. Since Cygnus was primarily an embedded
development tools supplier, it was critical that we be able to supply
this feature for arbitrary platforms which Purify did not support.
-
- <p>However, the project was cancelled, because Pure Software owned
+</p>
+<p>However, the project was cancelled, because Pure Software owned
patents on memory checking. It was not clear whether my code
interfered with those patents, since their product was linker based,
but based on reading the patents violation was a possibility.
-
- <p>Pure was known to be a litigious company, and had sued other companies
+</p>
+<p>Pure was known to be a litigious company, and had sued other companies
to uphold their patents. At that time, Cygnus was a relatively small
company, and a lawsuit would have been a serious drain on our
resources. Therefore, the project was cancelled.
-
- <p>I estimate that I implemented about 80% of the required work. I
+</p>
+<p>I estimate that I implemented about 80% of the required work. I
developed a simple testsuite of some twenty or thirty cases which were
all handled correctly. Most of the remaining required work was
optimizing the data structures and implementing compiler optimizations
based on known memory access checks–avoiding checking the same area
of memory twice, coalescing memory checks when possible, etc. The
goal was that checked code run at at least 50% of the speed of
-ordinary code; I don't know whether or not I would have reached that
+ordinary code; I don’t know whether or not I would have reached that
goal, as the project was cancelled before I did any serious speed
testing.
-
- <p>I'd be happy to answer questions, although of course this was a few
+</p>
+<p>I’d be happy to answer questions, although of course this was a few
years ago so I no longer recall all the details. I am no longer at
-Cygnus, and I don't know if the work I did is still available.
-
- </blockquote>
+Cygnus, and I don’t know if the work I did is still available.
+</p>
+</blockquote>
-<div class="node">
+<hr>
<a name="Programming"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#Drivers">Drivers</a>,
-Previous: <a rel="previous" accesskey="p" href="#Compilers">Compilers</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</a>
-
+<div class="header">
+<p>
+Next: <a href="#Drivers" accesskey="n" rel="next">Drivers</a>, Previous: <a
href="#Compilers" accesskey="p" rel="prev">Compilers</a>, Up: <a href="#Top"
accesskey="u" rel="up">Top</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="Programming-1"></a>
<h2 class="chapter">10 Programming</h2>
-<ul class="menu">
-<li><a accesskey="1" href="#HyperProf">HyperProf</a>
-<li><a accesskey="2" href="#OpenIPO">OpenIPO</a>
-<li><a accesskey="3" href="#Virtual-functions-in-C_002b_002b">Virtual
functions in C++</a>
-<li><a accesskey="4" href="#CDDB_002fFreeDB">CDDB/FreeDB</a>
-<li><a accesskey="5" href="#ElectricFence">ElectricFence</a>
-</ul>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#HyperProf"
accesskey="1">HyperProf</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#OpenIPO"
accesskey="2">OpenIPO</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a
href="#Virtual-functions-in-C_002b_002b" accesskey="3">Virtual functions in
C++</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#CDDB_002fFreeDB"
accesskey="4">CDDB/FreeDB</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">• <a href="#ElectricFence"
accesskey="5">ElectricFence</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+</table>
-<div class="node">
+<hr>
<a name="HyperProf"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#OpenIPO">OpenIPO</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Programming">Programming</a>,
-Up: <a rel="up" accesskey="u" href="#Programming">Programming</a>
-
+<div class="header">
+<p>
+Next: <a href="#OpenIPO" accesskey="n" rel="next">OpenIPO</a>, Previous: <a
href="#Programming" accesskey="p" rel="prev">Programming</a>, Up: <a
href="#Programming" accesskey="u" rel="up">Programming</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="HyperProf-1"></a>
<h3 class="section">10.1 HyperProf</h3>
<p>Tuomas Lukka <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-<a
href="http://web.archive.org/web/20060712210354/http://www.physics.orst.edu/~bulatov/HyperProf/index.html";>http://www.physics.orst.edu/~bulatov/HyperProf/index.html</a>
(archived)
-
- <p>This is home of my hyperbolic browser of Java profile. It allows to
+</p>
+<blockquote>
+<p><a
href="http://web.archive.org/web/20060712210354/http://www.physics.orst.edu/~bulatov/HyperProf/index.html";>http://web.archive.org/web/20060712210354/http://www.physics.orst.edu/~bulatov/HyperProf/index.html</a>
+(archived)
+</p>
+<p>This is home of my hyperbolic browser of Java profile. It allows to
represent results of Java profiling in more readable way, as well as it
offers cool interactive hyperbolic representation of packages, classes,
methods and calls of your Java program.
-
- <p>....
-
- <p>Downloading
-
- <p>You can NOT currently download HyperProf-1.3.tar.gz(90K) or
+</p>
+<p>....
+</p>
+<p>Downloading
+</p>
+<p>You can NOT currently download HyperProf-1.3.tar.gz(90K) or
HyperProf-1.3.zip (132K) because Xerox have patented algorithm
for tree visualization which is similar to one used in HyperProf and
things should be settled down first.
-
- <p>——
-
- <p>So this is one piece of really interesting visualization software that
+</p>
+<p>—–
+</p>
+<p>So this is one piece of really interesting visualization software that
has been withdrawn. Sad but true.
-</blockquote>
+</p></blockquote>
-<div class="node">
-<a name="OpenIPO"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#Virtual-functions-in-C_002b_002b">Virtual functions in C++</a>,
-Previous: <a rel="previous" accesskey="p" href="#HyperProf">HyperProf</a>,
-Up: <a rel="up" accesskey="u" href="#Programming">Programming</a>
+<hr>
+<a name="OpenIPO"></a>
+<div class="header">
+<p>
+Next: <a href="#Virtual-functions-in-C_002b_002b" accesskey="n"
rel="next">Virtual functions in C++</a>, Previous: <a href="#HyperProf"
accesskey="p" rel="prev">HyperProf</a>, Up: <a href="#Programming"
accesskey="u" rel="up">Programming</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="OpenIPO-1"></a>
<h3 class="section">10.2 OpenIPO</h3>
<p><a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-Around February 2000, I heard about W.R.Hambrecht and Cos.' IPO scheme
+</p>
+<blockquote>
+<p>Around February 2000, I heard about W.R.Hambrecht and Cos.’ IPO scheme
that was based on the work of the Nobel prize-winning economist John
-Vickrey. It's basically a fairer way to arrive at the issue price of a
-share based on potential investors' bids. The share floats at the
+Vickrey. It’s basically a fairer way to arrive at the issue price of a
+share based on potential investors’ bids. The share floats at the
highest price at which the required funds can be collected, not some
arbitrary price decided by underwriters.
-
- <p>I thought of writing a free software package to enable underwriters to
+</p>
+<p>I thought of writing a free software package to enable underwriters to
run such an IPO themselves, but first contacted W.R.Hambrecht & Co. to
see if they had patented the procedure. I can dig up the relevant
-correspondence (it's on another machine's mailbox somewhere...) but the
+correspondence (it’s on another machine’s mailbox somewhere...)
but the
gist of their reply was that they had made significant innovations on
-top of Vickrey's work and that they intended to defend their
+top of Vickrey’s work and that they intended to defend their
intellectual property. They did not explicitly mention any patent. I
lost interest in pursuing the OpenIPO software after that, even though I
-have the engine ready and working. If the patent threat is removed, I'll
+have the engine ready and working. If the patent threat is removed, I’ll
be happy to resume work on it.
-
- <p>Ganesh Prasad
+</p>
+<p>Ganesh Prasad
<a href="http://netwinsite.com";>http://netwinsite.com</a>
-</blockquote>
+</p></blockquote>
-<div class="node">
-<a name="Virtual-functions-in-C++"></a>
+<hr>
<a name="Virtual-functions-in-C_002b_002b"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#CDDB_002fFreeDB">CDDB/FreeDB</a>,
-Previous: <a rel="previous" accesskey="p" href="#OpenIPO">OpenIPO</a>,
-Up: <a rel="up" accesskey="u" href="#Programming">Programming</a>
-
+<div class="header">
+<p>
+Next: <a href="#CDDB_002fFreeDB" accesskey="n" rel="next">CDDB/FreeDB</a>,
Previous: <a href="#OpenIPO" accesskey="p" rel="prev">OpenIPO</a>, Up: <a
href="#Programming" accesskey="u" rel="up">Programming</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="Virtual-functions-in-C_002b_002b-1"></a>
<h3 class="section">10.3 Virtual functions in C++</h3>
<p>Tom Tromey <a href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
- <blockquote>
-
- <p>There are many patents surrounding how to implement virtual functions in
+<p>There are many patents surrounding how to implement virtual functions in
C++. Many of the obvious approaches to implementing vtables are
patented. I believe this has affected the design of the new G++ ABI.
+</p>
+<p>Jason Merrill <a href="mailto:address@hidden";>address@hidden</a> probably
has more details.
+</p>
+</blockquote>
- <p>Jason Merrill <a href="mailto:address@hidden";>address@hidden</a>
probably has more details.
-
- </blockquote>
-
-<div class="node">
-<a name="CDDB%2fFreeDB"></a>
+<hr>
<a name="CDDB_002fFreeDB"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n" href="#ElectricFence">ElectricFence</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Virtual-functions-in-C_002b_002b">Virtual functions in C++</a>,
-Up: <a rel="up" accesskey="u" href="#Programming">Programming</a>
-
+<div class="header">
+<p>
+Next: <a href="#ElectricFence" accesskey="n" rel="next">ElectricFence</a>,
Previous: <a href="#Virtual-functions-in-C_002b_002b" accesskey="p"
rel="prev">Virtual functions in C++</a>, Up: <a href="#Programming"
accesskey="u" rel="up">Programming</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="CDDB_002fFreeDB-1"></a>
<h3 class="section">10.4 CDDB/FreeDB</h3>
<p>Marc van Woerkom <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-If you haven't noticed yet, check out the Slashdot article on CDDB's
+</p>
+<blockquote>
+<p>If you haven’t noticed yet, check out the Slashdot article on
CDDB’s
stupid patent.
-
- <p><a
href="http://slashdot.org/article.pl?sid=00/12/08/2254214&mode=thread";>http://slashdot.org/article.pl?sid=00/12/08/2254214&mode=thread</a>
-
- <p>An Anonymous Coward writes: "Today I received a very ominous package
+</p>
+<p><a
href="http://slashdot.org/article.pl?sid=00/12/08/2254214&mode=thread";>http://slashdot.org/article.pl?sid=00/12/08/2254214&mode=thread</a>
+</p>
+<p>An Anonymous Coward writes: "Today I received a very ominous package
from GraceNote, owners of CDDB. Already infamous for turning a wonderful
open project into a quagmire of heavy contracts, licensing fees, forced
user registration and anti-competition clauses, the package from
GraceNote contained one thing: copies of their patents, freshly
-awarded. "Don't even think about using FreeDB", the packaged seemed to
-silently imply, "because we own the patents, period." That patent?
-"Method and system for finding approximate matches in a database."
-Ouch. Thanks, USPTO." Scary: I use freedb constantly. I'd hate to lose
+awarded. "Don’t even think about using FreeDB", the packaged
seemed to
+silently imply, "because we own the patents, period." That patent?
+"Method and system for finding approximate matches in a database."
+Ouch. Thanks, USPTO." Scary: I use freedb constantly. I’d hate to
lose
it.
-
- <p>Method and system for finding approximate matches in a database.
+</p>
+<p>Method and system for finding approximate matches in a database.
<a
href="http://www.delphion.com/details?&pn=US06061680__";>http://www.delphion.com/details?&pn=US06061680__</a>
+</p>
+</blockquote>
- </blockquote>
-
- <p>Robert Kaye <a href="mailto:address@hidden";>address@hidden</a>
- <blockquote>
-Two years ago I started a project called the CD Index
+<p>Robert Kaye <a href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
+<p>Two years ago I started a project called the CD Index
(http://www.cdindex.org) which was aimed to be a replacement for the
CDDB system. CDDB is designed to look up the title, artist name and
track names for a CD, so that a software CD player can display the
titles during playback.
-
- <p>Once upon a time CDDB was open and the data was freely available to
+</p>
+<p>Once upon a time CDDB was open and the data was freely available to
anyone who cared to download it. The server source code and the client
source code to calculate the unique ID for a given CD were freely
available on the net. IANAL (I am not a lawyer), so I cannot tell if
this would qualify as prior art to discredit this patent, but it sure
smells like it.
-
- <p>After a few years in existence CDDB was sold to Escient Inc., who then
+</p>
+<p>After a few years in existence CDDB was sold to Escient Inc., who then
stopped making the data available on the net and started to force
creators of software CD players to agree to very restrictive licensing
agreements in order for their players to access the CDDB database.
-
- <p>These restrictive licensing agreements to access the data that was
+</p>
+<p>These restrictive licensing agreements to access the data that was
contributed by the general public were the motivation for me to create
the CD Index. This summer I started the follow up project called
MusicBrainz (http://www.musicbrainz.org) in order to generalize the
project to be an open metadatabase for audio content. The system now
supports the identification of MP3s and Ogg/Vorbis files as well.
-
- <p>Last week CDDB/Gracenote (formerly Escient) was awarded a patent which
+</p>
+<p>Last week CDDB/Gracenote (formerly Escient) was awarded a patent which
now restricts the calculation of a unique ID for a CD/DVD disk based on
the table of contents of the CD/DVD. The patent also coveres other
aspects, but this is currently the most serious issue. Slashdot covered
this patent in the following article:
-
- <p>http://slashdot.org/article.pl?sid=00/12/08/2254214&mode=thread
-
- <p>I have not received a cease-and-desist letter, but given the CDDB's
+</p>
+<p>http://slashdot.org/article.pl?sid=00/12/08/2254214&mode=thread
+</p>
+<p>I have not received a cease-and-desist letter, but given the CDDB’s
previous track record it cannot be long before I will get that magic
letter. Without having read the complete patent, I cannot say how
MusicBrainz will be affected. In the worst case scenario, we may need to
stop our service to look up CD information.
-
- <p>If you have further questions, or if I can provide you with more
-information, please don't hesitate to ask. My contact information is
+</p>
+<p>If you have further questions, or if I can provide you with more
+information, please don’t hesitate to ask. My contact information is
below:
-
- <p>Robert Kaye
+</p>
+<p>Robert Kaye
Emusic.com SLO
1304 Garden St.
San Luis Obispo, CA 93401
(805) 785-0607
address@hidden
-
- <p>Thank you for taking the software patent issue up, and thank you for all
+</p>
+<p>Thank you for taking the software patent issue up, and thank you for all
the efforts of the GNU/FSF team.
+</p>
+</blockquote>
- </blockquote>
-
- <p>Drew Streib <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-Relevant patents are 5987525, 6154773, and 6061680.
- <p>(Drew sent anothe email where he exchanged some comments with John
+<p>Drew Streib <a href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
+<p>Relevant patents are 5987525, 6154773, and 6061680.
+</p>
+<p>(Drew sent anothe email where he exchanged some comments with John
Gilmore from EFF)
-
- <p>I've done some research in the subject and believe that the patent
+</p>
+<p>I’ve done some research in the subject and believe that the patent
is invalidated by prior art.
+</p>
+</blockquote>
- </blockquote>
-
-<div class="node">
+<hr>
<a name="ElectricFence"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p"
href="#CDDB_002fFreeDB">CDDB/FreeDB</a>,
-Up: <a rel="up" accesskey="u" href="#Programming">Programming</a>
-
+<div class="header">
+<p>
+Previous: <a href="#CDDB_002fFreeDB" accesskey="p" rel="prev">CDDB/FreeDB</a>,
Up: <a href="#Programming" accesskey="u" rel="up">Programming</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="ElectricFence-1"></a>
<h3 class="section">10.5 ElectricFence</h3>
<p>Francois PELLEGRINI <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
- I think Bruce Perens was threatened over his ElectricFence bounds
+</p>
+<blockquote>
+<p>I think Bruce Perens was threatened over his ElectricFence bounds
checking system for C programs by a company which obtained a patent
while he was still developing it.
-
- <p>If I remember well, the memory leak checking algorithm was patented by
-Pure Software for its "Purify" tool. Pure software merged with Atria
+</p>
+<p>If I remember well, the memory leak checking algorithm was patented by
+Pure Software for its "Purify" tool. Pure software merged with Atria
(www.pureatria.com), and finally got swallowed by Rational Software
(www.rational.com).
-
- <p>If I remember well, Pure Software reportedly threatened to sue any
+</p>
+<p>If I remember well, Pure Software reportedly threatened to sue any
individual trying to produce a libre enhanced version of memory-leak
checkers. It is why, although the need for such a tool is obvious in any
libre distribution for developers, it is still missing.
+</p>
+</blockquote>
- </blockquote>
-
-<div class="node">
+<hr>
<a name="Drivers"></a>
-<p><hr>
-Next: <a rel="next" accesskey="n"
href="#Communication-Protocols">Communication Protocols</a>,
-Previous: <a rel="previous" accesskey="p"
href="#Programming">Programming</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</a>
-
+<div class="header">
+<p>
+Next: <a href="#Communication-Protocols" accesskey="n"
rel="next">Communication Protocols</a>, Previous: <a href="#Programming"
accesskey="p" rel="prev">Programming</a>, Up: <a href="#Top" accesskey="u"
rel="up">Top</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="Drivers-1"></a>
<h2 class="chapter">11 Drivers</h2>
-<ul class="menu">
-<li><a accesskey="1" href="#CueCat">CueCat</a>
-</ul>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#CueCat"
accesskey="1">CueCat</a>:</td><td> </td><td align="left"
valign="top">
+</td></tr>
+</table>
-<div class="node">
+<hr>
<a name="CueCat"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#Drivers">Drivers</a>,
-Up: <a rel="up" accesskey="u" href="#Drivers">Drivers</a>
-
+<div class="header">
+<p>
+Previous: <a href="#Drivers" accesskey="p" rel="prev">Drivers</a>, Up: <a
href="#Drivers" accesskey="u" rel="up">Drivers</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="CueCat-1"></a>
<h3 class="section">11.1 CueCat</h3>
<p>Michael Rothwell <a href="mailto:address@hidden";>address@hidden</a>
+</p>
+<blockquote>
- <blockquote>
-
- <p><a
href="http://web.archive.org/web/20060615102119/http://www.flyingbuttmonkeys.com/foocat/";>http://www.flyingbuttmonkeys.com/foocat/</a>
(archived)
-
- <p>I've recieved two letters from the law firm representing Digital
-Convergence. I didn't back down, and they have not (as of yet) done
-anything about it. As far as I know, they are licensing NeoMedia's
-patents (search for NeoMedia on <a
href="http://www.delphion.com/";>delphion.com</a>). They've written a
-LOT of these letters, and most people folded.
-
- </blockquote>
+<p><a
href="http://web.archive.org/web/20060615102119/http://www.flyingbuttmonkeys.com/foocat/";>http://web.archive.org/web/20060615102119/http://www.flyingbuttmonkeys.com/foocat/</a>
+(archived)
+</p>
+<p>I’ve recieved two letters from the law firm representing Digital
+Convergence. I didn’t back down, and they have not (as of yet) done
+anything about it. As far as I know, they are licensing NeoMedia’s
+patents (search for NeoMedia on <a
href="http://www.delphion.com/";>http://www.delphion.com/</a>).
+They’ve written a LOT of these letters, and most people folded.
+</p>
+</blockquote>
-<div class="node">
+<hr>
<a name="Communication-Protocols"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p" href="#Drivers">Drivers</a>,
-Up: <a rel="up" accesskey="u" href="#Top">Top</a>
-
+<div class="header">
+<p>
+Previous: <a href="#Drivers" accesskey="p" rel="prev">Drivers</a>, Up: <a
href="#Top" accesskey="u" rel="up">Top</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="Communication-Protocols-1"></a>
<h2 class="chapter">12 Communication Protocols</h2>
-<ul class="menu">
-<li><a accesskey="1" href="#WAP">WAP</a>
-</ul>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">• <a href="#WAP"
accesskey="1">WAP</a>:</td><td> </td><td align="left" valign="top">
+</td></tr>
+</table>
-<div class="node">
+<hr>
<a name="WAP"></a>
-<p><hr>
-Previous: <a rel="previous" accesskey="p"
href="#Communication-Protocols">Communication Protocols</a>,
-Up: <a rel="up" accesskey="u"
href="#Communication-Protocols">Communication Protocols</a>
-
+<div class="header">
+<p>
+Previous: <a href="#Communication-Protocols" accesskey="p"
rel="prev">Communication Protocols</a>, Up: <a href="#Communication-Protocols"
accesskey="u" rel="up">Communication Protocols</a> </p>
</div>
-
-<!-- node-name, next, previous, up -->
+<a name="WAP-1"></a>
<h3 class="section">12.1 WAP</h3>
<p>Richard M. Stallman <a href="mailto:address@hidden";>address@hidden</a>
-
- <blockquote>
-WAP could be a good example of software patents that can be very
+</p>
+<blockquote>
+<p>WAP could be a good example of software patents that can be very
harmful. WAP includes a whole series of gratuitously-incompatible
modified versions of standard Internet protocols. The idea seems to
be to sell the public mobile phones that can only talk to specially
designed servers, not to ordinary Internet servers. And since the
protocols are patented, it will be impossible to write free software
to set up those servers.
+</p>
+<p>You can get more information from the Free Protocols Foundation.
+</p>
+<p><a href="http://www.freeprotocols.org";>http://www.freeprotocols.org</a>
+</p>
+</blockquote>
- <p>You can get more information from the Free Protocols Foundation.
-
- <p><a href="http://www.freeprotocols.org";>http://www.freeprotocols.org</a>
+<hr>
- </blockquote>
-</body></html>
+</body>
+</html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/patent-examp patent-examples.html,
Pavel Kharitonov <=