/
20.08.2020 at 08:59 pm
Cuttings

A Case for Legalese (Or Not)

Singular interpretations and written objectivity.

... ...For anyone who wonders why there's the need for a plain language summary in the first place: Research must be presented in such a way as to avoid misconceptions as much as possible, so very rigid language structure is used. That's also why legal writing is difficult to understand. It has to be written in such a way that only a singular interpretation can be derived.

- Reddit

Factual writing - touching on legalese, and why it is the way it is.

Another states that legalese is not (and should not behave) like code. Opposing, he admits that the law should never be strictly objective, nor written in that fashion:

... Programming language is imperative and declarative. If law/legal documents was to be written with the same objectivity, courts, lawyers and legal process would be rendered useless, as the legislation could be directly applied, on site, by immediate response authorities, with total disregard for context of events and motivation.

In fact, by being hard to interpret, law admits leeway that otherwise would be impossible to achieve.

Law making in about achieving a careful balance between being solely restrictive (you will not do) and being orienting (you can do, up to a given point).

Source: Reddit
Filed under:
#
#
#
Words: 151 words approx.
Time to read: 0.60 mins (at 250 wpm)
Keywords:
, , , , , , , , ,

Other suggested posts

  1. 06.01.2025 at 03:25 pm / Recursive Reflective Questioning With LLMs
  2. 02.01.2018 at 12:00 am / Genuinely Technical Modesty
  3. 05.03.2016 at 12:00 am / Rather Be (Alexa Goddard's Version)
  4. 13.06.2015 at 12:00 am / Sexism Against Modern Men
  5. 18.07.2014 at 12:00 am / Keep Learning Songs
  6. 03.01.2014 at 12:00 am / Write With Vigour
  7. 29.11.2013 at 12:01 am / 美しい - Beautifully Woolly
  8. 03.07.2013 at 12:00 am / Craft Versus Discipline
  9. 21.04.2012 at 12:00 am / Cinematic Mass Effect
  10. 26.03.2012 at 12:00 am / Apricot Orange Sunsets
© Wan Zafran. See disclaimer.