This site is supported by donations to The OEIS Foundation.
Propositional Equation Reasoning Systems
Author: Jon Awbrey
This article develops elementary facts about a family of formal calculi described as Propositional Equation Reasoning Systems (PERS). The work follows on the alpha graphs Charles Sanders Peirce devised as a graphical syntax for propositional logic and on the calculus of indications George Spencer Brown presented in his Laws of Form.
Contents
 1 Formal development
 2 Formal extension : Cactus calculus
 3 Case analysissynthesis theorem
 4 Logic as sign transformation
 5 Analysis of contingent propositions
 6 Proof as semiosis
 7 Computation and inference as semiosis
 8 Variations on a theme of transitivity
 9 References
 10 See also
 11 External links
 12 Document history
Formal development
The first order of business is to give the exact forms of the axioms we use, devolving from Peirce's “Logical Graphs” via SpencerBrown's Laws of Form (LOF). In formal proofs we use a variation of the annotation scheme from LOF to mark each step of the proof according to which axiom, or initial, is being invoked to justify the corresponding step of syntactic transformation, whether it applies to graphs or to strings.
Axioms
The axioms are just four in number, divided into the arithmetic initials, and and the algebraic initials, and
(1)  
(2)  
(3)  
(4) 
One way of assigning logical meaning to the initial equations is known as the entitative interpretation Under the axioms read as follows:

Another way of assigning logical meaning to the initial equations is known as the existential interpretation Under the axioms read as follows:

All of the axioms in this set have the form of equations. This means that all of the inference licensed by them are reversible. The proof annotation scheme employed below makes use of a double bar to mark this fact, but it will often be left to the reader to decide which of the two possible ways of applying the axiom is the one that is called for in a particular case.
Peirce introduced these formal equations at a level of abstraction that is one step higher than their customary interpretations as propositional calculi, which two readings he called the Entitative and the Existential interpretations, here referred to as and respectively. The early CSP, as in his essay on “Qualitative Logic”, and also GSB, emphasized the interpretation, while the later CSP developed mostly the interpretation.
Frequently used theorems
C_{1}. Double negation
The first theorem goes under the names of Consequence 1 the double negation theorem (DNT), or Reflection.
(5) 
The proof that follows is adapted from the one that was given by George Spencer Brown in his book Laws of Form (LOF) and credited to two of his students, John Dawes and D.A. Utting.

(6) 
The steps of this proof are replayed in the following animation.

(7) 
C_{2}. Generation theorem
One theorem of frequent use goes under the nickname of the weed and seed theorem (WAST). The proof is just an exercise in mathematical induction, once a suitable basis is laid down, and it will be left as an exercise for the reader. What the WAST says is that a label can be freely distributed or freely erased anywhere in a subtree whose root is labeled with that label. The second in our list of frequently used theorems is in fact the base case of this weed and seed theorem. In LOF, it goes by the names of Consequence 2 or Generation.
(8) 
Here is a proof of the Generation Theorem.

(9) 
The steps of this proof are replayed in the following animation.

(10) 
C_{3}. Dominant form theorem
The third of the frequently used theorems of service to this survey is one that SpencerBrown annotates as Consequence 3 or Integration. A better mnemonic might be dominance and recession theorem (DART), but perhaps the brevity of dominant form theorem (DFT) is sufficient reminder of its doubleedged role in proofs.
(11) 
Here is a proof of the Dominant Form Theorem.

(12) 
The following animation provides an instant re*play.

(13) 
Exemplary proofs
Based on the axioms given at the outest, and aided by the theorems recorded so far, it is possible to prove a multitude of much more complex theorems. A couple of alltime favorites are given next.
Peirce's law
 Main article : Peirce's law
Peirce's law is commonly written in the following form:
The existential graph representation of Peirce's law is shown below.
(14) 
A graphical proof of Peirce's law is shown next.

(15) 
The following animation replays the steps of the proof.

(16) 
Praeclarum theorema
An illustrious example of a propositional theorem is the praeclarum theorema, the admirable, shining, or splendid theorem of Leibniz.
If a is b and d is c, then ad will be bc. This is a fine theorem, which is proved in this way: a is b, therefore ad is bd (by what precedes), d is c, therefore bd is bc (again by what precedes), ad is bd, and bd is bc, therefore ad is bc. Q.E.D. (Leibniz, Logical Papers, p. 41). 
Under the existential interpretation, the praeclarum theorema is represented by means of the following logical graph.
(17) 
And here's a neat proof of that nice theorem.

(18) 
The steps of the proof are replayed in the following animation.

(19) 
Twothirds majority function
Consider the following equation in boolean algebra, posted as a problem for proof at MathOverFlow.

(20) 
The required equation can be proven in the medium of logical graphs as shown in the following Figure.

(21) 
Here's an animated recap of the graphical transformations that occur in the above proof:

(22) 
Formal extension : Cactus calculus
Let us now extend the CSP–GSB calculus in the following way:
The first extension is the reflective extension of logical graphs, or what may be described as the cactus language, after its principal graphtheoretic data structure. It is generated by generalizing the negation operator in a particular manner, treating as the minimal negation operator of order 1 and adding another such operator for each order greater than 1. Taken in series, the minimal negation operators are symbolized by parenthesized argument lists of the following shapes: and so on, where the number of argument slots is the order of the reflective negation operator in question.
Fundamental evaluation rule
The formal rule of evaluation for a lobe or operator may be summarized as follows:
oo  Fundamental Evaluation Rule  oo    x_1 x_2 ... x_k   oo...oo   \ /   \ /   \ /   \ /   \ /   \ /   \ /   @ = @       ( x_1, x_2, ..., x_k ) = <space>       IF AND ONLY IF     o   Just one of the x_1, x_2, ..., x_k =  = ( )   @    oo 
(23) 
These operators may be interpreted for logic as assertions about the values of their listed arguments, resulting in the following pair of dual interpretations.
oo  Interpretation Rule  oo    x_1 x_2 ... x_k   oo...oo   \ /   \ /   \ /   \ /   \ /   \ /   \ /   @       A "klobe operator" of the form "(x_1, ..., x_k)"   enjoys two commonly employed interpretations for   propositional logic, in other words, two ways of   taking it as an assertion about, or a constraint   upon, the logical values of the listed arguments,   the mentioned variables x_j, for j = 1 through k.     Existential Interpretation:     "Just one of the k arguments is not true."     Entitative Interpretation:     "Not just one of the k arguments is true."    oo 
(24) 
Additional evaluation rules
Three immediate corollaries of the fundamental evaluation rule are listed below for future reference.
oo  Emptiness Rule  oo    o oo ooo    \ / \ /   @ = @ = @ = ...    oo 
(23a) 
oo  Indistinctness Rule  oo    a a a a a   o oo ooo    \ / \ /   @ = @ = @ = ...    oo 
(23b) 
oo  Setup/Spike Evaluation Rule  oo    o    x_2 ... x_k   oo...oo   \ /   \ /   \ /   \ /   \ /   \ / x_2 ... x_k   @ = @    oo    ((), x_2, ..., x_k) = x_2 ... x_k    oo  Setup <  > Spike  oo 
(23c) 
Case analysissynthesis theorem
Discussion
The task at hand is build a bridge between modeltheoretic and prooftheoretic perspectives on logical procedure, though for now we join them at a point so close to their common source that it may not seem worth the candle at all. The substance of this principle was known to Boole in the 1850's, tantamount to what we now call the boolean expansion of a propositional expression. The only novelty here resides in a certain manner of presentation, in which we will prove the basic principle from the axioms given before. One name for this rule is the Case AnalysisSynthesis Theorem (CAST).
I am going to revert to my customarily sloppy workshop manners and refer to propositions and proposition expressions on rough analogy with functions and function expressions, which implies that a proposition will be regarded as the chief formal object of discussion, enjoying many proposition expressions, formulas, or sentences that express it, but worst of all I will probably just go ahead and use any and all of these terms as loosely as I see fit, taking a bit of extra care only when I see the need.
Let be a propositional expression with an unspecified, but contextappropriate number of variables, say, none, or or as the case may be.
 Strings and graphs that have no labels are called bare.
 A bare terminal node, symbolized by a small circle in text, is known as a stone.
 A bare terminal edge, symbolized by a vertical bar in text, is known as a stick.
