Skip to main content

A First Note on Partial Definitions

I think that partial definitions exist, and there are practical reasons for being interested in them.  I cannot find any literature about them, and this post is my first attempt at dealing with partial definitions.

The only conceptualization of a partial definition that I have figured out in any detail can be summarized by the formula:

Partial Definition = Name of Concept System + Type of Relation in Concept System

E.g., for "Wristwatch"

Definition of "Wristwatch" = "A type of timepiece"

Obviously, this parallels the Aristoteialan formula of Definiton = Genus + Specific Difference.  However, I think that Aristotle commits definitions to being only in a Concept System of generic relations (supertype-subtype to our data modeling friends).  Other types of Concept System exist, e.g. partative (part-whole), and associative. 

In a partial definition we provide information by locating the concept to be defined within a particular Concept System, giving context to the minds we are communicating with.  Of course, we must expect that these minds know about the Concept System we name in the partial definition.

The Concept System does not have to be a proximate Genus, as Aristotle would like.  It could be a much higher level generic concept, though this may broaden the context too much.  In the above example, locating "Wristwatch" in the concept system "Timepiece" provides more precise context than if I said "A type of instrument", "instrument being a more generic concept containing "Timepiece".  Obviously, there is skill required to choose the level appropriate to the mind being communicated with.

There is also the choice of Concept System to locate the concept in.  For "Wristwatch" I could have alternative partial definitions such as "A fashion accessory", or "An item of jewelery".  These identify different Concept Systems within which I wish to locate "Wristwatch" for whatever my purposes may be.

The Type of Relation in the Concept System in my formula above (e.g. "type", "part", "item") is one level of abstraction up from a description of the Concept System itself.  I think it serves to reinforce the essence of the Concept System.

While full definitons are not something we work on every day, I think partial definitions are very common in everyday communication. 

That's enough for now.  To summarize (and these points may need further proof): 
  • Partial Definitions exist
  • A common kind of Partial Definition is to locate a concept in a Concept System
  • The Partial Defintion also describes the type of relation that predominates in the Concept System
  • There is skill in selecting the Concept System as one concept can belong to many Concept Systems
  • There is skill in selecting the level of generalization of the Concept System
  • Partial Definitions are very common in everyday language (does that mean that everyone is an ontologist?)
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