/
20.08.2020 at 08:59 pm
Cuttings

A Case for Legalese (Or Not)

Singular interpretations and written objectivity.

There was a discussion on Reddit on the nature of factual writing. It touched on legalese, and why it is the way it is.

One makes the case:

...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.

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).


Filed under:
#
#
#
Words: 232 words approx.
Time to read: 0.93 mins (at 250 wpm)
Keywords:
, , , , , , , , ,

Other suggested posts

  1. 10.06.2022 at 07:44 pm / Teach Thy Tongue to Say: 'I Do Not Know'
  2. 19.02.2020 at 10:25 am / STEM, STEAM and Art
  3. 03.01.2020 at 10:46 am / Git for Legal Practice
  4. 15.12.2017 at 12:00 am / The Breakings of Julia
  5. 21.12.2015 at 12:00 am / Emails and English Weather
  6. 26.12.2013 at 12:00 am / Teal Stares
  7. 11.12.2013 at 12:00 am / Lighting Wizardry
  8. 02.12.2013 at 12:00 am / Coloured Plasmids
  9. 29.11.2013 at 12:00 am / ガラケー Garakei Evolution
  10. 21.07.2012 at 12:00 am / Hunted By GLaDoS
© Wan Zafran. See disclaimer.