<h1 id="epilog">Epilog<a aria-hidden="true" class="anchor-heading icon-link" href="#epilog"></a></h1>
<ul>
<li><a href="http://logic.stanford.edu/epilog/homepage/index.php">http://logic.stanford.edu/epilog/homepage/index.php</a></li>
<li>similar: <a href="/wiki/notes/ru39zbd1307zeubprtbihmk">Prolog</a> <a href="/wiki/notes/bbjubypy9l280othn6p5sie">Datalog</a> <a href="/wiki/notes/i7jl6i5ik1xz9w0bclxklxm">Game Description Language</a></li>
</ul>
<h2 id="description">Description<a aria-hidden="true" class="anchor-heading icon-link" href="#description"></a></h2>
<ul>
<li>"Epilog is similar to other logic programming languages, such as Datalog and Prolog, but there are some differences. Like Datalog, Epilog separates data and rules. Like Prolog, Epilog supports data and rules with functional terms. Like both of these languages, Epilog provides the ability to define views of data. However, Epilog also provides a way to express database dynamics. Whereas Prolog treats side effects implicitly using assert and retract as subgoals in view definitions, Epilog enables users to express side effects in the form of operations defined as database transformation"</li>
</ul>
<h2 id="benefits">Benefits<a aria-hidden="true" class="anchor-heading icon-link" href="#benefits"></a></h2>
<h3 id="programming-ease">Programming Ease<a aria-hidden="true" class="anchor-heading icon-link" href="#programming-ease"></a></h3>
<ul>
<li>Easier to create and modify than traditional programs
<ul>
<li>Programmers can get by with little or no knowledge of the
capabilities of systems executing those programs.</li>
<li>Less work. The specification is the program; no need to
make choices about data structures and algorithms.</li>
<li>Easier to learn logic programming than traditional
programming. Think spreadsheets.</li>
</ul>
</li>
</ul>
<h2 id="references">References<a aria-hidden="true" class="anchor-heading icon-link" href="#references"></a></h2>
<ul>
<li><a href="http://logicprogramming.stanford.edu/lectures/slides_01.pdf">http://logicprogramming.stanford.edu/lectures/slides_01.pdf</a></li>
</ul>
<hr>
<strong>Backlinks</strong>
<ul>
<li><a href="/wiki/notes/uejedfppzpvlb027wrud0p4">Introduction to Logic Programming</a></li>
</ul>

Epilog

public-notes


Welcome! And beware!  

## Purpose

This vault is the "[[learning-in-public|ar.swyx.learn-in-public]]" part of my Second Brain. If you share some of my interests, please [reach out](https://djradon.github.io)! 

## Contents

- [[t]] my personal wikipedia
- [[idea]] (not necessarily mine)
- Resource Notes, including highlights, thoughts and metadata, for various things:
  - [[ar]] mostly articles, papers and web pages
  - [[book]]
  - [[community]]
  - [[course]]
  - [[event]]
  - [[game]]
  - [[loc]]
  - [[org]]
  - [[user]] 
  - [[prdct]] mostly software products, but also ontologies
  - [[recipe]]
  - [[video]] movies, tv episodes, youtube, etc
- [[vs]]
- [[wanted]]
- Some "Metadata Notes":
  - [[tags]] which may refer to any and multiple (or none) of the above
  - [[c]]: ways to categorize resources
  - [[p]]: ways to assert things about resources (mostly abandoned)

In terms of the [[t.km.zettelkasten]] method, this wiki is a commingling of literature notes with something @Sönke-Ahrens warned about: a "personal Wikipedia or a database" [^1]. 

In terms of [[t.tm.getting-things-done]], it's references, someday-maybe, next actions, and public projects.

## Beware!

This is a cluttered cupboard of jumbled jottings riddled with inaccuracies, confusion, and mistakes.

## What This Is Not

- evergreen-notes/digital-garden: for "synthesized" / original-ish publishable big-idea notes that should evolve over time, props to @andy-matuschak and @maggie-appleton
- blog: for "point-in-time" items to be shared: personal news, articles, etc.
  - e.g., [[ar.substack.carpe-noctem]]


[^1]: [[book.how-to-take-smart-notes]]  