Would a patent on the Win32 API make Linux Wine illegal? There is the Win32 API which provides access to systems functions on Windows. For example there is the CreateFile API call to create a file. And then there is Linux Wine which implements this API to run Windows programs on Linux. Let's say Microsoft writes a specification for the Win32 API (which in fact already exists in Form of HTML help pages) and registers a patent on it. Would this make Linux Wine illegal? Would this force the Linux community to remove Wine (which implements the Win32 API) from all distributions and code repositories? I was told in this question that permission to implement a specification can be restricted by patents: Can the permission to implement a specification be restricted?
Too late. It is public knowledge and has been for many years. You can't patent something that isn't new.
First, just to be clear, this is an old story from 2014. Second, Microsoft wasn't seeking payments for patents on the OS per se, but on the drivers for the chips that connect the cell phone to the cellular networks. In 2014 Microsoft bought Nokia. Part of Nokia's value was that it held a whole bunch of fundamental patents for cellular communications. Microsoft was suing Samsung on the basis of those patents. Samsung in turn claimed that Microsoft's acquisition of Nokia, and their attempt to charge for the Nokia patents violated the terms of a 2011 agreement between Samsung and Microsoft. Samsung and Microsoft settled the dispute in 2015. The terms of the settlement were confidential. Microsoft and Google did wage a separate patent battle in the courts of the US and Germany. This was also settled in 2015. This is all water under the bridge now. In 2018 Microsoft joined the Open Invention Network (OIN), a consortium of companies that agreed to license their patent portfolios to Linux royalty-free, and agree not to assert their patents against Linux systems.
Yes and no. [note, the following is all written about US law. In other jurisdictions laws are, of course, different (though usually not drastically so.)] In the US there are (at least) three different bodies of law that might apply to code: copyright, patents, trade secrets. Copyright covers original expression. Anything you write is automatically, immediately protected under copyright. The copyright applies to the code itself, and anything "derived" from that code. It's up to the courts to decide exactly what "derived" means. One case that's long been viewed as a landmark in this area is Gates Rubber v. Bando Chemicals. The Court of Appeals for the tenth Circuit decision includes a section titled: "The Test for Determining Whether the Copyright of a Computer Program Has Been Infringed." Note that you can register a copyright, and that can be worthwhile, such as helping recover some damages you can't otherwise. Patents are quite different from copyrights. Where a copyright covers expression of an idea, a patent covers a specific invention. Rather than being awarded automatically, a patent has to be applied for, and awarded only after the patent office has determined that there's no relevant prior art to prevent it from being awarded. A patent, however, covers things like somebody else independently discovering/inventing what's covered by the patent. A trade secret could (at least theoretically) apply to some process or procedure embodied in the code. A trade secret mostly applies to a situation where (for example) you're trying to form an alliance with some other company, and in the process tell them things you don't tell the general public. If you've identified the fact that what you're telling them is a trade secret, and they then tell a competitor (or the general public, etc.) or more generally use that information in any way other than the originally intended purpose, it could constitute a trade secret violation. As a side-note: patents and copyright fall under federal law, so they're basically uniform nation-wide. Trade secrets mostly fall under state law, so the exact details vary by state. Absent a reason to believe otherwise, I'd guess your interest here is primarily in copyright infringement. The key here would be showing that one piece of code was derived from the other. That is, it specifically would not apply in a case where there were only a limited number of ways of doing something, so anybody who wanted to do that had to use one of those ways. Since this would not indicate actual derivation, it would not indicate copyright violation.
You seem to assume that copyrights require paperwork such as registration. This is wrong, copyright is automatic. And it prevents the downloader from making the sort of change that you suggest. In fact, it prevents the downloader from using your template at all. The only reason the downloader can use that template is because you've granted him a specific license to ignore some copyright rules, but the default remains. And you did not grant the right to alter the template to free users.
As you've presented them, I doubt the functions are protected by copyright in the first place. Originality is one of the threshold requirements for copyright protection, and it demands that the work in question be independently created by the author, and that it possess some minimal degree of creativity. If you're talking about programming at a level so basic that the function truly must be created in a particular way, there is no originality in simply following the instructions. And even if there's some wiggle room, but the language you used has likely been independently replicated by many programmers, that's still not original enough to be copyrightable. What you want to watch out for, though, is the possibility that they've been combined into an original arrangement that is protected. I don't know enough about how copyright law is applied to code to say where or how that line is drawn, but my instinct would be that it could be a fairly low threshold.
All Licenses are granted in the shape of contracts. Contracts contain clauses that allow or disallow their transferability. The typical way a License for a software is obtained is to buy a key that acts as proof of purchase, and then agreeing to an EULA. For example the Win10 one. very typical clauses from the Win10 EULA explicitly forbid to transfer of the license without the device it was installed on: Installation and Use Rights. a. License. The software is licensed, not sold. Under this agreement, we grant you the right to install and run one instance of the software on your device (the licensed device), for use by one person at a time, so long as you comply with all the terms of this agreement. Updating or upgrading from non-genuine software with software from Microsoft or authorized sources does not make your original version or the updated/upgraded version genuine, and in that situation, you do not have a license to use the software. c. Restrictions. The device manufacturer or installer and Microsoft reserve all rights (such as rights under intellectual property laws) not expressly granted in this agreement. For example, this license does not give you any right to, and you may not: (iii) transfer the software (except as permitted by this agreement); Transfer. The provisions of this section do not apply if you acquired the software in Germany or in any of the countries listed on this site (aka.ms/transfer), in which case any transfer of the software to a third party, and the right to use it, must comply with applicable law. a. Software preinstalled on device. If you acquired the software preinstalled on a device (and also if you upgraded from software preinstalled on a device), you may transfer the license to use the software directly to another user, only with the licensed device. The transfer must include the software and, if provided with the device, an authentic Windows label including the product key. Before any permitted transfer, the other party must agree that this agreement applies to the transfer and use of the software. b. Stand-alone software. If you acquired the software as stand-alone software (and also if you upgraded from software you acquired as stand-alone software), you may transfer the software to another device that belongs to you. You may also transfer the software to a device owned by someone else if (i) you are the first licensed user of the software and (ii) the new user agrees to the terms of this agreement. You may use the backup copy we allow you to make or the media that the software came on to transfer the software. Every time you transfer the software to a new device, you must remove the software from the prior device. You may not transfer the software to share licenses between devices Cincom Systems, Inc v Novelis Corp., 581 F.3d 431 (6th Cir. Sept 2009) held that you can not transfer software that was merely licensed, even as the part of your company that uses the software becomes part of another company through a merger. The licensor had put express language that forbids the transfer of the license by licensee into the contract: When Alcan Ohio merged with Alcan Texas, the license granted by Cincom solely to Alcan Ohio transferred to the surviving corporation, now known as Novelis. Because Novelis did not abide by the express terms of Cincom's license and gain Cincom's prior written approval, Novelis infringed Cincom's copyright. Likewise, the court in Capitol Records, LLC v. ReDigi Inc., 934 F. Supp. 2d 640 (S.D.N.Y. 2013) held that you can not re-sell an (installed) digital item as you create a new copy without the license for this. In a similar fashion, Disney recently changed the Terms of Service and contract on the digital codes that come with DVDs. The new terms explicitly forbid unbundling the code from the disk and forbid transferring the disk after using the code. This was what allowed Disney to gain an injunction in the case of Disney v RedBox. The end result is not out yet. In the EU, the ruling in one case fell different: UsedSoft GmbH v. Oracle International Corp. held in 2012 that there is possibly a right to resell your used license... as long as it is a license forever (emphasis mine): in the event of the resale of a user licence entailing the resale of a copy of a computer program downloaded from the copyright holder’s website, that licence having originally been granted by that rightholder to the first acquirer for an unlimited period in return for payment of a fee intended to enable the rightholder to obtain a remuneration corresponding to the economic value of that copy of his work, the second acquirer of the licence, as well as any subsequent acquirer of it, will be able to rely on the exhaustion of the distribution right under Article 4(2) of that directive As a result software licenses adapted and started to expressly sell the license as a license to obtain the service of a maintained software. To software as a service - which Windows and the Office suite are - this ruling does expressly not apply and you can not re-sell such a software license after it has been used. Signed License v. License Key That does not apply to the key, the representation of the payment. You can buy them in a store. They are a pretty tangible good. The principle is - in general - that you validate the license you sign by handing over the key to the supplier of the software. This usually voids the key. But... all those sites claim you can transfer?! not.... quite: once you agreed to the EULA and obtained the software service it can no longer be resold. Also, you just agreed you may not do that with transferable software. However, as long as you have the key unused the unused key for a license can be resold. That is a physical good that the first sale doctrine applies to. However, you may not retain a copy of the key to sell it, again and again, you would interfere with your customer's ability to contract as a used key often is rejected - you'd have defrauded the customer. Even in the EU, if you bought a perpetual license, you need to render your copy unusable under the ruling above: The CJEU held that the first purchaser needs to &quot;make his own copy unusable at the time of its resale…in order to avoid infringing the exclusive right of reproduction of a computer program which belongs to its author“ The CJEU therefore briefly commented “to solve that problem, it is permissible for the distributor – whether ‘classic’ or ‘digital’ – to make use of technical protective measures such as product keys“. The key is a means to show you are entitled to a contract. It is the consideration Microsoft gets for signing the other side of the contract. Most software resellers deal with keys, the resale of keys is expressly possible. Some software companies mark a used-and re-sold key and require to contact the company to make sure that the software has been disabled on the other end. Since many companies can't render the software disabled on the seller's end, they refuse to acknowledge the sale on the same basis: the software was not disabled or rendered useless, and as a result, the sale did not happen in accordance with the judgment.
According to the website, the VirtualBox base package is licensed under the GPL. That means you're free to use it for any purpose. The VirtualBox Extension Pack has a more restrictive license, which is only free for personal, educational, or evaluation use.
This is going to depend on several things. First of all, do you have a lawful, licensed copy of the SDK? My understanding is that Nintendo only licensed the SDK to selected game companies. If what you have is an unauthorized copy, you do not have the legal right even to use it. If what you have is properly licensed, then you do. Or is what you have an unofficial SDK created by someone other than Nintendo? Secondly, what does the license agreement that comes with the SDK provide? Does it require developers to register with Nintendo? If it does, you will need to comply. Nintendo cannot prevent others from writing programs designed to run on their hardware. But they can control who uses their development software, if they choose to. You cannot reproduce in your game any of Nintendo's copyrighted software (or anyone else's) without permission. That applies even more strongly if you intend to sell the software. But you can use any development software for which you have a valid license in whatever ways its license permits. I would expect this includes creating games. It would include selling games that you create that do not use any of Nintendo's code, unless there is a specific provision forbidding that in the license agreement.