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.
“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.”
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.
Help us to complete the source, original and additional information
Grace Hopper 22
American computer scientist and United States Navy officer 1906–1992Related quotes
Message to Git mailing list, Torvalds, Linus, 2006-06-27, 2006-08-28 http://lwn.net/Articles/193245/,
2000s, 2006
and that was simply false to begin with. We had no problem at all identifying these people from the beginning."
source: William Binney - 'The Government is Profiling You' - video lecture at MIT https://www.youtube.com/watch?v=qB3KR8fWNh0
Source: Seth, Dreams & Projections of Consciousness, (1986), p. 273, quoting from Session 212
Relational Database: A Practical Foundation for Productivity (1982)
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.
As quoted in "Exclusive: President François Hollande Talks Syria, Spies and Secrets With TIME" http://time.com/4936/exclusive-france-president-francois-hollande-time/ (5 February 2014), by Catherine Mayer, Time.
Towards a Systems Theory of Organization, 1985, From Data to Wisdom, 1989
"Universalism and Relativism in the Study of Ethnic music", Ethnomusicology 4, no. 2:49-54 (1960); reprinted in Reading in Ethnomusicology, p. 270-71.