Let the replacement expression of the form denote the proposition that results from by replacing every token of the variable with a blank, that is to say, by erasing
Let the replacement expression of the form denote the proposition that results from by replacing every token of the variable with a stick stemming from the site of
In the case of a propositional expression that has no token of the designated variable let it be stipulated that
I think that I am at long last ready to state the following:
oo  Case AnalysisSynthesis Theorem (CAST)  oo    x   o   x    Q[o/x] oo Q[/x]   Q \ /   @ = @    oo    Q = ( Q[o/x] x , Q[/x] (x) )    oo 
(25) 
In order to think of tackling even the roughest sketch toward a proof of this theorem, we need to add a number of axioms and axiom schemata. Because I abandoned prooftheoretic purity somewhere in the middle of grinding this calculus into computational form, I never got around to finding the most elegant and minimal, or anything near a complete set of axioms for the cactus language, so what I list here are just the slimmest rudiments of the hodgepodge of rules of thumb that I have found over time to be necessary and useful in most working settings. Some of these special precepts are probably provable from genuine axioms, but I have yet to go looking for a more proper formulation.
oo  Precept L_1. Indifference  oo    a   o   a    oo   \ /   @ = @    oo    (a, (a)) =    oo  Split <  > Merge  oo 
(26) 
oo  Precept L_2. Equality. The Following Are Equivalent:  oo    b a b a   o oo o   a  \ /  b   oo o oo   \ /  \ /   @ = @ = @    oo    (a, (b)) = ((a , b)) = ((a), b)    oo 
(27) 
oo  Precept L_3. Dispersion  oo    For k > 1, the following equation holds:     y_1 y_2 ... y_k x y_1 x y_2 ... x y_k   oo...oo oo...oo   \ / \ /   \ / \ /   \ / \ /   \ / \ /   \ / \ /   \ / \ /   \ / \ /   \ / \ /   \ / \ /   x @ = @     x (y_1, ..., y_k) = (x y_1, ..., x y_k)    oo  Distill <  > Disperse  oo 
(28) 
To see why the Dispersion Rule holds, look at it this way: If is true, then the presence of makes no difference on either side of the equation, but if is false, then both sides of the equation are false.
Here is a proof sketch for the Case AnalysisSynthesis Theorem (CAST):
oo  Case AnalysisSynthesis Theorem. Proof Sketch.  oo    Q   @    o=============================< L1. Split " " >=============o    x   o   x    oo   \ /   Q @    o=============================< L3. Disperse "Q" >==========o    x   o   x    Q oo Q   \ /   @    o=============================< C1. Reflect "x" >===========o    x   o   x    Q oo Q[((x))/x]   \ /   @    o=============================< C2. Weed "x", "(x)" >=======o    x   o   x    Q[o/x] oo Q[/x]   \ /   @    o=============================< QES >=======================o 
(29) 
Praeclarum theorema : Proof by CAST
Some of the jobs that the CAST can be put to work on are proving propositional theorems and establishing equations between propositions. Once again, let us turn to the example of Leibniz's Praeclarum Theorema as a way of illustrating how.

(30) 
The following Figure provides an animated recap of the graphical transformations that occur in the above proof:

(31) 
The logical graph that concludes this proof is a variant type of disjunctive normal form (DNF) for the logical graph that was to be demonstrated.
(32) 
Remembering that a blank node is the graphical equivalent of a logical value the resulting DNF may be read as follows:
oo    Either not 'a' and thus 'true'   Or 'a' and thus   Either not 'd' and thus 'true'   Or 'd' and thus   Either not 'b' and thus 'true'   Or 'b' and thus   Either not 'c' and thus 'true'   Or 'c' and thus true.    oo 
(33) 
That is tantamount to saying that the proposition being submitted for analysis is true in every case. Thus we are justified in awarding it the title of a Theorem.
Logic as sign transformation
We have been looking at various ways of transforming propositional expressions, expressed in the parallel formats of character strings and graphical structures, all the while preserving certain aspects of their “meaning” — and here I risk using that vaguest of all possible words, but only as a promissory note, hopefully to be cached out in a more meaningful species of currency as the discussion develops.
I cannot pretend to be acquainted with or to comprehend every form of intension that others might find of interest in a given form of expression, nor can I speak for every form of meaning that another might find in a given form of syntax. The best that I can hope to do is to specify what my object is in using these expressions, and to say what aspects of their syntax are meant to serve this object, lending these properties the interest I have in preserving them as I put the expressions through the paces of their transformations.
On behalf of this object I have been spinning in the form of this thread a developing example base of propositional expressions, in the data structures of graphs and strings, along with many examples of stepwise transformations on these expressions that preserve something of significant logical import, something that might be referred to as their logical equivalence class (LEC), and that we could as well call the constraint information or the denotative object of the expression in view.
To focus still more, let us return to that Splendid Theorem noted by Leibniz, and let us look more carefully at the two distinct ways of transforming its initial expression that we just used to arrive at an equivalent expression, one that made its tautologous character or its theorematic nature as evident as it could be.
Just to remind you, here is the Splendid Theorem again:
(34) 
The first way of transforming the expression that appears on the left hand side of the equation can be described as prooftheoretic in character. 
The second way of transforming the expression that appears on the left hand side of the equation can be described as modeltheoretic in character. 
What we have here amounts to a couple of different styles of communicative conduct, that is, two sequences of signs of the form each one beginning with a problematic expression and eventually ending with a clear expression of the logical equivalence class to which every sign or expression in the sequence belongs. Ordinarily, any orbit through a locus of signs can be taken to reflect an underlying signprocess, a case of semiosis. So what we have here are two very special cases of semiosis, and what we may find it useful to contemplate is how to characterize them as two species of a very general class.
We are starting to delve into some fairly picayune details of a particular sign system, nontrivial enough in its own right but still rather simple compared to the types of our ultimate interest, and though I believe that this exercise will be worth the effort in prospect of understanding more complicated sign systems, I feel that I ought to say a few words about the larger reasons for going through this work.
My broader interest lies in the theory of inquiry as a special application or a special case of the theory of signs. Another name for the theory of inquiry is logic and another name for the theory of signs is semiotics. So I might as well have said that I am interested in logic as a special application or a special case of semiotics. But what sort of a special application? What sort of a special case? Well, I think of logic as formal semiotics — though, of course, I am not the first to have said such a thing — and by formal we say, in our etymological way, that logic is concerned with the form, indeed, with the animate beauty and the very life force of signs and sign actions. Yes, perhaps that is far too Latin a way of understanding logic, but it's all I've got.
Now, if you think about these things just a little more, I know that you will find them just a little suspicious, for what besides logic would I use to do this theory of signs that I would apply to this theory of inquiry that I'm also calling logic? But that is precisely one of the things signified by the word formal, for what I'd be required to use would have to be some brand of logic, that is, some sort of innate or inured skill at inquiry, but a style of logic that is casual, catchascatchcan, formative, incipient, inchoate, unformalized, a work in progress, partially built into our natural language and partially more primitive than our most artless language. In so far as I use it more than mention it, mention it more than describe it, and describe it more than fully formalize it, then to that extent it must be consigned to the realm of unformalized and unreflective logic, where some say “there be oracles”, but I don't know.
Still, one of the aims of formalizing what acts of reasoning that we can is to draw them into an arena where we can examine them more carefully, perhaps to get better at their performance than we can unreflectively, and thus to live, to formalize again another day. Formalization is not the beall endall of human life, not by a long shot, but it has its uses on that behalf.
This looks like a good place to pause and take stock. The question arises: What is really going on here? We have all these signs, but what is the object? One object worth the candle is simply to study a nontrivial example of a syntactic system, simple in design but not entirely a toy, just to see how these systems tick. More than that, we would like to understand how sign systems come to exist or can be placed in relation to object systems, in the likes of which we possess some compelling independent reason to take an interest. What is the utility of setting up sets of strings and sets of graphs, and sorting them according to their semiotic equivalence class (SEC) based on this or that abstract notion of transformational equivalence?
Good questions.
I can but begin to address these questions in the present frame of work, but I can't hope to answer them in anything like a satisfactory fashion. Nevertheless, I will not mind one bit if you keep them in mind as we go.
Analysis of contingent propositions
For all of the reasons mentioned above, and for the sake of a more compact illustration of the ins and outs of a typical propositional equation reasoning system, let's now take up a much simpler example of a contingent proposition:
(35) 
For the sake of simplicity in discussing this example, let's stick with the existential interpretation of logical graphs and their corresponding parse strings. Under the formal expression translates into the vernacular expression in symbols, so this is the reading that we'll want to keep in mind for the present. Where brevity is required, we may refer to the propositional expression under the name by making use of the following definition:
Since the expression involves just three variables, it may be worth the trouble to draw a venn diagram of the situation. There are in fact two different ways to execute the picture.
Figure 2 indicates the points of the universe of discourse for which the proposition has the value 1, here interpreted as the logical value In this paint by numbers style of picture, one simply paints over the cells of a generic template for the universe going according to some previously adopted convention, for instance: Let the cells that get the value 0 under remain untinted and let the cells that get the value 1 under be painted or shaded. In doing this, it may be good to remind ourselves that the value of the picture as a whole is not in the paints, in other words, the in but in the pattern of regions that they indicate.
(36)  
There are a number of standard ways in mathematics and statistics for talking about the subset of the functional domain that gets painted with the value by the indicator function The region is called by a variety of names in different settings, for example, the antecedent, the fiber, the inverse image, the level set, or the preimage in of under It is notated and defined as Here, is called the converse relation or the inverse relation — it is not in general an inverse function — corresponding to the function Whenever possible in simple examples, we use lower case letters for functions and it is sometimes useful to employ capital letters for subsets of if possible, in such a way that is the fiber of 1 under in other words,
The easiest way to see the sense of the venn diagram is to notice that the expression read as can also be read as Its assertion effectively excludes any tincture of truth from the region of that lies outside the region In a similar manner, the expression read as can also be read as Asserting it effectively excludes any tincture of truth from the region of that lies outside the region
Figure 3 shows the other standard way of drawing a venn diagram for such a proposition. In this punctured soap film style of picture — others may elect to give it the more dignified title of a logical quotient topology — one begins with Figure 31 and then proceeds to collapse the fiber of 0 under down to the point of vanishing utterly from the realm of active contemplation, arriving at the following picture:
(37)  
This diagram indicates that the region where is true is wholly contained in the region where both and are true. Since only the regions that are painted true in the previous figure show up at all in this one, it is no longer necessary to distinguish the fiber of 1 under by means of any shading.
In sum, it is immediately obvious from the venn diagram that in drawing a representation of the following propositional expression:
in other words,
we are also looking at a picture of:
in other words,
Let us now examine the following propositional equation:
(38) 
There are three distinct ways that I can think of right off as to how we might go about formally proving or systematically checking the proposed equivalence, the evidence of whose truth we already have before us clearly enough, and in a visually intuitive form, from the venn diagrams that we examined above.
While we go through each of these ways let us keep one eye out for the character and the conduct of each type of proceeding as a semiotic process, that is, as an orbit, in this case discrete, through a locus of signs, in this case propositional expressions, and as it happens in this case, a sequence of transformations that perseveres in the denotative objective of each expression, that is, in the abstract proposition that it expresses, while it preserves the informed constraint on the universe of discourse that gives us one viable candidate for the informational content of each expression in the interpretive chain of sign metamorphoses.
A sign relation is a subset of a cartesian product where are sets known as the object, sign, and interpretant sign domains, respectively. These facts are symbolized by writing Accordingly, a sign relation consists of ordered triples of the form where belong to the domains respectively. An ordered triple of the form is referred to as a sign triple or an elementary sign relation.
The syntactic domain of a sign relation is defined as the settheoretic union of its sign domain and its interpretant domain It is not uncommon, especially in formal examples, for the sign domain and the interpretant domain to be equal as sets, in short, to have
Sign relations may contain any number of sign triples, finite or infinite. Finite sign relations do arise in applications and can be very instructive as expository examples, but most of the sign relations of significance in logic have infinite sign and interpretant domains, and usually infinite object domains, in the long run, at least, though one frequently works up to infinite domains by a series of finite approximations and gradual stages.
With that preamble behind us, let us turn to consider the case of semiosis, or sign transformation process, that is generated by our first proof of the propositional equation
(39) 
For some reason I always think of this as the way that our DNA would prove it.
We are in the process of examining various proofs of the propositional equation and viewing these proofs in the light of their character as semiotic processes, in essence, as signtheoretic transformations.
The second way of establishing the truth of this equation is one that I see, rather loosely, as modeltheoretic, for no better reason than the sense of its ending with a pattern of expression, a variant of the disjunctive normal form (DNF), that is commonly recognized to be the form that one extracts from a truth table by pulling out the rows of the table that evaluate to true and constructing the disjunctive expression that sums up the senses of the corresponding interpretations.
In order to apply this modeltheoretic method to an equation between a couple of contingent expressions, one must transform each expression into its associated DNF and then compare those to see if they are equal. In the current setting, these DNF's may indeed end up as identical expressions, but it is possible, also, for them to turn out slightly offkilter from each other, and so the ultimate comparison may not be absolutely immediate. The explanation of this is that, for the sake of computational efficiency, it is useful to tailor the DNF that gets developed as the output of a DNF algorithm to the particular form of the propositional expression that is given as input.

