xtdb VS entish

You don't necessarily need to embed it into the programming language itself to get a ton of value. XTDB (https://github.com/xtdb/xtdb) offer a Clojure, Java and HTTP API for interacting with the database, which is bitemporal and lets you query the database for a specific point in time for example.

XTDB is a bitemporal and dynamic relational database for SQL and Datalog, written in Clojure. The Python application I work on uses XTDB for its bitemporal and schema-less nature. There were a few Python clients that looked unmaintained and lacked some features we needed, so I tried to build something that would have fit our own requirements in hindsight. This includes:

it's bitemporal, will be SQL-compatible, and also has another query-language - XTQL :

https://github.com/xtdb/xtdb/tree/2.x/dev/xtql

You can also consider other durable Datalog options like datahike or datalevin which can work either as lib (SQLite style) or in a client-server setup; if you want to play with bi-temporality XTDB is a rock solid option with very good support and documentation.

You could look into http://xtdb.com/ if you want an open source alternative

XTDB, or Cross-Time Database, is a distributed and transactional database system designed to handle complex and changing data with ease. It is based on a bitemporal model, which allows for the tracking of both the valid time and transaction time of data, enabling powerful and flexible querying capabilities. With XTDB, developers can work with immutable data structures, which simplifies development and improves reliability. Its graph query language, Datalog, provides a powerful and expressive way to navigate relationships within the data.

Not exactly a virtual table top but check out https://github.com/etherealmachine/entish. This is a shameless plug, because it's a programming language I wrote for expressing rpg rules in machine readable format.

What do you think about https://github.com/etherealmachine/entish/tree/main/src/rules/dungeon_world. The idea is to group rules into a folder, then have the Markdown files contain nice human-readable descriptions as well as the parseable rules. That's just an idea for now - it would probably require implementing a Markdown parser (do-able but a bit of work) and then grabbing the code blocks out of the parser.