Referencing books or researches in a medium article for a potential profit So, I'm writing an article for Medium and I need to back up my words with some proofs. I found the researches all publicly available, via Google Search, some just PDF's from, some are leading to jstor.org. And my work of course is not a standalone resource, but just a review of closely related topics and results we are having up to this day. Part of the topics are common engineering knowledge, some is more specific. Is it legal to do such referencing (in any form, but with acknowledgment to origin of some data or facts I'm using) in my Medium article, if I can enable partner program and get money for that?
It is legsl to include references showing readers where facts you include in your article were derived, or where they can be supported. Indeed academic ethics generally require doing so, although there is (in most cases) no legal requirement to do so. Listing the title, author, and publication information of a source is not an infringement of copyright. That J. Jones published an article on &quot;How to Find the Purple Moth&quot; [imaginary example] in volume 28 of the Journal of Moth Science is a fact.Facts are never protected by copyright. Indeed in US law 17 USC 102(b) provides that: b) In no case does copyright protection for an original work of authorship extend to any idea, procedure, process, system, method of operation, concept, principle, or discovery, regardless of the form in which it is described, explained, illustrated, or embodied in such work. The laws of other countries are similar on this point. Indeed I do not know of any country in which facts are protected by copyright. So, including such references is fully legal, and no permission from the sources being cited is required. This is true whatever form the reference takes. In particular, if an online address for the content is included, this is still true. I do not know whether Medium, or any other specific publishing platform, will pat fees to authors based on clik-thru from such citations. That depends on their particular policies, which might be found in their Terms of Service or other policy document.
These files are not public domain Read it carefully, it only says “public domain musical compositions in a MIDI (Musical Instrument Digital Interface) file format.” The compositions are public domain, the MIDI files aren’t - they are a derivative work (a translation) covered by their own copyright. Specifically, “© Copyright 2001 University of Arizona. All rights reserved” right next to a big “Contact us” link. Literary and artistic works that are derived (legally) from existing works have independent copyright even if the original no longer does. Mozart, for example, did not write his compositions in MIDI format. Now, it may be the intention of the University of Arizona that you can use it but, if so, they have not made this clear. It’s possible that the authors (mistakenly) thought that because the originals were public domain, their derivatives would be too. The music school should have talked to someone from the law school. All of the purposes that they talk about on the “Purpose” page are equally applicable to widely licensed (e.g. everyone) or narrowly controlled (e.g. staff of the University). Overall, a prudent person would assume that these works are copyright of the University of Arizona and can’t be used without permission or a fair use exemption. Your proposed usage is not fair use. However, there is a big “Contact us” link on every page so you can always ask for permission.
Under the Berne Convention, a copyright notice is not required at all, although using one is good practice. Using one usually eliminates the claimed status of "innocent infringement", which, if found true by a court, greatly reduces damage awards. It is usual to place such notices at or near the start of a work. That is where people tend to look for them, and I don't see any good reason not to follow this practice. The book tradition is the the copyright page comes before any part of the actual work, including the table of contents, sometimes with a continuation at the end of the work, if there is more than one page of notices. But that is not now a legal requirement, if it ever was. In short, there are no rigid rules on this, but putting a copyright notice at or quite near the start is good practice, and I would suggest sticking to it.
From your question(s), as well as your various comments, I understand you to have two general inquiries: 1. Is there any infringement of copyright laws if you use things like the titles of books, games, apps, names, address (and any other number of things) which you will then put into datasets that will be licensed for proprietary commercial purposes? You may freely put titles, names of people, places or things into datasets without fear that you are infringing on copyright or any other laws. That is clear. Copyright law does not protect names, titles, short phrases or expressions. Even if a name, title, or short phrase is novel or distinctive it cannot be protected by copyright. So, there is no point in discussing the doctrine of fair use in this context, because Fair Use is a defense, or a legal safe harbor that is merely an exception to copyright infringement allowing people to use a copyrighted works under specific circumstances. As I understand your intended endeavor, you will not be infringing on any copyrights to the extent that you are merely using factual data, like names of copyrighted things for the purpose of creating a dataset or an application to help access it. This is why I say you need not concern yourself with the test for Fair Use with regard to this issue. The Copyright Office states clearly, despite what people may think, that there are no exclusive rights in brief combinations of words such as: • Names of products or services • Names of businesses, organizations, or groups (including the names of performing groups) • Pseudonyms of individuals (including pen or stage names) • Titles of works • Catchwords, catchphrases, mottoes, slogans, or short advertising expressions • Listings of ingredients, as in recipes, labels, or formulas. When a recipe or formula is accompanied by an explanation or directions, the text directions may be copyrightable, but the recipe or formula itself remains uncopyrightable. Hence, these things are not registrable under a copyright. While something may be potentially attached to or included in copyrighted material, is not in and of itself subject to the protections of these laws. If it (whatever it is) cannot be registered for a copyright, it is not copyrightable. Because copyright registration/notices have been optional since 1989, when the U.S. attached itself to the Berne Convention, whereby copyright protection is automatic as soon as a work is “fixed in a tangible medium of expression” (written down, recorded, painted, etc.) it’s protected. No notice is required. Registration only becomes required for litigation or enforcement purposes. But this is really extraneous to your inquiry anyway, as far as it applies to the actual data. When you get into copying whole databases for your purpose, that analysis is different. 2. You want to "scrub" the internet for information that you intend to put into your proprietary datasets and use for commercial purposes, some or most of which is already in a database or some organized form, and you want to know if there is some sort of copyright or duty owned to the person who originally databased the materials? Since ideas, procedures, principles, discoveries, and devices are all specifically excluded from copyright protection, if you want to compile this type of information from the internet for the purpose of creating datasets, or searchable databases, this is permissible. That said, there are protections for existing databases under copyright law, provided under the concept of a "compilation copyright". A compilation copyright protects the collection and creative assembling of data or other materials. Compilation copyrights protect the collection and assembling of data or other materials, such that databases are generally protected by copyright law as compilations. Under the Copyright Act, a compilation is defined as a "collection and assembling of preexisting materials or of data that are selected in such a way that the resulting work as a whole constitutes an original work of authorship." 17. U.S.C. § 101. The preexisting materials or data may be protected by copyright since the selections of materials and the form they take in an existing database may be original enough to be subject to a copyright. However, the data itself is merely information and is not protectable. The Copyright Act specifically states that the copyright in a compilation extends only to the compilation itself, and not to the underlying materials or data. 17 U.S.C. § 103(b). As a result, "compilation copyrights" can't be used to place protection upon those things that are otherwise not protectable. In the case of Feist Publications, Inc. v. Rural Telephone Service Company, Inc., the U.S. Supreme Court ruled that a compilation work such as a database must contain a minimum level of creativity in order to be protectable under the Copyright Act. Feist makes clear that even a copyright protected database does not hold the right to prevent an individual from extracting factual data from the database (so long as you're not copying the entire database as a whole). If you take an already compiled and copyrighted dataset in its entirety, you must obtain a license for its use. However, if you are merely amassing great amounts of data to then put into your own dataset, that you are free to do. The big issue will be (and you seem to realize this) where you will amass this data from. Some websites have specific licenses in place that say you cannot use or rework their content. However, many times these websites simply throw these license requirements out there for users to see, despite the fact that they may not be (and some would argue) are not enforceable. The courts have heard arguments that "contracts" (the end-user licenses) that protect databases and information on websites is beyond the protection available through copyright law should be "preempted" by the Copyright Act itself. The preemption argument goes like this: Federal law controlling something that is subject to interstate commerce or use, should be controlled by the federal laws. So,since the federal government has enacted the Copyright Act to govern any protections to any original works, states should be (arguably are) prohibited from having contradictory laws. Because of the ability of a federal statute to preempt state law, and the fact that the Copyright Act at 17 U.S.C. § 301 sets forth specific preemptions, no state may create rights that are equivalent to any of the exclusive rights provided under the Act. It is this concept of preemption that prevents copyright protection from varying depending upon the state where a work of authorship is created. Arguably, the same is true for the internet, and supposed contractual relationship created through licenses that dictates how non-copyrightable material may be used. In the case of ProCD, Incorporated v. Matthew Zeidenberg and Silken Mountain Web Services, Inc. the court examined whether an end-user of a CD ROM phone database was subject to the license, when they extracted a large portion of the database and made it available over the Internet. The database was almost the same as the type of data in the Feist case-The lower court rejected all copyright claims and found that the shrinkwrap license that controlled the end user's right to use the data was both unenforceable (as a shrink wrap license) and preempted by the Copyright Act. As a result, there was no relief available to the creator of the phone database and the end-user was free to extract the data and use it as he saw fit. However, on appeal this decision was reversed (7th circuit). The appellate court did acknowledge that the database (on the CD) was not original enough to be protected by copyright (finding no copyright infringement by the end-user); However, they did find the end-user was breach of contract, since the shrink-wrap license prohibited the end-user's conduct. What this tells us is that these licenses (on websites) may or may not be enforceable. While the 7th Circuit found a contract right pursuant to the license, despite the preemption argument, another appellate court that is more liberal may find otherwise. Also, this was a disk, not the internet, which is the "wild west" of information, largely unregulated and unlitigated as it pertains to the legality and enforceability of (some) regulations that do exist. License agreements for site use on the internet are everywhere. If you take a database from some site that has a license saying you cannot take their work and add to it, or whatever, and you do add it to other databases that are not licensed and then make your own dataset - chances are you are NOT going to be infringing on anyone's copyright. That said, you may be in breach of contract (the license) if they find out about it, and sue you (using it doesn't put you in breach; only getting sued and having a court determine you're in breach puts you in breach. It may be a distinction worth contemplation, but that is up to you). The safest, bet would be to get a license from them to rework the materials. If the material is generic enough, and will be changed enough, that you are creating your own new (copyrightable) work - I'm not sure how they would know you "scrubbed the data in contravention of their license agreement ( I have NO CLUE if there is coding or metadata attached to it such that it's identifiable in that way. I have not tech background and do not endorse taking what's not yours). But if they can and do know, they could cause problems for you. Lastly, I will just say that the internet is littered with sites that claim copyrights, or impose unenforceable licenses on material that is ripe for public use. Just because it says it's theirs does not make it so. The inverse is also true. Just because a site does not claim copyright to something, does not mean it is in the public domain. I would recommend either sticking to public domain/use sites for your scrubbing endeavors, or seeking permissions from the sites who impose licensing requirements. Short of that, I would recommend (as I already have) seeking an formal legal opinion to say that you are not imposing on anyone's copyrights (this could only be done once you showed an attorney every place you took material from, as well as what the material is), and that the licenses from sites with generalized information that may try to limit use, are unenforceable. I would do this before you invest a lot of time or money into something that is largely based on the accumulation of other peoples work product. I wish there was an answer certain, but there just isn't without seeing everything in the end.
The text of an ancient manuscript would indeed not be covered by copyright. A translation into a modern language normally would be protected by copyright. (Unless it is purely a machine or algorithmic translation.) The formatting of a publication could ber protected by copyright, but only if it includes some significantly original element. (In the US, and in many but not all other countries, only original works or original aspects of works may be protected by copyright. Thus where the copyright is for format the format must include an original element or elements.) If the format was a normal one for the type of publication, ther would be no original content to protect, and so no copyright at all. A work alleged to infringe a copyright on the format would need to be shown to have copied an original element or elements of the prior publication's format.
The author of the book may have a copyright, because he created a new piece of work from the/a original work. For example, by translating it in another language or in a modernized language, by rearranging the content, by adding images or commentaries etc. You will therefore have to find a book or other source that is not or not anymore copyrighted.
If the app (and the service accessed from the app) truly doesn't have any EULA, ToS, or license agreement, to include restrictions on reverse engineering, you can probably create an alternate front end, so long as you aren't using their logos, etc. However, their data may be a different beast, depending on the nature of it. For example, extracting data from Twitter would potentially violate Twitter's license on the original text copyright held by the authors in question. Wikipedia explicitly includes redistribution in their license agreement with authors/content creators. If all you are extracting and storing is the temperature at a particular weather station, you might have less of a concern. Anything beyond merely factual runs the risk of a copyright infringement as you store the data in your own database.
You Own The Code To answer your question on whether or not it is copyright infringement: Yes, you do own the rights to the written code but posting it on Github gives Github the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it. To simply put it, no matter what license you use, you give GitHub the right to host your code and to use your code to improve their products and features. This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive your Content. So with respect to code that’s already on GitHub, I think the answer to the question of copyright infringement is fairly straightforward. Things aren’t quite as clear-cut in a scenario where Copilot is trained on code that is hosted outside of GitHub. In that situation, the copyright infringement question would hinge largely on the concept of fair use. If Copilot is being trained on code outside of GitHub, we accept that at least some of what they’re looking at is copyrightable work. So, the question then becomes if it’s fair use. Now, you ultimately can’t conclude definitively that something is fair use until you go to court and a judge agrees with your assessment. But I think there’s a strong case to be made that Copilot’s use of code is very transformative, a point which would favor the fair use argument. There is precedent for this sort of situation. Take the case of Google Books, for example. Google scanned millions of books, provided people who were doing research with the ability to search the book, and provided the user a small snippet of the text that the user was searching for in the book itself. The court did in fact find that was fair use. The use was very transformative. It allowed people to search millions of books. It didn’t substitute for the book itself. It didn’t really take away anything from the copyright holders; in fact, it made it easier for readers to access the work and actually opened a broader market for book authors. And, it was a huge value add on top of the copyrighted corpus. In the latter scenario, a lot depends on the thoroughness and the length of Copilot’s suggestions. The more complex and lengthy the suggestion, the more likely it has some sort of copyrightable expression. If a suggestion is short enough, the fact that it repeats something in someone else’s code may not make it copyrightable expression. There’s also the question of whether what’s being produced is actually a copy of what’s in the corpus. That’s a little unclear right now. GitHub reports that Copilot is mostly producing brand-new material, only regurgitating copies of learned code 0.1% of the time. But, we have seen certain examples online of the suggestions and those suggestions include fairly large amounts of code and code that clearly is being copied because it even includes comments from the original source code.