The problem with the law isn't the language of the laws themselves, it's the input.
I mean, please show me the typedefs for attempted rape and reckless driving.
Most of the time, the interesting cases are about figuring out who's lying, if there was intent, determining what's reasonably expected, how a certain condition might count as an aggravating circumstance etc. etc.
Aren't a lot of the work, effort and expertise in legal fields(including learning) , is about legalese and knowing a lot of laws and cases ?
If at least some of the hard work around being a lawyer and being a judge could be codified in a computer and automated , lawyers and judges could be better in the other , harder parts of the legal profession ?
Comments
You're probably right, but compared to the DSL that hasn't been specified and that no one has agreed on, Python wins.
The more I think about it, there should be a DSL for all laws. (Something better than the legalese dialect of English, at least.)
The problem with the law isn't the language of the laws themselves, it's the input.
I mean, please show me the typedefs for attempted rape and reckless driving.
Most of the time, the interesting cases are about figuring out who's lying, if there was intent, determining what's reasonably expected, how a certain condition might count as an aggravating circumstance etc. etc.
Aren't a lot of the work, effort and expertise in legal fields(including learning) , is about legalese and knowing a lot of laws and cases ?
If at least some of the hard work around being a lawyer and being a judge could be codified in a computer and automated , lawyers and judges could be better in the other , harder parts of the legal profession ?
arguably "legal English" is already a DSL.
A DSL whose programmers are lawyers and whose interpreters are courts.
We may have problems with the quality of those interpreters. Are they developed with an Open process?