Level of Abstraction
From CasGroup
| Line 2: | Line 2: | ||
A "level of abstraction" for computing is the number of abstraction layers between the physical layer (of bits and binary code) and the current representation. A layer is a code, language or protocol which offers a certain service. For example in a computer we have the language cascade from binary code to machine code, byte code and high level code, or the OSI Reference Model. The most common abstraction layer is the programming interface (API) between an application and a framework or operating system. High-level calls are made to the system, which executes the necessary instructions to perform the task. | A "level of abstraction" for computing is the number of abstraction layers between the physical layer (of bits and binary code) and the current representation. A layer is a code, language or protocol which offers a certain service. For example in a computer we have the language cascade from binary code to machine code, byte code and high level code, or the OSI Reference Model. The most common abstraction layer is the programming interface (API) between an application and a framework or operating system. High-level calls are made to the system, which executes the necessary instructions to perform the task. | ||
| + | |||
| + | Russ Abbott has argued in "The reductionist blind spot" that the best way to understand [[Emergence|emergence]] is through the lens of implementation - emergent properties can be described as a high level abstraction which is implemented by low level elements. The lower level of abstraction implements the higher level. | ||
| + | |||
== Links == | == Links == | ||
