the distinction between data and intelligence

From: mountain man <>
Date: Fri, 10 Jun 2005 01:42:04 GMT
Message-ID: <Md6qe.11754$>

With varying reception I have attempted to discuss the concept of "organisational intelligence" (OI) informally defined as the collective sum of all program code elements associated with one or more DB applications used by an organisation, *and* the data held in the (R)DBMS. (ie: a union set)

I understand the contemporary database systems theory does not really invoke consideration of the associated application software environment of a database system, and basically considers only the (R)DBMS software layer, which essentially services the application and hosts the data and other DB services. (eg: Date has a small diagram in Ch.1)

In Codd's 1979 paper, "Extending the database relational model to capture more meaning", Codd opens his paper with the following phrased aim:

"The intent is to capture (in a more or less formal way) more of the meaning of the data so that database design can become more systematic and the database system itself can behave more intelligently".

Codd was aware of evolution, and was very much part of that process.

It is quite conceivable that, by their ability to also store processes and programs (such as stored procedures) current DBMS software is not just a repository for data, but for what may reasonably termed "intelligence" in respect of the organisation which has invested time and resources in incrementing automation.

Do you agree that the distinction between data and intelligence may be drawn informally as simply as I have done above (by the union with processes)?

Otherwise, how would you define the distinction between data and intelligence (for the purposes of database theory only budding philosophers!)?

Or, is such a distinction of little consequence?

Pete Brown
IT Managers & Engineers
Falls Creek
Received on Fri Jun 10 2005 - 03:42:04 CEST

Original text of this message