What happens to IP owned by a defunct company? Say you have a tech company that over the course of its run develops several projects worth of proprietary software and related IP. Then for whatever reason (insolvency/winding up, voluntary deregistration, etc.), the company ceases to be a valid corporate entity. My question is: What happens to the IP held by this company? For instance, if someone were to get ahold of the software/IP developed by the company and publish (or otherwise use) it, is there any legal recourse against them? And if so, who would have standing to take that action, and how is that standing established? Though this question is tagged with 'Australia', I think it would also be interesting to know how it might work in other jurisdictions such as the U.S. and/or other common-law nations, and what the key similarities/differences might be.
Companies dissolve by one of two modes: voluntarily or involuntarily. If it's a voluntary dissolution: the assets remaining after paying all the creditors are distributed among the owners according to their ownership percentages or by some other agreement. The successor owner of the IP will be determined at that time. In the case of an involuntary dissolution: usually as part of a bankruptcy proceeding, the bankruptcy court will first transfer all the corporate assets into a receivership managed by a trustee. The trustee will then disposition the company's assets (including the IP) per the laws of bankruptcy. The successor owner of the IP will be determined through that process. Many of the company's assets will be liquidated by auction and sold to the highest bidder; and the auction proceeds will be used to pay the company's creditors. So in the event of an involuntary bankruptcy dissolution, the successor owner of the IP will have most typically outbid all other bidders at the liquidation sale/auction. If there is any money left over after all the creditors and bankruptcy fees are paid, the remainder will be distributed to the shareholders as above described.
There are now 2 works. An original, abandoned work, and a new, derivative work. The original creator owns the copyright over the original, and the new person owns copyright over the derivative he created. In your scenario, it will be the new creator, who will have the right to sue, if the gpl of the new work has been infringed
In the most likely case No, but you can make it happen! First - almost every patent is rejected - at first. Then you respond to the office action rejection by arguing and/or amending and - guess what - you are likely to get a final rejection. That means the rejection is final until you pay them more money to file a Request for Continued Examination and get two more go-arounds with them. Can you keep doing this? Yes. A previous director of the USPTO tried to make a rule that limited the number of RCEs - the courts knocked it down. If you give up and let it go abandoned by not responding to an office action within the statutory limit (6 months) then the process of that application is over. If you have not filed a co-pending application before the initial application went abandoned then you are really starting over if you file a new application. The original application can be used against any new application on a similar subject matter if it has been published. But it might not have published. The law (35 USC 102) contains - (a) NOVELTY; PRIOR ART.—A person shall be entitled to a patent unless— (1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention; or (2) the claimed invention was described in a patent issued under section 151 , or in an application for &gt;patent published or deemed published under section 122(b) , in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention. Your application may or may not have been published. Then it is neither published or issued and does not fall under prior art under 102 or 103. Applications are automatically published by the USPTO at the 18 month point unless you requested non-publication. In that case if your application never issues it is never public and can't be used against you or anyone else as prior art. You could even decide to keep it a trade secret. Before the publication process came into being as part of TRIPS, an applicant could wait until they saw the claims that had been allowed and the patent was ready to go. If they didn't feel the claims were valuable enough they can chose to explicitly abandon and keep it secret.
No Let's consider a similar scenario. If you made a beverage which poisoned a number of people, would you be absolved of liability because you gave it away for free? Of course not. As there is no contract between you, they would have to bring an action against you in the tort of negligence or negligent misstatement OR under consumer protection law. To succeed at tort they would need to prove that you owed them a duty of care; from Donoghue v Stevenson "You must take reasonable care to avoid acts or omissions which you can reasonable foresee would be likely to injure ... persons who are so closely and directly affected by my act that I ought reasonably have them in contemplation ...". Most cases will founder on your inability to foresee the use to which your software may be put. Consumer law is jurisdiction specific but they generally contain warranties that what you provide (gratis or otherwise) is fit for purpose, merchantable and that you do not make false and misleading statements. There is a chance that a case brought under this sort of law could succeed as you have not limited the purpose, specifically declared that it is not of merchantable quality and have (presumable) said what it does so that, if it doesn't do what you said, you have been misleading and deceptive.
Why do you think Oracle have not been protecting their trade mark? Using a trade mark to describe the product (“Written in JavaScript”, “Seeking JavaScript developer”) is not an infringement and the trade mark owner is under no obligation to, indeed, cannot stop this. Where they are required to defend their trade mark is when it is being used in such a way that there is the risk of confusion that the goods or services could be confused with the trade mark owner’s goods or services. Further, they are not required to defend all breaches, only enough to show that they are actively doing so. Also it is not important that the trade mark be associated with the trade mark’s owner. Do you know who owns the trade mark “Ben &amp; Jerry’s”?
It is certainly possible to incorporate companies with the same name in two different states. If neither company does business in the other person's state under that name, it isn't actionable for either company. If one company was already doing business under its name in a state where another company is formed under that name, it would usually be possible to force the new company to cease and desist from using that name, either with an action directed at the infringer and the Secretary of State (or other official charged with business incorporations in a state) of that state, or in an action directly against the infringer alone. Also, even if a trademark isn't formally registered, it can arise at common law simply through use of a name in a particular market in a particular place. This is harder to prove and the remedies for violating a common law trademark a more limited, but it is not entirely unenforceable.
This is unlikely to be a problem. There are many companies that have already registered software-related trademarks prominently involving an X or the name Xcom. That Twitter has changed to X branding does not substantially change this general situation. With trademarks, the general question is whether similar branding causes confusion. It is unlikely that someone would confuse the X display server / X.Org project / X.Org Foundation with the social media service now being branded as X or x.com. Of course, anyone can sue anyone, the real question is whether that's possible successfully. Here, I have my doubts that x.com could successfully demonstrate confusion in its favour. It is worth noting that the X.Org Foundation does not seem to hold any relevant trademark registrations at all. This is not unusual for Open Source software projects and doesn't mean that X.Org has no rights, but does make a defense a bit more difficult. However, there also doesn't seem to be a relevant registration by the ex-Twitter company or by the X Corp. The x.org domain name is unlikely to be threatened. If the x.org domain name was being used in bad faith it could maybe be seized, but the X.Org Foundation has a pretty strong claim on this name. For historical context, both x.com and x.org were among the six single-letter .org/.net/.com domain names when such registrations were stopped in 1993. But while x.com has been pretty much dormant since that company was renamed to PayPal, x.org has (I think) always been associated with the display server software, and has been used continuously by the X.Org Foundation since its establishment in 2004.
If you use the reviewer's code, or code derived from it (e.g. if you just changed a variable name) then they own the copyright on that part of the software. If the reviewer describes a solution which you implement, or if you re-implement the code from scratch while taking ideas and methods from the reviewer's code, then you own the copyright on that code. However if there are only a few ways to implement something in code then the code is not creative and hence cannot be copyrighted. For example the regular expression in the question you link to is (as far as I can tell) the only correct solution to the problem: any programmer addressing the problem will have come up with that RE. In this the position is akin to a database of phone numbers: while the collection may be copyright (depending on whether selection or arrangement required creativity), the fact that Alice Jones has the number 012345 is not copyrightable, and neither is the alphabetical arrangement of names. Where it gets messy is the boundary between the two. The requirement to detect 4 or more repeated digits in a credit card number could be implemented in a number of ways, but whether there are enough of these to qualify any particular solution as "creative" would be a matter of fact for a court to decide.