[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/patent-examp index.html patent-examples.htm...
|
From: |
Karl Berry |
|
Subject: |
www/patent-examp index.html patent-examples.htm... |
|
Date: |
Sat, 10 Apr 2010 18:12:10 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: Karl Berry <karl> 10/04/10 18:12:10
Modified files:
patent-examp : index.html patent-examples.html
patent-examples.texi
Log message:
regenerate patent-examples.html, give it a title, link to it from
announcement, switch announcement to current boilerplate; #362989
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/patent-examp/index.html?cvsroot=www&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/www/patent-examp/patent-examples.html?cvsroot=www&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/www/patent-examp/patent-examples.texi?cvsroot=www&r1=1.4&r2=1.5
Patches:
Index: index.html
===================================================================
RCS file: /web/www/www/patent-examp/index.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- index.html 5 May 2005 19:37:13 -0000 1.5
+++ index.html 10 Apr 2010 18:12:00 -0000 1.6
@@ -1,121 +1,98 @@
-<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN">
-<HTML>
-<HEAD>
-<TITLE>Software Patents that have harmed Free Software - GNU Project - Free
Software Foundation (FSF)</TITLE>
-<LINK REV="made" HREF="mailto:address@hidden";>
-</HEAD>
-<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#1F00FF" ALINK="#FF0000"
VLINK="#9900DD">
-<H3>Software Patents that have harmed Free Software</H3>
-<A HREF="/graphics/agnuhead.html"><IMG SRC="/graphics/gnu-head-sm.jpg"
- ALT=" [image of the Head of a GNU] "
- WIDTH="129" HEIGHT="122"></A>
-
-[
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
- <A HREF="/index.html">English</A>
-<!-- | A HREF="/boilerplate.LG.html" LANGUAGE /A -->
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
-]
-
-<P>
-<!-- Replace this list with the page's contents. -->
-<H4>Table of Contents</H4>
-<UL>
- <LI><A HREF="#initannounce" NAME="TOCinitannounce">Initial Announcement</A>
-</UL>
-
-<P>
-<HR>
-<P>
-<H4><A HREF="#TOCinitannounce" NAME="initannounce">Initial
Announcement</A></H4>
-<P>
- Richard Stallman <address@hidden>
-<P>
- Date: Mon, 11 Dec 2000 10:00:08 -0700 (MST)
-<P>
- [Please repost this widely wherever appropriate]
-<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>
- 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 (see <http://www.freepatents.org>).
-<P>
- If you know of such a case, please write to
- <address@hidden> and tell us what happened.
-<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 information, please write anyway and tell
- us whatever you know. For 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 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 <address@hidden> rather
- than to me personally, so that we can collect the responses
- efficiency.
-
-<P>
-
-
-<!--
- * If needed, change the copyright block at the bottom. In general, all pages
- on the GNU web server should have the section about verbatim
- copying. Please do NOT remove this without talking with the webmasters
- first.
--->
-
-<HR>
-
-[
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
- <A HREF="./index.html">English</A>
-<!-- | A HREF="/boilerplate.LG.html" LANGUAGE /A -->
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
-]
-
-<HR>
-
-<P>
-Return to <A HREF="/home.html">GNU's home page</A>.
-<P>
-
-Please send FSF & GNU inquiries & questions to
-
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>.
-There are also <A HREF="/home.html#ContactInfo">other ways to
-contact</A> the FSF.
-<P>
-
-Please send comments on these web pages to
-
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>,
-send other questions to
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>.
-<P>
-Copyright (C) 2001 Free Software Foundation, Inc.,
-51 Franklin St, Fifth Floor, Boston, MA 02110, USA
-<P>
-Verbatim copying and distribution of this entire article is
-permitted in any medium, provided this notice is preserved.
-<P>
-Updated:
-<!-- hhmts start -->
-Last modified: Sun Feb 25 00:06:41 EST 2001
-<!-- hhmts end -->
-<HR>
-</BODY>
-</HTML>
+<!--#include virtual="/server/header.html" -->
+<title>Software patents that have harmed free software
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/server/banner.html" -->
+<h2>Software patents that have harmed free software</h2>
+
+<p>[Please repost this widely, anywhere it's 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
+software patents wherever possible.</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>
+
+<p>Ideally we would like to know the name of the program, its
+developer's name and email address or other contact information, 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 information, please write anyway and tell us whatever you know.
+For 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
+developer. We may write back to you to try to get more details; any
+leads for getting more details are also welcome.</p>
+
+<p>The <a href="patent-examples.html">information collected so far</a>
+is available.
+
+<p>Thanks.</p>
+
+<!-- If needed, change the copyright block at the bottom. In general,
+ all pages on the GNU web server should have the section about
+ verbatim copying. Please do NOT remove this without talking
+ with the webmasters first.
+ Please make sure the copyright date is consistent with the document
+ and that it is like this: "2001, 2002", not this: "2001-2002". -->
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+
+<p>Please send general FSF & GNU inquiries to
+<a href="mailto:address@hidden";><address@hidden></a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.<br />
+Please send broken links and other corrections or suggestions to
+<a href="mailto:address@hidden";><address@hidden></a>.</p>
+
+<p>Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+
+<p>Copyright © 2001, 2010 Free Software Foundation, Inc.</p>
+
+<p>Verbatim copying and distribution of this entire article are
+permitted worldwide, without royalty, in any medium, provided this
+notice, and the copyright notice, are preserved.</p>
+
+<p>Updated:
+<!-- timestamp start -->
+$Date: 2010/04/10 18:12:00 $
+<!-- timestamp end -->
+</p>
+</div>
+
+<div id="translations">
+<h4>Translations of this page</h4>
+
+<!-- Please keep this list alphabetical by language code.
+ Comment what the language is for each type, i.e. de is German.
+ Write the language name in its own language (Deutsch) in the text.
+ If you add a new language here, please
+ advise address@hidden and add it to
+ - /home/www/html/server/standards/README.translations.html
+ - one of the lists under the section "Translations Underway"
+ - if there is a translation team, you also have to add an alias
+ to mail.gnu.org:/com/mailer/aliases
+ Please also check you have the language code right; see:
+ http://www.loc.gov/standards/iso639-2/php/code_list.php
+ If the 2-letter ISO 639-1 code is not available,
+ use the 3-letter ISO 639-2.
+ Please use W3C normative character entities. -->
+
+<ul class="translations-list">
+<!-- English -->
+<li><a href="/server/standards/boilerplate.html">English</a> [en]</li>
+</ul>
+</div>
+</div>
+</body>
+</html>
Index: patent-examples.html
===================================================================
RCS file: /web/www/www/patent-examp/patent-examples.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- patent-examples.html 4 Sep 2009 13:00:45 -0000 1.5
+++ patent-examples.html 10 Apr 2010 18:12:00 -0000 1.6
@@ -1,130 +1,181 @@
-a<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en"><head>
- <meta http-equiv="Content-Type" content=
- "text/html; charset=utf-8">
-<title>Untitled</title>
+<html lang="en">
+<head>
+<title>Software patents that hurt free software</title>
<meta http-equiv="Content-Type" content="text/html">
-<meta name=description content="Untitled">
-<meta name=generator content="makeinfo 4.0">
-<link href="http://texinfo.org/"; rel=generator-home>
-</head><body>
-
-<p><hr>
-Node:<a name="Top">Top</a>,
-Next:<a rel=next href="#Original%20Announcement">Original Announcement</a>,
-Previous:<a rel=previous href="#(dir)">(dir)</a>,
-Up:<a rel=up href="#(dir)">(dir)</a>
-<br>
-
-<h1>Examples of Software Patents that hurt Free Software</h1>
-
-<ul>
-<li><a href="#Original%20Announcement">Original Announcement</a>:
-<li><a href="#Audio%2fVideo">Audio/Video</a>:
-<li><a href="#Graphics">Graphics</a>:
-<li><a href="#Speech%20Synthesis">Speech Synthesis</a>:
-<li><a href="#Fonts">Fonts</a>:
-<li><a href="#Text%20Processor">Text Processor</a>:
-<li><a href="#Compression">Compression</a>:
-<li><a href="#Web%20server">Web server</a>:
-<li><a href="#Compilers">Compilers</a>:
-<li><a href="#Programming">Programming</a>:
-<li><a href="#Drivers">Drivers</a>:
-<li><a href="#Communication%20Protocols">Communication Protocols</a>:
+<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><li><a href="#RealNetworks">RealNetworks</a>:
-<li><a href="#BladeEnc">BladeEnc</a>:
-<li><a href="#Ogg%20Vorbis">Ogg Vorbis</a>:
-<li><a href="#Virtual%20Dub">Virtual Dub</a>:
-<li><a href="#Broadcast%202000">Broadcast 2000</a>:
-<li><a href="#xanim">xanim</a>:
-<li><a href="#MPEGII">MPEGII</a>:
+</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="#xanim">xanim</a>
+<li><a href="#MPEGII">MPEGII</a>
+</li></ul>
<p>Graphics
-</p><li><a href="#GIF">GIF</a>:
-<li><a href="#GD%20Library">GD Library</a>:
-<li><a href="#GNUstep">GNUstep</a>:
-<li><a href="#XOR%20graphics">XOR graphics</a>:
-<li><a href="#GIMP">GIMP</a>:
+</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><li><a href="#MBROLA">MBROLA</a>:
+</p>
+<ul class="menu">
+<li><a href="#MBROLA">MBROLA</a>
+</li></ul>
<p>Fonts
-</p><li><a href="#FreeType">FreeType</a>:
+</p>
+<ul class="menu">
+<li><a href="#FreeType">FreeType</a>
+</li></ul>
<p>Text Processor
-</p><li><a href="#Ted">Ted</a>:
+</p>
+<ul class="menu">
+<li><a href="#Ted">Ted</a>
+</li></ul>
<p>Compression
-</p><li><a href="#ncompress">ncompress</a>:
-<li><a href="#bzip">bzip</a>:
-<li><a href="#zlib">zlib</a>:
+</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><li><a href="#Roxen">Roxen</a>:
+</p>
+<ul class="menu">
+<li><a href="#Roxen">Roxen</a>
+</li></ul>
<p>Compilers
-</p><li><a href="#GCC">GCC</a>:
+</p>
+<ul class="menu">
+<li><a href="#GCC">GCC</a>
+</li></ul>
<p>Programming
-</p><li><a href="#HyperProf">HyperProf</a>:
-<li><a href="#OpenIPO">OpenIPO</a>:
-<li><a href="#Virtual%20functions%20in%20C++">Virtual functions in C++</a>:
-<li><a href="#CDDB%2fFreeDB">CDDB/FreeDB</a>:
-<li><a href="#ElectricFence">ElectricFence</a>:
+</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
-</p><li><a href="#CueCat">CueCat</a>:
+</p>
+<ul class="menu">
+<li><a href="#CueCat">CueCat</a>
+</li></ul>
<p>Communication Protocols
-</p><li><a href="#WAP">WAP</a>:
+</p>
+<ul class="menu">
+<li><a href="#WAP">WAP</a>
</ul>
+<div class="node">
+<a name="Original-Announcement"></a>
<p><hr>
-Node:<a name="Original%20Announcement">Original Announcement</a>,
-Next:<a rel=next href="#Audio%2fVideo">Audio/Video</a>,
-Previous:<a rel=previous href="#Top">Top</a>,
-Up:<a rel=up href="#Top">Top</a>
-<br>
+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>
-<h1>Original Announcement</h1>
+</div>
-<p>Richard Stallman <address@hidden>
+<!-- node-name, next, previous, up -->
+<h2 class="chapter">1 Original Announcement</h2>
-<p>Date: Mon, 11 Dec 2000 10:00:08 -0700 (MST)
+<p>Richard Stallman <address@hidden>
-<blockquote>
-[Please repost this widely wherever appropriate]
+ <p>Date: Mon, 11 Dec 2000 10:00:08 -0700 (MST)
-<p>We would like to collect information about cases where free
-software has actually 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.
+ <blockquote>
+[Please repost this widely wherever appropriate]
-<p>We hope to use this information to argue against the system of
-software patents.
+ <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>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 (see <a
href="http://www.freepatents.org";>http://www.freepatents.org</a>).
-<p>If you know of such a case, please write to <a
href="mailto:address@hidden";>address@hidden</a>
+ <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>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
@@ -135,71 +186,76 @@
developer. We may write back to you to try to get more details; even
leads for getting more details may be useful.
-<p>Please do not report patents which are merely <em>possible</em> threats.
-There are thousands of those. Please report only cases of actual harm.
-
-<p>Please send your information to <a
href="mailto:address@hidden";>address@hidden</a>so that we can collect the
responses efficiency.
+ <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>
+<div class="node">
+<a name="Audio%2fVideo"></a>
+<a name="Audio_002fVideo"></a>
<p><hr>
-Node:<a name="Audio%2fVideo">Audio/Video</a>,
-Next:<a rel=next href="#Graphics">Graphics</a>,
-Previous:<a rel=previous href="#Original%20Announcement">Original
Announcement</a>,
-Up:<a rel=up href="#Top">Top</a>
-<br>
+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>
-<h1>Audio/Video</h1>
+<!-- node-name, next, previous, up -->
+<h2 class="chapter">2 Audio/Video</h2>
<p>Thomas Hudson <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
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>http://www.linuxdj.com/audio/lad/index.php3
-<p>Check the archives of the mailing list. Almost every development runs
+ <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>
-<ul>
-<li><a href="#RealNetworks">RealNetworks</a>:
-<li><a href="#BladeEnc">BladeEnc</a>:
-<li><a href="#Ogg%20Vorbis">Ogg Vorbis</a>:
-<li><a href="#Virtual%20Dub">Virtual Dub</a>:
-<li><a href="#Broadcast%202000">Broadcast 2000</a>:
-<li><a href="#xanim">xanim</a>:
-<li><a href="#MPEGII">MPEGII</a>:
+<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="6" href="#xanim">xanim</a>
+<li><a accesskey="7" href="#MPEGII">MPEGII</a>
</ul>
+<div class="node">
+<a name="RealNetworks"></a>
<p><hr>
-Node:<a name="RealNetworks">RealNetworks</a>,
-Next:<a rel=next href="#BladeEnc">BladeEnc</a>,
-Previous:<a rel=previous href="#Audio%2fVideo">Audio/Video</a>,
-Up:<a rel=up href="#Audio%2fVideo">Audio/Video</a>
-<br>
+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>
-<h2>RealNetworks</h2>
+</div>
+
+<!-- node-name, next, previous, up -->
+<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 =
+ <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 =
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 whole thing stinks.=20
-<p>The patent abstract is below - unfortunately, the core patent documents =
+ <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. ( =
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>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 =
patent cluster, and he actually rejected some of them last September =
@@ -208,14 +264,14 @@
algorithm relating to video compression in low-bandwidth situations that =
could have been applied very usefully, had it been freely distributed. =20
-<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>Audio-on-demand communication system=20
+ <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 =
@@ -237,27 +293,27 @@
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>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
+ <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>References Cited [Referenced By]
-<p>- ------------------------------------------------------------------------=
-- ------
+ <p>-
————————————————————————————————————=
+- ———
-<p>U.S. Patent Documents
+ <p>U.S. Patent Documents
4827256 May., 1989 Yokoyama. =20
5132992 Jul., 1992 Yurt et al.. =20
5237322 Aug., 1993 Heberle. =20
@@ -268,7 +324,7 @@
5915094 Jun., 1999 Kouloheris et al. 709/219. =20
5917835 Jun., 1999 Barret et al.. =20
-<p>Other References=20
+ <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 =
@@ -278,61 +334,64 @@
Bigelow S J; "Modem Communications Standards"; Electronics Now; =
pp. 35-42, Sep. 1994. =20
-<p>Primary Examiner: Rinehart; Mark H.=20
+ <p>Primary Examiner: Rinehart; Mark H.=20
Attorney, Agent or Firm: Knobbe, Martens, Olson & Bear, LLP=20
</blockquote>
+<div class="node">
+<a name="BladeEnc"></a>
<p><hr>
-Node:<a name="BladeEnc">BladeEnc</a>,
-Next:<a rel=next href="#Ogg%20Vorbis">Ogg Vorbis</a>,
-Previous:<a rel=previous href="#RealNetworks">RealNetworks</a>,
-Up:<a rel=up href="#Audio%2fVideo">Audio/Video</a>
-<br>
+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>
-<h2>BladeEnc</h2>
+<!-- node-name, next, previous, up -->
+<h3 class="section">2.2 BladeEnc</h3>
<p>Erkki Ruohtula <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
One free program with patent troubles is the BladeEnc MP3 encoder. See
-its homepage at <<code>http://bladeenc.mp3.no</code>> for the story,
especially
+its homepage at <a href="http://bladeenc.mp3.no";>http://bladeenc.mp3.no</a>
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>Kyle Sparger <a href="mailto:address@hidden";>address@hidden</a>
+ <p>Kyle Sparger <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
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>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>
+ <p>Tord Jansson <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
(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>European Patent numbers from the first round:
-<p>0378609
+ <p>0378609
0277613
0309974
0193143
0414838
0251028
-<p>European Patent numbers from the second round:
+ <p>European Patent numbers from the second round:
-<p>0287578
+ <p>0287578
0340301
0393526
0612156
@@ -350,20 +409,23 @@
0494990
0464534
-</blockquote>
+ </blockquote>
+<div class="node">
+<a name="Ogg-Vorbis"></a>
<p><hr>
-Node:<a name="Ogg%20Vorbis">Ogg Vorbis</a>,
-Next:<a rel=next href="#Virtual%20Dub">Virtual Dub</a>,
-Previous:<a rel=previous href="#BladeEnc">BladeEnc</a>,
-Up:<a rel=up href="#Audio%2fVideo">Audio/Video</a>
-<br>
+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>
-<h2>Ogg Vorbis</h2>
+</div>
+
+<!-- node-name, next, previous, up -->
+<h3 class="section">2.3 Ogg Vorbis</h3>
<p>Mike Coleman <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
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
@@ -371,50 +433,53 @@
it'll only be a matter of time.
</blockquote>
-<p>"Terry Dube" <a href="mailto:address@hidden";>address@hidden</a>
+ <p>"Terry Dube" <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
-<<code>http://mp3licensing.com/patents.html</code>> bragging about there
software
+ <blockquote>
+<a
href="http://mp3licensing.com/patents.html";>http://mp3licensing.com/patents.html</a>
bragging about there software
patents.
</blockquote>
+<div class="node">
+<a name="Virtual-Dub"></a>
<p><hr>
-Node:<a name="Virtual%20Dub">Virtual Dub</a>,
-Next:<a rel=next href="#Broadcast%202000">Broadcast 2000</a>,
-Previous:<a rel=previous href="#Ogg%20Vorbis">Ogg Vorbis</a>,
-Up:<a rel=up href="#Audio%2fVideo">Audio/Video</a>
-<br>
+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>
-<h2>Virtual Dub</h2>
+<!-- node-name, next, previous, up -->
+<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>"Ram'on Garc'ia Fern'andez" <a
href="mailto:address@hidden";>address@hidden</a>
+ <p>"Ram'on Garc'ia Fern'andez" <a
href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
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>Virtual Dub home page:
-<p><<code>http://www186.pair.com/vdub/</code>>
+ <p><a href="http://www186.pair.com/vdub/";>http://www186.pair.com/vdub/</a>
-<p>The story:
-<<code>http://www.advogato.org/article/101.html</code>>
+ <p>The story:
+<a
href="http://www.advogato.org/article/101.html";>http://www.advogato.org/article/101.html</a>
</blockquote>
-<p>Derrick Moser <a href="mailto:address@hidden";>address@hidden</a>
+ <p>Derrick Moser <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <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>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.
@@ -423,9 +488,9 @@
ability to transcode these media files to AVI format.
</blockquote>
-<p>David Berglund <a href="mailto:address@hidden";>address@hidden</a>
+ <p>David Berglund <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
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
@@ -435,22 +500,25 @@
device with any free software operating system, since Microsoft controls
the format. They do not give any "buyer beware" notices.
-<p>Information about the Sharp VN-EZ1:
-<<code>http://www.sharp.co.jp/sc/gaiyou/news-e/990317.html</code>>
+ <p>Information about the Sharp VN-EZ1:
+<a
href="http://www.sharp.co.jp/sc/gaiyou/news-e/990317.html";>http://www.sharp.co.jp/sc/gaiyou/news-e/990317.html</a>
</blockquote>
+<div class="node">
+<a name="Broadcast-2000"></a>
<p><hr>
-Node:<a name="Broadcast%202000">Broadcast 2000</a>,
-Next:<a rel=next href="#xanim">xanim</a>,
-Previous:<a rel=previous href="#Virtual%20Dub">Virtual Dub</a>,
-Up:<a rel=up href="#Audio%2fVideo">Audio/Video</a>
-<br>
+Next: <a rel="next" accesskey="n" href="#xanim">xanim</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>
-<h2>Broadcast 2000</h2>
+<!-- node-name, next, previous, up -->
+<h3 class="section">2.5 Broadcast 2000</h3>
<p>David Berglund <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
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
@@ -460,173 +528,191 @@
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:
-<<code>http://heroine.linuxave.net/bcast2000.html</code>>
+ <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>and the e-mail is:
<a href="mailto:address@hidden";>address@hidden</a>
</blockquote>
+<div class="node">
+<a name="xanim"></a>
<p><hr>
-Node:<a name="xanim">xanim</a>,
-Next:<a rel=next href="#MPEGII">MPEGII</a>,
-Previous:<a rel=previous href="#Broadcast%202000">Broadcast 2000</a>,
-Up:<a rel=up href="#Audio%2fVideo">Audio/Video</a>
-<br>
+Next: <a rel="next" accesskey="n" href="#MPEGII">MPEGII</a>,
+Previous: <a rel="previous" accesskey="p"
href="#Broadcast-2000">Broadcast 2000</a>,
+Up: <a rel="up" accesskey="u" href="#Audio_002fVideo">Audio/Video</a>
-<h2>xanim</h2>
+</div>
+
+<!-- node-name, next, previous, up -->
+<h3 class="section">2.6 xanim</h3>
<p>Mikael Hermansson <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
For example the most popular movie player for *nix is xanim It can't
support some of the codecs for quicktime(sorensen video codec)/avi(some
of intels/IBM)/mpeg4 because of those patents.
-<p>IMHO! this is bad because in the future people need to go back using
+ <p>IMHO! this is bad because in the future people need to go back using
windows because the users can't look at movies on *nix platforms.
-<p>For more info about this look at <<code>xanim.va.pubnix.com</code>>
+ <p>For more info about this look at <a
href="xanim.va.pubnix.com">xanim.va.pubnix.com</a>
</blockquote>
+<div class="node">
+<a name="MPEGII"></a>
<p><hr>
-Node:<a name="MPEGII">MPEGII</a>,
-Previous:<a rel=previous href="#xanim">xanim</a>,
-Up:<a rel=up href="#Audio%2fVideo">Audio/Video</a>
-<br>
+Previous: <a rel="previous" accesskey="p" href="#xanim">xanim</a>,
+Up: <a rel="up" accesskey="u" href="#Audio_002fVideo">Audio/Video</a>
+
+</div>
-<h2>MPEGII</h2>
+<!-- node-name, next, previous, up -->
+<h3 class="section">2.7 MPEGII</h3>
<p>Sengan <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
-<<code>http://www.mpegla.com/lic_agreement.html</code>>
+ <blockquote>
+<a
href="http://www.mpegla.com/lic_agreement.html";>http://www.mpegla.com/lic_agreement.html</a>
-<p>"There can't be any Free Software that encodes MPEG II without violating
+ <p>"There can't be any Free Software that encodes MPEG II without violating
this patent"
</blockquote>
+<div class="node">
+<a name="Graphics"></a>
<p><hr>
-Node:<a name="Graphics">Graphics</a>,
-Next:<a rel=next href="#Speech%20Synthesis">Speech Synthesis</a>,
-Previous:<a rel=previous href="#Audio%2fVideo">Audio/Video</a>,
-Up:<a rel=up href="#Top">Top</a>
-<br>
-
-<h1>Graphics</h1>
-
-<ul>
-<li><a href="#GIF">GIF</a>:
-<li><a href="#GD%20Library">GD Library</a>:
-<li><a href="#GNUstep">GNUstep</a>:
-<li><a href="#XOR%20graphics">XOR graphics</a>:
-<li><a href="#GIMP">GIMP</a>:
+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>
+
+<!-- node-name, next, previous, up -->
+<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>
-Node:<a name="GIF">GIF</a>,
-Next:<a rel=next href="#GD%20Library">GD Library</a>,
-Previous:<a rel=previous href="#Graphics">Graphics</a>,
-Up:<a rel=up href="#Graphics">Graphics</a>
-<br>
+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>
+
+</div>
-<h2>GIF</h2>
+<!-- node-name, next, previous, up -->
+<h3 class="section">3.1 GIF</h3>
<p>Patents (Unisys and IBM) covering the LZW compression algorithm which is
used in making GIF files.
+<div class="node">
+<a name="GD-Library"></a>
<p><hr>
-Node:<a name="GD%20Library">GD Library</a>,
-Next:<a rel=next href="#GNUstep">GNUstep</a>,
-Previous:<a rel=previous href="#GIF">GIF</a>,
-Up:<a rel=up href="#Graphics">Graphics</a>
-<br>
+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>
-<h2>GD Library</h2>
+</div>
+
+<!-- node-name, next, previous, up -->
+<h3 class="section">3.2 GD Library</h3>
<p>Moshe Zadka <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
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>pavlicek <a href="mailto:address@hidden";>address@hidden</a>
+ <p>pavlicek <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
-<p>The homepage of the project is at:
+ <p>The homepage of the project is at:
-<p><<code>http://www.boutell.com/gd/</code>>
+ <p><a href="http://www.boutell.com/gd/";>http://www.boutell.com/gd/</a>
-</blockquote>
+ </blockquote>
-<p>Don Marti <a href="mailto:address@hidden";>address@hidden</a>
+ <p>Don Marti <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
Patent number: 4,558,302
</blockquote>
+<div class="node">
+<a name="GNUstep"></a>
<p><hr>
-Node:<a name="GNUstep">GNUstep</a>,
-Next:<a rel=next href="#XOR%20graphics">XOR graphics</a>,
-Previous:<a rel=previous href="#GD%20Library">GD Library</a>,
-Up:<a rel=up href="#Graphics">Graphics</a>
-<br>
+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>
-<h2>GNUstep</h2>
+</div>
+
+<!-- node-name, next, previous, up -->
+<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>
+ <blockquote>
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, The Basics:
+————–
-<p>GNUstep, with regards to the current discussion, consists of three
+ <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>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"
standard by Apple several years ago).
-<p>The EOF is designed to be an Object-Oriented interface to a
+ <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,
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>WO is designed to be an Object-Oriented method of creating and
maintaining dynamic web pages. WO depends on EOF.
-<p>EOF:
----
+ <p>EOF:
+—–
-<p>Here is a basic description of EOF taken from the Apple
+ <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>"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>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
@@ -636,7 +722,7 @@
restrictions that come with accessing SQL databases within an
object-oriented application.
-<p>Enterprise Objects Framework solves this problem by providing
+ <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
@@ -644,51 +730,51 @@
that make it possible for these objects to persist in a relational
database."
-<p>Patents:
--------
+ <p>Patents:
+———–
-<p>The key patents that cover the implementation of EOF are:
+ <p>The key patents that cover the implementation of EOF are:
-<p>US6085197 07/04/2000 Object graph editing context and methods of use
+ <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:
<<code>http://www.patents.ibm.com/patlist?&like_assc=726196&issuedate_selected=CHECKED&title_selected=CHECKED&query=Assignee+=+NEXT%20SOFTWARE,%20INC.+(726196)&minisd=</code>>
+ <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>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>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
Key-Value pair. This applies to both EOF and WO.
-<p>US6085197 and US5956728 covers a system for managing changes to an
+ <p>US6085197 and US5956728 covers a system for managing changes to an
object-graph that includes also an undo stack.
-<p>Possible Prior Art:
-------------------
+ <p>Possible Prior Art:
+—————————
-<p>Rumbaugh, et al. "Object-Oriented Modeling and Design" published 1991,
+ <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>Objectpeople's product TOPLink for Java and Smalltalk, introduced in
1991.
-<p>Relational Object Framework (company bought by IONA). There are
+ <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>A More Detail Analysis (from Stephen MacDougall):
+————————————————————————
-<p>"From what I have read of the patent, my impression is that it
+ <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
creates a model that maps object classes in an object-oriented
@@ -696,7 +782,7 @@
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>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
@@ -704,7 +790,7 @@
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>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
@@ -712,155 +798,179 @@
Framework, the current working name unless someone comes up with
something better. "
-</blockquote>
+ </blockquote>
+<div class="node">
+<a name="XOR-graphics"></a>
<p><hr>
-Node:<a name="XOR%20graphics">XOR graphics</a>,
-Next:<a rel=next href="#GIMP">GIMP</a>,
-Previous:<a rel=previous href="#GNUstep">GNUstep</a>,
-Up:<a rel=up href="#Graphics">Graphics</a>
-<br>
+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>
-<h2>XOR graphics</h2>
+</div>
+
+<!-- node-name, next, previous, up -->
+<h3 class="section">3.4 XOR graphics</h3>
<p>Ingo Marks <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
someone holds a patent on XOR on graphics.
-<p>So you couldn't draw a selection frame with your mouse in Gimp
+ <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>
+<div class="node">
+<a name="GIMP"></a>
<p><hr>
-Node:<a name="GIMP">GIMP</a>,
-Previous:<a rel=previous href="#XOR%20graphics">XOR graphics</a>,
-Up:<a rel=up href="#Graphics">Graphics</a>
-<br>
+Previous: <a rel="previous" accesskey="p" href="#XOR-graphics">XOR
graphics</a>,
+Up: <a rel="up" accesskey="u" href="#Graphics">Graphics</a>
+
+</div>
-<h2>GIMP</h2>
+<!-- node-name, next, previous, up -->
+<h3 class="section">3.5 GIMP</h3>
<p>Richard Stallman <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
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>The GIMP developers may be able to tell you what the patent number is.
+ <p>The GIMP developers may be able to tell you what the patent number is.
</blockquote>
+<div class="node">
+<a name="Speech-Synthesis"></a>
<p><hr>
-Node:<a name="Speech%20Synthesis">Speech Synthesis</a>,
-Next:<a rel=next href="#Fonts">Fonts</a>,
-Previous:<a rel=previous href="#Graphics">Graphics</a>,
-Up:<a rel=up href="#Top">Top</a>
-<br>
+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>
-<h1>Speech Synthesis</h1>
+<!-- node-name, next, previous, up -->
+<h2 class="chapter">4 Speech Synthesis</h2>
-<ul>
-<li><a href="#MBROLA">MBROLA</a>:
+<ul class="menu">
+<li><a accesskey="1" href="#MBROLA">MBROLA</a>
</ul>
+<div class="node">
+<a name="MBROLA"></a>
<p><hr>
-Node:<a name="MBROLA">MBROLA</a>,
-Previous:<a rel=previous href="#Speech%20Synthesis">Speech Synthesis</a>,
-Up:<a rel=up href="#Speech%20Synthesis">Speech Synthesis</a>
-<br>
+Previous: <a rel="previous" accesskey="p" href="#Speech-Synthesis">Speech
Synthesis</a>,
+Up: <a rel="up" accesskey="u" href="#Speech-Synthesis">Speech
Synthesis</a>
-<h2>MBROLA</h2>
+</div>
+
+<!-- node-name, next, previous, up -->
+<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>"Thierry Dutoit" <a href="mailto:address@hidden";>address@hidden</a>
+ <p>"Thierry Dutoit" <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
France Telecom's patent on PSOLA (a well-known speech synthesis technique) :
US 005327498
-<p>Our own patent on MBROLA : US 005987413
+ <p>Our own patent on MBROLA : US 005987413
-<p>There is a third patent on similar thechniques, owned by Philips : EP
0527527 A2
+ <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>This is the European version of the France Telecom patent: EP 363 233
(B1)
-<p>This is the Canadian patent: C 1 324 670
+ <p>This is the Canadian patent: C 1 324 670
</blockquote>
+<div class="node">
+<a name="Fonts"></a>
<p><hr>
-Node:<a name="Fonts">Fonts</a>,
-Next:<a rel=next href="#Text%20Processor">Text Processor</a>,
-Previous:<a rel=previous href="#Speech%20Synthesis">Speech Synthesis</a>,
-Up:<a rel=up href="#Top">Top</a>
-<br>
+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>
-<h1>Fonts</h1>
+<!-- node-name, next, previous, up -->
+<h2 class="chapter">5 Fonts</h2>
-<ul>
-<li><a href="#FreeType">FreeType</a>:
+<ul class="menu">
+<li><a accesskey="1" href="#FreeType">FreeType</a>
</ul>
+<div class="node">
+<a name="FreeType"></a>
<p><hr>
-Node:<a name="FreeType">FreeType</a>,
-Previous:<a rel=previous href="#Fonts">Fonts</a>,
-Up:<a rel=up href="#Fonts">Fonts</a>
-<br>
+Previous: <a rel="previous" accesskey="p" href="#Fonts">Fonts</a>,
+Up: <a rel="up" accesskey="u" href="#Fonts">Fonts</a>
+
+</div>
-<h2>FreeType</h2>
+<!-- node-name, next, previous, up -->
+<h3 class="section">5.1 FreeType</h3>
<p>Thomas Hudson <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
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>More information can be found here:
+ <p>More information can be found here:
-<p>http://freetype.sourceforge.net/patents.html
+ <p>http://freetype.sourceforge.net/patents.html
</blockquote>
-<p>"Alexander Weber" <a href="mailto:address@hidden";>address@hidden</a>
+ <p>"Alexander Weber" <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
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>http://www.freetype.org/
http://www.freetype.org/patents.html
</blockquote>
+<div class="node">
+<a name="Text-Processor"></a>
<p><hr>
-Node:<a name="Text%20Processor">Text Processor</a>,
-Next:<a rel=next href="#Compression">Compression</a>,
-Previous:<a rel=previous href="#Fonts">Fonts</a>,
-Up:<a rel=up href="#Top">Top</a>
-<br>
+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>
-<h1>Text Processor</h1>
+</div>
-<ul>
-<li><a href="#Ted">Ted</a>:
+<!-- node-name, next, previous, up -->
+<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>
-Node:<a name="Ted">Ted</a>,
-Previous:<a rel=previous href="#Text%20Processor">Text Processor</a>,
-Up:<a rel=up href="#Text%20Processor">Text Processor</a>
-<br>
+Previous: <a rel="previous" accesskey="p" href="#Text-Processor">Text
Processor</a>,
+Up: <a rel="up" accesskey="u" href="#Text-Processor">Text Processor</a>
+
+</div>
-<h2>Ted</h2>
+<!-- node-name, next, previous, up -->
+<h3 class="section">6.1 Ted</h3>
<p>Mark de Does <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <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
that writing GIF files is a problem.
-<p>I probably suffer more from the cowardice of Linux distributors
+ <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
@@ -868,72 +978,84 @@
are GIF files formally.
</blockquote>
+<div class="node">
+<a name="Compression"></a>
<p><hr>
-Node:<a name="Compression">Compression</a>,
-Next:<a rel=next href="#Web%20server">Web server</a>,
-Previous:<a rel=previous href="#Text%20Processor">Text Processor</a>,
-Up:<a rel=up href="#Top">Top</a>
-<br>
-
-<h1>Compression</h1>
-
-<ul>
-<li><a href="#ncompress">ncompress</a>:
-<li><a href="#bzip">bzip</a>:
-<li><a href="#zlib">zlib</a>:
+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>
+
+</div>
+
+<!-- node-name, next, previous, up -->
+<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>
+<div class="node">
+<a name="ncompress"></a>
<p><hr>
-Node:<a name="ncompress">ncompress</a>,
-Next:<a rel=next href="#bzip">bzip</a>,
-Previous:<a rel=previous href="#Compression">Compression</a>,
-Up:<a rel=up href="#Compression">Compression</a>
-<br>
+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>
-<h2>ncompress</h2>
+<!-- node-name, next, previous, up -->
+<h3 class="section">7.1 ncompress</h3>
<p>Moshe Zadka <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
The "ncompress" program is very hard to find, and is not distributed in
many GNU/Linux distributions because it uses the patented LZW.
</blockquote>
+<div class="node">
+<a name="bzip"></a>
<p><hr>
-Node:<a name="bzip">bzip</a>,
-Next:<a rel=next href="#zlib">zlib</a>,
-Previous:<a rel=previous href="#ncompress">ncompress</a>,
-Up:<a rel=up href="#Compression">Compression</a>
-<br>
+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>
-<h2>bzip</h2>
+</div>
+
+<!-- node-name, next, previous, up -->
+<h3 class="section">7.2 bzip</h3>
<p>Sengan <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
I think the original version of bzip was impeded in that the arithmetic
compression section was taken out.
</blockquote>
-<p>Kyle Sparger <a href="mailto:address@hidden";>address@hidden</a>
+ <p>Kyle Sparger <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
"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." - <<code>http://www.kyz.uklinux.net/packers.php3#bzip2</code>>
+seems." – <a
href="http://www.kyz.uklinux.net/packers.php3#bzip2";>http://www.kyz.uklinux.net/packers.php3#bzip2</a>
</blockquote>
+<div class="node">
+<a name="zlib"></a>
<p><hr>
-Node:<a name="zlib">zlib</a>,
-Previous:<a rel=previous href="#bzip">bzip</a>,
-Up:<a rel=up href="#Compression">Compression</a>
-<br>
+Previous: <a rel="previous" accesskey="p" href="#bzip">bzip</a>,
+Up: <a rel="up" accesskey="u" href="#Compression">Compression</a>
+
+</div>
-<h2>zlib</h2>
+<!-- node-name, next, previous, up -->
+<h3 class="section">7.3 zlib</h3>
<p>Patrick Goltzsch <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
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
@@ -942,92 +1064,104 @@
did violate a patent. He found out about it before
publication and changed it accordingly.
-<p>If he did not already answer himself, you should write him,
+ <p>If he did not already answer himself, you should write him,
I'm sure he's very cooperative.
-</blockquote>
+ </blockquote>
+<div class="node">
+<a name="Web-server"></a>
<p><hr>
-Node:<a name="Web%20server">Web server</a>,
-Next:<a rel=next href="#Compilers">Compilers</a>,
-Previous:<a rel=previous href="#Compression">Compression</a>,
-Up:<a rel=up href="#Top">Top</a>
-<br>
+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>
-<h1>Web server</h1>
+<!-- node-name, next, previous, up -->
+<h2 class="chapter">8 Web server</h2>
-<ul>
-<li><a href="#Roxen">Roxen</a>:
+<ul class="menu">
+<li><a accesskey="1" href="#Roxen">Roxen</a>
</ul>
+<div class="node">
+<a name="Roxen"></a>
<p><hr>
-Node:<a name="Roxen">Roxen</a>,
-Previous:<a rel=previous href="#Web%20server">Web server</a>,
-Up:<a rel=up href="#Web%20server">Web server</a>
-<br>
+Previous: <a rel="previous" accesskey="p" href="#Web-server">Web
server</a>,
+Up: <a rel="up" accesskey="u" href="#Web-server">Web server</a>
-<h2>Roxen</h2>
+</div>
+
+<!-- node-name, next, previous, up -->
+<h3 class="section">8.1 Roxen</h3>
<p>Niels Möller <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <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"
patents.
-<p>The consequences (that I know of) were limited distribution to the US.
+ <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
+ <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">
+<a name="Compilers"></a>
<p><hr>
-Node:<a name="Compilers">Compilers</a>,
-Next:<a rel=next href="#Programming">Programming</a>,
-Previous:<a rel=previous href="#Web%20server">Web server</a>,
-Up:<a rel=up href="#Top">Top</a>
-<br>
+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>
-<h1>Compilers</h1>
+<!-- node-name, next, previous, up -->
+<h2 class="chapter">9 Compilers</h2>
-<ul>
-<li><a href="#GCC">GCC</a>:
+<ul class="menu">
+<li><a accesskey="1" href="#GCC">GCC</a>
</ul>
+<div class="node">
+<a name="GCC"></a>
<p><hr>
-Node:<a name="GCC">GCC</a>,
-Previous:<a rel=previous href="#Compilers">Compilers</a>,
-Up:<a rel=up href="#Compilers">Compilers</a>
-<br>
+Previous: <a rel="previous" accesskey="p" href="#Compilers">Compilers</a>,
+Up: <a rel="up" accesskey="u" href="#Compilers">Compilers</a>
+
+</div>
-<h2>GCC</h2>
+<!-- node-name, next, previous, up -->
+<h3 class="section">9.1 GCC</h3>
<p>Stefan Rieken <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
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>
+ <p>Sengan <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
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>Francois PELLEGRINI <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
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>Ian Lance Taylor <a href="mailto:address@hidden";>address@hidden</a>
+ <p>Ian Lance Taylor <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
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
@@ -1035,11 +1169,11 @@
inline checks which were constant folded when possible. The compiler
used constructors to automatically register every static variable.
Different versions of malloc and free were used to register heap data
-(I implemented the linker -wrap option to make this easily
+(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>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
@@ -1047,96 +1181,105 @@
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>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>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>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
+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
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>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>
+ </blockquote>
+<div class="node">
+<a name="Programming"></a>
<p><hr>
-Node:<a name="Programming">Programming</a>,
-Next:<a rel=next href="#Drivers">Drivers</a>,
-Previous:<a rel=previous href="#Compilers">Compilers</a>,
-Up:<a rel=up href="#Top">Top</a>
-<br>
-
-<h1>Programming</h1>
-
-<ul>
-<li><a href="#HyperProf">HyperProf</a>:
-<li><a href="#OpenIPO">OpenIPO</a>:
-<li><a href="#Virtual%20functions%20in%20C++">Virtual functions in C++</a>:
-<li><a href="#CDDB%2fFreeDB">CDDB/FreeDB</a>:
-<li><a href="#ElectricFence">ElectricFence</a>:
+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>
+
+<!-- node-name, next, previous, up -->
+<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>
+<div class="node">
+<a name="HyperProf"></a>
<p><hr>
-Node:<a name="HyperProf">HyperProf</a>,
-Next:<a rel=next href="#OpenIPO">OpenIPO</a>,
-Previous:<a rel=previous href="#Programming">Programming</a>,
-Up:<a rel=up href="#Programming">Programming</a>
-<br>
+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>
-<h2>HyperProf</h2>
+<!-- node-name, next, previous, up -->
+<h3 class="section">10.1 HyperProf</h3>
<p>Tuomas Lukka <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
-<<code>http://www.physics.orst.edu/~bulatov/HyperProf/index.html</code>>
+ <blockquote>
+<a
href="http://www.physics.orst.edu/~bulatov/HyperProf/index.html";>http://www.physics.orst.edu/~bulatov/HyperProf/index.html</a>
-<p>This is home of my hyperbolic browser of Java profile. It allows to
+ <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>....
-<p>Downloading
+ <p>Downloading
-<p>You can NOT currently download HyperProf-1.3.tar.gz(90K) or
+ <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>——
-<p>So this is one piece of really interesting visualization software that
+ <p>So this is one piece of really interesting visualization software that
has been withdrawn. Sad but true.
</blockquote>
+<div class="node">
+<a name="OpenIPO"></a>
<p><hr>
-Node:<a name="OpenIPO">OpenIPO</a>,
-Next:<a rel=next href="#Virtual%20functions%20in%20C++">Virtual functions in
C++</a>,
-Previous:<a rel=previous href="#HyperProf">HyperProf</a>,
-Up:<a rel=up href="#Programming">Programming</a>
-<br>
+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>
-<h2>OpenIPO</h2>
+</div>
-<a href="mailto:address@hidden";>address@hidden</a>
+<!-- node-name, next, previous, up -->
+<h3 class="section">10.2 OpenIPO</h3>
-<blockquote>
+<p><a href="mailto:address@hidden";>address@hidden</a>
+
+ <blockquote>
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
@@ -1144,7 +1287,7 @@
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>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
@@ -1155,49 +1298,57 @@
have the engine ready and working. If the patent threat is removed, I'll
be happy to resume work on it.
-<p>Ganesh Prasad
-<<code>http://netwinsite.com</code>>
+ <p>Ganesh Prasad
+<a href="http://netwinsite.com";>http://netwinsite.com</a>
</blockquote>
+<div class="node">
+<a name="Virtual-functions-in-C++"></a>
+<a name="Virtual-functions-in-C_002b_002b"></a>
<p><hr>
-Node:<a name="Virtual%20functions%20in%20C++">Virtual functions in C++</a>,
-Next:<a rel=next href="#CDDB%2fFreeDB">CDDB/FreeDB</a>,
-Previous:<a rel=previous href="#OpenIPO">OpenIPO</a>,
-Up:<a rel=up href="#Programming">Programming</a>
-<br>
+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>
-<h2>Virtual functions in C++</h2>
+<!-- node-name, next, previous, up -->
+<h3 class="section">10.3 Virtual functions in C++</h3>
<p>Tom Tromey <a href="mailto:address@hidden";>address@hidden</a>
-<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>Jason Merrill <a href="mailto:address@hidden";>address@hidden</a> probably
has more details.
+ <p>Jason Merrill <a href="mailto:address@hidden";>address@hidden</a>
probably has more details.
-</blockquote>
+ </blockquote>
+<div class="node">
+<a name="CDDB%2fFreeDB"></a>
+<a name="CDDB_002fFreeDB"></a>
<p><hr>
-Node:<a name="CDDB%2fFreeDB">CDDB/FreeDB</a>,
-Next:<a rel=next href="#ElectricFence">ElectricFence</a>,
-Previous:<a rel=previous href="#Virtual%20functions%20in%20C++">Virtual
functions in C++</a>,
-Up:<a rel=up href="#Programming">Programming</a>
-<br>
+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>
-<h2>CDDB/FreeDB</h2>
+</div>
+
+<!-- node-name, next, previous, up -->
+<h3 class="section">10.4 CDDB/FreeDB</h3>
<p>Marc van Woerkom <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
If you haven't noticed yet, check out the Slashdot article on CDDB's
stupid patent.
-<p><<code>http://slashdot.org/article.pl?sid=00/12/08/2254214&mode=thread</code>>
+ <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>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
@@ -1208,167 +1359,182 @@
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.
-<<code>http://www.delphion.com/details?&pn=US06061680__</code>>
+ <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>
-</blockquote>
+ </blockquote>
-<p>Robert Kaye <a href="mailto:address@hidden";>address@hidden</a>
+ <p>Robert Kaye <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
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>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>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>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>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>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>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
+ <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>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>Thank you for taking the software patent issue up, and thank you for all
the efforts of the GNU/FSF team.
-</blockquote>
+ </blockquote>
-<p>Drew Streib <a href="mailto:address@hidden";>address@hidden</a>
+ <p>Drew Streib <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
Relevant patents are 5987525, 6154773, and 6061680.
-<p>(Drew sent anothe email where he exchanged some comments with John
+ <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>I've done some research in the subject and believe that the patent
is invalidated by prior art.
-</blockquote>
+ </blockquote>
+<div class="node">
+<a name="ElectricFence"></a>
<p><hr>
-Node:<a name="ElectricFence">ElectricFence</a>,
-Previous:<a rel=previous href="#CDDB%2fFreeDB">CDDB/FreeDB</a>,
-Up:<a rel=up href="#Programming">Programming</a>
-<br>
+Previous: <a rel="previous" accesskey="p"
href="#CDDB_002fFreeDB">CDDB/FreeDB</a>,
+Up: <a rel="up" accesskey="u" href="#Programming">Programming</a>
-<h2>ElectricFence</h2>
+</div>
+
+<!-- node-name, next, previous, up -->
+<h3 class="section">10.5 ElectricFence</h3>
<p>Francois PELLEGRINI <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
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
+ <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>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.
-</blockquote>
+ </blockquote>
+<div class="node">
+<a name="Drivers"></a>
<p><hr>
-Node:<a name="Drivers">Drivers</a>,
-Next:<a rel=next href="#Communication%20Protocols">Communication Protocols</a>,
-Previous:<a rel=previous href="#Programming">Programming</a>,
-Up:<a rel=up href="#Top">Top</a>
-<br>
+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>
-<h1>Drivers</h1>
+<!-- node-name, next, previous, up -->
+<h2 class="chapter">11 Drivers</h2>
-<ul>
-<li><a href="#CueCat">CueCat</a>:
+<ul class="menu">
+<li><a accesskey="1" href="#CueCat">CueCat</a>
</ul>
+<div class="node">
+<a name="CueCat"></a>
<p><hr>
-Node:<a name="CueCat">CueCat</a>,
-Previous:<a rel=previous href="#Drivers">Drivers</a>,
-Up:<a rel=up href="#Drivers">Drivers</a>
-<br>
+Previous: <a rel="previous" accesskey="p" href="#Drivers">Drivers</a>,
+Up: <a rel="up" accesskey="u" href="#Drivers">Drivers</a>
-<h2>CueCat</h2>
+</div>
+
+<!-- node-name, next, previous, up -->
+<h3 class="section">11.1 CueCat</h3>
<p>Michael Rothwell <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
-<p><<code>http://www.flyingbuttmonkeys.com/foocat/</code>>
+ <p><a
href="http://www.flyingbuttmonkeys.com/foocat/";>http://www.flyingbuttmonkeys.com/foocat/</a>
-<p>I've recieved two letters from the law firm representing Digital
+ <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 <<code>delphion.com</code>>). They've
written a
+patents (search for NeoMedia on <a href="delphion.com">delphion.com</a>).
They've written a
LOT of these letters, and most people folded.
-</blockquote>
+ </blockquote>
+<div class="node">
+<a name="Communication-Protocols"></a>
<p><hr>
-Node:<a name="Communication%20Protocols">Communication Protocols</a>,
-Previous:<a rel=previous href="#Drivers">Drivers</a>,
-Up:<a rel=up href="#Top">Top</a>
-<br>
+Previous: <a rel="previous" accesskey="p" href="#Drivers">Drivers</a>,
+Up: <a rel="up" accesskey="u" href="#Top">Top</a>
+
+</div>
-<h1>Communication Protocols</h1>
+<!-- node-name, next, previous, up -->
+<h2 class="chapter">12 Communication Protocols</h2>
-<ul>
-<li><a href="#WAP">WAP</a>:
+<ul class="menu">
+<li><a accesskey="1" href="#WAP">WAP</a>
</ul>
+<div class="node">
+<a name="WAP"></a>
<p><hr>
-Node:<a name="WAP">WAP</a>,
-Previous:<a rel=previous href="#Communication%20Protocols">Communication
Protocols</a>,
-Up:<a rel=up href="#Communication%20Protocols">Communication Protocols</a>
-<br>
+Previous: <a rel="previous" accesskey="p"
href="#Communication-Protocols">Communication Protocols</a>,
+Up: <a rel="up" accesskey="u"
href="#Communication-Protocols">Communication Protocols</a>
-<h2>WAP</h2>
+</div>
+
+<!-- node-name, next, previous, up -->
+<h3 class="section">12.1 WAP</h3>
<p>Richard M. Stallman <a href="mailto:address@hidden";>address@hidden</a>
-<blockquote>
+ <blockquote>
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
@@ -1377,10 +1543,11 @@
protocols are patented, it will be impossible to write free software
to set up those servers.
-<p>You can get more information from the Free Protocols Foundation.
+ <p>You can get more information from the Free Protocols Foundation.
-<p><<code>http://www.freeprotocols.org</code>>
+ <p><a href="http://www.freeprotocols.org";>http://www.freeprotocols.org</a>
-</blockquote>
+ </blockquote>
</body></html>
+
Index: patent-examples.texi
===================================================================
RCS file: /web/www/www/patent-examp/patent-examples.texi,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- patent-examples.texi 1 Mar 2001 07:20:17 -0000 1.4
+++ patent-examples.texi 10 Apr 2010 18:12:00 -0000 1.5
@@ -1,7 +1,7 @@
\input texinfo @c -*-texinfo-*-
@setfilename patent-examples.info
-
address@hidden Software patents that hurt free software
@node Top, Original Announcement, (dir), (dir)
@comment node-name, next, previous, up
@@ -91,7 +91,7 @@
@comment node-name, next, previous, up
@chapter Original Announcement
-Richard Stallman <rms@@gnu.org>
+Richard Stallman <patent-examples@@gnu.org>
Date: Mon, 11 Dec 2000 10:00:08 -0700 (MST)
@@ -123,7 +123,7 @@
leads for getting more details may be useful.
Please send your information to @email{patent-examples@@gnu.org} rather
-than to me personally, so that we can collect the responses efficiency.
+than to me personally, so that we can collect the responses efficiently.
@end quotation
@node Audio/Video, Graphics, Original Announcement, Top
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/patent-examp index.html patent-examples.htm...,
Karl Berry <=