# "*": "https://raw.githubusercontent.com/wefindx/schema/master/method/oo-item.yaml" # "base:title": "0oo - A Transdisciplinary Lingua Franca" "og:title": "A Transdisciplinary Lingua Franca" "og:description": "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 …" "og:image": "https://avatars0.githubusercontent.com/u/28134655" "og:url": "/method/1041/" "base:css": "/static/css/bootstrap.min.9c25540d6272.css" "base:extra-css": "/static/css/base.57997aeac1df.css" "base:favicon": "/static/favicon.acaa334f0136.ico" "base:body_class": "" "layout:logo": "/static/0oo.8d2a8bbef612.svg" "layout:index": "/" "layout:menu": "/menu/" "layout:categories": "/intents/" "layout:ideas": "/methods/" "layout:projects": "/projects/" "layout:users": "/users/" "layout:about": "/about/" "layout:help": "/help/" "layout:bug_report": "https://github.com/wefindx/0oo" "layout:login": "/accounts/login/" "layout:light-off": "/darken/?darken=true" "layout:set-multilingual": "/mulang/?mulang=true" "layout:lang": "Язык" "layout:set-language-post-action": "/i18n/setlang/" "layout:csrf-token": "DS82wgRyDak2Vwj0cWwmDnwLR6sYyrstA1wOQcP220ALg2Ed94D3YZwweFs8JlxU" "layout:input-next": "/method/1041/" "layout:languages": [{"code": "ja", "is-active": "false", "name": "日本語"}, {"code": "lt", "is-active": "false", "name": "Lietuviškai"}, {"code": "zh-hans", "is-active": "false", "name": "简体中文"}, {"code": "en", "is-active": "false", "name": "English"}, {"code": "ru", "is-active": "true", "name": "Русский"}, {"code": "oo", "is-active": "false", "name": "O;o,"}] # "item:parent:intents": [{"url": "/intent/21/", "title": "Procedūrinių žinių prieinamumas"}, {"url": "/intent/1063/", "title": "Project Based Learning"}] "item:title": ".:en:A Transdisciplinary Lingua Franca.:cn:跨学科的语言文字" "item:summary": "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." "item:voting": +4 "item:voting:add": "/admin/hlog/voting/add/?method=1041" "item:voting:csrf_token": "DS82wgRyDak2Vwj0cWwmDnwLR6sYyrstA1wOQcP220ALg2Ed94D3YZwweFs8JlxU" "item:voting:submit-value-option": {"selected": "[-]", "value": "-"} "item:base-administration": false "item:body": | 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 `TYPES`, `FUNCTIONS`, `VARIABLES`, `VALUES`, `OPERATIONS` and `PROCESSES`. However, as Alan Turing had shown, these processes decompose into simple INPUT/OUTPUT of bits. In Physics, scientists study `INPUT/OUTPUT` processes of `MATTER` and `ENERGY` instead, and use mathematics to model the changes they see, formalizing and approximating their behaviors with [field equations](https://en.wikipedia.org/wiki/Field_equation) describing [phase spaces](https://en.wikipedia.org/wiki/Phase_space). (Note: as we discussed on the idea "[MRSGREN](https://0oo.li/method/1013/mrsgren-digital-organism-interface)", humans do that `I/O` of `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. "item:source-date": "" "item:permalink": "/method/1041/?l=ru" "item:owner": "Mindey" "item:created": "2021-02-21T07:01:18.772781" "item:ownerlink": "/user/147/Mindey" # "item:link:add": "/admin/hlog/link/add/?parent=1041" "item:link:items": - "id": "l-8001" "url": "https://github.com/wefindx/nrv/blob/master/nrv/v3.py" "text": ".:en:Data Alignment Protocol.:cn:数据对齐协议" "note": | 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' "owner": "Mindey" "ownerlink": "/user/147/Mindey" "permalink": "/method/1041/?l=ru#l-8001" "created": "2021-06-18T07:32:40.812689" "item:project:items": - "id": "p-1017" "title": "Network Resource Vocabulary Development Group" "url": "/project/1017/" "mission": "The sole purpose is to introduce, evolve and maintain data alignment protocol." "owner": "Mindey" "ownerlink": "/user/147/Mindey" "created": "2021-02-22T01:07:38.681480" "permalink": "/method/1041/?l=ru#p-1017" - "id": "p-235" "title": "0 > oo" "url": "/project/235/" "mission": "Global financial think-tank for pursuing goals together." "owner": "Mindey" "ownerlink": "/user/147/Mindey" "created": "2015-08-18T13:57:29.854000" "permalink": "/method/1041/?l=ru#p-235" # "item:comment:items": - "id": "a-11001" "mtrans": | Как ввод-вывод становится: <Типы, функции, процессы, операции, переменные и значения?> 10100111011010101010101101101100101011 Все это заставляет меня задаться вопросом, как простая машина Тьюринга превратилась в эти 6 вещей, с которыми мы так часто встречаемся. Очевидно: - ** Значения **: это данные ** ленты Тьюринга ** или состояния. - ** Типы **: просто общие шаблоны на ** Ленте Тьюринга **. - ** Переменные **: размещаются на ** ленте Тьюринга **. - ** Операции **: это то, что происходит, когда ** Часы ** тикают с места чтения-записи. - ** Процессы **: это физические ** Часы **, которые выполняют операции - двигатели машины Тьюринга и головка чтения / записи. - ** Функции **: это «функция» ** тип ** ** переменных **, которые хранят значения как возможные ** операции ** для выполнения. Нетрудно увидеть, как все, что делает компьютер, четко сводится к этим вещам. Мне было бы интересно узнать, как компьютер полностью построен из вентилей NAND или как мозг полностью построен из асинхронных нейронов, и какие идеи мы можем получить из понимания того, как эти низкоуровневые вещи превращаются в эти 6 концепций, потому что я видят те же самые [концепции](https://0oo.li/method/923/supercategories-for-public-intelligence-standardization) управляющие общества. Возможно, понимание того, как информационные процессы превращаются в эти 6 вещей, поможет придумать что-то (например, форму организации) принципиально нового. Есть более абстрактные вещи, такие как [модель уравнения](https://0oo.li/method/936/operation-search-equations), и даже более абстрактные вещи, такие как [поликонтекстный метасимвол](https://0oo.li / метод / 863 / метаформат). Есть ли что-то вроде универсальной аддитивности и как она может привести к универсальному благу? Интересно отметить, что «Категории» и «Типы» - это «Вопросы», «Квесты» и «Запросы» ... совпадают с «Целями», «Намерениями», «Проблемами», «Доменами», «Интересы». Это означает, что [Запросы - это категории](https://twitter.com/mindeyi/status/1373851121261940737): каждый поисковый запрос - это категория. "text": | 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: - **Values**: it's the **Turing Tape** data, or states. - **Types**: just common patterns on the **Turing Tape**. - **Variables**: places on **Turing Tape**. - **Operations**: it's what happens when the **Clock** ticks with read-write places. - **Processes**: it's the physical **Clocks** that make operations happen - the Turing Machine's motors and read/write head. - **Functions**: it's 'function' **type** of **variables** that store values as possible **operations** to execute. 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](https://0oo.li/method/923/supercategories-for-public-intelligence-standardization) 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](https://0oo.li/method/936/operation-search-equations), and even more abstract thing like [polycontext metasymbol](https://0oo.li/method/863/metaformat). Is there something like universal additivity, and how can it converge towards the universal good? It's interesting to observe, that `Categories` and `Types` are `Questions`, `Quests` and `Queries`... coincide with `Goals`, `Intents`, `Problems`, `Domains`, `Interests`. It means that [Queries are Categories](https://twitter.com/mindeyi/status/1373851121261940737): every search query is a category. "owner": "Mindey" "ownerlink": "/user/147/Mindey" "permalink": "/method/1041/?l=ru#a-11001" "created": "2021-03-22T08:03:01.416762" - "id": "a-147001" "mtrans": | Я думаю, важно отметить, что типы, переменные, классы, методы, классы типов - это просто синтаксический сахар, используемый компилятором. Как таковые, они фактически не существуют в компьютерном коде. В конечном итоге компилятор генерирует последовательность инструкций. Нет инструкции для переменной, метода или типа. Абстракции компилятора не приводят к вычислениям! Я думаю, что отчасти компьютеры настолько несовместимы, что это досадное ограничение. Важна структура данных и поля, которые используются разными реализациями. Это то, что делает код совместимым. Сделаю категорию несовместимого компьютерного кода. "text": | 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. "owner": "chronological" "ownerlink": "/user/198/chronological" "permalink": "/method/1041/?l=ru#a-147001" "created": "2021-09-04T10:39:16.482555" "base:js": "/static/js/base.c7357c06cc89.js"