Textual Geometry: The Engine Of Textual Calculus

Remember The Back Button On Your Browser

The Life Foundations Nexus

TEXTUAL GEOMETRY: THE ENGINE OF TEXTUAL CALCULUS

AKA “LEAVING THE FOG BEHIND”

Copyright July 31, 2005 3:04 PM CST

By Dr. Michael J. Bisconti

What good would all of our discoveries and research do if no one could understand it? The answer, of course, is no good at all or, at least, far less good than is possible and necessary. Therefore, when we saw early on that we were creating a complex mathematical system THAT EVEN WE WERE HAVING TROUBLE UNDERSTANDING, we spent a week praying about the matter. On the seventh day, the Lord gave us the answer – GEOMETRY. Why geometry? Geometry is PICTURES, pictures of lines, pictures of squares, pictures of rectangles, pictures of triangles, pictures of circles, etc., etc., and, of course, EVERYONE understands PICTURES. Having established the foundational principle of utilizing PICTURES (GEOMETRIC FIGURES) to represent data, we could now continue our work.

In our article on Probabilistic Textual Induction And Inductive Textual Calculus (you can just take a look at the animated graphic), we mentioned the notion of “textual rectangles.” What is a textual rectangle? A textual rectangle is “a picture (graphical representation) of a set of subdata.”

What is “subdata”? (The singular for “subdata” is “subdatum,” though the word “subdata” can be used as either singular or plural.) A subdatum (or subdata) is “an imaginary component of a piece of data.” For example, the number “1” is data. An imaginary piece of the number “1,” a subdata of the number “1” is “h1.” “H1” is read “aach-one.” The “h” stands for “half.” Therefore, “h1” can also be read “half-one.” What is h1? First, it is NOT half of the number 1; it is not ½. Remember, h1 is an imaginary thing. It exists only in the human mind and in computers.

Is h1 half of ANYTHING? Yes but not in the physical sense of half. We are not taking half of some physical thing like a pie or a loaf of bread. Think of it this way: you are looking at a number “1” on the computer screen. Suddenly, the number leaves the screen and flies off into space. You go chasing after it with a flyswatter. You manage to swat it. In doing so, you split it in half. At that point, each half grows into a full number “1.” Each of these new number “1’s” is an h1. In other words, an h1 is “a child of the number ‘1.’” To be more precise, an h1 is “a child of the number ‘1’ whose parents are the number “1” and the concept of ‘halfness’ (the quality of being half of something).”

Whew, do you have a headache, too?

Well, why do we need h1s…and h2s and h3s, etc., etc.? When we look at the history of traditional biblical textual criticism we see that macroscopic (overview) approaches to identifying the true text of the Bible DO NOT WORK. Until we came along, everyone thought that this was the only approach possible. Our approach is, if you will, “submicroscopic.” Instead of summarizing data, we split data apart. Now, in order to do this, we needed imaginary entities of some sort. (As we learned from the study of “i,” “the square root of negative one,” you can sometimes solve problems using imaginary entities [“i” is used in airplane and jet design]. A more common example of a useful, imaginary entity is the geographical concept of the “equator.”)

So, to carry on a submicroscopic approach to finding the true text of the Bible, we needed the help of imaginary entities. These imaginary entities are subdata and specific examples of subdata are “h1,” “h2,” and “h3.” Another class of subdata is based on the concept of “quarterness.” This results in “q1,” “q2,” “q3,” etc.

Now, how do we convert a verse written in…say…ancient Greek into subdata? We will explain this in terms of English. What we have to say applies equally to ancient Greek OR ANY OTHER LANGUAGE – PAST, PRESENT, OR FUTURE. We will use John 3:16:

For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life.

To simplify our discussion, we will just use the first six words of this verse:

For God so loved the world

Now, we begin the conversion process. We first replace each word with its numerical identifier. Next we find the h1 child for each of these numerical values. It is also necessary to find the h2 and h3 children but we will skip those at this time in order to avoid too much complexity in this discussion. Keep in mind that we had computers, virtual supercomputers, and (actual) supercomputers to aid us in our work; so, our job, though laborious, was not mind-numbing.

Word	Numerical Identifier	Subdata Child 1 (h1)	Subdata Child 2 (h2)	Subdata Child 3 (h3)
For	000006	.2
God	000049	.0002
so	000030	.11
loved	000233	.3
the	000003	.033303
world	000122	.0000000091

I think its time for us to introduce the pictures (geometrical figures). The table above can be translated into the following table, via some computer magic. We will focus on the words “God,” “loved,” and “world”:

Word	Geometric Identifier
God	cir (circle)
loved	tri (triangle)
world	squ (square)

Using the geometric identifiers above, we can write John 3:16 this way (this, of course, is only a partial “geometric translation” [graphic takes a couple of seconds to load]):

To read this verse in “geometrese,” you would say (“cir” is pronounced “sir,” “tri” is pronounced “try,” and “sku” is pronounced “skew”):

For cir so tri the squ, that cir gave cir only begotten Son, that whosever believeth in him should not perish but have everlasting life.

Now, of course, computers do not use geometric figures. Instead they use .0002 for “God”, .3 for “loved,” and .0000000091 for “world.” Also, these numerical identifiers are subdata, not data. Finally, for the precisionists among us, each root word and each derivative of a root word has its own numerical and geometric identifiers. For example, “loved” is .3 but “love” is .209. The geometric identifer for “love” is the same as that for “loved” except that there is a large dot in the center of the tri symbol. Computer software is able to correlate (connect) the subdata in John 3:16 in one ancient Greek manuscript with identical subdata elsewhere in this manuscript AND IN EVERY OTHER ANCIENT GREEK MANUSCRIPT. This results in the establishment of relationships and intervasalizations (“numerical evaluations of subdata”):

The following graphic takes a few seconds to load.