82,891
edits
Legal code: Difference between revisions
no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{a| | {{a|devil|}}How about this for a project: Reduce the potential ''logic'' of legal [[Contract|contracts]] down to set of linguistic expressions or axioms. There are surely only a certain number of propositions that are articulated in a normal legal contract. Even if there is an indefinite set of axioms, the number of common axioms must be finite and relatively manageable. So take industry standard contracts, for example, and reduce them to those propositions. These axioms can be agreed, open-sourced, even if the articulation of them on a contract is not. | ||
So, to take Section {{isdaprov|2(a)(i)}} of the {{isdama}}: | So, to take Section {{isdaprov|2(a)(i)}} of the {{isdama}}: | ||
| Line 11: | Line 11: | ||
Or | Or | ||
<nowiki> {{subject|everyone}} {{commitment|must}} {{action|pay}} {{conjunction|or}} {{action|deliver}} {{object|obligations in Confirm}} {{condition|per Agreement}} </nowiki> | <nowiki>{{subject|everyone}} {{commitment|must}} {{action|pay}} {{conjunction|or}} {{action|deliver}} {{object|obligations in Confirm}} {{condition|per Agreement}} </nowiki> | ||
The point being that “agrees to”, “will”, “shall”, “must”, “is obliged to”, “shall be obligated to”, “shall unconditionally be obligated to” and so on all code back to “<nowiki>{{commitment|must}}</nowiki>”. | The point being that “agrees to”, “will”, “shall”, “must”, “is obliged to”, “shall be obligated to”, “shall unconditionally be obligated to” and so on all code back to “<nowiki>{{commitment|must}}</nowiki>”. | ||
Ideally a lawyer would be able to code from principles. | Ideally a lawyer would be able to code from principles. | ||
So the question is, is this possible? Is this Bertrand Russell folly? Esperanto? | |||