Am I authorized to publish a solution manual for a book I haven&#39;t written? Bob wrote a solution manual for book X. (solution manual = a manual that presents solutions for some/all exercises of the book) Is Bob authorized to publish it, given that Bob hasn't written book X and doesn't own any right on it? Book X was written and published in the United States, and Bob plans to publish the solution manual in the United States (either on Internet or on paper, and either free of charge or with a charge).
Bob is not authorized, but he may legally do so (in the US, you don't need specific authorization to perform a non-forbidden act). In creating the manual, Bob would need to avoid reproducing the questions (which are protected by copyright), and just give the answers. Copyright protection for the textbook includes not just the actual words, but also organizational structure, so Bob would need to avoid copying the structure of the exercises. As for "structure of the exercises", textbooks often have exercises for each chapter, with a clear logic to the order and content of chapters. Within the chapter exercises, there is often some rationale to the order of presentation of the dozen exercises, like starting for with simplest concepts presented in the text and moving up the ladder. In a given exercise, there my be subparts, where understanding part 1 leads you to understanding part 2, and so on. In a well-structure textbook, maybe 20% of the creative nature of the book is that artful ordering. Imposing an entirely different order on your solutions avoids copying the author's protected expression.
Primary Theory I suspect there might not be a legal answer to this question. I have always suspected a sort of pseudo-intellectual elitism (or simple preference or carelessness) with passive voice sentence construction in general. I sense license writers have not (yet) escaped this general trend. I would love someone to prove this theory incorrect. But, alas, I doubt it will happen. Alternative Theory But because this is a Law Q&amp;A site, I will advance the following alternative theory. I don't believe it's correct. But I will advance it because it's the only possible explanation I can think of that might be even remotely based on legal reasoning... Maybe they are just basing their construction on the way the law itself is written? For example, if the law says, "Permission must be granted..." Then it would follow that a writer who wants to comply with the law might choose, "Permission is hereby granted..." instead of something like "The authors hereby grant permission..." or, as the OP suggested, "You may..."
Links are in French. As the author of a work, you would generally hold copyright unless there's a contract otherwise. L113 of the Code de la propriété intellectuelle determines who is the rights holder of a given work and I don't see anything there that changes things for you as a contractor. Even if you assigned some rights to your employer through a contract, France has moral rights which can never be ceded. In fact, even if you were a salaried employee, you still hold the rights by default, unlike the US. There are a few exceptions to that though: software, inseparable joint works, and works where the creative process was purely directed by your superiors.
The MIT License (as distributed by OSI) does not include an attribution requirement beyond the requirement to include the copyright notice in any re-distributed copy including derivative works. The same is true of the description of the license as described in the Wikipedia article. If you sent back to the maintainer a modified version including your own contributions with an MIT license notice and your name in the copyright statement, that is a new work released under that license. The maintainer (or anyone else) may not lawfully use your work or incorporate it into a new derived work without complying with the license terms, which require retaining the copyright notice. By distributing the combined work using a copyright notice not including your name, it would seem that your license is being violated. You could contact the maintainer with a request that your name be included in the notice or your contributions be removed. If that is not accepted, you could use a take-down notice, or file suit. That last would involve significant costs, of course.
The text may be public domain in the United States It depends on when it was created/published. The eBook is subject to its own copyright The eBook itself is a derivative work and subject to its own copyright protection. The translation of an ink and paper book into an eBook contains enough artistic choice to trigger copyright protection. If the original is really public domain, you can copy the text but not the eBook.
In most countries, there is a standard format for citations. The guiding principle behind these is to make it easy to verify the law says what you claim it says. So you only need to give information needed to find the law you are citing. Usually, citations go the opposite of your example -- they start with the most general reference, and get more specific. Also, most citations only give information for sections that are numbered or lettered. Unless sentences are numbered or lettered, I would not cite them. For example, to find something in the US code, we need to know the: Title/Chapter/Section/subsection...and so on. For example, the federal law prohibiting the ownership of machine guns is in US Code, Title 18: Crimes and Criminal Procedure, Ch 44 Firearms, § 922 Unlawful Acts subsection (o)(1). Since sections are numbered consecutively, we usually leave out the chapter: 18 USC § 922(o)(1). In Ukraine, it appears law is organized into Codes, Chapters, Articles and Sections. Since Articles are numbered consecutively, we can leave out the Chapters. Thus, the citation for the definition of murder would be Ukrainian Criminal Code, Art 115 § 1. Caveat: I am not an expert in Ukrainian law and may be wrong on some details, so you should look at some Ukrainian legal sources to double check.
Per the comment, the applicable license term seems to be Licensee agrees to maintain in confidence the source code version of the Licensed Software by using at least the same physical and other security measures as Licensee uses for its own confidential technical information and documentation, but in no case less than reasonable measures. So if your own code is on a physically unconnected thumbprint-secured blah blah blah computer deep in a mountain, with files encrypted, so must theirs be. If yours is stored in &quot;the cloud&quot; with decent password protection, theirs must be as well. This seems to describe your Github use (I don't have any knowledge of the degree of hackability of private Github repositories). The legal judgment as to whether this is &quot;reasonably secure&quot; is based on whether a prudent person would know that it is practical to gain unauthorized access. Protecting a file with the password &quot;password&quot; would probably be found to be unreasonably insecure.
In the US, the author would be able to wind an infringement lawsuit against the re-publisher. Title 17, the US copyright law codified, grants the author the exclusive right to authorize republication, and does not require that a person use their real name. The argument "It was on the internet, it's in the public domain" is utterly without legal merit. The same goes for the assertion that a person loses his rights if he is uncontactable. The author has stated the terms of the license, so there isn't even a reasonable argument that the infringement is innocent (unknowing: "I thought it was with permission). There is no requirement that you have to allow a potential user to hassle you about the license terms. The one thing that is special regarding anonymous and pseudonymous works is that under 17 USC 302, "copyright endures for a term of 95 years from the year of its first publication, or a term of 120 years from the year of its creation, whichever expires first". For a work whose author is identified, copyright "endures for a term consisting of the life of the author and 70 years after the author’s death". This assumes that the host site has not preempted author's license: Stack Exchange, for example, preempts an author's exclusive right, so you can copy stuff from here accorting to the SE terms of usage.