Information Modelling
If we want to store an information digitally, we have more or less two possibilities: If there is an app that is prepared for the type of information we need to store (maybe an address or a sales order) we can feed it to that app. If not, we need to write the information down as plain text and store it somewhere, maybe in the file system or in a content management system.
Both approaches have limitations. When we use an app, we are limited to the functionality the app provides, apps generally do not process arbitrary information. In addition, chances are that the information we feed into the app is “trapped” inside of it; we will not be able to use that information outside that app. On the other hand, if we write the information down as text and store it somewhere, that text is digitally meaningless, computers do not know what to do with it except for presenting it to us. We are also forced to store that text somewhere in a more or less rigid structure (file system, mail folder, etc.) which might make it hard to find in the future.
Today, there is simply no way to express arbitrary, semantic information digitally as we for example can design a house or a mechanical part using CAD.
Havel enables digital information modelling, which is like CAD for arbitrary information. Users can model an information just as they can design a house using CAD. In CAD, a drawing is an abstract of a real world item. In information modelling, an expression is an abstract of an information.
Information is usually modeled graphically using IMEs for specialists and NMEs for end-users. A modelling language like H/a or H/b can be used alternatively. The process of information modelling using an IME or NME is a bit like drawing a mind map. Users graphically create entities, give them properties and create relations using a mouse or touch screen. The modelling environment assists users when modelling entities of known types or when expressing situation details that follow known patterns, like the temporal sequence of events. Dynamic forms and custom UIs can assist when recording and presenting data.
Information modelling is also used when creating new functionality. Havel does conceptually not distinguish between information and instruction, the same tools that are used to model information can also be used to create functionality, a.k.a. programming.
Beyond technicalities, there is no limitation in Havel as of what type of information can be modeled. The complexity of the expressions is only limited by available resources. Users have the full power of Havel’s expressiveness to model every little detail that is required. Information modeled in Havel merge automatically with the infoverse.
This post is part of a comprehensive introduction into SRDM, graph languages and Havel.
Continue reading: Dynamic Expressiveness
Comments