Skip to main content

Should A Term Be Analyzed to Determine if It is an Analogy Before Attempting to Define It?

Much definitional work begins with terms.  However, it is surprising that analysts very often take a term on face value and do not try to analyze it further.  In particular, they do not try to determine if the term is an analogy.  There is value in recognizing if a term is an analogy because the analyst can be put on guard against making errors in the definition

An analogy seeks to explain a less familiar concept by some degree of resemblance to a more familiar concept.  By "explain" it is meant that there is an attempt to bring a mind to a better understanding of the less familiar concept (explanation being different to definition). 

There can be problems with analogies, e.g. a business concept explained by football analogies will be confusing to an individual with no interest in football.  Because of problems inherent in the use of analogies, the analyst must find out if the term requiring definition is an analogy.

It may be easy to detect an analogy in a term.  E.g. when it is said the economy will have a "soft landing", it is relatively easy to recognize "soft landing" as an analogy.  However, when we speak of "data ownership" (meaning responsibility for data management tasks), it is not so easy to recognize that "ownership" is an analogy (meaning possessing legal title to property).

The analyst must look at the term to be defined to see if it is entirely or partly composed of terms that signify concepts that are different to the candidate concept that the term to be defined is supposed to signify.  These analogous concepts will likely be more familiar.

A term that is an analogy may be trying to signify an empty concept.  What did Ben Bernanke mean by "green shoots".  If it was "economic improvement", why did he not use that term (which is still vague - increased productivity at the cost of job loss might not be "improvement").  "Green shoots" is probably just a term intended to provoke an emotional feeling of comfort rather than to signify an intelligible state of the economy.

Besides positing a null concept, an analogy may falsely suggest that an attribute in the more familiar concept must exist in the concept being defined.  This is not necessarily so (the fallacy of false analogy).

Because of these dangers, the analyst must detect if a term to be defined is an analogy.
Labels:

Comments

Post a Comment

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...
Post a Comment
Read more

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"....
Post a Comment
Read more

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 "...
Post a Comment
Read more