Skip to main content

How is a Definition Different from an Explanation? (Part 2)

In Part I of this series (http://definitionsinsemantics.blogspot.com/2011/11/how-is-definition-different-from.html), we explored explanation defined as "bringing a mind to an understanding of a topic".  

There is, however, another form of explanation, of which Aristotle said "We believe ourselves to know a thing when we are acquainted with its cause" (Posterior Analytics, II C. II para 1).

One way to provide this kind of explanation is by arguing from the cause to the effect.  Traditionally this involved using syllogisms where the cause was in the major premiss and the effect was in the conclusion.  E.g. All ellipses show a pattern of positions X; the orbit of Mars shows a pattern of positions X; therefore the orbit of Mars is an ellipse.

This form of explanation is very satifying, and it might seem natural to try to incorporate it into definitions.  However, there are reasons not to do so.  First, the above form requires putting the concept to be defined into propositions, and then putting the propositions into a syllogism (an argument).  And then putting all of that into the definition.  But if all this is part of the definition, and the definition is supposed to substitute for the term being defined, we would seem to end up with an infinite regression.  Of course, this is always a danger when the term to be defined is in the definition, but having an argument in the definition seems to assure this as the term has to be included in the argument.  At least it seems that way to me - although I cannot find any description of my opinion in the literature, and I will willingly defer to others who can prove me wrong.

Secondly, putting argument into a definition exposes the definition to much greater chance of error.  The propositions may be false, and the argumentation may be invalid.  And why would we put the concept into propositions and arguments before we have a completed definition - surely that is jumping the gun.

My provisional conclusion, therefore, is that causal explanations should not be placed in definitions.  

BUT, there is another consideration.  In modern enterprises, definitions are containers as well as content.  If an explanation has to be provided, and there is nowhere else to put it, then it should be put into the definition (as container, not content).  The distinction between container and content is not found (at least by me) in traditional logic.  Yet it is a most important consideration.  I suppose we need another blog on definition as container vs. content.

If we are forced to put a causal explanation in the definition (container) then at least get the concept defined fully (content) before any explanation is provided, so the explanation is not part of the true definition (content).

Comments

Popular Posts

Create Your Own Social Networking Site

Create Your Own Social Networking Site JCOW: Ethical Hacking Top 10 reasons to choose Jcow:- 1. Handle more traffic - Clean codes and Dynamic caching can lower the CPU load and  speed up your website. 2 Make your site more interactive - Well designed Jcow applications help you members to connect and communicate with others more effectively. 3 Add questions to the Registration Form - You can add new member fields, which will be displayed to the registration form, profile form, and the member browsing form. 4 Easily share stuff - Within the AJAX sharing Box, your members can publish status,  photos, videos, and blogs. 5 Customize and Extend your Jcow Network - A Jcow network consists of core apps(like "Friends" and "Messages") and optional apps(like "Blogs" and ""Videos"). You can enable/disable optional apps. You can also develop your own apps. 6 Every profile could be Unique - Members can customize their own profile theme and  add music play...

The Problem of Abstraction in Definitions of Data Objects

I think there is a major problem in not being able to understand and work with different levels of abstraction.  By "abstraction" in this sense I mean one concept system that somehow describes or defines (not merely relates to) another concept system.  I think this is a big problem for definitions in data models. Let us take an example in a retail business such as mortgage banking: Customer Name.  Customer Name exists in the business.  They use it all the time.  Maybe it is sometimes called Borrower Name, but the concept is the same.  This is the Level 1 abstraction. Now let us think of data values in a column in a table that holds Customer Name.  These data values are stored as a code of 1's and 0's.  Of course these bits are rendered into something we can read.  However, this is not the same as the Customer Name in the business.  I worked for a place where they prefixed the name of anyone who had recently left with "ZZZ"....

The Humpty-Dumpty Principle in Definitions

In dealing with empty concepts, we came across the issue that if somebody uses a term that potentially has an unintelligible definition, they are likely to defend themselves by quickly making up some kind of definition.   I strongly suspect that in such cases, the usage of the term will be inconsistent with the definition.  Which brings us to Humpty-Dumpty. Lewis Carroll (Rev. Charles Lutwidge Dodgson) is best known for his children's' books Alice's Adventures in Wonderland and Through the Looking Glass .  It is in the latter that Humpty Dumpty - an argumentative egg perched on a wall has the following exchange with Alice: 'And only one for birthday presents, you know. There's glory for you!' `I don't know what you mean by "glory",' Alice said. Humpty Dumpty smiled contemptuously. `Of course you don't -- till I tell you. I meant "there's a nice knock-down argument for you!"' `But "glory" doesn't mean "...