17 ms·
Poor writing, not specialized concepts, drives difficulty with legal language
- BMc2020 4y agoCtrl-F "slate card" The political party of your choice in the county you live in should have a slate card of how to vote on all the measures.
- torstenvl 4y agoSomething I think would be helpful would be to replace a "definitions" section with a "terms" section, with three subsections: General Terms of Art provide a vernacular English explanation for widely-used legal terms within the section. Example: "Joint tenants. A legal term meaning that the tenants not only hold a single undivided parcel together, but that ownership of the property passes to the other tenants if one tenant dies. If a tenant sells their interest, and the remaining tenants entered into a joint tenancy at the same time and on the same deed, the remaining tenants remain as joint tenants." Specific Terms of Art describe terms of art used in the particular contract or act. An example would be "protected health information" or "covered entity" in the context of HIPAA. Terms of Clarification are standard vernacular English terms that, for the sake of reducing frivolous navel-gazing, are defined precisely. An example would be "uniformed services" within Title 10, or "machine gun" in the Gun Control Act. A layman could read the two terms of art sections and should be able to understand most statutes or contracts. A lawyer familiar with the general terms of art could read the specific terms of art and understand most statutes or contracts. Terms of clarification could be consulted only if the precise scope of a term becomes an issue.
- bertil 4y agoThis is absolutely the same with science.
- zaphod420 4y agoWhy can't they just use normal English language for contracts? How did it get to be this way?
- Tomte 4y agoFor the same reason why programmers can't just use normal English when talking about software.
- pessimizer 4y agoSo because the computer doesn't understand English, or because the terminology is often new and constantly changing?
- choudharism 4y agoIn a way, both - along with a third reason. English (like any natural language) is ambiguous and often depends on context. The attempt to "reinforce" ideas in English so that there is no way to have different interpretations is what lands you with legalese. Imagine having to program with that.
- PeterisP 4y agoBecause normal human language doesn't describe things exactly and exhaustively specifying the edge cases; as soon as you need do that (and you do, in law, programming, math proofs, etc), even if you don't use a single specific term you get language that looks like legalese. In essence, none of the commonly used English words means exactly what you need to, so you need to add many explicit qualifiers to specify which parts of that wide and vague meaning shall apply and which shall not.
- deleted 4y ago[deleted]
- Sebguer 4y agoNormal English evolves. Contracts rely on precise, shared understanding, and so it builds up its own jargon and shibboleths to represent concepts that everyone can have a singular understanding of. You don't want there to be any ambiguity in your contract, or any chance that courtroom precedents may not apply because your language differed from the 'norm'.
- akie 4y agoThis is the same in any advanced academic field. Ever tried talking to a sociologist or a philosopher?
- r3trohack3r 4y ago> There was this sociologist who had written a paper for us all to read ahead of time. I started to read the damn thing, and my eyes were coming out: I couldn’t make head nor tail of it! I figured it was because I hadn’t read any of the books on the list. I had this uneasy feeling of “I’m not adequate,” until finally I said to myself “I’m gonna stop, and read one sentence slowly so I can figure out what the hell it means.” > So I stopped-at random-and read the next sentence very carefully. I can’t remember it precisely, but it was very close to this: “The individual member of the social community often receives his information via visual, symbolic channels.” I went back and forth over it, and translated. You know what it means? “People read.” > Then I went over the next sentence, and realised that I could translate that one also. Then it became a kind of empty business: “Sometimes people read; sometimes people listen to the radio,” and so on, but written in such a fancy way that I couldn’t understand it at first, and when I finally deciphered it, there was nothing to it. — Richard Feynman
- mistrial9 4y agohow about a museum historian !! I have a large vocabulary, and after a certain presentation, it seemed obvious to me that anytime one word could be used, three obscure words were its replacement.
- rickard 4y agoI think that it’s pretty relevant that this is from this year’s Ig Nobel prize winner in literature: https://news.mit.edu/2022/mit-cognitive-scientists-win-ig-nobel-shedding-light-legalese-0916 https://news.mit.edu/2022/mit-cognitive-scientists-win-ig-no...
- Our_Benefactors 4y ago> (b) suggest such processing difficulties result largely from working-memory limitations imposed by long-distance syntactic dependencies (i.e., poor writing) as opposed to a mere lack of specialized legal knowledge; It seems like a misrepresentation to call “long-distance syntactic dependencies” in a legal document the same thing as poor writing when comparing to other genres of written English including those that are written for pleasure. When exploring law the question an individual usually has is “If I do X, does Y happen?”. But legal frameworks don’t cover individual situations, they paint broad strokes over the human experience.
- johndhi 4y agoI'm guessing what they mean with long distance dependencies is section 3 of the contract sets one scenario and section 46 an exception to it. This happens (normally, intentionally) when there is a section up front or at the end that sets defined terms. It also happens in a way we lawyers agree kind of sucks but whatever who cares - when after a long negotiation we're adjusting one small point and don't want to go through the effort and consternation of rewriting the whole thing. Legal negotiation culture states that the longer/more involved your edits, the more presumptively unreasonable they are. So there is low incentive to rewrite something to make it "read better."
- Jtsummers 4y agoNo need to guess, they give an example of the kind of thing they mean: > “In the event that any payment or benefit by the Company (all such payments and benefits, including the payments and benefits under Section 3(a) hereof, being hereinafter referred to as the ‘Total Payments’), would be subject to excise tax, then the cash severance payments shall be reduced.” "center-embedding" is the term they use to describe this, note the long interruption of the primary sentence due to the embedding. A suggested alternative which removes the embedding making the primary sentence easier to understand: > “In the event that any payment or benefit by the Company would be subject to excise tax, then the cash severance payments shall be reduced. All payments and benefits by the Company shall hereinafter be referred to as the ‘Total Payments.’ This includes the payments and benefits under Section 3(a) hereof.”
- abhinai 4y agoSame with academic papers. Most of my efforts go into dealing with constant loss of attention that happens when I have to look up unnecessarily complex words or improperly defined symbols and variable names. I feel stupid until I realize that the paper is actually about a very simple concept. It doesn't have to be this hard to read.
- rq1 4y agoThat's the process of understanding no?
- pas 4y agothe problem is that journals have this fancy dream that they are still the communication medium between peers of the field, who are equals and up to speed, and they are simply exchanging notes on their eminent thoughts and theories. yes, that probably also happens every once in a while, but they should adopt a rule to assume that readers are absolutely not the seminal trailblazers of the field. [of course no need to go back to Simple English Wikipedia level] there's ample space in journals. no need to hide stuff in spreadsheets in the supplements. paper authors should write the fucking thing down with precision and accuracy. yes, of course cite things, but also they should finish their thoughts, spare the reader the endless goose chase. no need for the standards smug remarks that communicate absolutely nothing just namedrops citations. understanding should not be an adversarial process. (Socratic, yes, but that's cooperative/constructive.)
- johndhi 4y agoI am a lawyer who works with but doesn't do a MASSIVE amount of contract writing like some. I don't think "poor writing" is the right phrasing here, which implies ignorance or ineptitude. I think the reason contracts aren't readable to laypeople is because laypeople aren't the intended audience. We all know no one reads these, so we write them to future lawyers and courts who might want to get our clients in trouble. We try to create loopholes for our future selves.
- swayvil 4y agoI imagine that a contract must be written for the malevolent reader. The opposite of generous. Striving not to communicate, but to preemptively win every possible argument. An airtight construction. Quite different from a conversation. Well, an ideal conversation anyway. Internet conversations seem to be more combative every day.
- johndhi 4y agoWhat you're describing is more applicable to a motion filed in court (one party is in battle with the other and has no reason to be friendly to the other party at all). In the case of contracts, you're partially right, but it's more nuanced. The weird thing about contracts is that at the time they are signed, two parties need to agree with each other. If you're hiring a software vendor and I am your lawyer, I need to try to achieve two things at once: protect the company legally, but also sign the deal so that you can use the vendor. So I'm inclined to be somewhat friendly with the other side and to forego "air tight" legal defense of my side so that we can reach agreement. Unfortunately this process has a side externality for clarity: we negotiate little parts of a template and the way we do so probably doesn't jive all that well with the template language.
- johndhi 4y agoActually, clarification: what I'm saying applies to contracts between two sophisticated parties that are negotiating. If I'm Facebook and you're a user, there is no negotiation. So I try to make it as air tight as (legally) possible.
- gumby 4y agoTBF those structures do exist for a reason. Just take the “Total Compensation” as an example. Breaking it out as shown in the paper does work, but now some language is repeated; in an edit (and most contracts are edited rather than being created de novo) one of the duplicated clauses could be edited and the other overlooked, especially if they become separated by successive edits. I’m sure there are obscurantist
- dctoedt 4y agoThe inconsistent-edits problem is a real one; failure to follow D.R.Y. cost a Dallas lender $693K because a guaranteed repayment amount was written as "one million seven thousand dollars ($1,700,000)" and words take precedence over numbers, so the lender was repaid $1.07 million and not $1.7 million. In another example, the agreed deadline for a party to cure a breach of contract was written as "fifteen (30) days"; the breaching party cured before day 30 but after day 15 — which was too late, because the other party had already terminated the contract, and the court agreed that words take precedence over numbers. So D.R.Y. is a sound guideline to follow in contracts (within limits; it's not an absolute, ironclad rule). More: https://toedtclassnotes.site44.com/Notes-on-Contract-Drafting-2021-01-22.html#dont-repeat https://toedtclassnotes.site44.com/Notes-on-Contract-Draftin...
- swayvil 4y agoThe sheer verbosity of the average person on the internet has always amazed me. You can't say anything in less than 3 solid paragraphs. Sometimes I wonder if the problem is mine. It certainly seems a hinderance to communication.
- Victerius 4y ago
- thrown_22 4y ago>The top comment in this other HN thread: https://news.ycombinator.com/item?id=32888730 https://news.ycombinator.com/item?id=32888730 I don't get it. That post is great. The lead is at the top. It's highly visible and you don't need to read anything else if you don't want to. The rest is just a long form explanation of why they like physical books.
- georgeoliver 4y agoI couldn't agree more. If it's true that most in-person communication is non-verbal, I wonder if people then try to over-compensate with their prose. Maybe technical documents need more emoticons.
- Quarrel 4y agoI've been a CTO at companies in various bits of the Anglosphere, and signed contracts in all of the bits (and some other places). I'm also married to an Anglosphere lawyer (which gives me lots more exposure than I might have guessed to the idiosyncrasies of the profession). In my experience, I very much agree with the headline (and abstract) here, but would emphasise that the US is the worst for archaic language, creating a worse barrier to entry. Most other countries in the Anglosphere have been through a "plain english" language push in both contract & legislation, while the US has stuck to "this language is proven through precedent" more stubbornly than anywhere else. This seems to be particularly prevalent in IP law, although that might be my tech bias showing. I would very much argue against those (even in this thread), that say that the lay-person isn't the intended audience for lots of contracts, particularly for T&Cs where they are often written by a contracts lawyer, for a contracts lawyer or judge, but should ABSOLUTELY be written for the lay-person to understand. Anyway, I think the legal profession can & should do better.
- pclmulqdq 4y agoAmerican patents are written in a language that isn't English. It's very precise if you can learn to read it, though. The same seems to hold for contracts, but to a lesser degree.
- deleted 4y ago[deleted]
- AlbertCory 4y agoUsually when people say this, they mean the claims. The specification, which most engineers read, are not constrained by legal precedent.
- _ggwa 4y agoI'm a patent examiner and I can't agree with "It's very precise if you can learn to read it". A large fraction of patent applications I've worked on are unclear. I even wrote a linter to help catch some problems. (DOC lawyers make me add this: This post is just my personal opinion, not that of the USPTO, DOC, US govt., etc.) Edit: I will agree that patent claims can be precise, but so can normal English. I think patent claims are too often not precise.
- f1shy 4y agoBut one of the most basic principles of the legal system, is that you cannot defend yourself based on not knowing the law... This is a big problem all around the world.
- torginus 4y agoI think this "poor writing", as in hard to understand writing with long backreferences is due to the same reasons as why many academics are terrible at explaining things, as well as why source code is hard to read. I should know, others usually like pointing out how terrible I am at explaining things. And I think I know why. When I make a naive attempt at describing a complex, interconnected concept, such as a piece of math, or a program that does a thing I start with a mental picture - a graph of interconnected concepts. Then I try to describe the picture - the same way one would describe a painting. I describe each visible part separately, often in great detail, then I try to describe the links and interconnections between parts. This sort of 'accurate' descriptive style naturally leads to huge backreferences, and people usually have a ton of trouble following along. However I think there's a way of getting your point across - one basically needs to reproduce the thought process of how one would come up with the given model given the real world constraints, illustrating the issue and its proposed solution with examples. It is often said that people are much better at deriving the rules from a few examples than the other way around. However this sort of descriptive style takes both a lot of effort, and usually is less precise, which often is not acceptable, such as in the case of contracts or computer code.
- ilaksh 4y agoGood point at the beginning about how serialization of complex structures works, but false conclusion. Good writing, just like good code is well-factored and self-documenting. Easy to understand identifiers, short functions. What you suggesting is the equivalent of writing a module using a long string of function calls, some of which have very non-obvious meanings, and claiming that there isn't a way to factor it out.
- thechao 4y agoBuild a simple model you can explain in a few sentences; perhaps accompanied by a simple picture. Elaborate details in each important direction, separately. Finally, describe unusual complications that arise when different elaborations are combined. Use a narrative voice when there's a process to explain (but, be sure to use numbered statements!). Use a well-known top-level article structure to help familiarize your reader — but be sure they know to expect that structure. Finally, always edit for clarity.
- eimrine 4y agoIs there an interpreter from legal language to human? Here, from the comments, I understood that the fact that no one reads the licenses is kind of intentional, for reasons that you can find on this page. This means that someone has to write a translator.
- hn_throwaway_99 4y agoFor everyone commenting "laypeople aren't the intended audience", this monstrosity was a recent Texas constitutional ballot proposal, i.e. all voters in the state were asked to vote on it: > The constitutional amendment authorizing the legislature to provide for the reduction of the amount of a limitation on the total amount of ad valorem taxes that may be imposed for general elementary and secondary public school purposes on the residence homestead of a person who is elderly or disabled to reflect any statutory reduction from the preceding tax year in the maximum compressed rate of the maintenance and operations taxes imposed for those purposes on the homestead. I have an Ivy League education and I still could hardly understand it, and I still think some of the language is ambiguous (i.e. I think "the reduction of the amount of a limitation on the total amount" can be interpreted both ways). https://www.dallasnews.com/news/watchdog/2022/03/25/the-language-in-a-may-vote-to-lower-texas-property-taxes-is-so-confusing-that-its-incomprehensible/ https://www.dallasnews.com/news/watchdog/2022/03/25/the-lang...
- hnick 4y agoI wonder if it's a programmer thing, but as I read that I realised I was mentally bracketing related words together almost like a token parser to build a syntax tree.
- eru 4y agoDescribing it like that is a programmer thing, but the mental operation itself might be more common?
- johndhi 4y agoLol. Brutal
- zo1 4y agoWhoever wrote or approved that should be fired. Whether they are a lawyer or politician, it matters not. To parse it one needs to write it out, draw brackets around concepts, and then add lines between the potentially-grouped concepts because there is so much in-between that you forget it all by the time you get to the end.
- dctoedt 4y agoLawyer and contract-drafting teacher here. The biggest problem with unreadable contracts is that we have too many L.O.A.D.s: Lazy Or Arrogant Drafters. (You can decide for yourself: L.O.A.D. of what?) There's a relevant Dilbert cartoon: [0] To simplify contract language, the biggest bang for the buck comes from SSSP: Short, Single-Subject Paragraphs, which are much easier to read; to review and revise during contract negotiations; and to reuse in other contracts. (It's not unlike modularity and orthogonality in software.) For more ranting on that subject — with some pathological before-and-after examples — see my online course materials (this version isn't pretty; I'm almost done refactoring it). [1] [0] https://dilbert.com/strip/2008-08-28 https://dilbert.com/strip/2008-08-28 [1] https://toedtclassnotes.site44.com/Notes-on-Contract-Drafting-2021-01-22.html#short-sentences https://toedtclassnotes.site44.com/Notes-on-Contract-Draftin...
- titanomachy 4y agoThanks for sharing this. As you said, there is a very clear analogy to software factoring. Separating the definition of terms from the clauses relating them is very similar to factoring software logic out into functions. In a way, bad legalese is even worse: at least hard-to-read code can be still be effortlessly and quickly executed by a computer. Every "execution" of your example contract will give someone a headache.
- randomdata 4y agoWorse, when it comes to code if execution doesn't do what you intended it is your fault for not writing it correctly and you are who gets punished for it. When it comes to legalese, if execution doesn't do what you intended it is their fault for not understanding what you meant correctly and they get punished for it.
- bhawks 4y agoIn your experience how much of this is attributable to a party of the contract trying to sneak favorable terms into the agreement? Generally I am a fan of Hanlon's razor, assume ignorance/stupidity over maliciousness, but given the nature of the subject matter I am very suspicious.
- raincom 4y agoThe plausible explanation for "center-embedded clauses"(CAC) is this: whenever there is an issue of ambiguity about a concept in the main clause, CAC will clarify that ambiguity. If one makes CAC as an independent clause, this independent clause can clarify, or reduce ambiguity, in all clauses of that paragraph or the whole contract (all paragraphs). In some unforeseen circumstances, making CACs as independent clauses may cause problems. I see CACs as footnotes, directly attached to the clause.
- aliyeysides 4y agoShameless plug here but my startup's mission is to solve this problem. It seems wrong to me that in this day and age you have to hire someone to be able to read a legal document or TOS: https://layman.ai/ https://layman.ai/
- johndhi 4y agoThis is interesting. I was thinking while reading this thread that it would be cool if there was a way to solve the problem. My idea: get a significant percentage of users of a service to sign up for a 'union' of sorts to negotiate on their behalf. So you will boycott Facebook, along with 10million others, until they adjust their terms to at least make more sense (or ideally be a little more user friendly).
- max51 4y agoAt my job I have to deal with the structural design part of the building code for US and Canada (ei. calculating loads on structure). Part of my job is to find the differences in each new version to see if we need to implement anything new in our software. For seismic, the Canadian code is easy enough to understand that teachers use it in college instead of manuals or notes. To calculates something (eg. a specific wind load or seismic load), you just read the section from top to bottom and follow the recipe. Things are actually placed in the order that an engineer would use them. With the US code, you have to deal with triple negations and 80% of the usefully information is presented as references to other sections. It's really not fun trying to understand it when a single sentence will link you to 8 paragraphs, 6 of which are in a completely different chapters or sub-chapters. And as you can imagine, these 8 paragraphs will also have their own references to other part of the code. It's a complete mess that is impossible to follow unless you write your own summary and/or take screenshots and rearrange them in order. You end up with a situation where even experienced engineers can't understand it and have to rely on notes from colleagues, college textbooks, calculation examples, or they just blindly follow the design software they bought. Working the support line for a high end structural analysis and design software has really opened my as to how incompetent and lazy a lot of the senior engineer from highly reputable firm can be. It would be a lot safer for the public if the "easy to understand" version of the code came from those who wrote the original. I suspect it's the same in other professions too.
- mistrial9 4y agothank you for this reply -- here in California, there is no secret that much building activity has been legally curtailed to such an extent that it becomes another endeavor entirely.. that of seeking and obtaining permission at every turn. Obscure and contradictory rule books specifically enable this kind of gatekeeping IMHO.
- astrange 4y agoA big problem with US building codes is just there’s too many of them - every town has its own rules, so you can’t share knowledge or buildings between them. Some of the common rules in the US don’t help though; aesthetic rules like setbacks are pointless and expensive, but even the safety rules other countries don’t have cause big problems. Can’t have single stair apartments and everything has to be built to accommodate gigantic fire trucks.
- bradleyjg 4y agoAs a general matter writers that try to use a formal voice but don’t have a lot of practice with it produce writing that is much worse than if they just settled for something more casual. I’m not saying emojis and text-speak but most of the time writers shouldn’t reach for words or phases that they think sound impressive.
- westurner 4y agoWhich attributes of a person are necessary to answer a legal question? Python: def has_legal_right(person: dict, right: str): -> bool assert person assert right # return NotImplementedError def have_equal_rights(persons: list): -> bool return NotImplementedError Javascript: function hasRight(person, right) { console.assert(person); console.assert(right); // return true || false; } function haveEqualRights(persons) { // return true || false; } Maybe Lean Mathlib or Coq? ... Therefore you've failed at the Law of Reciprocity.
- dqpb 4y agoWriting laws and contracts in natural language is kind of insane given that they are formal specifications.
- randcraw 4y agoPoor writing is the main cause for the illegibility of referreed science and engineering articles too. Historically this was partly due to publishers' demand that the article be quite short (often < 8-10 pages). Of course, this constraint is obsolete now that pubs are electronic. In addition to a format guide, every journal should specify a style guide (like the NY Times does), so the reader can expect a highly structured layout AND argument. (Explanatory content can go in 1+ supplement docs.) I'd even like to see standards for the use of emphasis (like bold, italics, colored text), especially for first mention of term/names that occur repeatedly. The sooner we can make all professional writing trivial to skim, the better.
- kfarr 4y agoI wish I could find the original link but I remember years ago a HN submission from a startup doing document summarization. The founder was on the discussion and responding to question about what documents are not possible to summarize with his software. Their response was after lots of research they determined that legal documents are the most challenging to summarize because they are intentionally obfuscated
- gnicholas 4y agoA lot of this is driven by inertia. When a lawyer goes to write a contract, she'll typically start with a prior contract or form agreement. This will either be used as a template, or large chunks will be borrowed and modified as needed. In either case, the lawyer is unlikely to reword a bunch of provisions in an attempt to improve readability. It's like the legal version of Chesterton's Fence — if you don't know why a particular clause is phrased a particular way, you leave it as-is. Your client/partner might ding you if you include a boilerplate provision you shouldn't have, but you'd probably get in more trouble if you affirmatively reworded something and broke a cross-reference or other logical linkage that was supposed to remain in place. As a result, language that was written a long time ago is still circulating in modern agreements. Note: I'm not defending any of this. As a lawer-turned-founder, I try to keep my agreements as short as possible!
- AlbertCory 4y agoIANAL, but I AM a patent agent, which means I passed the Patent Bar. So I haven't dealt in contracts, but a lot of the same considerations apply to patent claims. There is some claim language which is absolutely not required and any lawyer who uses it is just showing off. The article mentioned "aforesaid" which is a prime example in contracts (in patent claims, it's just "said"). For example: A TCP packet, comprising TCP header and body, where said header comprises etc. etc. -- or -- A TCP packet, comprising TCP header and body, where the header comprises etc. etc. The second is absolutely as valid as the first. "The" is just as good as "said." Another example: What is claimed and desired to be secured by US Letters Patent, is -- or -- I claim The first one is just pretentious. It adds nothing. Maybe you don't like "comprising"? Well, that one is specialized language. A chair, comprising four legs, a seat, and a back -- or -- A chair, consisting of four legs, a seat, and a back The second is not just as good as the first. "Comprising" allows for the chair to have arms, while "consisting of" does not.
- lamontcg 4y agoYour last example is why reading the law is tricky and why we need both a push for plain language and a push to explain language that is necessarily very specific.
- AlbertCory 4y agoIn general, yeah, but I have mixed feelings on that particular one. Claims wouldn't be much more understandable if they said: A chair, with four legs, a seat, and a back, and possibly other elements. A good explanation for obtuseness in legal language is: In normal writing, you're trying to be understood. In legal writing, you're trying to make it impossible to be misunderstood.
- photochemsyn 4y agoHere's a good example of 'center-embedded clauses' making a paragraph difficult to interpret - it's from the revamped USA-Canada-Mexico trade deal, specifically a side agreement between the USA and Canada on energy-related trade: > "Each Party shall endeavor to ensure that energy-related activities that do not result in a facility exceeding its previously authorized capacity and that are limited to performing maintenance work on, or ensuring the safety of, existing cross-border infrastructure may be undertaken under the initial authorization and shall not require a new authorization." Unpacking all this is rather difficult. The intent appears to be ensuring that energy-related activities should not require periodic re-authorization by a regulatory body after an initial authorization is granted. An example would certainly help - a cross-border power grid interconnect, say. The embedded clauses are of two different kinds. If our grid interconnect doubles its capacity, this would be a violation of the first (restrictive) clause, and would thus require a new round of authorization. Under the second (permissive) clause, one can shut down the grid interconnect for safety or maintenance reasons. Taking the grid interconnect offline to restrict supply and jack up prices would thus be a violation, although one could monkey around with this (see Russia shutting down Nordstream to Europe for 'maintenance' at present). That's just one paragraph, the document is hundreds of pages of this kind of thing.
- Pxtl 4y agoI feel like complex sentences like this need braces to make them clear. Like, programming-language-style indentation would help a lot. " Each Party shall endeavor to ensure that { energy-related activities that { do not result in a facility exceeding its previously authorized capacity AND that are limited to { performing maintenance work on, OR ensuring the safety of, } existing cross-border infrastructure } may be undertaken under the initial authorization and shall not require a new authorization. } " this is silly, but in this view I can clearly see "okay, where's the beginning and end of the stuff Each Party Shall Endeavor To Ensure".
- xboxnolifes 4y agoIts not that silly. Many of these run on sentences could be made much more clear by using bulleted lists, which is basically what you are suggesting. Though, mixing ANDs and ORs can be tricky in such cases at times.
- _ggwa 4y agoMy experience working as a patent examiner agrees fully with the title: legal texts tend to be hard mostly because they're poorly written. (DOC lawyers make me add this: This post is just my personal opinion, not that of the USPTO, DOC, US govt., etc.) I've been trained in patent legal terminology, which isn't that bad. Patent documents are still frequently difficult to understand. I have one application on my docket where I'm going to have to rewrite one of the claims to understand what it's saying, and no, that shouldn't be necessary... And the situation with patent documents is worse than the situation described in the abstract as many attorneys write vaguely. The argument that "lawyers are the intended audience" isn't legally sound either, as under 35 USC 112(a), patents are supposed to "enable a person skilled in the art [...] to make and use the [invention]". If an attorney argues that patents aren't supposed to be understood by non-attorneys, they're wrong, full stop. Unfortunately, I'm not really allowed to do 112(a) enablement rejections. I'd do those sorts of rejections frequently if I could, but I think I can count the number of times I've done 112(a) enablement rejections on one hand. The law in other countries seems more strict than in the US. I'm told that Japan in particular takes enablement a lot more seriously than the US does.
- johndhi 4y agoIf the examiners can't enforce enablement, doesn't that mean it isn't a true requirement? And that in fact patents wind up being drafted not for the layperson?
- _ggwa 4y agoYes, my personal opinion is that enablement is not a true requirement in the US. I think a lot of problems with the current patent system would be helped by making the law stricter about enablement and also giving the USPTO more resources (money, in particular) so that examiners can enforce the enablement requirement. Also, to be clear: Patents legally aren't for laypeople. They're for people working in the field of the invention.
- AstralStorm 4y agoMost patents omit crucial details to actually reproduce the invention. This is especially important in case of pharmaceutical and chemical patents. Full hardware and conditions are not documented nearly as well as a typical grad paper, which already tend to have holes. "Software" patents, often similarly omit "irrelevant" modules. Chocking it to "a specialist can make the module from scratch" is insufficient and should never be allowed. In addition, a lot of the patents, due to lacking the details, are obvious as written to a specialist, just the details are not.
- mistrial9 4y agoas part of graduate school, I participated in State of California hearings, studied particular regulations that were adopted after a major law was passed in my chosen field, and finally submitted (and had accepted) amendments to their final regulations. (this is not trivial, since there were more than 400 public comments and suggested changes to the administrative rulings, but less than three dozen were accepted - including mine). What I learned: the written law is ambiguous, mostly intentionally. The reply at the time was that the legislators "set the direction" and it is up to political appointees at an agency, working with their staff, to write regulation based on the "intent of the Legislature." The published regulations that implemented the law were written in such a way, that the references were actually circular, and the same term (noun) was used in two different places to mean two different things, without acknowledging that. I did as others suggested, and drew diagrams with notes to check the very very dense legalese in the regulations. My change was regarding that twice-defined noun, which they acknowledged by accepting the change. Overall - what is said is not what is done -- the saying I heard in Sacramento was "never write what you can say, never say what you can imply, and never imply if you can nod or wink" What that means is cynical; that you habitually do not write what you really mean to do, knowing that it will be reviewed by your adversaries, and taken out of context to be used against you. The regulations writing was adversarial, and the response from the agency involved was measured and ready for court, at every step. The default action in the public comment period is to ignore your comment, and they do that in most cases.
- deleted 4y ago[deleted]
- torstenvl 4y agoConsider the following two function definitions: int add(int a, int b) { return a + b; } int add(int a, int b) { if ((a > 0 && b > 0) && (INT_MAX - a < b)) { return INT_MIN + (b - (INT_MAX - a + 1)); } else if ((a < 0 && b < 0) && (INT_MIN - a > b)) { return INT_MAX + (b - (INT_MIN - a - 1)); } else { return a + b; } } Which one expresses the intent more simply and understandably? Which one is more robust? Which one would you bet the future of your company on? I offer that, sometimes, simplicity of expression is at odds with protection against edge cases.
- deanmen 4y agoWhy not int add(int a, int b) { unsigned res = (unsigned) a + (unsigned) b; return (int) res; }
- torstenvl 4y ago"When a value with integer type is converted to another integer type ... [if] the new type is signed and the value cannot be represented in it; the result is implementation-defined." C99, 6.3.1.3. "When a value with integer type is converted to another integer type ... [if] the new type is signed and the value cannot be represented in it; either the result is implementation-defined or an implementation-defined signal is raised." C23 Draft, 6.3.1.3. Calling add(2147483647, 2147483647) with your code could trap, not from the overflow (which is well-defined for unsigned integers) but from casting 4294967294 to a signed integer. I also don't know if it would work with one's complement.
- kemitchell 4y agoDon't let lawyers confuse form and substance as cover. It's perfectly possible to address more possibilities in simple language. The result might run longer, but it won't hurt to read. Too many companies run on legal docs execs don't read. Too may lawyers write those docs to put readers off. If you want robust legal work for your company, maximize accountability for your legal advisers. All the usual tools.
- coldtea 4y agoPoor incentives and interests in obscuration, not poor skills, drive poor writing in legal language
- thayne 4y agoI suspect in at least some cases terms of service and privacy policies are intentionally hard to read because they don't want you to know how one sided they are.
- jakub_g 4y agoMy father recently got a letter from a law office. What it wanted to convey was "we saw you sent a bank transfer to Bob lately..." (this was not stated implicitly but it's the only way how they could get address to send the letter) - "FYI Bob owes us 10k, please don't send him any money anymore, instead send it to us directly; or if you send to his account we'll take it anyway" (now that I'm thinking about it, this could be a nice scam tactic, but I'm pretty sure that one was legit). Anyway, the letter was written in such lingo that on first reading it was as if my father owed Bob 10k. Some elderly person receiving such letter could have had a stroke.
- abledon 4y agoOne of the pillars of the mars civilization is that all laws should be written in clear language
- gersh 4y agoIsn't a lot of legal language intentionally written to be hard to understand? Doesn't that drive up billing hours for lawyers, and benefit those with the most lawyers? Could we have more rules that difficult to understand language isn't enforceable? Could courts do more to rule against contracts that have poor language?
- giantg2 4y agoA lot of cases hinge on definitions and wording. It's pretty common that bad writing is involved. It's pretty common that the theory of law is also in contradiction with many opinions (eg strict construction).
- Eleison23 4y agoI have started making it a habit to read all Terms of Service and EULAs before accepting them, and particularly with financial stuff at stake, like opening a new account I need to read all the disclosures. Those financial agreements I've found to be comparatively well-written. I also have occasion to sign off on a lot of health care-related agreements, and I find these to be very difficult: it's an emotional flashpoint for me, the documents are often presented in times of stress and the signature is extracted under some sort of duress. Firstly, the health care facilities (and banks and others) now uniformly use electronic signature pads and they don't like to print the documents anymore. But if you insist, they will print them. This is a good pro forma procedure to force them to correlate what you're signing what what you've (presumably) read. But I've also found that it's nearly pointless to make a fuss about reading what you sign, because there's always a Swiss cheese of loopholes and convoluted phrasing that will confuse you. Once a few years ago, I "carefully" read and signed off on a 3-page document for release of records, but no records were produced. (It failed silently, and the onus was on me to follow up.) Upon investigation, I found that the health care professional had prepared the document for me to authorize me to release records to me (rather than for the facility to release the facility's records to me). I attribute this to malice on his part - he was a jerk, and of course even after I read this document with a glaring error, I didn't catch it, either. Nevertheless, don't let anyone shove an electronic signature pad in your hand before you've made an effort to read what you sign. I've found it useful to read EULAs and TOS, though, for the simple fact that they include policies & procedures in case of dispute. If you have trouble with a service, you're supposed to know the steps for resolution, and if you haven't followed them, the service isn't under any obligation to hold your hand and walk you through it. The document often includes essential email and postal contact addresses, and I guarantee that you'll never find those contact addresses ever again if you don't print/save that document before ticking the "I agree" checkbox. So I highly encourage you to make a folder in your cloud storage, or on your phone, and make liberal use of "Save/Print as PDF" for every TOS, EULA, and legal document that you sign or agree to. Eventually, you'll get into a situation, and you'll be thankful that you have recourse to the document you signed.
- deleted 4y ago[deleted]
- supernova87a 4y agoI lay a fair bit of fault also at an almost visual/UI level of how we write laws. If you look at our law books, they are almost all words/text. Paragraphs and paragraphs of it. Yet in a lot of areas of law or regulation, graphical explanations are rarely used when they could help clarify immensely. To use a simple example, just think of when a map is needed -- and whether you would try to describe that by text. I also have an analogy in my mind that when you ask a typical programmer to explain something, they start showing you the code. Only a skilled rare few have a picture in their mind that they can draw you the relationship between the things they have written (and start a chat based on that). Lawyers / politicians are by default writing in long, wordy, text to try to lay out complicated systems. This is often not ideal, when a diagram or schematic of what you are legislating to have happen would be more clear. It also produces an effect where laws tend to just bolt on more text, and have little contextualization of what already exists or what is being modified. And I also have a feeling it tends to miss the problem cases. I seriously believe our hundred books of CFR/laws are a significant result of this. If people were forced to summarize how a proposed law interacts with current laws, etc. I think there would be more hesitation and better thought about what is being enacted.
- fractallyte 4y agoRight! So 'legalese' could be generated from simpler diagrams which make edge cases much more evident. I've always thought that statements of law are a centuries-long struggle to get to a level of expression that we achieve in computer programs. We also have unit testing and versioning, plus a lot of other relevant processes.
- ninefathom 4y agoWhile the research appears well-considered and the article does indeed appear to make a valid conjecture, I'm a bit put off by the fact that the very first example of simplified "legalese" (re: severance payments, in the introduction) loses quite a bit of fidelity compared to the original. It even adds some major points for potential litigation due to ambiguous verbiage. Rephrased, even the PIs seem to have trouble parsing legalese. That doesn't invalidate the conclusion of the research, but it does highlight the need for some additional peer review.
- bubblethink 4y agoThis gives me an idea. Like obfuscated code competitions, can we get obfuscated contract competitions where the goal is two fold. 1) Write the most difficult to parse contracts, and 2) Sneak it into actual contracts with ever increasing importance. Eventually, one of these contracts/laws would go to trial, and nobody would be able to understand it. Hilarity ensues.
- klabb3 4y agoMarked as duplicate. This is not only already implemented, but an alternative implementation, DOS, is available and often preferred by users. I.e. have a bill be so long that a politician can't read it all before having to vote on it.
- jononomo 4y agoThis is the most painfully obvious headline I have ever read. I wonder when they'll realize that the writing is intentionally poor in order to prevent comprehension.
- jononomo 4y agoCongress should pass a law requiring every software end user agreement to be written at a sixth grade level and to be no more than 800 words in length. If it's a federal law, then companies will just figure out how to do it.
- pjscott 4y agoAnecdotally: when that guy in Wisconsin ran his car through a parade, I was curious what would happen to him. I looked up the relevant parts of the Wisconsin criminal laws, which had a rewrite some years ago. And holy shit they were amazing! So clearly written! So well thought out! This was what it sounds like when lawyers who knew what they were talking about decided to write it down clearly. I salute everyone involved. At least one lawyer out there can write worth a damn, and (having read some godawful wording in contracts) I wish more would try.
- philosopher1234 4y agoExactly the same situation in software
- deleted 4y ago[deleted]
- jakey_bakey 4y agoThis is 100% the case. I've been a consultant reading legal documents hammered out between the senior partners and VPs of the supplier - the language is so straightforward a child could understand what each party is getting.
- habosa 4y agoMost lawyers only exist to protect you from other lawyers. The language is all part of that, consciously or not.
- ThinkBeat 4y agoThis is of cours entirely the point. Regular people are not meant to understand what it says and means. If it was spelled out in plain simple English for everyone to read a lot more people would object to the terms and feel upset. When it is obfuscated nearly to the point of encryption no normal person will be able to, or at least spend the time it would take to decrypt it. This seems like a job where AI could be utilized to read legal language and output a plan English interpretation. It also has to do with job security. You need lawyers to read them, because other lawyers write them.
- qwerty456127 4y agoSure. I've read an agreement (by a tier-1 ISP) which was a pure pleasure to read.
- mihaaly 4y agoI'd add overcomplication. At least in the UK (I moved here btw.). I signed two rental agreements, 3 employment contracts and refused one employment contract on the basis of poor content. Each legal text were 40+ pages, taking very long to process not just beacuse of the sheer size but the obscure phrasing and errors as well. Tiny aspects were added to each in obscure language that a common person is supposed to process and give full consent with legal consequences. With the rental agreements I had no choice but to sing as is despite repeated chapters and typos changing the meaning, also internal discrepancies. I had to live somewhere and there was not much choice, not in the given time. But the refused employment contract was so poor to the level of pathetic, that I had to refuse. Chapters with common language altered uncomprehensible old english legal text, dead references, same text repeated 3(!) times in different places and two kind of paragraphs repeated in 2 locations. It also contained detailed rules about checking tyre pressure on own car when being out on company business and the rules of chewing gum in the office and the consequences of causing damage by the improperly disposed bubble gum. Accepting all in full with the consequence of disciplinary proceedings. Their reasoning addding so many tiny details was that the lawyer suggested adding anything, just in case. Yet, as there are millions of such small details possible in life it was hopefully incomplete still, failing to regulate other very possible scenarios. I am convinced that this urge to include as much as possible led to the very state of poor and erronous content. As the contract grew and changed throughout the years dead paragraph references, content altering typos, rushly wrote nonsense sentences, inconsistency and errors grew. Led to me being the first (which I am very very surprised about) refusing to sign after about 2 weeks of intense deliberation (plus some days of processing and a full day intense work I had on a 40+ item list about problems and errors above my persoanal wishes). Many of the suggestions went into the contract but others were not possible to change without paying the lawyer and some weeks of work and of course they did not want to deviate too much from the common content, accepting the new contract with everyoen else, so it became hopeless to get to agreement eventually. If the contract was ca. 3-6 pages max, like in my previous positions from elsewhere in Europe, then it was not in this bad state as it was easier to maintain and also comprehend (like my rental agreement in Sweden being one page premade to standard, purchased in a bookshop). Less was more in this case. My current contract is also 30+ pages, with an international company but with individual contracts for the various locations, naturally. Our new HR head in the continental Europe is amazed how big the UK contract is compared to the one used in her country. Also agreeing pure details here and there, prepared by a local solicitor hired. We had to have long discussions about the content similar to the case with the refused one, but with less errors and accepting some remaining issues tentatively until the text is altered later during the employment (with the involvement of lawyers). The contracts I meet here are huge, filled with obsure text difficult to understand for the common people mandated to accept its content in full, also buggy as the consequence of the shear size. I feel the whole purpose is lost this way. Especially when those supposed to comply with each and every details (there is a clause saying violating any clause could allow summary dismissal) cannot understand everything, due to unclear text or buggy content. Additionally the process is long, laborous, and at the same time rushed through in a competitive situation. I can safely say that I am pretty unhappy about the contractual procedures around me and cannot take those seriously, despite the legal consequences being very real.
- error_salad 4y agoDouble speak in a nutshell.