(40) 
The final graph in the sequence of equivalents is a disjunctive normal form (DNF) for the proposition on the left hand side of the equation
(41) 
Remembering that a blank node is the graphical equivalent of a logical value the resulting DNF may be read as follows:
oo    Either not 'p' and thus 'true'   Or 'p' and thus   Either not 'q' and thus 'false'   Or 'q' and thus   Either not 'r' and thus 'false'   Or 'r' and thus 'true'.    oo 
(42) 
It remains to show that the right hand side of the equation is logically equivalent to the DNF just obtained. The needed chain of equations is as follows:

(43) 
This is not only a logically equivalent DNF but exactly the same DNF expression that we obtained before, so we have established the given equation Incidentally, one may wish to note that this DNF expression quickly folds into the following form:
(44) 
This can be read to say which gives us yet another equivalent for the expression and the expression Still another way of writing the same thing would be as follows:
(45) 
In other words,
One lemma that suggests itself at this point is a principle that may be canonized as the Emptiness Rule. It says that a bare lobe expression like with any number of places for arguments but nothing but blanks as filler, is logically tantamount to the prototypical expression of its type, namely, the constant expression that interprets as denoting the logical value To depict the rule in graphical form, we have the continuing sequence of equations:
oo  Emptiness Rule  oo    o oo ooo    \ / \ /   @ = @ = @ = ...    oo 
(46) 
Yet another rule that we'll need is the following:
oo  Indistinctness Rule  oo    a a a a a   o oo ooo    \ / \ /   @ = @ = @ = ...    oo 
(47) 
This one is easy enough to derive from rules that are already known, but just for the sake of ready reference it is useful to canonize it as the Indistinctness Rule. Finally, let me introduce a ruleofthumb that is a bit more suited to routine computation, and that serves to replace the indistinctness rule in many cases where we actually have to call on it. This is actually just a special case of the evaluation rule listed above:
oo  Evaluation Rule  oo    o    x_2 ... x_k   oo...oo   \ /   \ /   \ /   \ /   \ /   \ / x_2 ... x_k   @ = @    oo    ((), x_2, ..., x_k) = x_2 ... x_k    oo  Setup <  > Spike  oo 
(48) 
To continue with the beating of this stillkicking horse in the form of the equation let's now take up the third way that I mentioned for examining propositional equations, even if it is literally a third way only at the very outset, almost immediately breaking up according to whether one proceeds by way of the more routine modeltheoretic path or else by way of the more strategic prooftheoretic path.
Let's convert the equation between propositions:

into the corresponding equational proposition:

If you're like me, you'd rather see it in pictures:
(49) 
We may now interrogate the alleged equation for the third time, working by way of the case analysissynthesis theorem (CAST).

(50) 
And that, of course, is the DNF of a theorem.
Proof as semiosis
We have been looking at several different ways of proving one particular example of a propositional equation, and along the way we have been exemplifying the species of sign transforming process that is commonly known as a proof, more specifically, an equational proof of the propositional equation at issue. Let us now draw out these semiotic features of the business of proof and place them in relief.
Our syntactic domain contains an infinite number of signs or expressions, which we may choose to view in either their text or their graphic forms, glossing over for now the many details of their particular correspondence.
Here are some of the expressions that we find salient enough to single out and confer an epithetic nickname on:

Under we have the following interpretations:
expresses the logical constant 
expresses the logical constant 
says 
says 
says 
says that and say the same thing. 
We took up the Equation that reads as follows:
Each of our proofs is a finite sequence of signs, and thus, for a finite integer takes the form:
Proof 1 proceeded by the straightforward approach, starting with as and ending with as
 That is, Proof 1 commenced from the sign and ended up at the sign by legal moves.
Proof 2 lit on by burning the candle at both ends, changing into a normal form that reduced to and changing into a normal form that also reduced to in this way tethering and to a common stake.
 Filling in the details, one route went from to and another went from to thus equating the two points of departure.
Proof 3 took the path of reflection, expressing the metaequation between and in the form of the naturalized equation then taking as and exchanging it by dint of value preserving steps for as
 This way of proceeding went from to the blank expression that recognizes as the value
Computation and inference as semiosis
Equational reasoning, as distinguished from implicational reasoning, is wellevolved in mathematics today but grievously shortschrifted in contemporary logic textbooks. Consequently, it may be advisable for me to draw out and place in relief some of the more distinctive characters of equational inference that may have passed beneath the notice of a casual reading of these notes.
By way of a very preliminary orientation, let us consider the distinction between information reducing inferences and information preserving inferences. It is prudent to make make our first acquaintance with this distinction in the medium of some concrete and simple examples.


