Skip to main content

One Term, Many Meanings - Why Are We Surprised?

David Eddy kindly supplied me with the following military tale:

A true story heard around the Pentagon goes like this:

One reason the services have trouble operating jointly is that they don't speak the same language.

"secure a building" has been found to have the following meanings...
  • Navy would turn off the lights and lock the doors.
  • Army would occupy the building so no one could enter. 
  • Marines would assault the building, capture it, and defend it with suppressive fire and close combat. 
  • Air Force, on the other hand, would take out a three-year lease with an option to buy.

I think that we can all appreciate the humor in this, but must recognize that there is something deep and important about it.  But what is the moral in this tale?

The story shows that "secure a building" means different things to four different groups.  In each case the term refers to a different concept.  And in each case the concept is clearly defined.  The concepts are all very distinct - there is no chance of confusing them.

However, the four groups are all part of the same overall organization - the Armed Forces of the United States.  It is a common assumption that one organization is a monolithic semantic community.   The reality is that enterprises are often mosaics of different subcultures, who each see the enterprise through a different ontology.  At least, this is my observation.  I would like to find some research material on it, rather than anecdotes like the one quoted above.

The view that that enterprises are mosaics of subcultures also goes against the idea that there is a single data model - a "single reality", or a "single version of the truth" - that must underlie every enterprise.

Saying that the services "don't speak the same language" is a telling statement.  Rather than suggest that each service has its own view of the world - its own ontology - the fundamental difference is attributed to language.  This brings us back to the idea of the primacy of language over conception, and Wittgenstein's notion that language is the mirror of reality.  I believe these views are invalid, and that we need to "make our ideas clear" as Peirce said, and that language can as easily trick us as inform us. 

Perhaps the lesson for an analyst is not to be surprised when the same term is used to mean different things in the same enterprise.  Indeed, the analyst should be on guard for it when technical or unusual terms are used.  Homonyms can also indicate the existence of different concept systems, or ontologies.

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...

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...

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 ...