Skip to main content

Why Do Definitions - Why Not Just Use Wikipedia?

Today I spoke to the New York ERwin Modeling User Group (NYEMUG) on "Creating Great Definitions".  One question came up, which was why bother crafting definitions at all - why not simply rely on Wikipedia for them?  I suppose it could be any external source, and not necessarily Wikipedia (e.g. the Enterprise Data Management's Semantics Repository).  The way it would work conceptually would be to associate a link to Wikipedia with any term.

It might be thought that Wikipedia only deals with common terms, and not specialized technical terms.  However, there are a good number of technical terms that are present in Wikipedia.

My first reaction was both "yes" and "no".  "Yes" because it is simply obvious there is considerable value in Wikipedia, but "no" because Wikipedia does not understand the enterprise I work in, which ultimately supplies an enormous amount of context that influences definitions.   

I will have to think about this topic some more before I can fully answer it.  But, I at least wanted to capture a few initial ideas.  I take it for granted that Wikipedia has value, so I need to think why this value might be so limited that we still need to do definitions.   

(a) Wikipedia cannot provide details of a concept which is defined by a common relation of the instances included in the concept to another concept (usually a special way of managing these instances) that is unique to the enterprise (or part of the enterprise).  So Wikipedia cannot tell us what a Financial Asset is for our enterprise, because what we include in "Financial Asset" depends on our business model.    

(b) Wikipedia cannot deal with definitions modified on a per-context basis.  Speech communities are contexts.  So, for instance, Wikipedia cannot tell us what our Marketing department considers a Customer to be, versus what our Accounts Receivables department considers a Customer to be.  Wikipedia does not know the speech communities in our enterprise.

(c) The structure of Wikipedia entries differs on a per page basis.  There is no consistent set of sections to a definition, nor metadata for a definition.  This might inhibit use in an enterprise.

(d) Concepts are arranged in concept systems.  A definition shows how a concept is placed in a concept system.  One concept can occur in many concept systems, and the definition is modified in each case.

(e) Wikipedia can be wrong.  I have found errors, but very few - so I am not sure how valid this objection is.

Some of the above points may or may not overlap.  They are also preliminary, so subject to revision. 

That is all for now - I will have to return to this one.  However, the question raised in the title is one that must be answered.

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