Let us examine these two types of inference in a little more detail. A rule of inference is stated in the followed form:
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \begin{array}{l} ~ \textit{Expression}~\textit{1} \\ ~ \textit{Expression}~\textit{2} \\ \overline{~~~~~~~~~~~~~~~~~~~~~~~~~} \\ ~ \textit{Expression}~\textit{3} \end{array}} 
The expressions above the line are called premisses and the expression below the line is called a conclusion. If the rule of inference is simple enough, the prooftheoretic turnstile symbol Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle {}^{\backprime\backprime} \vdash {}^{\prime\prime}} may be used to write the rule on a single line, as follows:
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \textit{Premiss}~\textit{1}, \textit{Premiss}~\textit{2} ~\vdash~ \textit{Conclusion}.} 
Either way, one reads such a rule of inference in the following manner:
From Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle {\textit{Expression}~\textit{1}}} and Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle {\textit{Expression}~\textit{2}}} infer Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle {\textit{Expression}~\textit{3}}.} 
Looking to Example 1, the rule of inference known as modus ponens says the following: From the premiss Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle p \Rightarrow q} and the premiss Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle p} one may logically infer the conclusion Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle q.}
Modus ponens is an illative or implicational rule. Passage through its turnstile incurs the toll of some information loss, and thus from a fact of Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle q} alone one cannot infer with any degree of certainty that and Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle p} are the reasons why Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle q} happens to be true.
Further considerations along these lines may lead us to appreciate the difference between implicational rules of inference and equational rules of inference, the latter indicated by an equational line of inference or a 2way turnstile Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle {}^{\backprime\backprime} \Vdash {}^{\prime\prime}.}
Variations on a theme of transitivity
The next Example is extremely important, and for reasons that reach well beyond the level of propositional calculus as it is ordinarily conceived. But it's slightly tricky to get all of the details right, so it will be worth taking the trouble to look at it from several different angles and as it appears in diverse frames, genres, or styles of representation.
In discussing this Example, it is useful to observe that the implication relation indicated by the propositional form Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle x \Rightarrow y} is equivalent to an order relation on the boolean values Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0, 1 \in \mathbb{B},} where is taken to be less than
•  Example 2. Transitivity  
Information Reducing Inference  
 
Information Preserving Inference  

In stating the informationpreserving analogue of transitivity, I have taken advantage of a common idiom in the use of order relation symbols, one that represents their logical conjunction by way of a concatenated syntax. Thus, means The claim that this 3adic order relation holds among the three propositions is a stronger claim — conveys more information — than the claim that the 2adic relation holds between the two propositions and
To study the differences between these two versions of transitivity within what is locally a familiar context, let's view the propositional forms involved as if they were elementary cellular automaton rules, resulting in the following Table.










Taking up another angle of incidence by way of extra perspective, let us now reflect on the venn diagrams of our four propositions.
(52)  
(53)  
(54)  
(55)  
Among other things, these images make it visually obvious that the constraint on the three boolean variables that is indicated by asserting either of the forms Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \texttt{(} p \texttt{(} q \texttt{))(} q \texttt{(} r \texttt{))}} or implies a constraint on the two boolean variables that is indicated by either of the forms or but that it imposes additional constraints on these variables that are not captured by the illative conclusion.
One way to view a proposition Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle f : \mathbb{B}^k \to \mathbb{B}} is to consider its fiber of truth, and to regard it as a Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle k} adic relation Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle L \subseteq \mathbb{B}^k.}
By way of general definition, the fiber of a function Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle f : X \to Y} at a given value of its codomain is the antecedent (also known as the inverse image or preimage) of under This is a subset, possibly empty, of the domain notated as
In particular, if is a proposition then the fiber of truth is the subset of that is indicated by the proposition Whenever we assert a proposition we are saying that what it indicates is all that happens to be the case in the relevant universe of discourse Because the fiber of truth is used so often in logical contexts, it is convenient to define the more compact notation
Using this panoply of notions and notations, we may treat the fiber of truth of each proposition as if it were a relational data table of the shape where the triples are bittuples indicated by the proposition
Thus we obtain the following four relational data tables for the propositions that we are looking at in Example 2.
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1}  
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0}  
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1} 
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0} 
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1} 
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle p}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle q}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle r} 
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0} 
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0}  
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0}  
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1}  
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1}  
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1} 
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle p}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle q}  
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0} 
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1}  
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1}  
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1} 
In the medium of these unassuming examples, we begin to see the activities of logical inference and methodical inquiry as information clarifying operations.
First, we drew a distinction between information preserving and information reducing processes and we noted the related distinction between equational and implicational inferences. I will use the acronyms EROI and IROI, respectively, for the equational and implicational analogues of the various rules of inference.
For example, we considered the brands of information fusion that are involved in a couple of standard rules of inference, taken in both their equational and their illative variants.
In particular, let us assume that we begin from a state of uncertainty about the universe of discourse that is standardly represented by a uniform distribution such that for all in in short, by the constant proposition This amounts to the maximum entropy sign state (MESS). As a measure of uncertainty, let us use either the multiplicative measure given by the cardinality of commonly notated as or else the additive measure given by In this frame we have and to wit, 3 bits of doubt.
Let us now consider the various rules of inference for transitivity in the light of their performance as informationdeveloping actions.
•  Transitive Law (Implicational Inference)  
 
•  By itself, the information would reduce our uncertainty from bits to bits.  
•  By itself, the information would reduce our uncertainty from bits to bits.  
•  By itself, the information would reduce our uncertainty from bits to bits. 
In this situation the application of the implicational rule of inference for transitivity to the information and the information to get the information does not increase the measure of information beyond what any one of the three propositions has independently of the other two. In a sense, then, the implicational rule operates only to move the information around without changing its measure in the slightest bit.
•  Transitive Law (Equational Inference)  
 
