Skip to main content

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

This topic will require more than one post, because there is more than one definition of "Explanation".  That is, the term "Explanation" signifies more that one concept.

The first kind of explanation we will deal with can be defined as:

"Bringing a mind to an understanding of a topic".

This means that an explanation must be relative to the mind which is to be brought to the intended understanding.  For instance, the way we explain the solar system to an 8-year old child will likely be different to the way we explain the solar system to a college undergraduate.  The explanation offered will depend on prior knowledge, experience, developed intelligence, and probably many other factors.  Differences between defintion and explanation can be summarized as follows:
  • A definition is not intended to be proportional to any mind.  It has to be the best description of a concept that is available. This is is quite unlike explanation, where there will be many explanations proportionate to the types of minds which are to be provided with a given explanation.  
  • There can be many explanations for a concept, but there should be only one definition.  
  • An explanation may exclude difficult points (say to convey an initial understanding), but a definition must be as complete as possible.  
  • An explanation may avoid technical language.  A definition should aim to exclude technical language, but it may sometimes need to include technical language.
There is always a danger that an analyst creating a definition will treat it as an explanation.  This will likely make the definition unusable as an authoritative reference.  The analyst will probably only be guessing at the type of mind any explanation is aimed at.  It is one reason careful governance of definitions is needed (so analysts do not go in the wrong direction).  

It can be argued that there is an environment in which the definition is to be used, and that the definition should be the best for that environment - but might be vary across such environments.  For instance, the insurance concept of "Incurred But Not Reported" can be defined within the environment of Insurance Company X, without any intent to be used in any other insurance company.

An issue here is that if a definiton is the best for a particular environment, how can this satisfy the vision of the Semantic Web which would seem to have common definitions of concepts across the entire web?  However, this is an issue beyond comparing definition to explanation.

Labels

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

HL7V2.x to HL7V3.0 Translation Issues Details-2

In continuation of my previous post this post lists the other issues associated with HL7 v2.x to HL7v3 translation Conformance Patterns: The other major issue with the transformation of messages is the behavior of application when a particular information exchange takes place. In HL7V3.0 apart from the trigger events and interactions there exists the notion of application role as senders and receivers. The application role is characterized as the entire set of interactions for which the sender and receiver are responsible for transmitting. HL7V3.0 clearly defines the possible interactions and the application behavior associated these interactions in the form of responses for which the sender and receiver needs to adhere to. The differences in messages between V2.x and V3.0 and absence of clear guidance on V2.x regarding application behavior on receipt of message makes the transformation exercise more difficult. Vocabulary: It is a well known fact that 80% of HL7 V2.x message failu...
Post a Comment
Read more

Hack WiFi Account From Phishing Attack With WifiPhisher

WiFi Phishing Attack With WifiPhisher Tool  Wifiphisher   is a security tool that mounts fast automated phishing attacks against WiFi networks in order to obtain secret passphrases and other credentials. It is a social engineering attack that unlike other methods it does not include any brute forcing. It is an easy way for obtaining credentials from captive portals and third party login pages or WPA/WPA2 secret passphrases. From the victim's perspective, the attack makes use in three phases: 1. Victim is being deauthenticated from her access point. Wifiphisher continuously jams all of the target access point's wifi devices within range by sending deauth packets to the client from the access point, to the access point from the client, and to the broadcast address as well. 2. Victim joins a rogue access point. Wifiphisher sniffs the area and copies the target access point's settings. It then creates a rogue wireless access point that is modeled on the target. It also sets up ...
Post a Comment
Read more