Читаем Free Software, Free Society: selected essays of Richard M. Stallman. 2nd edition. полностью

These are fairly lightweight cases: one patent on jpeg, two patents on the LZW algorithm used in gif. Now you might wonder how come there are two patents on the same algorithm? It’s not supposed to happen, but it did. And the reason is that the patent examiners can’t possibly take the time to study every pair of things they might need to study and compare, because they’re not allowed to take that much time. And because algorithms are just mathematics, there’s no way you can narrow down which applications and patents you need to compare.

You see, in physical engineering fields, they can use the physical nature of what’s going on to narrow things down. For instance, in chemical engineering, they can say, “What are the substances going in? What are the substances coming out?” If two different [patent] applications are different in that way, then they’re not the same process so you don’t need to worry. But the same math can be represented in ways that can look very different, and until you study them both together, you don’t realize they’re talking about the same thing. And, because of this, it’s quite common to see the same thing get patented multiple times [in software].

Remember that program that was killed by a patent before we released it? Well, that algorithm got patented twice also. In one little field we’ve seen it happen in two cases that we ran into—the same algorithm being patented twice. Well, I think my explanation tells you why that happens.

But one or two patents is a lightweight case. What about mpeg2, the video format? I saw a list of over 70 patents covering that, and the negotiations to arrange a way for somebody to license all those patents took longer than developing the standard itself. The jpeg committee wanted to develop a follow-on standard, and they gave up. They said there were too many patents; there was no way to do it.

Sometimes it’s a feature that’s patented, and the only way to avoid that patent is not to implement that feature. For instance, the users of the word processor Xywrite once got a downgrade in the mail, which removed a feature. The feature was that you could define a list of abbreviations. For instance, if you define “exp” as an abbreviation for “experiment,” then if you type “exp-space” or “exp-comma,” the “exp” would change automatically to “experiment.”

Then somebody who had a patent on this feature threatened them, and they concluded that the only thing they could do was to take the feature out. And so they sent all the users a downgrade.

But they also contacted me, because my Emacs editor had a feature like that starting from the late 70s. And it was described in the Emacs manual, so they thought I might be able to help them invalidate that patent. Well, I’m happy to know I’ve had at least one patentable idea in my life, but I’m unhappy that someone else patented it.

Fortunately, in fact, that patent was eventually invalidated, and partly on the strength of the fact that I had published using it earlier. But in the meantime they had had to remove this feature.

Now, to remove one or two features may not be a disaster. But when you have to remove 50 features, you could do it, but people are likely to say, “This program’s no good; it’s missing all the features I want.” So it may not be a solution. And sometimes a patent is so broad that it wipes out an entire field, like the patent on public-key encryption, which in fact put public-key encryption basically off limits for about ten years.

So that’s the option of avoiding the patent—often possible, but sometimes not, and there’s a limit to how many patents you can avoid.

What about the next possibility, of getting a license for the patent?

Well, the patent holder may not offer you a license. It’s entirely up to him. He could say, “I just want to shut you down.” I once got a letter from somebody whose family business was making casino games, which were of course computerized, and he had been threatened by a patent holder who wanted to make his business shut down. He sent me the patent. Claim 1 was something like “a network with a multiplicity of computers, in which each computer supports a multiplicity of games, and allows a multiplicity of game sessions at the same time.”

Now, I’m sure in the 1980s there was a university that set up a room with a network of workstations, and each workstation had some kind of windowing facility. All they had to do was to install multiple games and it would be possible to display multiple game sessions at once. This is so trivial and uninteresting that nobody would have bothered to publish an article about doing it. No one would have been interested in publishing an article about doing it, but it was worth patenting it. If it had occurred to you that you could get a monopoly on this trivial thing, then you could shut down your competitors with it.

But why does the Patent Office issue so many patents that seem absurd and trivial to us?

Перейти на страницу:

Похожие книги

Африканский дневник
Африканский дневник

«Цель этой книги дать несколько картинок из жизни и быта огромного африканского континента, которого жизнь я подслушивал из всего двух-трех пунктов; и, как мне кажется, – все же подслушал я кое-что. Пребывание в тихой арабской деревне, в Радесе мне было огромнейшим откровением, расширяющим горизонты; отсюда я мысленно путешествовал в недра Африки, в глубь столетий, слагавших ее современную жизнь; эту жизнь мы уже чувствуем, тысячи нитей связуют нас с Африкой. Будучи в 1911 году с женою в Тунисии и Египте, все время мы посвящали уразуменью картин, встававших перед нами; и, собственно говоря, эта книга не может быть названа «Путевыми заметками». Это – скорее «Африканский дневник». Вместе с тем эта книга естественно связана с другой моей книгою, изданной в России под названием «Офейра» и изданной в Берлине под названием «Путевые заметки». И тем не менее эта книга самостоятельна: тему «Африка» берет она шире, нежели «Путевые заметки». Как таковую самостоятельную книгу я предлагаю ее вниманию читателя…»

Андрей Белый , Николай Степанович Гумилев

Публицистика / Классическая проза ХX века
Кто и как развалил СССР. Хроника крупнейшей геополитической катастрофы ХХ века
Кто и как развалил СССР. Хроника крупнейшей геополитической катастрофы ХХ века

В этой книге рассказано о цепочке событий, которые привели к одной из величайших геополитических трагедий XX века – распаду СССР.В ней вы не найдете эффектных эпизодов – погонь, стрельбы, трюков, обворожительных красавиц и мужественных суперагентов. Все происходило, на первый взгляд, обыденно: собрались, обсудили, не договорились. Собрались, проголосовали, нарушили Конституцию. И, так далее… А в результате – катастрофа. Страна разломилась по забытым, казалось бы, границам. Миллионы людей оказались за рубежами, стали изгоями – лицами без гражданства, иностранцами – в своей собственной стране.О чем думали политики, в руках которых в те годы находились судьбы страны? Переживали за будущее? Думали об ответственности перед законами и совестью? Просчитывали возможные экономические и политические последствия своих действий? Да ничего подобного! Распад Советского Союза явился побочным результатом азартной игры, где ставками были власть, собственность, президентские и правительственные посты и привилегии.В любой игре не бывает без проигравших: в данном случае в дураках остался народ, который шел за своими правителями и слепо верил им.Ну а как же «рука Запада»? Козни и интриги врагов России? Были? Были! Чего-чего, а врагов у России хватало всегда. О них тогда писали в газетах, говорили на открытых и закрытых совещаниях в Кремле. Однако власть, имевшая одну из самых мощных армий и спецслужб в мире, становилась удивительно беспомощной и слабой, когда речь заходила о сохранении единства собственной страны.

Владимир Борисович Исаков

Публицистика