•  The contents and the measures of information that are associated with the propositions and Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle q \le r} are the same as before.  
•  On its own, the information Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle p \le q \le r} would reduce our uncertainty from log(8) = 3 bits to log(4) = 2 bits, a reduction of 1 bit. 
These are just some of the initial observations that can be made about the dimensions of information and uncertainty in the conduct of logical inference, and there are many issues to be taken up as we get to the thick of it. In particular, we are taking propositions far too literally at the outset, reading their spots at face value, as it were, without yet considering their species character as fallible signs.
For ease of reference in the rest of this discussion, let us refer to the propositional form Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle f : \mathbb{B}^3 \to \mathbb{B}} such that Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle f(p, q, r) = f_{139}(p, q, r) = \texttt{(} p \texttt{(} q \texttt{))(} q \texttt{(} r \texttt{))}} as the syllogism map, written as Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \mathrm{syll} : \mathbb{B}^3 \to \mathbb{B},} and let us refer to its fiber of truth Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle [ \mathrm{syll} ] = \mathrm{syll}^{1}(1)} as the syllogism relation, written as Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \mathrm{Syll} \subseteq \mathbb{B}^3.} Table 60 shows Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \mathrm{Syll}} as a relational dataset.
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle p}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle r}  
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0} 
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1}  
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1} 
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1} 
One of the first questions that we might ask about a 3adic relation, in this case Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \mathrm{Syll},} is whether it is determined by its 2adic projections. I will illustrate what this means in the present case.
Table 61 repeats the relation in the first column, listing its 3tuples in bitstring form, followed by the 2adic or planar projections of in the next three columns. For instance, is the 2adic projection of on the plane that is arrived at by deleting the column and counting each 2tuple that results just one time. Likewise, is obtained by deleting the column and is derived by deleting the column, ignoring whatever duplicate pairs may result. The final row of the right three columns gives the propositions of the form that indicate the 2adic relations that result from these projections.




Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \texttt{(} p ~ \texttt{(} q \texttt{))}}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \texttt{(} p ~ \texttt{(} r \texttt{))}}  Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \texttt{(} q ~ \texttt{(} r \texttt{))}} 
Let us make the simple observation that taking a projection, in our framework, deleting a column from a relational table, is like taking a derivative in differential calculus. What it means is that our attempt to return to the integral from whence the derivative was derived will in general encounter an indefinite variation on account of the circumstance that real information may have been destroyed by the derivation.
One will find that some relations can be reconstructed from various types of derivatives and projections, others cannot. The reconstuctible relations are said to be reducible to the types of reductive data in question, while the others are said to be irreducible with respect to those means.
The analogies between derivation, differentiation, implication, projection, and others sorts of information reducing operation will undergo extensive development in the remainder and sequel of the present discussion.
We were in the middle of discussing the relationships between information preserving rules of inference and information destroying rules of inference — folks of a 3basket philosophical bent will no doubt be asking, “And what of information creating rules of inference?”, but there I must wait for some signs of enlightenment, desiring not to tread on the rules of that succession.
The contrast between the information destroying and the information preserving versions of the transitive rule of inference led us to examine the relationships among several boolean functions, namely, those that qualify locally as the elementary cellular automata rules Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle f_{139}, f_{175}, f_{187}, f_{207}.}
The function Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle f_{139} : \mathbb{B}^3 \to \mathbb{B}} and its fiber Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle [ f_{139} ] \subseteq \mathbb{B}^3} appeared to be key to many structures in this setting, and so I singled them out under the new names of Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \mathrm{syll} : \mathbb{B}^3 \to \mathbb{B}} and Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \mathrm{Syll} \subseteq \mathbb{B}^3,} respectively.
Managing the conceptual complexity of our considerations at this juncture put us in need of some conceptual tools that I broke off to develop in my notes on "Reductions Among Relations". The main items that we need right away from that thread are the definitions of relational projections and their inverses, the tacit extensions.
But the more I survey the problem setting the more it looks like we need better ways to bring our visual intuitions to play on the scene, and so let us next lay out some visual schemata that are designed to facilitate that.
Figure 62 shows the familiar picture of a boolean 3cube, where the points of Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \mathbb{B}^3} are coordinated as bit strings of length three. Looking at the functions and the relations Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle L \subseteq \mathbb{B}^3} on this pattern, one views the construction of either type of object as a matter of coloring the nodes of the 3cube with choices from a pair of colors that stipulate which points are in the relation Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle {L = [ f ]}} and which points are out of it. Bowing to common convention, we may use the color Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 1} for points that are in a given relation and the color Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle 0} for points that are out of the same relation. However, it will be more convenient here to indicate the former case by writing the coordinates in the place of the node and to indicate the latter case by plotting the point as an unlabeled node "o".
oo    111   /\   /  \   /  \   /  \   /  \   /  \   /  \   110 101 011   \ / \ /    \ / \ /     \ / \ /     \ /     / \ / \     / \ / \    / \ / \   100 010 001   \  /   \  /   \  /   \  /   \  /   \  /   \/   000    oo Figure 62. Boolean 3Cube B^3 
(62) 
Table 63 shows the 3adic relation Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \mathrm{Syll} \subseteq \mathbb{B}^3} again, and Figure 64 shows it plotted on a 3cube template.
Table 63. Syll c B^3 oo  p q r  oo  0 0 0   0 0 1   0 1 1   1 1 1  oo 
(63) 
oo    111   /\   /  \   /  \   /  \   /  \   /  \   /  \   o o 011   \ / \ /    \ / \ /     \ / \ /     \ /     / \ / \     / \ / \    / \ / \   o o 001   \  /   \  /   \  /   \  /   \  /   \  /   \/   000    oo Figure 64. Triadic Relation Syll c B^3 
(64) 
We return once more to the plane projections of Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \mathrm{Syll} \subseteq \mathbb{B}^3.}
Table 65. Syll c B^3 oo  p q r  oo  0 0 0   0 0 1   0 1 1   1 1 1  oo 
(65) 
Table 66. Dyadic Projections of Syll oo oo oo  Syll_12   Syll_13   Syll_23  oo oo oo  p q   p r   q r  oo oo oo  0 0   0 0   0 0   0 1   0 1   0 1   1 1   1 1   1 1  oo oo oo  (p (q))   (p (r))   (q (r))  oo oo oo 
(66) 
In showing the 2adic projections of a 3adic relation Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle L \subseteq \mathbb{B}^3,} I will translate the coordinates of the points in each relation to the plane of the projection, there dotting out with a dot “.” the bit of the bit string that is out of place on that plane.
Figure 67 shows Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \mathrm{Syll}} and its three 2adic projections:
oo    111   /\   /  \   /  \   /  \   /  \   /  \   /  \   o o 011   \ / \ /    \ / \ /     \ / \ /     \ /     / \ / \     / \ / \    / \ / \   o o 001   \  /   11. \  / .11   \ \  / /    \ \  / /     \ \  / /     \ \  / /     \ \/ /     \ 000 /     \ /    o 01. o .01   \   /   \   /   \   /   \  1.1  /   \  / \  /   \  / \  /   \ / \ /   00. / \ .00   / \   / \   / \   o 0.1   \ /   \ /   \ /   \ /   \ /   \ /   \ /   0.0    oo Figure 67. Syll c B^3 and its Dyadic Projections 
(67) 
We now compute the tacit extensions of the 2adic projections of Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \mathrm{Syll},} alias Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle f_{139},} and this makes manifest its relationship to the other functions and fibers, namely, Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle f_{175}, f_{187}, f_{207}.}
Table 68. Syll c B^3 oo  p q r  oo  0 0 0   0 0 1   0 1 1   1 1 1  oo 
(68) 
Table 69. Dyadic Projections of Syll oo oo oo  Syll_12   Syll_13   Syll_23  oo oo oo  p q   p r   q r  oo oo oo  0 0   0 0   0 0   0 1   0 1   0 1   1 1   1 1   1 1  oo oo oo  (p (q))   (p (r))   (q (r))  oo oo oo 
(69) 
Table 70. Tacit Extensions of Projections of Syll oo oo oo  te(Syll_12)   te(Syll_13)   te(Syll_23)  oo oo oo  p q r   p q r   p q r  oo oo oo  0 0 0   0 0 0   0 0 0   0 0 1   0 1 0   1 0 0   0 1 0   0 0 1   0 0 1   0 1 1   0 1 1   1 0 1   1 1 0   1 0 1   0 1 1   1 1 1   1 1 1   1 1 1  oo oo oo  [ (p (q)) ]   [ (p (r)) ]   [ (q (r)) ]  oo oo oo  [ f_207 ]   [ f_175 ]   [ f_187 ]  oo oo oo 
(70) 
oo    111   /\   /  \   /  \   /  \   /  \   /  \   /  \   110 o 011   \ / \ /    \ / \ /     \ / \ /     \ /     / \ / \     / \ / \    / \ / \   o 010 001   \  /   11. \  /   \ \  /    \ \  /    \ \  /    \ \  /    \ \/    \ 000    \   o 01.   \    \    \    \    \    \    \   00.    oo Figure 71. Tacit Extension te_12_3 (Syll_12) 
(71) 
oo    111   /\   /  \   /  \   /  \   /  \   /  \   /  \   o 101 011   \ / \ /    \ / \ /     \ / \ /     \ /     / \ / \     / \ / \    / \ / \   o 010 001   \  /   \  /   \  /   \  /   \  /   \  /   \/   000       1.1   / \   / \   / \   / \   / \   / \   / \   o 0.1   \ /   \ /   \ /   \ /   \ /   \ /   \ /   0.0    oo Figure 72. Tacit Extension te_13_2 (Syll_13) 
(72) 
oo    111   /\   /  \   /  \   /  \   /  \   /  \   /  \   o 101 011   \ / \ /    \ / \ /     \ / \ /     \ /     / \ / \     / \ / \    / \ / \   100 o 001   \  /   \  / .11   \  / /   \  / /    \  / /    \  / /    \/ /    000 /    /    o .01    /    /    /    /    /    /   /   .00    oo Figure 73. Tacit Extension te_23_1 (Syll_23) 
(73) 
The reader may wish to contemplate Figure 74 and use it to verify the following two facts:
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \begin{array}{lcc} \mathrm{Syll} & = & \mathrm{te}(\mathrm{Syll}_{12}) \cap \mathrm{te}(\mathrm{Syll}_{23}) \\[6pt] \mathrm{Syll}_{13} & = & \mathrm{Syll}_{12} \circ \mathrm{Syll}_{23} \end{array}} 
oo    *   /\   /  \   /  \   /  \   /  \   /  \   /  \   o o *   /\ / \ /\   /  \ / \ /  \   /  \ / \ /  \   /  \ /  \   /  / \ / \  \   /  / \ / \  \   / / \ / \ \   / o o * \   / \ / / \ \   * \ /  / \ *   \ \ /  / \ /    \ /  / \ /     \ / \  / \ /     \ / \  / /     \ / \/ / \     \ / * / \     \ / / \ / \   o * / \ o *   \  / \  /   \  / \  /   \  / \  /   \  / * \  /   \  / / \ \  /   \  / / \ \  /   \/ / \ \/   * / \ *   / \   / \   / \   o *   \ /   \ /   \ /   \ /   \ /   \ /   \ /   *    oo Figure 74. Syll = te(Syll_12) ^ te(Syll_23) 
(74) 
I don't know about you, but I am still puzzled by all of thus stuff, that is to say, by the entanglements of composition and projection and their relationship to the information processing properties of logical inference rules. What I lack is a single picture that could show me all of the pieces and make the pattern of their informational relationships clear.
In accord with my experimental way, I will stick with the case of transitive inference until I have pinned it down thoroughly, but of course the real interest is much more general than that.
At first sight, the relationships seem easy enough to write out. Figure 75 shows how the various logical expressions are related to each other: The expressions Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle {}^{\backprime\backprime} \texttt{(} p ~ \texttt{(} q \texttt{))} {}^{\prime\prime}} and are conjoined in a purely syntactic fashion — much in the way that one might compile a theory from axioms without knowing what either the theory or the axioms were about — and the best way to sum up the state of information implicit in taking them together is just the expression Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle {}^{\backprime\backprime} \texttt{(} p ~ \texttt{(} q \texttt{))} ~ \texttt{(} q ~ \texttt{(} r \texttt{))}{}^{\prime\prime}} that would the canonical result of an equational or reversible rule of inference. From that equational inference, one might arrive at the implicational inference Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle {}^{\backprime\backprime} \texttt{(} p ~ \texttt{(} r \texttt{))} {}^{\prime\prime}} by the most conventional implication.
oo oo      q   r   o   o         p o   q o         @   @      oo oo  (p (q))   (q (r))  oo oo  f_207   f_187  ooo ooo \ / \ Conjunction / \ / v v oo        q r   o o       p o o q   \ /   @    oo  (p (q)) (q (r))  oo  f_139  ooo  Implication  v ooo    r   o      p o      @    oo  (p (r))  oo  f_175  oo Figure 75. Expressive Aspects of Transitive Inference 
Most of the customary names for this type of process have turned out to have misleading connotations, and so I will experiment with calling it the expressive aspect of the various rules for transitive inference, simply to emphasize the fact that rules can be given for it that operate solely on signs and expressions, without necessarily needing to look at the objects that are denoted by these signs and expressions.
In the way of many experiments, the word expressive does not seem to work for what I wanted to say here, since we too often use it to suggest something that expresses an object or a purpose, and I wanted it to imply what is purely a matter of expression, shorn of consideration for anything objective. Aside from coining a word like ennotative, some other options would be connotative, hermeneutic, semiotic, syntactic — each of which works in some range of interpretation but fails in others. Let's try formulaic.
Despite how simple the formulaic aspects of transitive inference might appear on the surface, there are problems that wait for us just beneath the syntactic surface, as we quickly discover if we turn to considering the kinds of objects, abstract and concrete, that these formulas are meant to denote, and all the more so if we try to do this in a context of computational implementations, where the "interpreters" to be addressed take nothing on faith. Thus we engage the denotative semantics or the model theory of these extremely simple programs that we call propositions.
Figure 76 is an attempt to outline the modeltheoretic relationships that are involved in our study of transitive inference. A couple of alternative notations are introduced in this Table:
The forms Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle X:Y:Z} and Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle x:y:z} are used as alternative notations for the cartesian product Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle X \times Y \times Z} and the tuple Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle (x, y, z),} respectively. 
In situations where we have products like Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle X:Y:Z} with and relations like Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle {L \subseteq X:Y},} Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle {M \subseteq X:Z},} Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle {N \subseteq Y:Z},} the forms Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle {L \subseteq \mathbb{B}:\mathbb{B}:},} Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle {M \subseteq \mathbb{B}::\mathbb{B}},} Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle {N \subseteq :\mathbb{B}:\mathbb{B}}} are used to remind us that we are considering particular ways of situating Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle {L, M, N}} within the product space Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle X:Y:Z.} 
oo oo      0:0:0   0:0:0   0:0:1   0:0:1   0:1:0   0:1:1   0:1:1   1:0:0   1:1:0   1:0:1   1:1:1   1:1:1      oo oo te(Syll_12) c B:B:B te(Syll_23) c B:B:B oo oo  [ f_207 ]   [ f_187 ]  oooo oooo ^ \ / ^  \ Intersection /   \ /   v v   oo        0:0:0     0:0:1     0:1:1     1:1:1        oo    Syll c B:B:B    oo    [ f_139 ]    ooo      Projection      v   ooo        0:0     0:1     1:1        oo    Syll_13 c B:~:B    oo    [ (p (r)) ]    oooo   ^ ^   / \   / Composition \   / \  oooo oooo      0:0   0:0   0:1   0:1   1:1   1:1      oo oo  Syll_12 c B:B:~   Syll_23 c ~:B:B  oo oo  [ (p (q)) ]   [ (q (r)) ]  ooo ooo Figure 76. Denotative Aspects of Transitive Inference 
A piece of syntax like Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle {}^{\backprime\backprime} \texttt{(} p \texttt{(} q \texttt{))} {}^{\prime\prime}} or Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle {}^{\backprime\backprime} p \Rightarrow q {}^{\prime\prime}} is an abstract description, and abstraction is a process that loses information about the objects described. So when we go to reverse the abstraction, as we do when we look for models of that description, there is a degree of indefiniteness that comes into play.
For example, the proposition Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \texttt{(} p \texttt{(} q \texttt{))}} is typically assigned the functional type Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \mathbb{B}^2 \to \mathbb{B},} but that is only its canonical or its minimal abstract type. No sooner do we use it in a context that invokes additional variables, as we do when we next consider the proposition Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \texttt{(} q \texttt{(} r \texttt{))},} than its type is tacitly adjusted to fit the new context, for instance, acquiring the extended type This is one of those things that most people eventually learn to do without blinking an eye, that is to say, unreflectively, and this is precisely what makes the same facility so much trouble to implement properly in computational form.
Both the fibering operation, that takes us from the function Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \texttt{(} p \texttt{(} q \texttt{))}} to the relation Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle [ \texttt{(} p \texttt{(} q \texttt{))} ],} and the tacit extension operation, that takes us from the relation Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle [ \texttt{(} p \texttt{(} q \texttt{))} ] \subseteq \mathbb{B}:\mathbb{B}} to the relation Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle [ q_{207} ] \subseteq \mathbb{B}:\mathbb{B}:\mathbb{B},} have this same character of abstractionundoing or modelling operations that require us to reinterpret the same pieces of syntax under different types. This accounts for a large part of the apparent ambiguities.
Up till now I've concentrated mostly on the abstract types of domains and propositions, things like Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \mathbb{B}^k} and Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \mathbb{B}^k \to \mathbb{B},} respectively. This is a little like trying to do physics all in dimensionless quantities without keeping track of the qualitative physical units. So much abstraction has its obvious limits, not to mention its hidden dangers.
To remedy this situation I will start to introduce the concrete types of domains and propositions, once again as they pertain to our current collection of examples.
We have been using the lower case letters Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle p, q, r} for the basic propositions of abstract type Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \mathbb{B}^3 \to \mathbb{B}} and the upper case letters Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle P, Q, R} for the basic regions of the universe of discourse where Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle p, q, r,} respectively, hold true.
The set of signs Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \mathcal{X} = \{ {}^{\backprime\backprime} p {}^{\prime\prime}, {}^{\backprime\backprime} q {}^{\prime\prime}, {}^{\backprime\backprime} r {}^{\prime\prime} \}} is the alphabet for the universe of discourse that is notated as Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle X^\bullet = [\mathcal{X}] = [p, q, r],} already getting sloppy about quotation marks to single out the signs.
The universe Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle {X^\bullet}} is composed of two different spaces of objects. The first is the space of positions Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle X = \langle p, q, r \rangle = \{ (p, q, r) \}.} The second is the space of propositions Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle X^\uparrow = (X \to \mathbb{B}).}
Let us make the following definitions:
Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \begin{matrix} P^\ddagger & = & X_p & = & \{ \texttt{(} p \texttt{)}, p \}, \\[4pt] Q^\ddagger & = & X_q & = & \{ \texttt{(} q \texttt{)}, q \}, \\[4pt] R^\ddagger & = & X_r & = & \{ \texttt{(} r \texttt{)}, r \}. \end{matrix}} 
These are three sets of two abstract signs each, altogether staking out the qualitative dimensions of the universe of discourse
Given this framework, the concrete type of the space Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle X} is Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle P^\ddagger \times Q^\ddagger \times R^\ddagger ~\cong~ \mathbb{B}^3} and the concrete type of each proposition in Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle X^\uparrow = (X \to \mathbb{B})} is Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle P^\ddagger \times Q^\ddagger \times R^\ddagger \to \mathbb{B}.} Given the length of the type markers, we will often omit the cartesian product symbols and write just Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle P^\ddagger Q^\ddagger R^\ddagger.}
An abstract reference to a point of Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle X} is a triple in Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \mathbb{B}^3.} A concrete reference to a point of Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle X} is a conjunction of signs from the dimensions picking exactly one sign from each dimension.
To illustrate the use of concrete coordinates for points and concrete types for spaces and propositions, Figure 77 translates the contents of Figure 76 into the new language.
oo oo      (p)(q)(r)   (p)(q)(r)   (p)(q) r   (p)(q) r   (p) q (r)   (p) q r   (p) q r   p (q)(r)   p q (r)   p (q) r   p q r   p q r      oo oo TE(Syll_12) c B:B:B TE(Syll_23) c B:B:B oo oo  [ f_207 ]   [ f_187 ]  oooo oooo ^ \ / ^  \ Intersection /   \ /   v v   oo        (p)(q)(r)     (p)(q) r     (p) q r     p q r        oo    Syll c P‡ Q‡ R‡    oo    [ f_139 ]    ooo      Projection      v   ooo        (p) (r)     (p) r     p r        oo    Syll_13 c P‡ R‡    oo    [ (p (r)) ]    oooo   ^ ^   / \   / Composition \   / \  oooo oooo      (p) (q)   (q) (r)   (p) q   (q) r   p q   q r      oo oo  Syll_12 c P‡ Q‡   Syll_23 c Q‡ R‡  oo oo  [ (p (q)) ]   [ (q (r)) ]  ooo ooo Figure 77. Denotative Aspects of Transitive Inference 
References
 Leibniz, G.W. (1679–1686 ?), “Addenda to the Specimen of the Universal Calculus”, pp. 40–46 in Parkinson, G.H.R. (ed.), Leibniz : Logical Papers, Oxford University Press, London, UK, 1966. (Cf. Gerhardt, 7, p. 223).
 Peirce, C.S. (1931–1935, 1958), Collected Papers of Charles Sanders Peirce, vols. 1–6, Charles Hartshorne and Paul Weiss (eds.), vols. 7–8, Arthur W. Burks (ed.), Harvard University Press, Cambridge, MA. Cited as CP volume.paragraph.
 Peirce, C.S. (1981–), Writings of Charles S. Peirce : A Chronological Edition, Peirce Edition Project (eds.), Indiana University Press, Bloomington and Indianoplis, IN. Cited as CE volume, page.
 Peirce, C.S. (1885), “On the Algebra of Logic : A Contribution to the Philosophy of Notation”, American Journal of Mathematics 7 (1885), 180–202. Reprinted as CP 3.359–403 and CE 5, 162–190.
 Peirce, C.S. (c. 1886), “Qualitative Logic”, MS 736. Published as pp. 101–115 in Carolyn Eisele (ed., 1976), The New Elements of Mathematics by Charles S. Peirce, Volume 4, Mathematical Philosophy, Mouton, The Hague.
 Peirce, C.S. (1886 a), “Qualitative Logic”, MS 582. Published as pp. 323–371 in Writings of Charles S. Peirce : A Chronological Edition, Volume 5, 1884–1886, Peirce Edition Project (eds.), Indiana University Press, Bloomington, IN, 1993.
 Peirce, C.S. (1886 b), “The Logic of Relatives : Qualitative and Quantitative”, MS 584. Published as pp. 372–378 in Writings of Charles S. Peirce : A Chronological Edition, Volume 5, 1884–1886, Peirce Edition Project (eds.), Indiana University Press, Bloomington, IN, 1993.
 Spencer Brown, George (1969), Laws of Form, George Allen and Unwin, London, UK.
