While a conventional document represents just absolute truth, the 2D-information contains a flexible set of similar concepts.
The 2D-infoExplorer allows creating info-structures with arbitrary number of Levels and Instances. A conventional MS Word or HTML document is nothing more than just a private case in this system. Namely, this is only one Instance at a certain Level of abstraction! Even having all .doc files, each of which represents text for a specific Instance and Level, is not enough to manage knowledge effectively. Only the 2D-infoSpace allows integrating the text objects into one system, and provides an unique mechanism for navigation between the objects. The result is in creating a very dynamic information environment, which can be easily customized, or further extended.
Take for example the Word Pro from Lotus, which is number one in versioning. It boasts with extremely efficient memory management. We can save disk space because only differences between versions are saved. Like Lotus Word Pro, the 2D-infoExplorer creates a single file that contains multiple versions, and always displays the most recent version when you open the file. Unlike the Word Pro, the 2D-infoExplorer's file format is a cross-platform Java program, it can operate with full copies of all versions (problems with memory can be resolved by introducing a completely different approach to data compression*), and the term "version" is encouraged to be used in a more wide sense,- to show a point with the same meaning from variety of sources. Main advantage is in applying a more flexible control over relationships between the versions. As versions are in essence equivalents of the same meaning (and often very subjective equivalents), we should reserve an opportunity to dynamically change an order of their importance. Our opinions change in time, so do the priority of versions.
In addition, the things like calling a specified fragment from the body of a particular version are simply impossible in the Word Pro.
And another conceptual difference.
While programs like MS Word and Lotus Word are oriented towards visual representation of documents, the 2D-infoExplorer is devoted to managing knowledge classes. That shift in priority of aims is a key in understanding the difference between these two approaches. Forming layout for texts is not the same as forming object-oriented layout of knowledge.
Current software products have almost achieved the highest level of perfection as for visual formatting of documents. This means advanced text layout options,- with using variety of colors, fonts, and graphics. The HTML format is a very good example of that orientation. In contrast, my concept treats content separately from its visual representation: usually only plain text is used. Although the 2D-infoExplorer uses only a minimal set of the visual options, its advantage is in providing more effective way of processing information. This becomes especially important taking into account growing amount of information "noise" in the large data banks, including the Internet.
Although what we are actually doing in the both cases is converting data into meaningful information, this aim is achieved by using completely different approaches. Word processors help us to attach an additional meaning to the data by using visual effects, and ultimately, to form a required emotional impression for the whole document. However, computers are not humans, they able to process only the first component,- data. Therefore, it would be advisable to represent information with data separated from its visual formatting. Among other things, this simplifies further fragmentation of the data, if required. In essence, that fragmentation becomes a kind of another, more effective, meaning formatting. That's where a shell like the 2D-infoExplorer can be extremely convenient.
In short, the underlying objective of word processors is to make data attractive. In contrast, 2D-infoExplorer's objective is to develop clear information objects.
* Is implemented in the 2D-infoExplorer starting from version 2.0.