--- Generator: 'texi2html 1.82' description: Untitled Document distribution: global keywords: Untitled Document resource-type: document title: Untitled Document ... 1. Giving the Software Field Protection from Patents {#giving-the-software-field-protection-frompatents .chapter} ==================================================== 保护软件领域免受专利困扰 ======================== @firstcopyingnotice{{ 另请参阅我的文章 “Patent Reform Is Not Enough,”,位于 . @medskip @footnoterule @smallskip 著作权所有 (C) 2012, 2013 自由软件基金会,本文的一个版本最初以标题 “Let’s Limit the Effect of Software Patents, Since We Can’t Eliminate Them” 发表于 Wired 网站 (Wired, 1 November 2012, )。该版本于 2012 年发表于 in 2012. 此版本是 @fsfsthreecite 的一部分。} Patents threaten every software developer, and the patent wars we have long feared have broken out. Software developers and software users—which, in our society, is most people—need software to be free of patents. 专利会对每位软件开发者构成威胁,我们长久以来一直担忧的专利之争终于打响了。软件开发者和软件用户——我们社会中的大多数人——需要保证软件不受专利困扰。 The patents that threaten us are often called “software patents,” but that term is misleading. Such patents are not about any specific program. Rather, each patent describes some practical idea, and says that anyone carrying out the idea can be sued. So it is clearer to call them “computational idea patents.” 对我们构成威胁的那一类专利通常称为“软件专利”,但这个短语是带有误导性的。这些专利并非针对任何具体的程序。与之相反,每一项专利描述了某种实践上的想法和创意,并且宣称任何人试图实施这样的思想将会被起诉。因此,将它们称为“计算思想专利”更清楚。 The US patent system doesn’t label patents to say this one’s a “software patent” and that one isn’t. Software developers are the ones who make a distinction between the patents that threaten us—those that cover ideas that can be implemented in software—and the rest. For example, if the patented idea is the shape of a physical structure or a chemical reaction, no program can implement that idea; that patent doesn’t threaten the software field. But if the idea that’s patented is a computation, that patent’s barrel points at software developers and users. 美国专利体系并不会为每一项专利贴标签,称这项专利属于软件专利而那项不属于。事实上,是由软件开发者来为我们区分那些将会对我们构成威胁的——那些覆盖了可能在软件开发过程中实施的想法的专利——以及其他的专利。例如,如果一项专利所保护的想法是关于一种物理结构或者一种化学反应的,没有程序可以实现那种想法;这样的专利并不对软件领域构成威胁。但如果一项专利所保护的想法是一种计算过程,那么该专利的炮筒是对准软件开发者和用户的。 This is not to say that computational idea patents prohibit only software. These ideas can also be implemented in hardware—and many of them have been. Each patent typically covers both hardware *and* software implementations of the idea. 这并不意味着那些计算思想专利仅仅会禁止软件。这些想法也会被实施在硬件中——并且它们中的很多已经被实施在硬件中。每项专利通常同时覆盖关于某种想法的硬件和软件实现。 ### The Special Problem of Software {#the-special-problem-of-software .subheading} ### 关于软件的特别问题 Still, software is where computational idea patents cause a special problem. In software, it’s easy to implement thousands of ideas together in one program. If 10 percent are patented, that means hundreds of patents threaten it. 时至今日,软件领域仍然是计算思想专利会造成特别的问题的地方。在软件领域,在一个程序中实施数千种想法是很平常的。如果它们中的 10% 受到专利保护,这意味着该程序受到数百项专利的威胁。 When Dan Ravicher of the Public Patent Foundation studied one large program (Linux, which is the kernel of the GNU/Linux operating system) in 2004, he found 283 US patents that appeared to cover computing ideas implemented in the source code of that program. That same year, a magazine estimated that Linux was .25 percent of the whole GNU/Linux system. Multiplying 300 by 400 we get the order-of-magnitude estimate that the system as a whole was *threatened by around 100,000 patents.* 当供职于公共专利基金会(PUBPAT)的 Dan Ravicher 于 2004 年对一款大型软件(Linux,即 GNU/Linux 操作系统的内核)进行研究时,发现了 283 项美国专利可能覆盖了该程序中实施的计算思想。同年,一家杂志预计 Linux 约占整个 GNU/Linux 操作系统的 0.25%。将 300 乘以 400,我们可以得到这样的数量级估计,即该系统作为一个整体正在受到约 10 万项软件专利的威胁。 If half of those patents were eliminated as “bad quality”—mistakes of the patent system, that is—it would not really change things. Whether 100,000 patents or 50,000, it’s the same disaster. This is why it’s a mistake to limit our criticism of software patents to just “patent trolls” or “bad quality” patents. The worst patent aggressor today is Apple, which isn’t a “troll” by the usual definition; I don’t know whether Apple’s patents are “good quality,” but the better the patent’s “quality” the more dangerous its threat. 如果那么多的专利中的半数由于“品质不良”——即由于专利系统本身的问题——而被判无效,这并不能真正带来改观。不论是 10 万项专利还是 5 万项专利,都是同样的灾难。这是为什么不应该将我们对于软件专利的批评局限于“专利流氓”或“劣质专利”的层面的原因。当今最坏的专利侵略者是苹果,它不仅仅是通常意义上的“专利流氓”;我不清楚苹果的专利是否属于“优质”,但是那些专利的“质量”越好,其所带来的威胁就越大。 We need to fix the whole problem, not just part of it. 我们需要解决全部的问题,而非部分。 The usual suggestions for correcting this problem legislatively involve changing the criteria for granting patents—for instance, to ban issuance of patents on computational practices and systems to perform them. This approach has two drawbacks. 关于解决这一问题的常见建议包括在立法层面修改专利授予的评价尺度——例如,禁止对计算实践以及实现它们的系统进行专利保护。这种方式有两个明显的缺陷。 First, patent lawyers are clever at reformulating patents to fit whatever rules may apply; they transform any attempt at limiting the substance of patents into a requirement of mere form. For instance, many US computational idea patents describe a system including an arithmetic unit, an instruction sequencer, a memory, plus controls to carry out a particular computation. This is a peculiar way of describing a computer running a program that does a certain computation; it was designed to make the patent application satisfy criteria that the US patent system was believed for a time to require. 其一,专利律师精于将专利换一种方式表达,使其能够适合任何规则;他们将任何旨在限制专利实质的尝试化解为仅仅是形式上的要求。例如,美国的很多计算思想专利描述了这样一种系统,它包括一个算术单元、一个指令排序器、一块内存、加上用于执行特定计算过程的控制器。这是对于一台计算机运行一个程序以进行某种计算的一种古怪描述;它是被设计用于使专利申请满足那些美国专利体系在一段时间内要求满足的评估标准的。 Second, the US already has many thousands of computational idea patents, and changing the criteria to prevent issuing more would not get rid of the existing ones. We would have to wait almost 20 years for the problem to be entirely corrected through the expiration of these patents. We could envision legislating the abolition of these existing patents, but that is probably unconstitutional. (The Supreme Court has perversely insisted that Congress can extend private privileges at the expense of the public’s rights but that it can’t go in the other direction.) 其二,美国已经有了数千项计算思想专利,更改评估标准以阻止批准更多的专利并不能帮助我们摆脱已有的那些。我们不得不等上将近 20 年,才能等到这一问题随着那些已有专利过期而彻底解决。我们可以展望立法废除那些现存的专利,但这很可能是不符合宪法的。(美国最高法院不顾一切地坚持要求国会有权以牺牲公共权利为代价扩展私人特权,而不是相反。) ### A Different Approach: Limit Effect, Not Patentability {#a-different-approach-limit-effect-not-patentability .subheading} ### 另一种方式:限制专利的效果,而非专利的可获得性 My suggestion is to change the *effect* of patents. We should legislate that developing, distributing, or running a program on generally used computing hardware does not constitute patent infringement. This approach has several advantages: 我的建议是改变专利的效果。我们应当立法规定,在通用计算硬件上开发、发布、运行程序并不构成专利侵犯。这样有几个好处: - It does not require classifying patents or patent applications as “software” or “not software.” - 不再需要区分专利或者专利申请到底属于“软件专利”还是“非软件专利”; - It provides developers and users with protection from both existing and potential future computational idea patents. - 可以对开发者和用户提供保护,不论对于现存的还是将来潜在的计算思想专利; - Patent lawyers cannot defeat the intended effect by writing applications differently. - 专利律师不能再通过以其他方式编写专利申请来消除这种有意而为的效果。 This approach doesn’t entirely invalidate existing computational idea patents, because they would continue to apply to implementations using special-purpose hardware. This is an advantage because it eliminates an argument against the legal validity of the plan. The US passed a law some years ago shielding surgeons from patent lawsuits, so that even if surgical procedures are patented, surgeons are safe. That provides a precedent for this solution. 这种方式并不会使现存的计算思想专利完全失效,因为它们仍然可以被应用于基于使用特殊用途的硬件的实现。这是一种好处,由于它打消了有关这一计划的合法性的争论。几年之前,美国曾经通过一项法律,保护外科医生不受专利起诉,因此即使一些外科手术流程受专利保护,外科医生仍然是安全的。这样的实践为这种解决方案提供了先例。 Software developers and software users need protection from patents. This is the only legislative solution that would provide full protection for all. We could then go back to competing or cooperating…without the fear that some stranger will wipe away our work. 软件开发者和软件用户需要得到对于专利威胁的保护。这是唯一能够提供对所有人的全面保护的法律解决方案。然后我们可以重新回到竞争或合作……并且无需担心某些陌生人会抹除我们的工作成果。 ------------------------------------------------------------------------ This document was generated by *tonghuix* on *March 25, 2016* using [*texi2html 1.82*](http://www.nongnu.org/texi2html/).\