See also
Related essays and projects
 Futures Of Logical Graphs
 Information = Comprehension × Extension
 Inquiry Driven Systems
 Introduction to Inquiry Driven Systems
 Peirce's Logic Of Information
 Semiotic Theory Of Information
Related concepts and topics
External links
 Spencer Brown's Talks at Esalen 1973 • Selfreferential forms are introduced in the section entitled “Degree of Equations and the Theory of Types”.
Document history
Standard Upper Ontology (Mar–Apr 2001)
 http://web.archive.org/web/20140423181000/http://suo.ieee.org/email/msg04187.html
 http://web.archive.org/web/20070922193822/http://suo.ieee.org/email/msg04305.html
 http://web.archive.org/web/20071007170752/http://suo.ieee.org/email/msg04413.html
 http://web.archive.org/web/20070121063018/http://suo.ieee.org/email/msg04419.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/email/msg04422.html
 http://web.archive.org/web/20070305132316/http://suo.ieee.org/email/msg04423.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/email/msg04432.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/email/msg04454.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/email/msg04455.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/email/msg04476.html
 http://web.archive.org/web/20060718091105/http://suo.ieee.org/email/msg04510.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/email/msg04517.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/email/msg04525.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/email/msg04533.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/email/msg04536.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/email/msg04542.html
 http://web.archive.org/web/20050824231950/http://suo.ieee.org/email/msg04546.html
