- + From there comes following idea: Maybe every problem can be
- translated to geometry (use any shapes and as many dimensions as
- you need). Solution(s) to such problems would then appear as
- relatively simple search/comparison/lookup results. As a bonus,
- such geometrical *data storage* AND *computation* can be
- naturally made in *parallel* and *distributed*. That's what
- neurons in the brain appear to be doing ! :) . Learning means
- building/updating the model (the hard part). Question answering
- is making (relatively simple) lookups (geometrical queries)
- against the model.
+
++ From there come following ideas:
+ + Maybe every problem can be translated to geometry (use any shapes
+ and as many dimensions as you need). Solution(s) to such problems
+ would then appear as relatively simple search/comparison/lookup
+ results. As a bonus, such geometrical *data storage* AND
+ *computation* can be naturally made in *parallel* and
+ *distributed*. That's what neurons in the brain appear to be doing
+ ! :) . Learning means building/updating the model (the hard
+ part). Question answering is making (relatively simple) lookups
+ (geometrical queries) against the model.
+
+ + Mapping of hyperspace to traditional object-oriented programming
+ model:
+ + Object is a point in space (universe). Each object member
+ variable translates to its own dimension. That is: if class
+ declares 4 variables for an object, then corresponding object
+ can be stored as a single point inside 4 dimensional
+ space. Variable values translate to point coordinates in
+ space. That is: Integer, floating point number and even boolean
+ and string can be translated to linear value that can be used as
+ a coordinate along particular dimension.
+
+ + Each class declares its own space (universe). All class
+ instances (objects) are points inside that particular
+ universe. References between objects of different types are
+ hyperlinks (portals) between different universes.