Does this Intellectual Property Agreement assign the rights to IP created after employment ends? This is an extract from a software developer Intellectual Property Agreement: “Intellectual Property Rights”: patents, rights to Inventions, utility models, copyright and neighboring and related rights, trademarks, trade names and domain names, rights in get-up, goodwill and the right to sue for passing off, unfair competition rights, rights in designs, rights in computer software, software application development rights, database rights, topography rights, rights to use and preserve the confidentiality of information (including know-how and trade secrets) and any other intellectual property rights, in each case whether registered or unregistered and including all applications (or rights to apply) for and be granted, renewals or extensions of, and rights to claim priority from, such rights and all similar or equivalent rights or forms of protection which subsist or will subsist now or in the future in any part of the world. “Invention”: any invention, idea, discovery, development, improvement or innovation, whether or not patentable or capable of registration, and whether or not recorded in any medium. ......... Further, and in the alternative, all Employment IPRs and Employment Inventions Intellectual Property Rights insofar as they are capable of prospective assignment, are hereby assigned by the Employee to the Branch. To the extent that any such Intellectual Property rights cannot be prospectively assigned, Employee undertake to assign all such Intellectual Property Rights as and when they are created or promptly thereafter. The worrying part is marked in bold and italic format in the above, plus the last 2 quotes from below (also marked in bold and italic format) Does this mean that if the employee leaves the company, and then creates or gain an intellectual property right, does the company own that right ? Because the definition of Intellectual Property Rights states: in the future Note that before the above extract comes the definition of Employment IPRs and Employment Inventions, which are not worrying because they restrict the rights to the ones created during the course of his employment “Employment Inventions”: any Invention which is made wholly or partially by the Employee at any time during the course of his employment with the company (whether or not during working hours or using Branch premises or resources, whether or not recorded in material form, and which relate in any way whatsoever, directly or indirectly and/or is developed for the benefit of the Branch or Branch’s clients or business prospects). “Employment IPRs”: Intellectual Property Rights created by the Employee in the course of his or her employment with the company
Does this mean that if the employee leaves the company, and then creates or gain an intellectual property right, does the company own that right ? No. The reference to &quot;the future&quot; pertains only to the IPRs of inventions that ensued in the course of his employment. Even if the employer alleged that the clause also encompasses post-employment creations and/or post-employment acquisitions of IPR, such extension would be unconscionable (and therefore null and void).
It does mean that you cannot reuse any parts of the source code, even small simple ones. You would have to rebuild the code from scratch. There is a significant chance that the code would be "substantially similar" to the code that you were hired to build, also that if anybody else were to write a bubble sort or 24-to-am/pm conversion routine, it would look the same, where even variable names (which should describe function) are the same or very similar. In case of an infringement lawsuit, you would have to defend yourself by showing that there are only a few ways to code a given function. Copyright protects only the "expression", not the abstract idea. A linked list is an idea, which can't be protected by copyright; same with recursion, pointers, stacks, object-oriented programming... Anything that involves copy and paste is infringement. If you re-read the copyrighted code and then try to reconstruct it, you probably crossed the infringement line. If you remember the problems and solutions and accidentally write somewhat similar code, that is probably on the safe side. From the perspective of the programmer not wanting to always reinvent the wheel, it would be most useful to make a distinction in the contract between "the essentials of the customer's program" versus "incidental utility work". The difficulty will arise in saying specifically what is essential vs. incidental. For instance, I know that if I were to hire you to develop a speech-recognition system, low-level audio-acquisition and encoding would not be essential to my purpose, whereas DSP parsing routines would be the center of my interest. The programmer would then want to retain recycling rights to all non-essential code.
In simple terms: Except as expressly set forth in this Agreement, ... Whatever follows next is only limited by what the agreement clearly says is limited. ... the exercise by Company of any of its remedies under this Agreement ... A remedy is something that helps to fix a situation back to what it "should be" in legal terms. There is an implication that the agreement provides for a number of ways of fixing any problems that occur, related to following or breaching the contract. Whatever follows next is assuming that one of those remedies has been used or chosen for fixing a problem. ... shall be without prejudice to its other remedies under this Agreement or available at law or in equity. Having chosen to use one or some remedies, it still has the choice of using any of the others in the agreement and also those available generally under the law. The election by the Company to terminate this Agreement in accordance with its terms shall not be deemed an election of remedies, ... Ending the agreement doesn't count as choosing one of the remedies. ... and all other remedies provided by this Agreement or available at law or in equity shall survive any termination. It doesn't matter if the agreement is ended, regardless of why, the company still has the choice of any remedies as before.
1) I saw that no where during registration you actually tell what your work does, you only fill up details, how exactly is it protecting you if you don't specify? For example I have a computer program/website that do something, how exactly the copyright protects you if you did not specify about it? A copyright protects a particular single expression of an idea and versions that are derived from that particular expression. When you copyright software you have to provide approximately 50 pages of printed code so as to make it possible to distinguish your code from someone else's and you generally deposit a full copy with the Library of Congress. The ideas in the computer program are not protected. You only protect the exact language of the code in the computer program and other programs that use that exact language as a starting point. If someone reverse engineers a way to achieve the same process or outcome with different code language (or even comes up with exactly the same code language without ever looking at the language used in your code) then their software does not infringe on your copyright. To protect the ideas in a computer program you need a patent. 2) If I am a non-us citizen, do I need to select in State "Non-US", or leave it blank on "Select"? Because it allows me to complete registration with either. State "Non-US" refers to where you are located, not to your citizenship. If you are located outside the U.S., then you select "Non-US" and if you are located in a U.S. state, but are a non-citizen, you select the state where you are located. The answer does not affect the validity of your copyright. It is used for economic statistics and to determine where the copyright office should locate its own offices to be maximally useful to the public.
The software being free and open source has no impact on whether it infringes any patents or violates any copyrights. Copyrights attach to fixed representations of creative work in a tangible medium (e.g., the actual code and graphical elements of the software in question). As long as you aren't copying the copyrighted work of someone else, you should be in the clear. So, if you write your own code from scratch, or rely on code that you're allowed to use (e.g., "free" software with a permissive license that allows it to be used freely), you should be fine. On the other hand, if you copy a chunk of code that you aren't allowed to use, and then change the variable names so that it's superficially different, you're likely violating someone's copyright. Patents are a much more difficult question. To determine whether you would infringe any patents, you would have to read the independent claims of every patent that might be related. If you perform all the steps of any one of those claims, then you are infringing that claim (and therefore, the patent in which it is found). Unfortunately, this is much easier said than done. First, it may be difficult to search for all the potentially relevant patents, and once you've found them, there may be far too many to read. Second, claims are written in a type of language that is specific to patents, and someone without experience in patent law may not understand them correctly. Finally, the terms in the claims may not take on their plain English meaning, but rather may have been defined by the language in the rest of that patent, so it's possible that you might incorrectly think you were in the clear based on a misunderstanding arising from that. All that said, it may be best to go ahead with implementing an idea and then waiting to see what happens. Chances are that the implementation will arguably infringe some patent in some way, no matter what's done. But chances are also high that there will never be any worrisome enforcement action taken against it by a patent owner, simply due to the difficulty and expense associated with enforcing patent rights.
I've been wondering if it is possible to hire / create a company with someone who would open a restaurant in my place and manage it according to my guidelines. Yes, of course. You can do it just like you described: Create a company, hire employees, (let them) open the restaurant. You, as the owner of the company, could set up whatever guidelines you have in mind, and your employees would be bound by them (limited only by general laws, such as on health and safety). Some caveats, however: You will need money to set this up - for buying / renting space for the restaurant, for paying your employees, obtaining supplies, initial marketing etc. It may take a while until the restaurant earns money (if ever), and you'll need money in the mean time. Someone will need to manage, that is make decisions. You can do that yourself, but then you will work for the restaurant (which you write you do not want to do). Or you can hire someone to do it for you, but that will cost more (in salary), plus you will have to find someone you can trust. That's a tradeoff for you to make. I guess it'd be like an intellectual property. That depends, but usually there will be little in terms of intellectual property. If you have a unique idea for the restaurant, you could patent it, but there are many restrictions on what you can protect, and ways around it, plus this also costs money (a lot if you need a lawyer's advice). Apart from that, you can register a trademark for the restaurant, but that only protects the name / logo, not any ideas. Finally, some of your ideas might be considered trade secrets, but again the protection is limited. In general, there is no blanket "idea protection". If you have a good idea for a restaurant, in most cases other restaurants will be able to copy them, possibly with slight changes - take that into account.
If it's patented then it doesn't matter that you independently came up with it. Most software is not patented, though. Most developers do not even think about patents when writing code. In theory you could spend your time keeping up to date on software patents so that you avoid infringing. But this probably only makes sense for specialists who would want to read the latest patents in their field anyway. All software is protected by literary copyright, though. In this case they will try to prove that you did not independently created it, and did copy it. Whelan v. Jaslow in 1986 ruled that structure, sequence and organization of a computer program were protected by copyright. So you could be liable even if you did not just copy and paste sections of code. But even if you're worried the court would get things wrong and think you copied a program when you never even saw it in the first place, there is really nothing you can do about it.
Patents become enforceable when granted, not before. However there is something called provisional rights (absolutely nothing to do with provisional applications). In the US, under 35 USC 154(d), if a claim in a published application is “substantially identical” to a claim that eventually issues, a patent owner can get damages of at least a reasonable royalty on units produced between the publication and notice and the issue date. Enforcement on this must await the granting of the patent. The infringer must have actual notice of the published application. It is rarely invoked see this article.