Unified Data Model

I'm going to define a unified data model as a model of data architecture that is necessarily rooted in actual digital hardware (otherwise it would just be a DataModel or ObjectModel) that can encompass every data relationship and scale arbitrarily large.

Somewhere on this wiki it's pointed out that tools are often defined by their limits as well as what they can do. Standards impose limits, otherwise they won't be standards. It could be called a form of discipline or regimentation in order to "tame" things. The trick is to find something that's flexible and can cover a lot of domains, yet not be so open-ended that it's RAM-like mush.

Of course, for a such a unified model to scale and to be navigable, we need a ThreeDimensionalVisualizationModel.

In theory this could be done with EndemeSets using a KnowledgeDatabase and a clever EndemePath structure. I'm taking a shot at it, mostly so that I can create a game that regenerates universes once time travelers have affected the time stream. -- JonGrover
See also UnifiedObjectModel, PangaiaProject

EditText of this page (last edited December 11, 2014) or FindPage with title or text search