Note on coercion

In the last post we saw several means of organizing data, namely templates, subsumption, and examplification. However, those means could be made more effective if there was more direction on how they operate. For instance, examplify() should be able to feed a record without having to repeat type names explicitly, but we didn’t choose the … Continue reading Note on coercion


How to use subdatabases

Subdatabases (subdbs in short) do not differ deeply from formats, but provide a type-record and thus allow subrecords to be created according to a defined structure. When subdbs are there, functions such as examplify(), subsume(), templatize() and get_subject() become available. ? select * from subdbs i sdb n a t u: -47 ~ #Data Structure … Continue reading How to use subdatabases

How to modify information

No surprise that with various recording levels, Unidatab provides also various means of modifying information.  Let' start by looking at how we can change some input data and we'll admit that we should better act on properties and types. Changing data Since pure data is only entered once and not duplicated, we understand that changing … Continue reading How to modify information

From type policy to typology

Now that the founding dichotomy is chosen, there are additional steps to achieve in order to build what the database shall exemplify, a typology. But the type policy can't restrict to this preliminary choice. The construction of a typology requires to obey explicit naming rules and is probably closely bond to the evolution of implied … Continue reading From type policy to typology

Types : the primacy of unicity explained

Whatever we choose as type policy for our properties will nevertheless pertain to a record that can't divert from its unicity-based type policy. For there are functional reasons (e.g. the ability to create subdbs) that involve to consider records this way. Thus the type policy relies on a unique principle only when this principle is … Continue reading Types : the primacy of unicity explained

More about properties and types

As we can grasp it now the node table is mess: nodes don't appear in the order of their chain but according to the moment in which they were created. Though located in another table, symbols look like nodes but constitute another type of entry. But of what types are we talking about in this … Continue reading More about properties and types

Aliases and network development

Setting an alias for a record isn't mandatory in Unidatab but it can make a database available for multi-user and online use. Just as much as a type policy is needed for the sake of inner soundness of a database, an alias policy is needed in order to combine several databases over the network, making … Continue reading Aliases and network development