Patent search - Intellectual property
Intellectual Property strategies
Software intellectual property is an issue for everybody involved in using or producing software. However, so far, only large firms with legal departments paid the needed attention to this issue. Smaller companies tend to see software patents as an unnecessary burden; refuse to spend time on Intellectual Property issues and when they realize that there is a danger at doing so lobby to ban software patents. We believe that it is a short-minded view for the following reasons:
In this section we focus on smaller companies. Large firms develop sensible patenting strategies with the help of lawyers and consultants. They need more data than we can possibly present here. However this section may also be useful for people who work in these large firms on a business uncovered by the patent strategy and understand that ignoring Intellectual Property for any activity of the large firm is a suicidal negligence.
A company has three ways to protect its intellectual property:
Secrecy is the default Intellectual Property policy. If nothing is done programs, documentation, ideas remain hidden in the hard disks of programmers and sometimes in the company repositories. Default secrecy is free but has several drawbacks:
To address the first issue the management may ask for additional reporting and for a software inventory. To address the second issue the company may put in place a document management system (DMS), forums and mailing lists with search means and build an Internet-like internal system. This system may be expensive to set up and operate and is usually ineffective for the following reasons:
To address the third issue companies can deposit their program sources and documentation in escrow.
Escrow serves three functions:
With escrow a trusted third party can assert that the company owned sources, documentation and implied processes and methods at a given date. Because the company did not publish its processes or methods someone else can patent it. The patentee cannot ask for patent fees if the company can prove that it owned the invention before the filing date. However because it has no knowledge of the owned process or method, the patentee cannot find that the company had possession of the invention and invisibly abandon legal actions against the company. Therefore the company must address the patentee action, usually hire a lawyer and often go to court. Remember that the plaintiff complains to the richest party. If the company is a small software publisher that sells to large firms the plaintiff may choose to sue the largest customers. Therefore the company may suffer from the dispute even it is able to present convincing evidences of its ownership. Some Internet documents suggest that prior possession is not necessarily considered in all countries and that a company must either patent or make public in some places.
Escrow service is relatively inexpensive. You can find many escrows on Google with the keywords "software", "deposit" and "escrow".
A common attitude is program fetishism. Program fetishists put only sources in escrow and consider that the major risk that they face is disgruntled employees that steal programs.
A company must put in escrow:
Secrecy is what you get when you do nothing and is cheap. Secrecy is convenient to hide little secrets like "borrowed" and plagiarized code and poorly written and tested programs. More important secrecy does not help a company to assess its strengths and weaknesses and maximizes its exposure to patent infringement liability.
To patent you need competent resources or help. Patenting is not an option if
If your company has a patent portfolio strategy you can patent almost everything novel and inventive and you should turn your attention at filing good quality patents in cooperation with your lawyers.
Otherwise consider that patenting like programming is a job with a sharp experience curve. Your first patent will cost you more than the second and so forth. Therefore filing a first patent is a strategic decision. For this decision to be profitable you need to file other patents and to dedicate a significant part of your resources to patenting. When we analyzed 5,838,906 we found that the assignee, a small company called Eolas owned at least seven patents and that 5,838,906 was indeed the second Eolas patent.
You must be honest about your position on the market. If you are a me-too company you probably should not patent. You need to be a technological leader that (1) by chance had to implement something substantially different of what already exists (2) has good chances to have again to implement novel processes or methods because you will need to file subsequent patents. Even if your invention is really novel, non obvious and useful the software industry can follow a different path and ignore your patent. Patenting is a risky business.
Eventually you have to go fast. We have seen that browser controls and plug-ins would have invented anyway between 1994 and 1995. This is not unique to software inventions. Without Bell and Edison the telephone and the electric bulb would have been invented anyway when they were invented. At a given time the technology is mature and different teams work independently on the same idea. You must quickly and thoroughly assess the novelty and the potential of the invention, write a patent draft, explain the invention to lawyers, check their rewording. It does not finish when the application is filed. The examiner can require changes and even reject the application. This is not easy in a small company. Filing a patent is urgent but to the opposite of product deadlines there is nobody to remind you that it is urgent.
Here is an introduction to patent writing. This explanation is useful even if you do not plan to file a patent. Before starting a new project you should look for possible infringement. For this search as we have seen in the toolkit section the best is to create a reference text that looks like a patent and to use this text to find patents with the same word frequencies. This work complements a design. It points out the differences between your design and existing products and lists the problems that you were trying to solve. You should refine your product definition according to your finding in prior art:
We may have to iterate the product definition, the design, the patent writing and the prior art search. The design answers the feasibility question and the patent search the legal question. For prior art search you do not need to write a full patent. You may focus on background, prior art and summary.
According to the USPTO guidelines a patent is made of three sections:
The reference guide for writing a patent is the Manual of Patent Examining Procedure (MPEP). Read in particular the Chapter 2100 Patentability.
We found this useful definition:
"A patent abstract is a concise statement of the technical disclosure of the patent and should include that which is new in the art to which the invention pertains. If the patent is of basic nature, the entire technical disclosure may be new in the art and the abstract should be directed to the entire disclosure. If the patent is in the nature of an improvement in an old apparatus, process, product or composition, the abstract should include the technical disclosure of the improvement. [...] If the new disclosure involves modifications or alternatives, the abstract should mention by way of example the preferred modification or alternative.
The abstract should not refer to purported merits or speculative applications of the invention and should not compare the invention with the prior art.
Where applicable, the abstract should include the following:
The function of claims is explained in 35 USC 112: "The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention."
Here is an example of claim:
"A computer-implemented method of searching for an item in a plurality of independently operated electronic auctions interconnected by a computer network, each electronic auction having an associated data repository, the method comprising:
It has a preamble and a number of elements (words or phrases) that describe the claim limitations. There is infringement when another party use a system with each and every limitation of a claim. So the inventor must include the absolute minimal set of elements that differentiate a new invention over what came before. If US patents contain many claims this is to maximize the chances to get a match. When a claim contains many limitations this is usually because the examiner rejected the first version of the claim for lack of novelty (it was anticipated by prior art) or obviousness and because the applicant had to add additional limitations to get a patent.
This claim has a function, which is to search "an item in a plurality of independently operated electronic auctions interconnected by a computer network" and two steps:
Such claims are called means or steps plus function claims. They are so important that 35 USC 112 describes them: "An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof."
So the precise scope of such claims is determined by the claim and by the description. There was a trial for infringement of the patent that contains the claim above. The court determined the meaning of words like item and also whether the steps recited a sequence. To learn more about this case you may look at the Business method page. For details about the construction of means plus function claims you may look at http://www.uspto.gov/go/og/con/files/cons089.htm and http://jip.kentlaw.edu/nart/2004/A-2.htm.
As implicitly stated by 35 USC 112 a claim may also recite structure, material, or acts. In this case the claim loses its function limitation. A claim for a popcorn dispenser was rejected because the claimed structure was the same as the structure of an oil can.
The description is made of:
When you write your first patent document the most important problems you face is that you do not have the right mindset and you were not prepared to describe your work in such terms. A patent is neither a marketing nor a analysis document. Use the same sentence structure and the same verbs as in IBM patents (on the USPTO advanced search an/IBM). Check that you do not use words like innovative, powerful, successful, synergy, strategy and project. Do not use the word product outside the background and the prior art section.
If patenting is not an option you can make your invention public. Your competitors will be able to use it but not to patent it because a public process or method is prior art. This can actually help in your business. Software patents are repellent to competitors and if you are the only company doing things in one way your product will not sell. If you made your invention public competitors will use it and because you have some advance you should increase your market shares.
As we have seen in the 5,838,906 case a public mailing list whose readers are concerned by the invention matter is sufficient because "An electronic publication, including an on-line database or Internet publication, is considered to be a 'printed publication' within the meaning of 35 U.S.C. 102(a) and (b) provided the publication was accessible to persons concerned with the art to which the document relates." A mail is probably the cheapest and fastest way to make public an invention.
On the other hand the court of MercExchange v. eBay found that a newsgroup posting does not have the status of a printed publication. It gave two reasons:
So to make public an invention we recommend to not use newsgroups and forums whose read access is password protected.
According to most national laws a mailing list can be in a country and a language different of the court country and language. However, to be on the safe side, make your disclosures in English.
Article and presentation
There are two other solutions that you can combine with mails to mailing lists:
Both solutions produce prior art of premium quality but they have a common drawback, which is to take time. You usually submit a proposal either to the publisher or to the organization. Your proposal may be approved with some amendments one month later. Then you send your article or presentation. Next the publisher or organization has to find a slot for you in its next issues or meetings. In case of newspaper article or presentation it takes between four and six months. Electronic publication is faster. According to most national laws the article can be written or the presentation given in a country and language different of the court country and language. However, to be on the safe side, make your disclosures in English.
A publication on your Web site is usually not considered as an Internet publication because you cannot prove the last modification date of your publication. There are however a couple of cases worth to consider:
A popular and content-rich web site is not only a contribution to Internet knowledge and a way to attract programmers. It can also limit your exposure to patent lawsuits.
Some companies offer a technical disclosure service, typically on Internet. An example is http://www.ip.com. For a single publication the price is $155 (November 2003). This kind of service is interesting because you do not have the travel and membership fee associated to a presentation and you do not need the writing skills needed for an article. You can just publish a cleaned up version of a design document.
The most radical solution is to release your core code with an Open Source or free (GPL) license.
The best location for this is probably SourceForge because this site is well known of persons concerned with most computer arts. Two key points are:
SourceForge registration and hosting are free.
According to the OSI definition an Open Source license must conform to the following rules:
The OSI definition comes actually from Debian. Debian is a Linux distribution and the authors of the license definition had in mind to give a definition enabling a business including:
This section aims to help you choosing a license. The two most important families of Open Source licenses are BSD-based licenses are GNU licenses.
The Berkeley University had developed a number of programs under this license that were used in institutions and industry. This license addresses three needs:
These needs were typical of 70’s and 80’s University needs. The following products have a BSD-based license:
Quite interestingly the BSD license is titled "Berkeley-based copyrights". The most important constraint of this license is that you have to advertise the contribution of the publisher. However there are even more user-friendly licenses like the ACE / TAO and the MIT license used with some changes by Expat. Use a BSD-based license when you want to facilitate the life of your users, for instance:
As far as Intellectual Property is concerned you do not need to use a BSD-based license and GNU licenses usually serve better your needs because they prevent users to derive non-free products from your code. We use free here because the father of GNU, Richard Stallman rejects the "Open Source" term and prefers the "free" word: "When we speak of free software, we are referring to freedom of use, not price." Note that in the rest of this document when we talk about Open Source we mean Open Source or free. The two most important GNU licenses are the GNU General Public license, GPL in short and the Lesser General Public License, LGPL in short. These licenses enforce the copyleft principle, which states that you must release a modified [L]GPL program with the same license as the original program. Things are however more complex because of derivative works.
First the difference between GPL and LGPL is that the LGPL license allows linking non-free programs to LGPL libraries whereas GPL doesn't allow it. Here is the rationale: "When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library." More precisely the LGPL permits to programs containing no derivative of any portion of the Library, but designed to work with the Library by being compiled or dynamically linked with it, to be a non-free product. An executable statically linked with the library contains the library and therefore should be released under a [L]GPL license but objects used to build the executable that don't contain portions of the library don't need to.
GNU license put no restriction on the program use. The GPL license says: "Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program)." The restriction on the output is clarified by the GNU FAQ: "If the user uses your program to enter or convert his own data, the copyright on the output belongs to him, not you. More generally, when a program translates its input into some other form, the copyright status of the output inherits that of the input it was generated from. So the only way you have a say in the use of the output is if substantial parts of the output are copied (more or less) from text in your program. For instance, part of the output of Bison (see above) would be covered by the GNU GPL, if we had not made an exception in this specific case."
GPL is the license of GCC and most Linux programs. LGPL is the license of the GCC library.
The GNU wrote a couple of documents of interest for choosing a license:
In some circumstances releasing your core code with an Open Source or free (GPL) license is a rational choice from an economical and legal point of view. When a new market emerges a patent and publication race starts. If you never patented and never published you have almost no chance to win. If you distribute your core product and documentation with an Open Source license starting with the alpha version you have a good chance to win the race even if you have less resources than your competitors. In that respect Open Source acts as publication. Your competitors will be able to use your invention but not to patent it because your implementation is prior art. Obviously your competitors can also use your implementation. This is not necessarily a bad thing:
Open Source has other strong points:
You still can sell a product that uses the Open Source part and contains other facilities like configuration and administration user interfaces. The differences between the core part and the whole product are the prerequisites. The core part requires an intimate knowledge of the product technology whereas the whole product can be administrated and used by almost anybody. While they do not usually contain a significant amount of Intellectual property the extra facilities are essential to the product success and frequently more expensive to implement that the core product.
There are other solutions:
You may read that Open Source and free software are untested in court and therefore unproven. As we have seen in the Patent issues section software Intellectual property will continue to evolve, especially regarding how much care must be taken by a company to get an enforceable patent. Furthermore this is only half the truth. From time to time free software goes to court. Before considering Open Source legal issues we must first briefly explain what Copyright and trademark are.
A copyright comes into effect immediately, as soon as something that can be protected is created and "fixed" in some way. A copyright is an unregistered right. In most country the copyright notice is not even necessary. Writing the copyright symbol (c) followed by the company or organization name, the date and "all rights reserved" warns others against copying the copyrighted stuff, which may strengthen your position in case of dispute.
There is no incompatibility between Open Source licenses and Copyright. You actually must claim to be the owner of your code to license it with an Open Source license.
You can find the Copyright law of USA at http://www.copyright.gov/title17/. Copyright law is covered by Trade-Related Aspects of Intellectual Property Rights (TRIPs) like patent law. Governments try to harmonize their Copyright law like their patent law.
A trademark is any sign that can distinguish the goods and services of one trader from those of another. For more information about trademark you can read our trademark page.
MySQL v. Progress
The case opposed MySQLAB (plaintiff) to the NuSphere subsidiary of Progress (defendant). The two companies had formed a "strategic" alliance. Here is an excerpt from the press release: "To create an open source business, Progress Software has formed NuSphere, a Progress Software Company, to distribute and support the NuSphere MySQL open source database. Progress Software will be providing up to $2.5 million (US) to help further the development of MySQL. NuSphere will extend the core development team's efforts by creating NuSphere MySQL; a multi-platform integrated distribution of MySQL and related open source products. NuSphere will provide commercial support, consulting, and training for customers deploying MySQL as part of their web infrastructure. As a single, global source of integrated services for MySQL, NuSphere will provide support from three main support centers in the U.S., the Netherlands and Australia. NuSphere chose to support MySQL because of its position as the market-leading open source database for web infrastructure. MySQL is especially well suited for capturing web site traffic, providing authentication and authorization services, and content personalization. The MySQL database is the first widely used database product released under the Free Software Foundation's General Public License (GPL)."
We understand that at some stage NuSphere released a database product called Gemini statically linked to MySQL's code without the accompanying source code. NuSphere did another thing that may have triggered the dispute. Though MySQL has a GPL license the original MySQL Web site was http://www.mysql.com. NuSphere opened a http://www.mysql.org Web site.
MySQL asked to a Boston court to issue a preliminary injunction to bar Progress, and its subsidiary NuSphere Corp., from using MySQL's trademarks in their products and from distributing any software that included MySQL's self-titled database program. MySQL alleged that Progress failed to include the source code for a software tool NuSphere built and included in its MySQL Advantage package, which included MySQL's database. GPL requires that any software built using components released under the GPL must also include the source code of the new application. Eben Moglen, General Counsel to the Free Software Foundation (FSF) testified as an expert witness. Here is his affidavit. Ed Kelly and John Palfrey reported the meeting to Tim O’Reilly: "Judge Saris was surprised at how many people were there to hear the arguments on a motion for a preliminary injunction barring use of the MySQL mark by NuSphere. She noted the almost religious zeal of the open-source community. She also noted that both parties came loaded for bear and that MYSQL had flown in David Axmark from Sweden [MySQL is a Swedish company] and both parties had expert witnesses prepared to testify."
Judge Sarris refused to allow arguments to expand beyond the trademark dispute. Though she did not issue any orders in court, Saris made clear that she intended to issue a preliminary injunction against NuSphere's use of the marks in question and that she was not going to issue a preliminary injunction in the more complicated matter of the use of the MySQL code and terms the GPL. She urged both parties to come to an out-of-court settlement. From our perspective the most important is her comments about the GPL license:
ComputerWire reported the story with different words and a different title: Judge blocks route to GPL legal test case.
Then Judge Saris issued a preliminary injunction. In the ruling she barred Progress and NuSphere from advertising or selling any products using the MySQL name and from registering or operating any Web sites that include the MySQL name. The ruling did allow Progress to state that its products interoperate with MySQL. Saris, however, declined to rule on the GPL issue, stating that MySQL had not shown a likelihood of success in the matter or irreparable harm, two prerequisites for the issuance of a preliminary injunction. MySQL seems to have the better argument in the matter, Saris wrote, but said that the release of source code by Progress in July 2001 may have solved the problem. Because of MySQL's central place in NuSphere's product line, barring the company from using the software could substantially hurt NuSphere, she said.
Eventually MySql and NuSphere concluded a settlement on November 7, 2002. We read the settlement that way: "The settlement resolves all outstanding issues between the two companies including [...] assignment to MySQL AB of copyrights for all NuSphere contributions to the MySQL program", which means that (1) the GPL license was extended to NuSphere contributions (2) the copyright of NuSphere contributions was transferred to MySQL AB. Again ComputerWire reported the settlement is a different way in MySQL, NuSphere Settle GPL Contract Dispute.
This case shows that:
SCO v. IBM
SCO filed a suit against IBM in the district court of Salt Lake City through its Caldera subsidiary. SCO wrote: "IBM has breached its own obligations to SCO [the Unix owner], induced and encouraged others to breach their obligations to SCO, interfered with SCO’s business, and engaged in unfair competition with SCO, including by misusing and misappropriating SCO’s proprietary software, incorporating (and inducing, encouraging, and enabling others to incorporate) SCO’s proprietary software into open source software offerings and incorporating (and inducing, encouraging, and enabling others to incorporate) SCO’s proprietary software into open source software offerings.
The proprietary code SCO is talking about is primarily UNIX and the Open Source software SCO is talking about is primarily Linux. SCO, summarizes the UNIX story: "AT&T Technologies originally licensed the UNIX operating system software code to approximately 30,000 software licensees, including defendant IBM, for the UNIX operating system software source code, object code and related schematics, documentation and derivative works (collectively, the UNIX Software Code). To protect the confidential and proprietary source code information, these license agreements, as detailed below, contained strict limitations on use and dissemination of UNIX Software Code. When SCO acquired the UNIX assets from Novell in 1995, it acquired rights in and to all (1) underlying, original UNIX software code developed by AT&T Bell Laboratories, including all claims against any parties relating to any right, property or asset used in the business of developing UNIX and UnixWare; (2) the sale of binary and source code licenses to various versions of UNIX and UnixWare; (3) the support of such products and (4) the sale of other products that are directly related to UNIX and UnixWare."
SCO explained the IBM strategy in this way: "In the process of moving from product offerings to services offerings, IBM dramatically increased its staff of systems integrators to 120,000 strong under the marketing brand IBM Global Services. [...] IBM sought to move the corporate enterprise computing market to a services model based on free software on Intel processors. By undermining and destroying the entire marketplace value of UNIX in the enterprise market, IBM would gain even greater advantage over all its competitors whose revenue model was based on licensing of software rather than sale of services. To accomplish the end of transforming the enterprise software market to a services-driven market, IBM set about to deliberately and improperly destroy the economic value of UNIX and particularly the economic value of UNIX on Intel-based processors."
About Linux SCO wrote: "Prior to IBM involvement, Linux was the software equivalent of a bicycle. UNIX was the software equivalent of a luxury car. To make Linux of necessary quality for use by enterprise customers, it must be re-designed so that Linux also becomes the software equivalent of a luxury car. This re-design is not technologically feasible or even possible at the enterprise level without (1) a high degree of design coordination, (2) access to expensive and sophisticated design and testing equipment; (3) access to UNIX code, methods and concepts; (4) UNIX architectural experience; and (5) a very significant financial investment."
SCO explained: "This case is not about the debate about the relative merits of proprietary versus open source software. Nor is this case about IBM right to develop and promote open source software if it decides to do so in furtherance of its independent business objectives, so long as it does so without SCO proprietary information."
You can find the reaction of the OSI. A technician may also disagree: SCO, the second-hand buyer of UNIX, did not significantly enhance UNIX. Why investing on something that does not make money? Actually ATT and Novell sold UNIX for the same reason. In early 90’s ATT had a successful Operating System but they did not find the way to convert this technical success into money. Therefore Unix licensees had to substantially invest to port and optimize UNIX performance on their hardware and to support their devices. IBM did this effort twice, one for AIX with the UNIX code, one for Linux with Linux code. A technician would not understand either how a company that releases a Linux distribution (Caldera) can find that Linux contains proprietary code.
So far this story was just another example of weak to strong action in Intellectual Property. However on October 24, 2003 in an answer to IBM SCO wrote: "The GPL violates the US Constitution together with copyright, antitrust and export control laws" (eighth affirmative defense). An article of LinuxWorld reports this news.
Before this answer Darl Mc Bride, the CEO of SCO wrote an open letter to the open source community: "In copyright law, ownership cannot be transferred without express, written authority of a copyright holder. Some have claimed that, because SCO software code was present in software distributed under the GPL, SCO has forfeited its rights to this code. Not so – SCO never gave permission, or granted rights, for this to happen. Transfer of copyright ownership without express written authority of all proper parties is null and void. Use of derivative rights in copyrighted material is defined by the scope of a license grant. An authorized derivative work may not be used beyond the scope of a license grant. License grants regarding derivative works vary from license to license – some are broad and some are narrow. In other words, the license itself defines the scope of permissive use, and licensees agree to be bound by that definition."
This letter triggered the comment from Grocklaw, another SCO group company: "You have continued to distribute the Linux kernel, despite alleging that it contains infringing source code. Simultaneously, you are attempting to compel purchase of "Linux Intellectual Property" licenses for binary-only use, the terms of which are incompatible with freedoms granted under the GPL. According to the GPL, any violation of its license terms automatically and immediately terminates your permission to modify or distribute the software or derivative works. Note the wording of the GPL:
4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.
Releasing software under the GPL is not the same as releasing it into the public domain. Authors retain their copyrights to software licensed under the GPL. Even when authors assign their copyrights to someone else, such as to the Free Software Foundation, the copyrights remain valid, but with the new owner. Therefore, subsequent to termination of your permissions under the GPL, you are in the unhappy position of violating the copyrights of the software authors, if you continue to distribute their software. Under copyright law, you are not allowed to distribute at all without their permission -- and they have chosen to grant that permission only by means of the GPL."
In its answer to IBM SCO does not give details about its assertion that GPL infringes the Copyright law. LinuxWorld believes that the argument is that under the GPL, mere human beings - American citizens - arrogate to themselves the right to give permission to copy, modify, or redistribute intellectual property, while that kind of regulation of copyright, according to SCO's contention, can and must only be done - per Article 1 Section 8 of the US copyright law - by Congress itself. This explanation is consistent with the open letter of Darl Mc Bride.
The US copyright law (circular 92) says: "unless authorized by the owner of copyright in a computer program any person in possession of a particular copy of a computer program may, for the purposes of direct or indirect commercial advantage, dispose of, or authorize the disposal of that computer program by rental, lease, or lending, or by any other act or practice in the nature of rental, lease, or lending" and "Any exact copies prepared in accordance with the provisions of this section may be leased, sold, or otherwise transferred, along with the copy from which such copies were prepared, only as part of the lease, sale, or other transfer of all rights in the program. Adaptations so prepared may be transferred only with the authorization of the copyright owner." Our understanding is that authorizations granted by the GPL license are well described in the Copyright law and that the issue rose by SCO is whether implicit authorization is legal or not. From our point this is legal because, for instance, opening a CDROM seal is already considered as an implicit approval of license terms. However we think that this is time to clarify this issue in a judgement.
Intellectual Property tasks
We have seen above that Intellectual Property can no longer be ignored. We may also add that this is no longer only the job of specialists. In that respect Intellectual Property follows the evolution of the Society. Since the beginning of the 60’s people are massively educated. Up to the 80’s computers were black boxes operated by aliens talking a language that nobody else understood. Now the whole workforce has a coarse understanding on computer matters and everyone talk the computing jargon. We wrote Air transport because we wanted to illustrate the close integration of all parties involved in providing a service, companies of different size and government agencies, which is, we believe, one of the deepest changes in the Society and because we were asked to. Now people also understand what revenue management and landing slots are. We see that not-so-easy-to-understand concepts of the Air Transport and of the banking system are commonly understood. Intellectual property will become a part of our common culture. Now managers understand that in the next decade they will spend a third of their time on Intellectual property issues. In this section we explain how this time should be spent:
Intellectual Property out
A company or organization communicates with the rest of the world and therefore constantly discloses information about its technical choices, methods and processes through mails, messages posted on public forums, Web sites, press releases, presentations, documentation, trainings, RFP, products and patents. Employees of large firms frequently get more and better data about their company on Internet than using the firm internal communication systems. This is not always a drawback. The real issue is that Murphy’s Law also applies here: things that you would like to keep hidden quickly spread whereas things that you would like to spread are unnoticed.
Our experience is that mails and messages are less important:
Very early in a project a company should take a final decision about its Intellectual Property policy regarding this project:
Procrastination is not an option because the date when a publication was made or a patent was filed determines who legally invented a process or method. When you take your time to decide you have to keep your innovations secret during the while to keep the choice open. If you opt for publication or for open source sooner you disclose better it is.
When you chose secrecy or patent protection you have to handle three sorts of disclosure:
We take the example of a software publisher.
The license agreement should include a confidentiality clause.
If you sell service with the product the service contract should also include a confidentiality clause like "Each party may disclose confidential information to the other party. The parties shall preserve of the confidentiality of such information during the performance of the service and during sometime [to be defined] as from the Agreement expiry."
Documentation manuals and training support documents should include a page with something like: "This documentation may not be copied, transferred, reproduced, disclosed or duplicated in whole or in part, without the prior consent of [your company]. This documentation is proprietary information of [your company] and protected by the applicable law of [your country] and international treaties." This page should refer to the license agreement. It may also refer to a restricted rights definition. The industry commonly follows the definition used by government for its own purchases. Magic keywords to find samples on the Web are 48 CFR Section 12.212 and 48 CFR 227.7202. 48 stands for Federal Acquisition Regulations System, 12 for Acquisition of commercial items, 212 for Computer software, 227 for Patents, data, and copyrights, 7202 for Statutes pertaining to administrative claims of infringement. You may find these Federal regulations on http://www.access.gpo.gov/nara/cfr/cfr-table-search.html.
A secret shared by thousand or more customer employees is longer a secret (a user may copy a product method if this method is not patented and competitors have your documentation) but if you follow the guidelines above this is still a legal secret: you still can file a patent and a competitor cannot show your user manual as evidence in an infringement prosecution or reference your manual in its patent applications.
Prospects and partners
You keep your intellectual property secret though a non-disclosure agreement (NDA). An NDA is a contract whereby the signer agrees not to disclose certain information, except under terms as described in the contract. In a one-way NDA one party agrees to give to a second party confidential information and the second party agrees not to share this information with anyone else for a specified period of time. In a two-way NDA both parties agree to give confidential information and to not share this information with anyone else for a specified period of time.
A one-way NDA may be fine for the first presentation to a prospect. If they have to explain how they intent to use the product, then the prospect will probably ask for a two-way NDA. In case of answer to an RFP or of partnership you also need a two-way NDA. The problem is that each party usually has its own NDA. The stronger party and when parties are of similar strength the customer tends to impose its NDA or to refuse to sign the NDA of the weaker party. This is especially true in countries and businesses in which actors are not fully aware of Intellectual Property issues. NDA negotiation is an extra burden for an already tough job. Furthermore when a sale or an RFP cycle is three to six months, when a partnership lasts two years, the consequence of negligence in an NDA may be fully appreciated eight or ten years later, which is more than the average experience of the actors in their job and sometimes more than the time they will work for their company.
Here we consider Web site, press releases, brochures and public presentations. Intellectually property is made of functions whose combination solves a set of problems and of how these functions are implemented. Look at the description part and at the drawings of a software patent. You will find screenshots, block diagrams and relatively high-level explanations. The description of a patent contains the same data as an article.
A site that does not disclose intellectual property is a site that does not answer to the how question. Such site does not attract visitors because it contains no information and is poorly indexed by search engines because it has no content. If you choose secrecy or patenting you cannot effectively use one of the cheapest and most effective communication means. You may however design a site with a public part and a private, password protected, part. When you can identify the users you are in the same situation as for paper documentation: the content is not public but at the same time the very last persons you would like to see on your site will be your most regular visitors. You may allow self-registration. In that case ask the user to acknowledge a confidentiality clause. You can check her identity by sending a mail with a confirmation number. Oracle uses such a system. You can find in Oracle documents: "The Programs (which include both the software and documentation) contain proprietary information of Oracle Corporation; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent and other intellectual and industrial property laws. Reverse engineering, disassembly or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited." Only highly motivated users accept to register, which is both a drawback (few visitors) and a benefit (good quality visitors).
A press release is a news exercise and because of that an unlikely place for intellectual property disclosure. Neither the format nor the reader expectations, nor the press release goal really enable disclosures. Furthermore in a company that has software intellectual property people who create and understand this intellectual property are in development teams and not a communication services. We only mention press releases because we were asked if a press release could prevent patenting. To check if a press release contains intellectual property answer the following questions:
If you answer no to all of these questions then do not worry about the press release. This also works for brochures. A public technical presentation is a much more dangerous exercise for two reasons:
This is difficult to not disclose intellectual property. In an ideal world the company would define what it is ready to disclose and record what and to whom that it has disclosed. Things made public still have a value. We can illustrate it with a simple example. Your competitor patents a method. If you can show that you owned the method before, you still can use the method but this is bad for your business and for your customers. If you can prove that you presented the method to the public the patent will be rejected.
Patenting has the merit of forcing people to think about these issues. Most of the time what we call secrecy should be called "not care". Open Sourcing your development implies taking care to not infringe copyright of others. Publishing requires extra work. Secret is definitely the cheapest option. For instance it makes sense to keep internal developments for internal users secret. Even the most dedicated patent portfolio makers realize that not everything can be patented: there is always novelty in a large project but this novelty may have a so narrow scope that this is not worth to protect it. Large firms use all methods:
The most obvious example is IBM, which has the biggest patent portfolio and is also one of the biggest Open Source publishers. Companies like BEA, Cisco and Oracle publish large amount of content on their Web sites. Even a small company probably has to make some things public in a conscious way.
Intellectual Property in
Intellectual Property in is obviously related to competitive analysis and market intelligence. However whereas the latter aims to answer the questions: Who are our competitors? How well are they doing? What are their plans? Intellectual Property in aims to answer a single question: Are we allowed to do that?
In some way competitive analysis and market intelligence are the other side of Intellectual Property out and suffers the same problem. Marketing, sales forces and everybody who meet customers is doing market intelligence. A company collects a huge amount of market data but these data are disseminated. Furthermore it is difficult to measure the relative importance of these data, which are in different formats, more or less reliable and hard to link together. However despite their flaws competitive analysis and market intelligence are the first input of Intellectual Property in. They provide raw data such as competitor names, market and mind shares.
Understanding the "that" in "are we allowed to do that?" is another difficulty. Even if you do not plan to patent you must follow the principle exposed above in Patent writing: the product design is the other input of Intellectual Property in. You use this input to write a reference text, which is a patent subset:
Use the reference text to make searches in the patent databases with the toolkit presented above. You can use the patent class of the found patents to broaden the search scope. Look at the referenced patents. Look at the patents referencing the patents. At this stage you may have found forty or more patents. Then consolidate your results with the list of competitors identified by the competitive analysis and market intelligence. A direct competitor will go to court with a case weaker than a company that is on a different market or that is also your provider, customer or partner. It has also more chance to be granted an injunction, in which case you will have to stop selling or using your product. On the other hand patent search may identify new entrants on your market. In that respect Intellectual Property in also feeds competitive analysis and market intelligence. You must also consider patent families: a patent filed in a country may have been promoted to other countries through PCT, which implies a stronger commitment of the patentee. Such patent may represent a stronger threat for your product.
Next compare the independent claims of each remaining patent with the product design. If you find a match between an independent claim and a part of the design ask for a redesign. You should also send a document presenting the most threatening patents and claims to analysts and programmers. Then throughout the project you should periodically check for new patent applications. This is a tough and time-consuming job. If you frequently file patents and if you never stop being sued (which means that you make money and have an enviable position on your market) you represent a sizeable and regular source of revenue for your lawyers and it makes sense to ask their help. A software patent attorney usually knows something about software, which is not always the case of legal departments. On the other hand we do not recommend hiring a patent attorney only to assess legal risks related to a particular project:
Therefore it can make sense to do the search yourself. This is a senior programmer or designer job that requires a holistic view of the company and market. This document may help starting in this activity. Public databases and our toolkit are probably enough to identify threats and find corrective actions. You can also use http://www.freepatentsonline.com/ as an alternative to the USPTO web site. freepatentsonline allows downloading patent files in PDF format, which may be preferred notably for printing. Today freepatentsonline only lists granted patents. In the future they should also list patent applications. You may need to check other sources of information. The Patent Information Users Group site may be a good starting point: "This Patent Information Users Group, Inc. (PIUG), the International Society for Patent Information is a not-for-profit organization for individuals having a professional, scientific or technical interest in patent information." This site contains a good FAQ. You can also use commercial databases and tools. You can find a list of vendors at http://www.piug.org/vendor.html. There is a good presentation of patent tools, Software Tools for Analyzing Patents by Anthony Trippe. The most popular commercial sites may be:
Corporate subscriptions can be expensive but these sites frequently offer pay-per-use service (vouchers, one day subscription) at a much lower price.
You can be in three situations:
You have to focus on competitors’ patents and patent applications because:
The net result is that you will be sometimes notified by a patentee about a patent infringement because:
There are several reasons to not go to court:
Uncertainty and litigation costs are also issues for the patentee. And if he is awarded damages these damages will be awarded after a couple of years. So the interest of the patentee is also to negotiate a license agreement.
There are two factors to consider when you prepare the negotiation:
A reader informed me about a Settlement help site containing a "large Directory of Settlements Help Sites, financial websites and general sites of interest". An article of this site entitled "How $50 Million Settlement Was Reached – Hours Before Trial Began- Esquire Litigation Solutions Seen As Key In Forcing Settlement" shows the way you should present your data. In the negotiation you must demonstrate that:
Patents Presentation Search Issues Strategies Business Methods Patentability Analysis MercExchange eBay Trial Reexamination Business view Granted patents Examination USPTO EPO PanIP Eolas 1-click family 1-click analysis 1-click prior art Trademark Copyright