# <!-- METAHEADER
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"*": "https://raw.githubusercontent.com/wefindx/schema/master/method/oo-item.yaml"
# <!-- HEADER
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"base:title": "0oo - A Numeric Code to Refer to Goals and Ideas, etc."
"og:title": "A Numeric Code to Refer to Goals and Ideas, etc."
"og:description": "Use culturally-neutral supra-organizational IDs for goals, ideas, projects, etc. to refer to them in multilingual media, so that it is clear what goals and ideas we are representing, regardless of language. For example, it is probably not hard to imagine &quot;[G 15](https://0oo.li/intent/15)&quot;, &quot;[G 20](https://0oo.li/intent/20)&quot;, &quot;[I 120](https://0oo.li/method/120)&quot;, etc. becoming well known, like brand names. In fact, on Infinity Project, we already have something like it, for example, we use letters and our database object IDs to refer to: - G [Goal] - I [Idea] - P [Plan/Project] - S [Step/Milestone] - T [Task] Make this database available over API, and IDs …"
"og:image": "https://avatars0.githubusercontent.com/u/28134655"
"og:url": "/method/186/"
"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": "Kalba"
"layout:set-language-post-action": "/i18n/setlang/"
"layout:csrf-token": "Pta687OfpbCCqftar9dlGu9MY8aoFsCaLNNFjJhcnpXH3ejds9qqkU3PzThZvt6e"
"layout:input-next": "/method/186/"
"layout:languages": [{"code": "ja", "is-active": "false", "name": "日本語"}, {"code": "lt", "is-active": "true", "name": "Lietuviškai"}, {"code": "zh-hans", "is-active": "false", "name": "简体中文"}, {"code": "en", "is-active": "false", "name": "English"}, {"code": "ru", "is-active": "false", "name": "Русский"}, {"code": "oo", "is-active": "false", "name": "O;o,"}]
# <!-- TOPIC
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"item:parent:intents": [{"url": "/intent/63/", "title": "Uniting behind goals"}]
"item:title": ".:en:A Numeric Code to Refer to Goals and Ideas, etc."
"item:summary": ".:en:Design a code name system to refer to goals and ideas, easy to use in any language."
"item:voting": +1
"item:voting:add": "/admin/hlog/voting/add/?method=186"
"item:voting:csrf_token": "Pta687OfpbCCqftar9dlGu9MY8aoFsCaLNNFjJhcnpXH3ejds9qqkU3PzThZvt6e"
"item:voting:submit-value-option": {"selected": "[-]", "value": "-"}
"item:base-administration": false
"item:body": |
    .:en
    Use culturally-neutral supra-organizational IDs for goals, ideas, projects, etc. to refer to them in multilingual media, so that it is clear what goals and ideas we are representing, regardless of language. For example, it is probably not hard to imagine "[G 15](https://0oo.li/intent/15)", "[G 20](https://0oo.li/intent/20)", "[I 120](https://0oo.li/method/120)", etc. becoming well known, like brand names.
    
    In fact, on Infinity Project, we already have something like it, for example, we use letters and our database object IDs to refer to:
    
    - G [Goal]
    - I [Idea]
    - P [Plan/Project]
    - S [Step/Milestone]
    - T [Task]
    
    Make this database available over API, and IDs - globally-register-able.
"item:source-date": ""
"item:permalink": "/method/186/?l=lt"
"item:owner": "Mindey"
"item:created": "2016-06-16T13:25:47.391000"
"item:ownerlink": "/user/147/Mindey"
# <!-- LINKS
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"item:link:add": "/admin/hlog/link/add/?parent=186"
"item:link:items":
"item:project:items":

# <!-- COMMENTS
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"item:comment:items":
- "id": "a-251001"
  "mtrans": |

    Atominiai skaičiai apibrėžia atomų savybes. Taigi skaičiai yra tapatybės.

  "text": |
    Atomic numbers define the properties of atoms. So numbers are identities.
  "owner": "chronological"
  "ownerlink": "/user/198/chronological"
  "permalink": "/method/186/?l=lt#a-251001"
  "created": "2022-05-06T07:57:50.566847"
- "id": "a-252001"
  "mtrans": |

    Galbūt nukleonų skaičius [atomuose](https://ptable.com/) yra susijęs su [sveikųjų skaičių sekomis](https://oeis.org/) – kas žino? Be to, skaičiai gali būti vardų erdvėje, kaip ir kintamieji OOP programavimo kalbose, ir tai jau plačiai naudojama įvairiose srityse.

  "text": |
    Maybe the numbers of nucleons within [atoms](https://ptable.com/) are associated with [integer sequences](https://oeis.org/) - who knows? That said, numbers can be namespaced, just like variables in OOP programming languages, and it is already being widely used in various domains.
  "owner": "Mindey"
  "ownerlink": "/user/147/Mindey"
  "permalink": "/method/186/?l=lt#a-252001"
  "created": "2022-05-06T16:37:02.669833"
- "id": "a-253001"
  "mtrans": |

    Aš klydau, kad logaritmas buvo naudojamas intervalams tarp atomų subapvalių. Nežinau, kodėl taip maniau.
    
    Įdomus ir atominių skaičių pasiskirstymas.

  "text": |
    I was wrong of the logarithm being used for ranges between atom subshells..not sure why I thought that.
    
    The distribution of atomic numbers is interesting too.
  "owner": "chronological"
  "ownerlink": "/user/198/chronological"
  "permalink": "/method/186/?l=lt#a-253001"
  "created": "2022-05-09T05:59:13.403885"
"base:js": "/static/js/base.c7357c06cc89.js"