LDAP is an object oriented data base, that can store any kinds of data. Although it is mainly used for account information to be used as authentication back end. many more things can be done with LDAP.

This presentation will talk about plans to implement a historical simulation interface, using LDAP as back end. Such a simulation interface could be used for transporting information as edutainement, which could be an alternative to conventional schoolbooks. It could also be used to configure simulations and or to discuss the impact of certain historical decisions.

Basically the interface will be a world map divided into hexagons, as known from strategy games like Civilization V-VII). Each hexagon will be an entry in LDAP with attributes that describe the coordinates, the landscape (e.g. tundra), general resources (integers for food, wood, stone, ore, etc.) as well as special resources (tee, fish, pearls, etc.). Hexagons can also contain settlements and cities, where different kinds of building can be built on such hexagons, that add to the general resource values, but also to different less tangible values like science (e.g. via a university building), culture (e.g., a theater), religion (e.g., a temple), money (e.g. bank), touristic attraction (e.g. a theme park), etc. In addition, there will be objects (settlers, traders, warriors of different kinds, etc.) of different civilizations that can be moved on that map.

The software will allow for creating rules, e.g. food resource will increase after the invention of artificial fertilizers, and for discussing such rules. It will have two pillows Research and Education: Research results can be displayed or referenced in the software, but also teachers can use it to teach any event that can be referred to by location and point in time.

Currently a first version of the LDAP model exists and plans to implement the interface with an Angular-based framework. The idea is to used our IdM solution didmos as code base, since that consists of an OpenLDAP server as back end and REST based APIs (e.g. a SCIM implementation) called by the Angular based front end.

So Why LDAP? The project aims at a multiplayer platform that should allow for very big Maps (thousands of hexagons) and a big number of participants, thus a scalable network connected database like LDAP was an quite obvious choice. The flexible object oriented data model allows for specifying any kinds of objects, like hexagon, building, continent, civilization, moving objects, etc. thus LDAP as high-performance and highly flexible technology seems to be a good fit.

The presentation will describe the current status of the concept, which I plan to implement via agentic coding in my future leasure time.