Ontology List (Mar–Apr 2001)
 http://web.archive.org/web/20070326233418/http://suo.ieee.org/ontology/msg01779.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg01897.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg02005.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg02011.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg02014.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg02015.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg02024.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg02046.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg02047.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg02068.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg02102.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg02109.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg02117.html
 http://web.archive.org/web/20040116001230/http://suo.ieee.org/ontology/msg02125.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg02128.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg02134.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg02138.html
Arisbe List (Feb 2003)
 http://web.archive.org/web/20140619114651/http://stderr.org/pipermail/arisbe/2003February/001541.html
 http://web.archive.org/web/20140619114657/http://stderr.org/pipermail/arisbe/2003February/001542.html
 http://web.archive.org/web/20140619115440/http://stderr.org/pipermail/arisbe/2003February/001543.html
 http://web.archive.org/web/20140619114703/http://stderr.org/pipermail/arisbe/2003February/001544.html
 http://web.archive.org/web/20140619115220/http://stderr.org/pipermail/arisbe/2003February/001545.html
 http://web.archive.org/web/20140619115225/http://stderr.org/pipermail/arisbe/2003February/001546.html
 http://web.archive.org/web/20140619114707/http://stderr.org/pipermail/arisbe/2003February/001547.html
 http://web.archive.org/web/20140619114712/http://stderr.org/pipermail/arisbe/2003February/001548.html
 http://web.archive.org/web/20140619115446/http://stderr.org/pipermail/arisbe/2003February/001549.html
 http://web.archive.org/web/20140619114829/http://stderr.org/pipermail/arisbe/2003February/001550.html
 http://web.archive.org/web/20140619115451/http://stderr.org/pipermail/arisbe/2003February/001552.html
 http://web.archive.org/web/20140619115230/http://stderr.org/pipermail/arisbe/2003February/001553.html
 http://web.archive.org/web/20140619115456/http://stderr.org/pipermail/arisbe/2003February/001554.html
 http://web.archive.org/web/20140619114834/http://stderr.org/pipermail/arisbe/2003February/001555.html
 http://web.archive.org/web/20140619115501/http://stderr.org/pipermail/arisbe/2003February/001557.html
 http://web.archive.org/web/20140619115235/http://stderr.org/pipermail/arisbe/2003February/001559.html
Ontology List (Feb 2003)
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/thrd19.html#04522
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/thrd19.html#04532
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg04522.html
 http://web.archive.org/web/20070302152422/http://suo.ieee.org/ontology/msg04523.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg04524.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg04525.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg04526.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg04527.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg04528.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg04529.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg04530.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg04531.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg04532.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg04533.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg04534.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg04536.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg04537.html
 http://web.archive.org/web/20070705085032/http://suo.ieee.org/ontology/msg04538.html
Inquiry List (Mar 2003)
 http://web.archive.org/web/20150109150400/http://stderr.org/pipermail/inquiry/2003March/000126.html
 http://web.archive.org/web/20150109150401/http://stderr.org/pipermail/inquiry/2003March/000127.html
 http://web.archive.org/web/20140619114723/http://stderr.org/pipermail/inquiry/2003March/000128.html
 http://web.archive.org/web/20140619115507/http://stderr.org/pipermail/inquiry/2003March/000129.html
 http://web.archive.org/web/20140619115246/http://stderr.org/pipermail/inquiry/2003March/000130.html
 http://web.archive.org/web/20140619115251/http://stderr.org/pipermail/inquiry/2003March/000131.html
 http://web.archive.org/web/20140619114728/http://stderr.org/pipermail/inquiry/2003March/000132.html
 http://web.archive.org/web/20140619114733/http://stderr.org/pipermail/inquiry/2003March/000133.html
 http://web.archive.org/web/20140619115256/http://stderr.org/pipermail/inquiry/2003March/000134.html
 http://web.archive.org/web/20140619114844/http://stderr.org/pipermail/inquiry/2003March/000135.html
 http://web.archive.org/web/20140619114849/http://stderr.org/pipermail/inquiry/2003March/000136.html
 http://web.archive.org/web/20140619114738/http://stderr.org/pipermail/inquiry/2003March/000137.html
 http://web.archive.org/web/20140619115512/http://stderr.org/pipermail/inquiry/2003March/000138.html
 http://web.archive.org/web/20140619115301/http://stderr.org/pipermail/inquiry/2003March/000139.html
 http://web.archive.org/web/20140619114743/http://stderr.org/pipermail/inquiry/2003March/000140.html
 http://web.archive.org/web/20140619115306/http://stderr.org/pipermail/inquiry/2003March/000141.html
 http://web.archive.org/web/20140619114748/http://stderr.org/pipermail/inquiry/2003March/000142.html
