Is a license necessary to produce patented inventions? Say I am a malicious CEO of Company A which has patented one of our products. At a later point in time, I then publicly give verbal permission to Company B to produce this product. (Permission is not given over any other avenue of communication) After Company B has made a fortune off of our product, would I be on good grounds for infringement? Does it change if I have given them written permission but not filled out a licensing agreement? In short, can I use anything besides a licensing agreement to give permission to produce a patented product? If the answer is different from country to country, then assume we are talking about US law.
You say the permission was "public", therefore I am going to assume that it cannot be argued that there was no agreement. There are two possibilities: If Company B has given consideration for the promise then there is a binding contract and Company A may be able to end it but could not seek redress for when it was in place. If there is no contract then the principle of promissory estoppel should have essentially the same effect. An agreement, including an IP licence, does not have to be in writing nor does it have to have any particular form.
The inventor or would-be developer can require potential investors to sign a non-disclosure agreement (NDA) before revealing the details of the idea. In an initial letter a statement such as &quot;This idea is being disclosed in confidence to enable4 you to consider if you wish to invest in the project.&quot; That would put the investor on notice, and if the investor discloses it to another or makes use of the idea in a competitive project, there may be grounds for a suit for breach of confidence. If reasonable precautions are taken to disclose the information only to those under a duty of confidence, and to protected it from unauthorized disclosure, it may be protected as a trade secret, and any evasion of those precautions or breach of confidence may give grounds for a lawsuit. In the US the Uniform Trade Secret Act has been adopted by almost every state. In other jurisdictions there are other similar laws. As stated in the Wikipedia article A trade secret is information that is not generally known to the public; confers economic benefit on its holder because the information is not publicly known; and where the holder makes reasonable efforts to maintain its secrecy.
What are exactly the legal consequences of "All rights reserved"? Almost none. You have to explicitly grant copyright rights. You don't even need the Copyright notice for them to apply. My "almost" is because the notice makes it harder for somebody to argue "they didn't realize". Do I still need an additional SW License Agreement or is the Copyright notice above + a Disclaimer of liability sufficient? If this is free software (I know you said it isn't), do yourself (and everyone else) a favour by picking a license you like. Preferably either GPL or MIT (depending on your taste). There are far too many free licenses already. Please don't add another. (It also makes it much easier for any user of your software: "Oh yeah, GPL v2. We understand that. We can use it." as opposed to "What are the implications of using this one??" As this is not free software, I think you need a paid-for lawyer (who understands IPR in your juridiction.) Edit: In principle, I believe you don't need anything. The code is copyright, so the customer can't do anything with it (without explicit permissions that you haven't granted). However if the customer doesn't realize that or thinks you won't mind, you then have to go to court to enforce your rights (and probably end up with a disgruntled customer). A short, clear, license will make it clear to the customer what they are allowed to do, and save all that aggravation.
It doesn't work like that! If the code is not properly licensed, you can not acquire a license for it. If you don't have a license, you can not use it. Usage without a license is copyright infringement and not allowed: the copyright is with the author, and only the author may make derivates or copies or allow them to be made by licensing it. You do not gain copyright by fixing a licensing error - in fact, you commit copyright infringement if you do not have a license, and providing wrong copyright management information is illegal under 17 USC 1202
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.
Of course you have to follow the license. You seem to have a license that doesn't allow distribution and want to know if giving copies to the Dutch or Chinese branch of your company is distribution. First, you should not make that decision. Your company's lawyers should do that. Second, such distribution is with some licenses perfectly legal if you distribute the software with source code. That's a business decision which you or your manager or his/her manager... can make. Such questions (whether giving a copy to your Dutch branch is distribution) often don't have an answer that is yes or no but maybe - if you went to court, would a judge say that it is distribution? The answer is quite clearly "maybe". So unless you can find a safe way, there is a risk. Again, your lawyers will assess the risk.
Do you have an explicit permission by the artist? Does the artist give a blanket permission to anyone which covers this kind of use of their work (a license)? If no, then you commit a copyright violation when you use their work for your blog. This applies to practically any country which signed the Berne convention which is almost everywhere in the world. Having no commercial interest is usually not an excuse to violate copyright. Regarding which jurisdiction applies when you, your website and the copyright holder are in different countries: I opened a new question about this.
Whoever "derived" the illegal derivative work most likely has copyright in his derivations, unless they are not worth copyright protections. Say I take the Harry Potter books and add a few chapters and try to sell it - that's copyright infringement of course, but I have the copyright on these additional chapters. However, I don't have the right to allow you to copy the derived work. And even if you have the right to copy the original work, you don't have the right to copy the derived work because it is a different work. I could extract my changes, and allow you to take them and do with them what you like. You could then create an illegally derived work yourself. I couldn't sue you, but the original copyright holder could. To the comments: One, a work and a derivative of the work are not the same, so even if you have the right to make a copy of a work, that doesn’t give you any right whatsoever to copy a derivative work - they are not the same work. Two, the copyright holder has the exclusive right to control copying and the creation of derivative works. If the copyright holder doesn’t want derivatives to exist, then creating them, copying them etc. is always copyright infringement.