Skip to main content

Definition Reference


In the previous posts I had the idea of a person or group that creates a definition.  This was a rough draft of a part of another concept system that I am calling Definition Reference.  Figure 1 shows this concept system.  The unquoted terms are the official terms in this concept system.  The quoted terms are shortened versions of the official terms, which are univocal (have only one meaning) within the concept system, but are generally equivocal (have more than one meaning) if you increase scope to beyond the system shown here, and must be used with care.





Figure 1: Definition Reference Concept System

The Concepts in The System

The concepts in this system are as follows:

Definition Reference: a source of a definition

Informal Definition Source: a Definition Reference that cannot be relied upon. There is no guarantee that it is correct.

Definition Authority: a Definition Reference that can be relied on. There is some kind of guarantee that it is correct.

Definition Authoritative Reference: a Definition Authority that has recorded a definition, but did not create it.

Definition Creator: a Definition Authority that created a definition

Definition Analyst: a Definition Creator who creates a definition in the absence of one, but does not claim to have originally created the definition.

Definition Stipulator: a Definition Creator who claims to have originally created a definition

Legislative Definition Authority: a Definition Stipulator who has legitimacy sufficient to make a definition they create binding upon one or more Legislative Definition Users.

Recognized Expert: a Definition Stipulator whose prestige or reputation is sufficient to make a definition they create acceptable to one or more people.

Informal Stipulator: a Definition Stipulator who has no basis for obtaining acceptance of a definition they create.

Thoughts

I am happy with this so far. Here are some random thoughts:

(1) The concept system is a purely generic one (like a Tree of Porphyry). Everything in it is a genus or species of something else (or supertype and subtype if you prefer). This makes it easy to deal with - every relationship if of the same type ("is genus of").

(2) It is easy to see how terms will be shortened and how confusion can occur even within this concept system. For instance, if someone uses the term "Authority" they might mean Definition Authority, Definition Authoritative Reference, or Legislative Definition Authority.

(3) The species (subtypes) of Definition Stipulator are worrying. They only exist in reference to how people accept the definitions. A law with a particular definition that is passed in Canada will not affect me in the USA. I might not recognize an individual as an expert because I am unfamiliar with their work. This area needs further investigation, and it is missing relationships to users of definitions (see Legislative Definition User in prior posts). Also, this is where we depart from the Tree of Porphyry structure.

(4) I think the concept system provides good input to a governance framework for definition management.

(5) I need to expand the definitions provided above - they are preliminary and abbreviated.

(6) I think I can make some of the differentia contradictory. For instance Definition Authority descends into two contradictory species, depending on whether the definition was created or not. This means that I will not have missed any other class at this level. However, I do not think I can reliably do this everywhere.

(7) By creating a visual concept system, it becomes much easier to formulate definitions. I know this is not the point of this post, but it struck me how easy it was to write the definitions with the diagram in front of me. If I was doing a glossary, all the terms would be distributed throughout it and would need much more robust definitions. For example in a prior post I had Legislative Definition Authority (then simply termed "Authority") defined as "an individual person or organization who has legitimacy sufficient to make any Legislative Definition they create binding on one or more Legislative Definition Users".

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

WRITE "I LOVE YOU" ON CMD BY USING NOTEPAD

I had previously posted about   Matrix effect   using Notepad   as well as cool batch file  programs. In this post i will share with you guys  the cool and awesome  Notepad Tricks .  As name suggest you don't require any program other then Notepad.  So lets get started. 1. Open  Notepad   and copy below code. @echo off color 0A :A echo IIIIIII     L      OOOOOO V           V  EEEEEE     Y       Y  OOOOOO  U     U  ping -a .9 >nul echo    I        L      O    O  V         V   E           Y     Y   O    O  U     U  ping -b .9 >nul  echo    I        L      O    O   V       V    E   ...

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