Where is the line between copying code that isn&#39;t yours and getting idea from trivial code? I have a tendency to overthink things. Even when writing a paper in school I wondered when I needed to add a citation, as technically people are born knowing nothing and must have learned any fact from somewhere. For example should I cite who claimed Obama is the current president of the US? Should I cite where I got the speed of light from? This over thinking still haunts me when it comes to code without a license (or a restrictive license) found on the internet. Where is the line drawn between studying example code and applying what you learned violating copyright For example if I see some code with a license saying it can't be reproduced, and it has a method called is_prime(int x) and has a for loop checking odd numbers up with the square root, would I be breaking copyright if I wrote a similar method? What if I copied and pasted? What if I changed the names? (E.g. maybe is_prime is a better name for the method than check_if_prime.) The point is some ideas are so simple they can't really be changed, yet still complex you probably won't create it by yourself yet. If a person is implementing a linked list, they probably have seen example code for it somewhere. Is this not violating copyright as they just aren't looking at the code while they implement their own?
Not having immediate access to the source doesn't preclude a finding of copyright infringement. If you have seen the source material, subconscious infringement can happen. However, in this example, both the short phrases doctrine and the merger doctrine would likely prevent the is_prime function from having copyright. Words and short phrases are not individually copyrightable, so the name would be free to take. Regarding the implementing code, if it isn't an exact copy (i.e. copy and paste), courts will apply the abstraction-filtration-comparision test. They may find that you took the selection and arrangement of instructions from the original source, albiet using different names. That selection and arrangement would probably be considered a substantial similarity and, if not for the merger doctrine, infringement. However, given the limited number of ways to express the prime-detection algorithm means that the expression of that idea has merged with the idea, and thus is not protected by copyright. (Or in some jurisdictions, merger is a defence to infringement rather than a bar to copyrightability).
Written down computer code is subject to copyright. If you do not have the permission of the owner to copy it you are breaching their copyright unless your use constitutes fair use/dealing.
If you say something twice, eventually they’ll be in conflict Law codes are vast. They deal with many things and sometimes, as here, they deal with the same thing twice. If they duplicated themselves, rather than cross-referencing, every time the law was changed, every single instance would have to be tracked down and changed. Admittedly, that is not as big a problem with digital codes (but still not infallible and definitely time-consuming) but when these would have to be found by hand, it was damn near impossible. Written this way, change it once and it’s changed everywhere. My first boss taught me that. The fired was engineering rather than law but the principle is the same.
Copyright doesn't protect methods, only particular fixed expressions. 17 USC 102 Some methods (but not algorithms) may be protected by patent. Diamond v. Diehr 450 U.S. 175 (1981) More exactly, "an algorithm, or mathematical formula, is like a law of nature, which cannot be the subject of a patent". However, in Diamond, the respondents here do not seek to patent a mathematical formula. Instead, they seek patent protection for a process of curing synthetic rubber. Their process admittedly employs a well-known mathematical equation, but they do not seek to preempt the use of that equation. Rather, they seek only to foreclose from others the use of that equation in conjunction with all of the other steps in their claimed process. Said another way: the algorithm cannot be protected, but if you are using the algorithm as part of a method or process that as a whole is patented, you would be infringing the patent. The paper does not have to disclose the patent - you could email the authors to see if they have any patent that protects any particular methods using the algorithm in the paper, but that doesn't rule out patents that the paper author is unaware of.
It depends on the nature of the quote. Quotes from Buddha, Aristotle and Lincoln are out of copyright. Otherwise, the two basic questions are: who put that quote in fixed form, and is copying it "fair use"? If for example you happen to be at a political rally where a politician makes a noteworthy extemporaneous quote, you could be the copyright holder, because copyright law protects the person who first puts the work into fixed form. (If he's reading from prepared text, the speech writer or his employer would hold copyright). You can also quote small bits from any source, such as "Don't think about your errors or failures; otherwise, you'll never do a thing". It would not be "fair use" to chop up a novel into a sequence of 2-3 sentence quotes. This assumes that you manually assemble the quotes from legal sources, such as a print copy of "The Martian". Whether or not you can legally pull the data from an online source depends on the terms of service for that site. That lets out brainyquote as a source, so check the TOS for whatever source you get the material from.
If I draw something, having been inspired by looking at some other thing, you are not copying that thing. If you carefully copy something even if you are also deliberately changing features of the original, then you are copying. Copyright law gives the copyright holder the exclusive right to make copies. There is a difference between copying music and visual art in this respect, since music can be reduced to a small set of specific symbols, so "being inspired by" a musical work is often found to be infringement. The difficult part is legally distinguishing "making a copy" versus "being inspired by". The courts use a subjective test of "substantial similarity" to decide if there has been copying. the case of Mannion v. Coors. "Pose" is an element that is considered in assessing similarity: the question the court would ask (itself) is whether such a pose could ever have come from elsewhere (such as, your own creative efforts).
That would be pretty much a classical case of copyright infringement. Drawing a thing from memory is copying just as much as drawing a thing with the original before you or xeroxing a thing. The degree of match between the original and your copy may vary depending on how good your memory is, but that doesn't matter, because copyright protection is not about "making exact replicas", it is about copying in any form.
Yes, if the book was published in 1913, the copyright has expired. You can freely scan it in and publish it. But note you have NO copyright to the material. You didn't write it. Copyright law gives rights to the AUTHOR of a work. It doesn't matter how much effort you went to scanning it in and formatting it. Nothing in copyright law says that that gives you any rights. If you add anything creative of your own, you would own the copyright to the new material. Like if you drew new illustrations and added them to the book. Or if you included your own commentary. Or you added explanatory footnotes. That still wouldn't give you rights to the original text, but you would own the new material. But in the same vein, if the book was originally published in 1913, but the copy you have includes material added by a later editor, that later material might still be protected by copyright. Just a side thought, it occurs to me that if I was going to republish a public domain book, a good idea would be to add footnotes. If my footnotes appear on almost every page, then no one else could just take my electronic files and sell them himself. He'd have to go through page by page and purge out all the footnotes. Make it hard for someone to "borrow" your work and you might scare them off.