“But no one, no matter how intelligent, could make good inferences from bad data.”
Source: The Heritage Universe, Transcendence (1992), Chapter 11 (p. 126)
Swift, 2 September 2005, "Another New Fan" http://www.randi.org/jr/2006-10/100620sentient.html#i7
“But no one, no matter how intelligent, could make good inferences from bad data.”
Source: The Heritage Universe, Transcendence (1992), Chapter 11 (p. 126)
Towards a Systems Theory of Organization, 1985, From Data to Wisdom, 1989
David A Nadler, Feedback and Organizational Development Using Data-Based Methods. Reading, Mass Addison-Wesley, 1977, p. 140; Cited in: Arthur G. Bedeian (1980). Organizations: Theory and Analysis : Text and Cases. p. 43.
“We’re inferring from an absence of data,” Jacque said. “That’s lousy science.”
Source: Mindbridge (1976), Chapter 28 “Chapter Eight” (p. 104)
any data having geospatial referencing
Source: Research challenges in geovisualization (2001), p. 3
Source: The Relevance of Manipulation to the Process of Perception, 1977, p. 133
“Data! data! data!" he cried impatiently. "I can't make bricks without clay.”
Source: The Adventure of the Copper Beeches
As quoted in Management and the Computer of the Future (1962) by Sloan School of Management, p. 273
Context: We must include in any language with which we hope to describe complex data-processing situations the capability for describing data. We must also include a mechanism for determining the priorities to be applied to the data. These priorities are not fixed and are indicated in many cases by the data.
Thus we must have a language and a structure that will take care of the data descriptions and priorities, as well as the operations we wish to perform. If we think seriously about these problems, we find that we cannot work with procedures alone, since they are sequential. We need to define the problem instead of the procedures. The Language Structures Group of the Codasyl Committee has been studying the structure of languages that can be used to describe data-processing problems. The Group started out by trying to design a language for stating procedures, but soon discovered that what was really required was a description of the data and a statement of the relationships between the data sets. The Group has since begun writing an algebra of processes, the background for a theory of data processing.
Clearly, we must break away from the sequential and not limit the computers. We must state definitions and provide for priorities and descriptions of data. We must state relationships, not procedures.