Can I write my signature in my conlang&#39;s script? Can I write my signature in my conlang's (constructed language) script, which consists entirely of straight lines? If not, why?
Legally, yes. A legally binding signature doesn't have to be written in cursive, or in English, or even be your name, or any text at all for that matter. The purpose of a signature is to identify the person who is signing the document, and to indicate that they have understood and approved the document. So long as you have a reasonably unique and reproducible mark, your signature can be pretty much anything, from your name, to a pseudonym, to pictograph. A classic trope in media is for pirates or peasants or other illiterate people to simply sign contracts with an &quot;X&quot; or to &quot;make their mark&quot;, since they are unable to write their own name. Now, using things other than your name written in cursive might be frowned upon and difficult to implement in practice, since a pictograph can't be as easily linked to an individual as a name can, and signing a contract with something other than a recognizable form of your name is a downright unusual way to conduct business. When signing for a mortgage, for example, a lender might get fears that you're trying to defraud them if you start signing all your documents with a smiley face. But in principle, signing a mortgage with a smiley face or conlang script is exactly as binding as signing your real name in cursive. Local laws may vary in what constitutes a signature, but it seems this is generally the case.
Your understanding of the GPL is a bit off. GPLed code doesn't generally force you to GPL the output of the program, but that's just because the output of the program is normally not a derivative work of the program. For instance, if you write a novel in Emacs, your novel is an entirely original work. The fact that you used Emacs as a tool doesn't mean that your novel is somehow based on Emacs. This generator is different. It generates sprites by putting together art assets made by the program's creator. That means that the output contains a substantial amount of content made by the program creator, which means that it would likely be covered by the program creator's copyright. If the content was licensed to you under the GPL, you normally have to abide by GPL restrictions when you redistribute the content or incorporate it into your own program. Copyright holders can, if they want, grant additional permissions to their content and allow you to incorporate that content into nonfree software. For instance, the GCC compilers have an additional permission for their runtime libraries to let you use them in any GCC-compiled code; without that permission, GCC could only be used to compile GPL-compatible code. But unless the copyright holder has granted those permissions, when program output contains large amounts of their copyrighted content you're bound by the GPL when using it. In this case, the program specifically says that the art is dual-licensed under GPLv3 and CC-BY-SA-3.0. Since the generator's output is a combination of premade art assets (the buttons just let you tell the program which art assets to combine), the output is a derivative work of those assets. You can't use it unless your use is compatible with the GPL v3 or CC-BY-SA-3.0 (either works, since dual licensing lets you pick either license).
To use an API over a network connection (as opposed to, e.g., the Windows API), a user communicates a request to the API host, or server, and awaits a response. The host of the remote API can refuse to serve requests from users for probably any reason. Such services often require users to accept a license as a condition of using the service, and they may charge a fee as a condition of the license. A license to use a service is obviously not necessarily bound to a license for the use of its source code, just as the ability to reach the service is not dependent on the ability to see (let alone use) the code in any format, whether it be the source code or some compiled form of the code. In essence, source licenses and service licenses have different primary goals, at least inasmuch as the source license seeks to restrict someone who has actual physical access to compiled code, and possibly source code. Service licenses do not have that concern, though I have seen service licenses that also prohibit decompiling. This is probably the result of a CYA attitude among lawyers: the language is already in the standard software license text, and it doesn't hurt anything to leave it in, and it could help if a service user somehow managed to download the program code.
I've seen prohibito used in a few places, but never by any source that I'd use as a model for my writing. As I understand it, the Latin names for the other writs were adopted in medieval times, when Latin was much more heavily used in the English courts, while the writ of prohibition developed centuries later. In that case, I think it would have been natural to simply give it a standard English name.
In theory "legalese" is English: you will find every word in the dictionary, and the rules of grammar are exactly the same. However in practice it is true that legal documents are often written in a very specific style. There are a number of possible reasons for this: The document must say what it intends very precisely. Most regular language is quite sloppy and ambiguous, but lawyers share with computer programmers the need to ensure that what is said is precisely what is meant. A legal document exists within a legal system in which certain words or phrases carry very specific meanings. For instance in the UK the words "in trust" when talking about money or property will automatically import a huge body of law (and its also possible to have that law apply even if you don't use the magic words). Lawyers know about these things, and will write a document to either invoke or avoid those bodies of law as they see fit. Related to (2) above, laws and legal precedents give lists of things that must be done or proved. Legal documents will often follow these lists using the same terms in order to avoid future challenges. For instance US patent law specifies what must go into a patent application, so you had better follow the format and use the same subject headings. Within patents in particular, the patent office manual allows a patent to be rejected because of informal language that leaves the patent unclear. Patent lawyers and examiners have evolved an informal set of conventions about how things are said. If you use these conventions the examiner will have a much easier time understanding what you mean. Its not "cargo cult", more a specialised language. (Note: the following is about the US patent system, but similar considerations apply everywhere.) Lets take a look at an example patent picked at random: The abstract lists the key elements of the invention in very abstract terms, such as "vibrating mechanism" and "power source". If you were writing this in "informal" language you might mention a specific power source such as a battery. But doing so limits your invention: what if something other than a battery (such as a super-capacitor or spring-driven generator) is used? That would be a separate invention not covered by your patent. So patent lawyers take time to think and ask about generalisations. The next interesting part is the Claims. These set out precisely what is and is not covered by the invention. If the Claims don't cover it then its not in the patent. The format of each Claim is defined in 35 US 112, so if you don't do it like that it won't count. Finally we get to the Description. This is intended to explain the invention to "any person skilled in the art". It also needs to explain the prior art and show why the invention is new and useful, because those are statutory requirements. Much of this is in fact written in an ELI5 way, if the 5-year-old had swallowed a dictionary. The reason is that any little thing omitted or assumed can be used by a future challenger claiming that the hypothetical "person skilled in the art" would have failed to understand or know it. So lets take a sample paragraph from this patent (numbers refer to diagrams in the patent): The electrical connection 22 may include a circuit device that transforms a DC power provided by the power source 26 to AC power for the vibrating mechanism 28, which circuit devices are known to those having ordinary skill in the art of circuit design. This anticipates a possible variation on the invention and stops it being patented separately. It asserts that the "circuit devices" are known, so it doesn't need to describe them in detail. If that assertion wasn't there then someone might challenge the patent on that point, but since the assertion has been accepted by the patent examiner it is presumed to be correct. Note the "... ordinary skill in the art ..." phrase: this is explicitly calling out to the language in Title 35. You might imagine that such a variation would be obvious, and therefore not patentable. However it is very difficult for a court to decide in hindsight whether something would really be obvious to a person skilled in the art; you wind up with each side hiring expert witnesses who will give competing testimony as to whether it seems obvious to them. As a result the courts have set a very low bar to a claim that something is "non-obvious". The language used throughout a patent is of vital importance: infringement cases can hinge on the most trivial of linguistic issues. This blog post by a patent lawyer has a list of examples, including this one: For example, in Chef America, Inc. v. Lamb-Weston, Inc., Chef America tried to protect a cooking step for heating a dough at a certain temperature inside an oven. But Chef America drafted the claim to read “heating the . . . dough to a temperature in the range of about 400 degrees F. to 850 degrees F.” The Federal Circuit reasoned that “to” is not “at” and, thus, the claim required the dough (not the oven) to be heated to the specified temperature. The Court then ruled that the claim was not infringed. In fact, under the Court’s claim construction, this claim could not possibly be infringed unless one wanted to make burned dough. See also this case on "partially" not including "totally", and this post on why the word "disclosure" is now used instead of "invention". Patent lawyers call this kind of thing "patent profanity", i.e things you simply do not say. So if you don't use this kind of "legalese" in your patent the following things are much more likely: Your application will be rejected because the examiner cannot understand exactly what your invention consists of. Trivial variations on your invention will turn out not to be covered. Someone will challenge your patent on the grounds that you didn't explain everything that a "person skilled in the art" might need to know.
The CC-ND license seems to be what you are looking for. However, Sec. 2(a) has two conditions, one allowing copying and distribution of the unmodified original (as stated in A), but also allows the user to modify but not distribute a modified version of the work (they may "produce and reproduce, but not Share, Adapted Material"). This would mean that a reader could rewrite your paper, as long as they keep it to themselves. If this bothers you, I think you could not rely on a standard named license, instead you'd have to provide your own – such as CC-ND 4.0 without clause (2)(a)(B). Rewriting a legal document is a risky proposition, even for a legal professional, because you have to carefully think through all of the implications of any new punctuation, adjectives, and deletions. If you contemplate deleting clause (2)(a)(B), you should come up with a line of reasoning that compels you do delete it in order to accomplish your goal, and check that the deletion doesn't thwart that goal. That is why people pay money to lawyers (and also why you need to make your goal clear to that lawyer, lest the agreement be inconsistent with your goal).
This can't be right. If I modify open source code as part of the work done, by nature of the open source license that code can not become intellectual property of the client. Certainly it can. That which is "developed or produced" would be the modifications to the pre-existing code, i.e the copyright on the derivative work so created. If the base code was under a share-alike or copy-left license, then the client can only distribute it under the same license (or a compatible one, perhaps). But nothing compels the client to distribute it, and for the client's use, the client owns the copyright, without fear of any future claims by the contractor. If I have my own code/scripts/settings/templates/etc that I use as a contractor, and I modify those in the interest of coding efficiency in the interest of serving the client, it hardly seems correct that these assets become property of the Client. Those are your work, and you can choose whether to sell the copyrights to the client or not. Again, only the work done for that client would be covered under the wording quoted above, unless there is another provision that grants the client a license to use the pre-existing work which you modified for the job, which there probably ought to be. Or I suppose the agreement could assign copyrights in pre-existing work to the client, but that seems an odd choice, and the language in the question would not do that. You and the client could agree on a different provision such as: The contractor grants to the client a fully-paid, non-exclusive permanent license to use all intellectual property developed under this agreement, and any pre-existing works that may be incorporated therein. The contractor warrants that s/he is entitled to grant such license, without infringing on the intellectual property of any other person or entity. That wording would have the contractor retain all copyrights and other IP, but provide a license to the client to use it without further payment or expiration. Many other ways to structure such a provision are possible, dividing the rights up however the contractor and client can agree. The price for the work might vary depending on what rights the client obtains. Both forms, and many others, are perfectly legal, it is just a question of what the contractor chooses to sell, and what th4e client chooses to buy.
Legalese is not required You can and should write a will in plain English. However, you need to ensure that your simple wishes can: Actually be understood, Actually be implemented, Don't have unintended consequences, Cover all bases. Use a lawyer I suggest that you write your simple wishes out as you have done and take them to a lawyer. A good lawyer will be able to: Draft a will and have it executed so that it complies with the law, Keep a copy of the will so that your executor can find the damn thing without having to tear your house apart, Consider the contingencies that you haven't. My lawyer charged me and my wife $150 each - 20 years latter the estate has twice as many children and would be worth several million dollars; I consider it one of the cheapest pieces of insurance I have ever bought. Contingencies Who is the executor of the will? This is the person who administers the estate until it is finalised. As written, you haven't named one: in most jurisdictions this makes the government's Public Trustee the executor. How and how much will the executor get paid? Executor's are entitled to be paid for their services. What happens if you and your wife are separated or divorced at the time of your death? Wills are not automatically terminated by these events. What if Bob is dead before you die? Or has emigrated? Or is insane? What if Bob dies in the same car crash that kills you and your wife? What if Bob dies after he becomes the trustee of the trust? Who will be your child's guardian? As written, Bob is responsible for the finances but he is not the guardian. The child would be reliant on kinship guardianship or become a ward of the state. For what purposes can Bob use the trust money? Education of the child? Vacations for the child? His own gambling problem? Can the trust borrow money? What types of investments can the trust make? Bolivian palm tree futures anyone? Does Bob need to get professional financial advice about this? Who will audit the trust to ensure Bob is behaving appropriately? Your wife falls pregnant tomorrow. Do you want to write a new will or have one that works no matter how many children you have? What if all 3 of you die in the same car crash? Who gets the estate then? Only people with no assets or dependants have a simple estate