Transversality of Information in Heptabase (Part 1)

Summary

Heptabase is an information management tool that distinguishes between "Definitional" and "Presentational" aspects of information, providing dedicated spaces for mapping (Whiteboard) and organizing (Tag) to enhance the utility and arrangement of information.

Abstract

The article discusses the concept of "Transversality of Information in Heptabase," emphasizing the dual nature of information: "Definitional" information, which is effective when indexed, and "Presentational" information, which is effective when arranged. Heptabase, a unique application, addresses this by offering two distinct areas for information handling. The "Whiteboard" serves as a mapping attribute area, while the "Tag" area functions as a management attribute space. Unlike traditional information applications, Heptabase allows information to exist solely within the Tag area, even without a corresponding entry on the Whiteboard. This design recognizes that information can be purely definitional or presentational, requiring different handling methods. The article reflects on the initial discomfort with the equivalence of the Tag area to the Whiteboard but concludes that the thoughtful structure of Heptabase, which allows for the appropriate utilization of information according to its aspect, is a deliberate choice by the developer to facilitate concurrent and effective use of both types of information under a unified system.

Opinions

The author initially found the equivalence of the Tag area to the Whiteboard in Heptabase disconcerting, as it deviated from the conventional understanding of tags as secondary classifications.
After using Heptabase for a month, the author appreciated the deep structure of both the Whiteboard and Tag areas, recognizing the developer's intention to create an operational system where each aspect of information has its appropriate place for utilization.
The article suggests that the careful design of Heptabase's structure allows for a more nuanced approach to information management, where definitional and presentational aspects can be effectively managed and influence each other positively.
The author implies that traditional information applications may limit the potential of information by not allowing tags to exist independently of the information they classify.
The author believes that Heptabase's approach to information management, which allows information to exist in either or both of the dedicated spaces, is superior for handling the complexity of information's dual aspects.

Two “Aspects” of Informati⁠on

Information has two types, or aspects: “Definitional” and “Presentational”. Definitional information becomes effective when indexed, while presentational information becomes effectively utilized when arranged.

Definitional information often converges or encompasses concepts, or is classified to clarify its role. It’s not necessarily effective just by being arranged. On the other hand, presentational information may serve as an intermediate point when arranged, or may indicate the relevance or weight between things, often not identifiable as “definitional”.

Moreover, these two aspects can either give depth to a single piece of information if they are facets of the same, or influence each other if separate. For example, if “definitional information” is well-organized, it can become a catalyst for effectively arranging the other, “presentational information”. Alternatively, new “definitions” may arise when “presentational information” is better arranged.

Although most information has both aspects, more purely definitional information functions better when not arranged, while more purely presentational information should ideally not be indexed.

Each aspect should be handled in the form most suited to it, and should be utilized concurrently.

Two “Spaces” Provided in Heptabase

Heptabase offers a mapping attribute area called “Whiteboard” and a management attribute area called “Tag”. Information can be handled in both areas, or exist in just one.

In general information apps, the Tag function is often an additional feature. Whether the structure is directory-based or map-based, the tags are usually “added” to the information existing on the underlying infrastructure. In most such apps, information that “exists nowhere but only has tags” does not exist.

However, in Heptabase, if a Tag is attached, the information exists in the management area, even if it does not exist on the Whiteboard.

This means there are:

Information existing in both the Whiteboard and Tag areas

Information only arranged

Information only managed

Unaffiliated information

What I strongly felt disconcerting when I first used Heptabase was the “equivalence” of the Tag area to the Whiteboard area. The general notion had been that tags were classifications “belonging somewhere”, and in many cases, tags quickly became saturated and unusable.

However, a month after starting to use Heptabase, it made sense. Both the Whiteboard and Tag have deep structures, which are very carefully designed.

Information has its “appropriate place for utilization” according to its aspect, and each needed to be mutually utilized under the same operational system. That’s why the developer created such a structure, I understood. (To be continued)