From faec47e3d5e544d712e13ea1309d41dbf85a8d52 Mon Sep 17 00:00:00 2001 From: Inari Listenmaa Date: Tue, 16 Jun 2020 10:18:15 +0200 Subject: [PATCH] Add files via upload --- cnl.md | 43 ++++++++++++++++++++++++++++++++++++ computable_contracts.md | 7 ++++++ daml_smart_contracts.md | 11 +++++++++ index.md | 4 ++++ legal_drafting_is_broken.md | 23 +++++++++++++++++++ normalized_legal_drafting.md | 9 ++++++++ scope_ambiguity.md | 23 +++++++++++++++++++ spreadsheets_for_law.md | 7 ++++++ 8 files changed, 127 insertions(+) create mode 100644 cnl.md create mode 100644 computable_contracts.md create mode 100644 daml_smart_contracts.md create mode 100644 index.md create mode 100644 legal_drafting_is_broken.md create mode 100644 normalized_legal_drafting.md create mode 100644 scope_ambiguity.md create mode 100644 spreadsheets_for_law.md diff --git a/cnl.md b/cnl.md new file mode 100644 index 0000000..ce74908 --- /dev/null +++ b/cnl.md @@ -0,0 +1,43 @@ +--- +date: "2020-06-15" +--- + +# Controlled Natural Language + +Based on real natural languages, but restricted in some way. (Paraphrased from [SIGCNL definition](https://www.sigcnl.org/index.html).) + +## Types of restrictions + +### Vocabulary +Example: only words related to seafaring or instruction manuals. + +### Grammar +Example: don't allow [PP attachment](https://www.gabormelli.com/RKB/Prepositional_Phrase_Attachment_Task) ambiguity: + +> I saw the man with a telescope + +Variations [man with a telescope] and [saw with a telescope] need to be marked explicitly: + +1. I saw the (man with a telescope) +1. I (saw with a telescope) the man + +### Semantic + +Example: TODO + +## Purposes + +### Improve communication among humans + +Example: [Maritime English](https://en.wikipedia.org/wiki/Standard_Marine_Communication_Phrases) + +People who work on ships need to learn a specific subset of English. When your ship hits an iceberg, you say: + +> “I am fast in ice. I require assistance”. + +instead of "the ship has crashed in ice, can somebody help me?" + +This allows people to work on ships without knowing the full English language. +## +- +Some CNLs are designed to improve communication among humans, especially for non-native speakers of the respective natural language. In other cases, the restrictions on the language are supposed to make it easier for computers to analyze such texts in order to improve computer-aided, semi-automatic, or automatic translations into other languages. A third group of CNL has the goal to enable reliable automated reasoning and formal knowledge representation from seemingly natural texts. diff --git a/computable_contracts.md b/computable_contracts.md new file mode 100644 index 0000000..d186535 --- /dev/null +++ b/computable_contracts.md @@ -0,0 +1,7 @@ +--- +date: "2020-06-15" +--- + +# Computable contracts + +- diff --git a/daml_smart_contracts.md b/daml_smart_contracts.md new file mode 100644 index 0000000..a4f46c3 --- /dev/null +++ b/daml_smart_contracts.md @@ -0,0 +1,11 @@ +--- +date: "2020-06-15" +--- + +# DAML smart contracts + +A different interpretation of contracts as code, where the contracts are +automatically generated and signed by computers and sent between servers. + +For example, one company places an order of T-shirts for a conference. Now it +is important for both companies that they can prove that the order is placed and confirmed diff --git a/index.md b/index.md new file mode 100644 index 0000000..65202cc --- /dev/null +++ b/index.md @@ -0,0 +1,4 @@ +# Overview + +- +- diff --git a/legal_drafting_is_broken.md b/legal_drafting_is_broken.md new file mode 100644 index 0000000..7222b30 --- /dev/null +++ b/legal_drafting_is_broken.md @@ -0,0 +1,23 @@ +--- +date: "2020-06-15" +--- + +# Legal drafting is broken + +### Legal drafting uses suboptimal workers + +Humans are imprecise: +* Incomplete information +* Semantically vague +* Syntactically ambiguous (e.g. ) + +### Legal drafting uses a suboptimal format +Plain text is lacking: +* Can't be checked for inconsistencies (except by humans who aren't good at it) +* Can't keep track of the overall state. If one thing changes, the rest needs to be updated manually. + +Proposed solutions to fix legal drafting: + +- +- +- diff --git a/normalized_legal_drafting.md b/normalized_legal_drafting.md new file mode 100644 index 0000000..7fab085 --- /dev/null +++ b/normalized_legal_drafting.md @@ -0,0 +1,9 @@ +--- +date: "2020-06-15" +--- + +# Normalized legal drafting + +1978 paper by Layman E. Allen _Normalized legal drafting and Query method_ + +Precursor to rules as code, computational contracts etc. "Normalized" legal document à la Allen ≈ . diff --git a/scope_ambiguity.md b/scope_ambiguity.md new file mode 100644 index 0000000..355f7b6 --- /dev/null +++ b/scope_ambiguity.md @@ -0,0 +1,23 @@ +--- +date: "2020-06-15" +--- + +# Scope ambiguity + +Example from Allen & Engholm (1978) _Normalized Legal Drafting and the Query Method_ + +> Persons who are doctors and lawyers qualify. + +What is the scope of _and_? + +1. _[Persons who are doctors] and [persons who are lawyers] qualify_ +1. Persons who are [doctors and lawyers] qualify + + +We will 100% need to support all kinds of scope ambiguity. Natural language +contracts are full of it. People like reading it and writing it. To spell out +"persons who are doctors qualify and persons who are lawyers qualify" +sounds like the worst kind of robotic . + +A full explicit sentence is useful for a human-directed ambiguity check +("did you mean … or …"), but not as the primary compilation target. diff --git a/spreadsheets_for_law.md b/spreadsheets_for_law.md new file mode 100644 index 0000000..e0e7787 --- /dev/null +++ b/spreadsheets_for_law.md @@ -0,0 +1,7 @@ +--- +date: "2020-06-15" +--- + +# Spreadsheets for law + +I don't know yet what this is, but Meng thinks it's important.