Introduce a tiny set of exhaustive transdisciplinary concepts that most people are intimately familiar with, that can represent all processes that people go through to build their worlds, then use them to organize information, and get people understand the modern world.
One of the hardest things in ensuring access know-how is knowledge representation. It is not easy to find concepts that most people would be intimately familiar with, and yet that those concepts would map well across disciplines. So, here is one set of such concepts: to ask
Questions, then proceeding to search for
Ideas to answer them, then to start and run
Projects based on those ideas, and to do
Tasks (or "
Challenges") with respect to relevant
Places to obtain
Results. The below is an illustration of how transdisciplinary those concepts are, comparing them with the equivalent concepts in computer science and how they are related to the physics.
In Computer Sciences, these concepts correspond to what programmer does within their programs, that rely on
PROCESSES. However, as Alan Turing had shown, these processes decompose into simple INPUT/OUTPUT of bits.
In Physics, scientists study
INPUT/OUTPUT processes of
ENERGY instead, and use mathematics to model the changes they see, formalizing and approximating their behaviors with field equations describing phase spaces. (Note: as we discussed on the idea "MRSGREN", humans do that
M/E as they live as well.)
Think of "
FIELD FLUX" in the image as computation -- in that sense, our industries are "physics apps", and if projects are examples of groups of humans "self-programming" to execute on their dreams, then having such examples of contextualized execution (or running of projects) in public would work like open source software, and this is an idea of one set of hypothetical of concepts to achieve this. This idea is currently is being tested here on 0oo.
The sole purpose is to introduce, evolve and maintain data alignment protocol.
This protocol (NRV v3) is based on this idea. Correspondance:
- 'VALUE' is '100 RESOURCE',
- 'TYPE' is '200 CATEGORY',
- 'FUNCTION' is '300 METHOD',
- 'PROCESS' is '400 SYSTEM',
- 'OPERATION' is '500 OPERATION',
- 'VARIABLE' is '600 LOCATION'
I / O如何變爲：<類型，函數，過程，操作，變量和值？>
10100111011010101101101101101100101011 這一切都使我感到奇怪，一個簡單的圖靈機如何變成這6種事物，我們如此共通。 明顯地：
-值：這是 Turing Tape 數據或狀態。 -類型：僅是圖靈磁帶上的常見圖案。 -變量：放在 Turing Tape 上。 -操作：當時鐘帶有讀寫位置時，會發生這種情況。 -過程：是物理的時鐘使操作得以實現-圖靈機的電機和讀/寫頭。 -函數：它是“變量”的“函數”類型，它存儲儘可能多的值來執行操作。
How does I/O become:
10100111011010101010101101101100101011 That all makes me wonder, how does a simple Turing Machine become these 6 things, that we are so common with. Obviously:
It's not hard to see how everything what computer does, clearly breaks down to these things. I would be interested in learning how computer is built entirely out of NAND gates, or how brain is built entirely out of asynchronous neurons, and what insights can we get from the understanding of how these low-level things becomes these 6 concepts, cause I do see these same concepts running societies. Perhaps understanding how information processes become these 6 things, would be help to come up with something (like a form of organization) that's fundamentally new. There are more abstract things, like the equation model, and even more abstract thing like polycontext metasymbol. Is there something like universal additivity, and how can it converge towards the universal good?
It's interesting to observe, that
Queries... coincide with
Interests. It means that Queries are Categories: every search query is a category.
I think it is important to note that types, variables, classes, methods, typeclasses are just syntactic sugar used by the compiler. As such they dont actually exist in computer code.
Ultimately what gets generated by the compiler is a sequence of instructions. There is no instruction for a variable or a method or a type.
Compiler abstractions result in no computation! I think part of why computers are so incompatible is that this is an unfortunate limitation. What matters is the data structure and fields that are shared between implementations. This is what makes code compatible.
I will make a category for incompatible computer code.