In Part 2 of this series we introduced the Atomic Information Resource (AIR) data model of the AtomicDB database management system. In this part we present a simple but extensive example on various representations of number three using the poweful Mathematica functions and the unique features of Mathematica notebooks. We relate these with the three-faceted abstraction mechanism in R3DM and we discuss the principles and the architectural design of R3DM, a conceptual framework based on semiosis, in Part 4.
Functional representation is the core operation of R3DM. Everything is represented as a function that is mapping values from one domain to another. You may view functions, as transformations. This is also how they operate in Wolfram Language. They transform expressions from one symbolic form to another.
In this section we investigate the various forms that a symbol related to number '3' can take. In R3DM this is the sign that is used to signify something at a higher level and at the same time it is used to symbolize an internal representation, a realization. Read the examples here on
The Wolfram Language provides a uniform mechanism, the Interpreter function, for specifying how input of different types should be interpreted. Interpretations can involve either structural or semantic conversions. The strings that appear in $InterpreterTypes are the possible first arguments to Interpreter.
Generally speaking interpretation is closely related with the assignment of meaning to any expression or concept. But in computer science an interpreter is a computer program that executes instructions. In Wolfram Language the interpreter is involved in the evaluation of an expression. In R3DM any interpretation is directly linked to the signified, the semantics of any information resource.
We define our own interpretations. Wolfram Language provides the interpretation function for that purpose. Read more about
We end our discussion on the three-faceted abstraction mechanism that we use for number '3' with the analysis of data types and encoding/decoding mechanisms to store various representations of '3'. First we will compare atomic and complex data types. We can view data types as containers of a specific type of content.
We present an Image container (symbol) realized in Mathematica as a raw array of bytes, and a Sound container (symbol) realized in Mathematica as a list of sound amplitude levels samples. Read here about
For a full length discussion and demonstration of the above in Mathematica, you may download the third part of the series "Towards a New Data Modelling Architecture" as a PDF or as a Mathematica Notebook