A more substantial TODO item.
Chris Pressey
6 years ago
74 | 74 | can generate a scenario where the condition is met (by whatever method). |
75 | 75 | * Consider what it would take to add a predicate that evaluates to whether |
76 | 76 | a given action has been taken previously or not. |
77 | * Remove functions as I believe they are not necessary -- if you want to look | |
78 | up a property, you can just pattern-match for it. e.g. the example currently is | |
79 | ||
80 | their(Alice) → her | |
81 | their(Bob) → his | |
82 | ||
83 | but we can just say | |
84 | ||
85 | possessive(Alice, her), | |
86 | possessive(Bob, his) | |
87 | ||
88 | in the world-database, then write rules like | |
89 | ||
90 | [actor(α),possessive(α,ξ)] α scratches ξ head. [] | |
91 | ||
92 | This loses the nice property of the function name being a placeholder, but | |
93 | you could use named variables instead: | |
94 | ||
95 | [actor(?Actor),possessive(?Actor,?their)] ?Actor scratches ?their head. [] |