NKS Forum (Apr–May 2004)
 http://web.archive.org/web/20141210150520/http://forum.wolframscience.com/archive/topic/297.html
 http://web.archive.org/web/20130929153121/http://forum.wolframscience.com/showthread.php?threadid=297&perpage=50
 http://web.archive.org/web/20140619112627/http://forum.wolframscience.com/showthread.php?postid=950#post950
 http://web.archive.org/web/20140619112742/http://forum.wolframscience.com/showthread.php?postid=952#post952
 http://web.archive.org/web/20140619112632/http://forum.wolframscience.com/showthread.php?postid=953#post953
 http://web.archive.org/web/20140619112642/http://forum.wolframscience.com/showthread.php?postid=954#post954
 http://web.archive.org/web/20140619112748/http://forum.wolframscience.com/showthread.php?postid=957#post957
 http://web.archive.org/web/20140619112648/http://forum.wolframscience.com/showthread.php?postid=958#post958
 http://web.archive.org/web/20140619112753/http://forum.wolframscience.com/showthread.php?postid=959#post959
 http://web.archive.org/web/20140619112758/http://forum.wolframscience.com/showthread.php?postid=961#post961
 http://web.archive.org/web/20140619112804/http://forum.wolframscience.com/showthread.php?postid=962#post962
 http://web.archive.org/web/20140619112653/http://forum.wolframscience.com/showthread.php?postid=964#post964
 http://web.archive.org/web/20140619112658/http://forum.wolframscience.com/showthread.php?postid=965#post965
 http://web.archive.org/web/20140619112808/http://forum.wolframscience.com/showthread.php?postid=967#post967
 http://web.archive.org/web/20140619112813/http://forum.wolframscience.com/showthread.php?postid=968#post968
 http://web.archive.org/web/20140619112703/http://forum.wolframscience.com/showthread.php?postid=973#post973
 http://web.archive.org/web/20140619112819/http://forum.wolframscience.com/showthread.php?postid=976#post976
 http://web.archive.org/web/20140619112708/http://forum.wolframscience.com/showthread.php?postid=977#post977
 http://web.archive.org/web/20140619112824/http://forum.wolframscience.com/showthread.php?postid=981#post981
 http://web.archive.org/web/20140619112829/http://forum.wolframscience.com/showthread.php?postid=988#post988
 http://web.archive.org/web/20140619112917/http://forum.wolframscience.com/showthread.php?postid=990#post990
 http://web.archive.org/web/20140619112922/http://forum.wolframscience.com/showthread.php?postid=994#post994
 http://web.archive.org/web/20140619112718/http://forum.wolframscience.com/showthread.php?postid=1003#post1003
 http://web.archive.org/web/20140619112535/http://forum.wolframscience.com/showthread.php?postid=1005#post1005
 http://web.archive.org/web/20140619112723/http://forum.wolframscience.com/showthread.php?postid=1015#post1015
 http://web.archive.org/web/20140619112540/http://forum.wolframscience.com/showthread.php?postid=1022#post1022
 http://web.archive.org/web/20140619112727/http://forum.wolframscience.com/showthread.php?postid=1025#post1025
 http://web.archive.org/web/20140619112545/http://forum.wolframscience.com/showthread.php?postid=1031#post1031
 http://web.archive.org/web/20140619112551/http://forum.wolframscience.com/showthread.php?postid=1220#post1220
 http://web.archive.org/web/20140619112733/http://forum.wolframscience.com/showthread.php?postid=1224#post1224
 http://web.archive.org/web/20140619112556/http://forum.wolframscience.com/showthread.php?postid=1227#post1227
 http://web.archive.org/web/20140619112601/http://forum.wolframscience.com/showthread.php?postid=1228#post1228
 http://web.archive.org/web/20140619112606/http://forum.wolframscience.com/showthread.php?postid=1232#post1232
 http://web.archive.org/web/20140619112611/http://forum.wolframscience.com/showthread.php?postid=1249#post1249
 http://web.archive.org/web/20140619112737/http://forum.wolframscience.com/showthread.php?postid=1262#post1262
 http://web.archive.org/web/20140619112616/http://forum.wolframscience.com/showthread.php?postid=1265#post1265
 http://web.archive.org/web/20140619112621/http://forum.wolframscience.com/showthread.php?postid=1273#post1273
Inquiry List (2004–2006)
 http://web.archive.org/web/20141210145032/http://stderr.org/pipermail/inquiry/2004April/thread.html#1341
 http://web.archive.org/web/20141207162001/http://stderr.org/pipermail/inquiry/2004May/thread.html#1391
 http://web.archive.org/web/20140619115359/http://stderr.org/pipermail/inquiry/2006January/thread.html#3364
 http://web.archive.org/web/20141210153038/http://stderr.org/pipermail/inquiry/2004April/001341.html
 http://web.archive.org/web/20141210153039/http://stderr.org/pipermail/inquiry/2004April/001342.html
 http://web.archive.org/web/20140619115316/http://stderr.org/pipermail/inquiry/2004April/001343.html
 http://web.archive.org/web/20140619114854/http://stderr.org/pipermail/inquiry/2004April/001344.html
 http://web.archive.org/web/20140619115522/http://stderr.org/pipermail/inquiry/2004April/001345.html
 http://web.archive.org/web/20140619114758/http://stderr.org/pipermail/inquiry/2004April/001346.html
 http://web.archive.org/web/20140619114900/http://stderr.org/pipermail/inquiry/2004April/001347.html
 http://web.archive.org/web/20140619115321/http://stderr.org/pipermail/inquiry/2004April/001348.html
 http://web.archive.org/web/20140619115527/http://stderr.org/pipermail/inquiry/2004April/001349.html
 http://web.archive.org/web/20140619115326/http://stderr.org/pipermail/inquiry/2004April/001350.html
 http://web.archive.org/web/20140619115532/http://stderr.org/pipermail/inquiry/2004April/001351.html
 http://web.archive.org/web/20140619115537/http://stderr.org/pipermail/inquiry/2004April/001352.html
 http://web.archive.org/web/20140619115331/http://stderr.org/pipermail/inquiry/2004April/001353.html
 http://web.archive.org/web/20140619115542/http://stderr.org/pipermail/inquiry/2004April/001354.html
 http://web.archive.org/web/20140619115336/http://stderr.org/pipermail/inquiry/2004April/001355.html
 http://web.archive.org/web/20140619115547/http://stderr.org/pipermail/inquiry/2004April/001356.html
 http://web.archive.org/web/20140619114905/http://stderr.org/pipermail/inquiry/2004April/001357.html
 http://web.archive.org/web/20140619115552/http://stderr.org/pipermail/inquiry/2004April/001358.html
 http://web.archive.org/web/20140619114803/http://stderr.org/pipermail/inquiry/2004April/001359.html
 http://web.archive.org/web/20140619114808/http://stderr.org/pipermail/inquiry/2004April/001360.html
 http://web.archive.org/web/20140619115343/http://stderr.org/pipermail/inquiry/2004April/001361.html
 http://web.archive.org/web/20140619114910/http://stderr.org/pipermail/inquiry/2004April/001362.html
 http://web.archive.org/web/20140619115557/http://stderr.org/pipermail/inquiry/2004April/001363.html
 http://web.archive.org/web/20140619114917/http://stderr.org/pipermail/inquiry/2004April/001364.html
 http://web.archive.org/web/20140619114922/http://stderr.org/pipermail/inquiry/2004April/001365.html
 http://web.archive.org/web/20140619115348/http://stderr.org/pipermail/inquiry/2004April/001366.html
 http://web.archive.org/web/20140619115609/http://stderr.org/pipermail/inquiry/2004April/001389.html
 http://web.archive.org/web/20140619115614/http://stderr.org/pipermail/inquiry/2004April/001390.html
 http://web.archive.org/web/20140619114819/http://stderr.org/pipermail/inquiry/2004May/001391.html
 http://web.archive.org/web/20140619114824/http://stderr.org/pipermail/inquiry/2004May/001392.html
 http://web.archive.org/web/20140619115619/http://stderr.org/pipermail/inquiry/2004May/001393.html
 http://web.archive.org/web/20140619114928/http://stderr.org/pipermail/inquiry/2004May/001394.html
 http://web.archive.org/web/20140619114933/http://stderr.org/pipermail/inquiry/2004May/001395.html
 http://web.archive.org/web/20140619115641/http://stderr.org/pipermail/inquiry/2004May/001396.html
 http://web.archive.org/web/20140619115649/http://stderr.org/pipermail/inquiry/2004May/001398.html
 http://web.archive.org/web/20140619115354/http://stderr.org/pipermail/inquiry/2006January/003364.html