Ontologies + revise tags

automatic_contract_processing.md

@@ -1,7 +1,7 @@
 ---
 date: "2020-06-17"
 tags:
-  - approach
+  - task
 ---
 
 # Automatic contract-processing

decision_table.md

@@ -2,7 +2,6 @@
 date: "2020-06-17"
 tags:
   - method
-  - approach
   - tool
   - formalism
 ---

generality.md

@@ -8,7 +8,7 @@ tags:
 
 Event `A` is more general than event `B`, iff every instance of `B` is also an instance of `A`.
 
-Example from Layman E. Allen (1978) <normalized_legal_drafting_query_method>
+Example from <normalized_legal_drafting_query_method>
 
 * "penalty" is more general than "fine"
 * "penalty" is more general than "imprisonment"

index.md

@@ -22,13 +22,10 @@ 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:
+Approaches to fix legal drafting:
+
+<z:zettels?tag=approach&cf>
 
-- <teach_humans>
-- <summarize_for_humans>
-- <rules_as_code>
-- <contracts_as_code>
-- Legal <ontology>
 
 Alternative points of view:
 

legal_expert_systems.md

@@ -6,6 +6,7 @@ date: "2020-06-17"
 
 Automated legal advice. Replace a lawyer with a program.
 
-Bloomgerg Law: _[Automating Legal Advice: AI and Expert Systems](https://news.bloomberglaw.com/business-and-practice/automating-legal-advice-ai-and-expert-systems/)_
+Possibly powered by <legal_ontology>.
 
-Example of a legal expert system in Jason Morris: _[“Rules as Code” Can and Should Be Done Without Programmers](https://medium.com/@jason_90344/rules-as-code-can-and-should-be-done-without-programmers-fb3e0f4dafa5#a1b0)_. That system is written using <datalex>.
+- Bloomgerg Law: _[Automating Legal Advice: AI and Expert Systems](https://news.bloomberglaw.com/business-and-practice/automating-legal-advice-ai-and-expert-systems/)_
+- Example of a legal expert system in Jason Morris: _[“Rules as Code” Can and Should Be Done Without Programmers](https://medium.com/@jason_90344/rules-as-code-can-and-should-be-done-without-programmers-fb3e0f4dafa5#a1b0)_. That system is written using <datalex>.

legal_ontology.md

@@ -0,0 +1,27 @@
+---
+date: "2020-06-17"
+tags:
+  - approach
+---
+
+# Legal ontology
+
+Model legal knowledge in an <ontology>.
+
+Say that you write a law that says
+
+> You have the obligation to pay taxes.
+
+Maybe you link your law to [WordNet](https://wordnet.princeton.edu/) and make sure you have the right sense of "you", "have", "obligation", "pay" and "taxes". Now you can translate it into any other language that has a [linked WordNet](https://github.com/GrammaticalFramework/gf-wordnet#readme) with the same identifiers.
+
+Now you know that _obligation_ in the sense `06785951` 'a legal agreement specifying a payment or action and the penalty for failure to comply' is translated into Bulgarian as _обвързаност_.
+
+But this advanced NLP system has still no idea how _obligation_ relates to other concepts in the world. In a legal ontology, you can specify relations and rules like "if you are __obliged__ to do something, you are also __permitted__ to do it."
+Example from Mitrović et al. _[Modeling Legal Terminology in SUMO](https://www.researchgate.net/publication/338937692_Modeling_Legal_Terminology_in_SUMO)_
+
+    (=>
+      (modalAttribute ?FORMULA Obligation)
+      (modalAttribute ?FORMULA Permission))
+
+
+See also: <legalruleml>

normalized_legal_drafting_query_method.md

@@ -4,7 +4,7 @@ tags:
   - paper
 ---
 
-# Normalized legal drafting and the Query method
+# Normalized legal drafting and the Query method (Allen, 1978)
 
 1978 paper by Layman E. Allen: _Normalized legal drafting and the Query method_.
 

ontology.md

@@ -10,8 +10,4 @@ Kind of like this zettelkasten: here we link concepts to each other. In addition
 
 Contrast with a web of free text, this kind of structure allows for e.g. automated question answering.
 
-### Legal ontologies
-
-TODO
-
-- <legalruleml>
+(That is just one kind of ontology, there are other designs. I don't know this area very well. But other ontologies seem to contain _axioms_ or _facts_.)

rules_as_code.md

@@ -4,11 +4,11 @@ tags:
   - approach
 ---
 
-# Rules as Code
+# Rules as code
 
 Legal drafting = writing code.
 
-(Remember the old days when you had to write contract in English and then <formal_models_of_legal_text>)
+(Remember the old days when you had to draft in English and then <formal_models_of_legal_text>)
 
 Useful things can be generated from that code:
 - <automatic_contract_processing>

scope_ambiguity.md

@@ -4,7 +4,7 @@ date: "2020-06-15"
 
 # Scope ambiguity
 
-Example from Layman E. Allen (1978) <normalized_legal_drafting_query_method>
+Example from <normalized_legal_drafting_query_method>
 
 > Persons who are doctors and lawyers qualify.
 

spreadsheets_for_law.md

@@ -2,7 +2,6 @@
 date: "2020-06-15"
 tags:
   - concept
-  - approach
 ---
 
 # Spreadsheets for law

summarize_for_humans.md

@@ -1,14 +1,15 @@
 ---
 date: "2020-06-16"
+tags:
+  - approach
 ---
 
 # Classification and summarization
 
-Human volunteers go through legal contracts like license agreements or privacy policies, and write a human-readable summary. Examples:
+Human volunteers go through <legal_contract> like license agreements or privacy policies, and write a human-readable summary. Examples:
 - [ToS;DR](https://tosdr.org/)
 - [tl;dr Legal](https://tldrlegal.com/)
 
-
 [Creative Commons licenses](https://creativecommons.org/licenses/) has a three-layer design:
 - Legal code
 - Human readable

tabular_interface.md

@@ -1,7 +1,6 @@
 ---
 date: "2020-06-16"
 tags:
-  - approach
   - design
 ---
 

visualization.md

@@ -1,7 +1,7 @@
 ---
 date: "2020-06-16"
 tags:
-  - approach
+  - design
 ---
 
 # Visualization