# "*": "https://raw.githubusercontent.com/wefindx/schema/master/method/oo-item.yaml" # "base:title": "0oo - Tagfixes" "og:title": "Tagfixes" "og:description": "Now, today, people use simple hashtags, where they have a TOPIC, as a hashtag. E.g., today we had a hashtag #FOW (future of work), and people came to talk about the problem, namely [the technological unemployment problem](https://0oo.li/intent/77/). This topic connects various problems, ideas, etc. about objects, and events of the future. In the conceptual structure of the Infinity Project, we have **NGIPS**: - **N**EEDS (=CONCEPTS refering to RANDOM VARIABLES that may be needed or not needed) - **G**OALS (=vectors of inequalities or domain regions about the things NEEDs refering to RANDOM VECTOR of concepts refer to) - **I**DEAS (=TRANSFORMATIONS or …" "og:image": "https://wiki.mindey.com/shared/shots/3890806df1ebf44142f150c1d.png" "og:url": "/method/184/" "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-monolingual": "/mulang/?mulang=false" "layout:lang": "Language" "layout:set-language-post-action": "/i18n/setlang/" "layout:csrf-token": "g3X5Q3pVR1ezpS8NKi6Mk95V0R530wsGUYiyPFqDUBjvtJ7TMQruiTeUHQkweFKm" "layout:input-next": "/method/184/" "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": "true", "name": "English"}, {"code": "ru", "is-active": "false", "name": "Русский"}, {"code": "oo", "is-active": "false", "name": "O;o,"}] # "item:parent:intents": [{"url": "/intent/61/", "title": "People often talk about solutions in conferences, but don't collect them for action afterwards"}] "item:title": ".:en:Tagfixes" "item:summary": ".:en:Property tags -- tags to refer to properties of topics in social conversations" "item:voting": +1 "item:voting:add": "/admin/hlog/voting/add/?method=184" "item:voting:csrf_token": "g3X5Q3pVR1ezpS8NKi6Mk95V0R530wsGUYiyPFqDUBjvtJ7TMQruiTeUHQkweFKm" "item:voting:submit-value-option": {"selected": "[-]", "value": "-"} "item:voting:submit-value-option": {"selected": "[+]", "value": "+"} "item:base-administration": false "item:body": | .:en Now, today, people use simple hashtags, where they have a TOPIC, as a hashtag. E.g., today we had a hashtag #FOW (future of work), and people came to talk about the problem, namely [the technological unemployment problem](https://0oo.li/intent/77/). This topic connects various problems, ideas, etc. about objects, and events of the future. In the conceptual structure of the Infinity Project, we have **NGIPS**: - **N**EEDS (=CONCEPTS refering to RANDOM VARIABLES that may be needed or not needed) - **G**OALS (=vectors of inequalities or domain regions about the things NEEDs refering to RANDOM VECTOR of concepts refer to) - **I**DEAS (=TRANSFORMATIONS or methods or dependencies that allow to affect concepts of NEEDs definign GOALs via other variables) - **P**LANS (=instances of IDEAs, organized attempts to apply IDEA=Transformation to actual resources) - **S**TEPS (explicit parts of PLAN) // we plan to remove STEP, WORK, and leave only what we call "STEP hierarchy" or a PROGRAM. However, according to the [NOPES idea](http://www.halfbakery.com/idea/NOPES_20-_20Notes_20for_20interPersonal_20communications) on halfbakery, notes about subjects can be summarized by extracting **NOPES**: - **N**AMES (=references to individuals and organizations) - **O**BJECTS (=references to physical things) - **P**LACES (=references to physical places) - **E**VENTS (=references to spatio-temporal locations) - **S**UBJECTS (=references to locations of mind-spaces, e.g., propositions) **NGIPS** can be desired and executed by individuals and organizations (NAMES), and defined in terms of other NAMES, OBJECTS, PLACES, EVENTS. So, in order to define **NGIPS**, people generally use **NOPE**. The remaining part, seems to be the "S" (SUBJECTS), which are the topics themselves under this conceptualization. Therefore recently, renaming some parts of NOPES, I had [tweeted](https://twitter.com/mindeyi/status/727416767056859136) that it seems, that NAMES talk about SUBJECTS, which are NEEDS, GOALS, IDEAS, PLANS,.. regarding OBJECTS, PLACES, EVENTS, and other NAMES. In other words, I told it a bit more humanly: All TOPICS seem to be about the NEEDS, GOALS, IDEAS and PLANS of AGENTS regarding physical THINGS, PLACES, EVENTS, them and other AGENTS... So, to index them, we could introduce "tagfixes" -- hierarchical namespaced hashtags. Some simple syntax sugar might be necessary for this to work. E.g #FOW%PROBLEM -- for describing a problem #FOW%IDEA -- for describing an idea There are many types of ideas, for example, some could be called "INSIGHTS" and used as tagfix `#FOW%INSIGHT` when tweeting , and while insights not always have an explicit problem that they address, they could be mapped with the problems later on, after discussion. Of course, we use a different sign, and not necessarily percent sign to create (`#`) hashtags with "suffixes" (`%`) ("tagfixes"). "item:source-date": "" "item:permalink": "/method/184/?l=en" "item:owner": "Mindey" "item:created": "2016-05-04T12:05:13.746000" "item:ownerlink": "/user/147/Mindey" # "item:link:items": "item:link:add": "/admin/hlog/link/add/?parent=184" "item:project:items": "item:project:add": "/admin/hlog/project/add/?parent=184" "item:comment:add": "/methods/addnote?parent=184" "item:comment:add:csrf_token": "g3X5Q3pVR1ezpS8NKi6Mk95V0R530wsGUYiyPFqDUBjvtJ7TMQruiTeUHQkweFKm" "item:comment:form": |
  • Mark if the comment raises new questions.
  • Mark if the comment contributes potential solutions.
  • Mark if the comment contributes facts for reasoning.
  • Please, log in. # "item:comment:items": "base:js": "/static/js/base.c7357c06cc89.js"