Can you have a software patent for a method that can be done in way one only? Is it possible to patent a software to do something which can only be done in one way due to limitations well known to everyone? Here is the scenario, I want to acquire an image from a digital sensor from my web based application: The browser itself cannot take images from the sensors, this is a known technical limitation For that reason, you will need install a client application on the client's computer to acquire the images You still want to take the image from the browser, so you will have a button on your web application which will tell the client application to acquire an image from the sensor The acquired image is then uploaded to the server where it is stored Any software developer will tell you this is the only way to do it... But what if someone patents this exact method? Is it possible? Can it be enforced and should I worry about these kind of patents?
Can only be done one way and has been done - not novel; you can only think of one way to do it and don't know if it has done that way or at all, may be is patentable. From one example it is hard to give a general answer that might apply to a case you might actually be thinking about. One can not get a patent on something that is not novel or is obvious (using U.S. patent law concepts) or not useful. Novelty is judged by trying to find a single reference, published before the filing date, that contains all elements of the claimed invention. An examiner can't just say &quot;that is the way I would have solved the problem&quot; or &quot;everybody knows that already&quot;. This is to make the test for novelty more objective and give the applicant something tangible to argue against. Next consider obviousness. The examiner can't just say &quot;seems obvious to me&quot;. Besides the problem that it is far from objective, there is a strong psychological effect called &quot;hindsight bias&quot;. Once you know a solution, it seems obvious even if you would never have come up with it independently. To assert a rejection based on obviousness an examiner needs to find one or more references that, together, have all the elements in a claimed invention. That part is pretty objective. Then they need to argue that a (fictitious) person of ordinary skill in the art would think to combine those references to achieve the claimed invention. A POSITA knows everything that was ever published anywhere at any time in any language in the relevant field or specifically relevant to the problem from an other field and is of median/average skill in the field. There are rare cases where the problem was never recognized and the recognition of the problem is an important part of the invention. In that case the solution might be obvious once the problem was (inventively) identified. That would still not be an obvious invention. Your example might fit into this. In the rest-of-the-world obviousness is replaced by &quot;having an inventive step&quot;, not exactly the same concept. And the rules of what can be considered prior art different. A third criteria is &quot;useful&quot; in the U.S. It is somewhat analogous to &quot;industrial applicability&quot; in the rest of the world. Until about 2000 this was a trivial hurdle in the U.S. As long it was not a law of nature (abstract), something completely done in your head or a perpetual motion machine, it was probably useful. There have been many rulings since then that have put more and more things in the &quot;abstract&quot; category and if it's abstract its not useful. This is the basis of the &quot;you can't patent software&quot; mantra. There are plenty of things that look like software that get patented but it is getting harder.
A fundamental principle of copyright law is that protection is only afforded to the concrete expression, and not the abstract idea. Therefore, if you write a sort program, what is protected is &quot;that specific program&quot;, and not the general idea of a sort program. There are many kinds of sort algorithms: if you write a bubble sort program, you don't &quot;own&quot; all bubble sort programs, you only own the one that you wrote. If you sell your right to a particular bubble sort program, you don't thereby prevent yourself from writing another bubble sort program. But, technically, you do prevent yourself from copying that program, changing some variable names or maybe manually recoding a couple of lines, and re-licensing the code (assuming that you fully transferred copyright, or gave the customer exclusive rights to the code). The basic question that the courts will ask is &quot;did you copy that program&quot;, which they answer by looking at the similarity between the two programs. All bubble sorts have a necessary similarity. To prove infringement, the plaintiff would (ultimately) have to prove that the similarity had to have come from copying rather than independent coincidental re-creation. Functional considerations and general programmer practice would tend to weigh against an allegation of infringement in certain cases, where &quot;counter&quot; is a common name for a counter variable, and bubble sort is a well known algorithm with limited practical differences in lines of code. The hard part is establishing that it would be natural for such similarities to exist even when independently coded by a single person. It may be common practice to take a program that you've sold and tweak it in some fashion, but that is copyright infringement, whereas &quot;applying the lessons that you learned in writing X to a new program&quot; is not infringement, it is using the same ideas, and the ideas are not what is protected.
Trivial is hard to judge after the fact due to hindsight bias. Once you know the answer to a riddle it seems obvious but you couldn’t figure it out without already knowing it. The criteria for get a patent in the US does not include the word or concept “trivial”. It does include non-obviousness. To reduce hindsight bias an examiner needs to follow a process of identifying all sub- components of an invention in the prior art and then making a good argument as to how someone of ordinary skill in the field would be motivated to put them together. Also there is no measure of improvement over past technology required for a patent. A trivial improvement in cost or performance is fine. Actually no objective improvement is required at all. An existing solution might work as well or better than your invention. That means probably no one will buy it but if it is novel and not obvious one can get a patent.
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.
It is unclear whether WINE is infringing copyright or if it can rely on a fair use defense. The CAFC held that: that the declaring code and the structure, sequence, and organization of the API packages are entitled to copyright protection In that light, if WINE had original content in the structure, sequence, and organization of its API, the CAFC would likely also find that it is entitled to copyright protection. However, because this issue is outside the scope of the CAFC's exclusive jurisdiction (this is a copyright issue, not a patent issue), the holdings are not binding in any other circuit. Each circuit is free to review anew the copyrightability of APIs when such a case comes up. My guess is that this is the reason the Supreme Court declined to hear an appeal on CAFC's Oracle v. Google opinion. To address your fair use question would be simply speculation, because fair use is always assessed case-by-case, and even in WINE's closest analogy (Oracle v. Google), the CAFC remanded the fair use question back to the trial court, and that question hasn't been decided yet: we remand for further consideration of Google’s fair use defense in light of this decision
Disclaimer: I'm from the US and don't claim to know German or Turkish law. So let me discuss some general principles here, but details may well be different in Germany and Turkey. You're mixing together three very different things: trademark, copyright, and patent. Copyright protects the expression of an idea, in this case, the exact computer code, images, etc. If you didn't copy his code, the chance that you would coincidentally write identical code is remote. The fact that you both have a line of code that says x=x+1 wouldn't give him any grounds for a lawsuit. He'd have to show substantial portions of the code were identical. If you didn't deliberately copy his code, this isn't going to happen. Barring some extraordinary and unbelievable coincidence, you can't violate copyright accidentally. Trademark protects names and symbols used to identify a company or a product. If you decided to call your software company "Microsoft", then that other Microsoft could sue you for trademark infringement. Likewise if you copied somebody else's logo or other distinctive graphics. This is very different from copyright. It is quite possible to violate someone's trademark accidentally. Especially if he gave his company or product a rather generic name. Like if someone called his product, say, "Password Manager", someone else might make a product with the same name without ever having heard of the original. Ditto if he has some simple logo or other graphics. If you did accidentally duplicate a name or graphic elements, well, in the US a court would likely order you to change your name or graphics and that would be the end of it, unless you refused, in which case you'd end up in court. US Courts have ruled that very generic names have limited trademark protection. An example I saw recently was "Main Street Auto Repair". A court said that the owner of that name could prevent someone else from opening a shop in the same town with the same name, but he couldn't sue someone in another town who happened to use the same name. This is why, by the way, companies often use made-up words for their product names. In your case, this should be a trivial issue. If he is claiming trademark to the look of the main menu screen, just change the colors or move some buttons around. If it actually went to court, you should be able to argue that the similarity was accidental and when you were informed you promptly changed it, and that should be the end of it. Depending, I guess, on how hard-nosed the judge is, etc. Patents are different still. A patent gives the owner the exclusive right to use an invention or process for a specified period of time. It doesn't matter if you invented the same thing entirely independently. Whoever filed the patent first has exclusive rights. There have been cases where an inventor lost out to someone with a similar invention because he submitted his patent application one day later. If this other person has patents that you are infringing, you are pretty much out of luck.
Yes. The copyright owner of a work has the exclusive right to "reproduce the copyrighted work" or to make "derivative works" of it. 17 USC 106. Copyright law is older than the photocopier, and it applies to copies made by means of any technology. If your intent is to duplicate the protected work, whether you do it by tracing, photocopying, or even freehand, you are infringing that right. It is possible that you could squeeze into one of the copyright exceptions, such as fair use, but these are much narrower than people tend to assume they are (especially outside of the U.S.), and they boil down to: "Well, yes, I copied your copyrighted work, but..." The bottom line is: is it copyrighted? Did you copy it, in whole or in part? Then, unless you have a very good reason, you've infringed the copyright. Whether you do it by means of tracing paper, jellygraph, or iPhone doesn't matter.
You are absolutely allowed to discuss or describe or criticizes software (or books or other copyrighted or trademarked things) without any permission from the copyright holder or trademark holder. This includes teaching people how to use those things. You may not, however, copy protected software without permission. For example you could not include a CD with a copy of Windows 10 as part of a course you taught on using Windows 10, without permission from Microsoft. Also, you may not use a trademark in such a way as to imply that your course is approved or endorsed by the trade mark holder, or by the maker of the trademarked item. If reasonable people could think that your Windows course was approved by Microsoft, you are probably infringing their trademark. Use of screenshots is more of a grey area. Such use, for purposes of teaching or of commentary, is probably covered by fair use (in the US) or fair dealing (in any of several other countries). But that is always a case-by-case determination, and depends on the exact facts, such as how extensive the use is, and whether it in any way harms the market for the original. If in doubt consulting a lawyer experienced in IP issues is wise. But aside from the issues of screenshots, the makers or copyright or trademark holders of software have no right to grant or withhold permission to one who teaches about the softrware, nor to demand any fee from any such person.