# "*": "https://raw.githubusercontent.com/wefindx/schema/master/project/oo-item.yaml" # "base:title": "0oo - Network Resource Vocabulary Development Group" "og:title": "Network Resource Vocabulary Development Group" "og:description": "The project provides a package with an evolution of versions of the vocabulary (latest being [v3](https://github.com/wefindx/nrv/blob/master/nrv/v3.py)), to help categorize tables or collections of databases into categories based on the kinds of records, that they store. The vocabulary is derived, mostly, from the ideas linked, especially the "A Transdisciplinary Lingua Franca" idea. It can be used simply annotating tables in the databases using them as part of database collection names or storing the labels as part of the collection or table metadata. Currently, it is in use in some of our databases by naming collections, and using double-colon, in the following …" "og:image": "https://avatars0.githubusercontent.com/u/28134655" "og:url": "/intent/1017/" "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": "d60ck0jJDSK1ZSJQ8dhJo6QI4hMiz1MRWijmd3om2bzwgfmfSmsjKkEVbr1T85QY" "layout:input-next": "/project/1017/" "layout:languages": [{"code": "ja", "is-active": "true", "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": "false", "name": "Русский"}, {"code": "oo", "is-active": "false", "name": "O;o,"}] # "item:parent:methods": [{"url": "/method/1041/", "title": "A Transdisciplinary Lingua Franca"}, {"url": "/method/923/", "title": "Supercategories for Public Intelligence Standardization"}, {"url": "/method/222/", "title": "Network of Functions"}] "item:title": "Network Resource Vocabulary Development Group" "item:score": -1.0 "item:mission": "The sole purpose is to introduce, evolve and maintain data alignment protocol." "item:permalink": "/project/1017/?l=ja" "item:base-administration": false "item:body": | The project provides a package with an evolution of versions of the vocabulary (latest being [v3](https://github.com/wefindx/nrv/blob/master/nrv/v3.py)), to help categorize tables or collections of databases into categories based on the kinds of records, that they store. The vocabulary is derived, mostly, from the ideas linked, especially the "A Transdisciplinary Lingua Franca" idea. It can be used simply annotating tables in the databases using them as part of database collection names or storing the labels as part of the collection or table metadata. Currently, it is in use in some of our databases by naming collections, and using double-colon, in the following fashion. Suppose you have a database collection named `table_name`, we just write: `table_name::v3/system:person` to indicate that this collection stores information about systems, that are persons. This is useful, especially in information retrieval, when there is large quantity of databases, each with a different structure, and is helpful to see, what each table is about at a glance. The vocabulary also introduces the short codes from 100 to 600 to refer concisely to these category classes. For example, `system:person` is **[470](https://github.com/wefindx/nrv/blob/master/nrv/v3.py)** according to NRV v3. This is partly inspired by [HTTP response codes](https://www.restapitutorial.com/httpstatuscodes.html): just like we can know the nature of response, wouldn't it be great, if a data packet that we receive would tell also the semantic information on what it is about? Therefore, some time, once this vocabulary matures, this may make sense to introduce it as an RFC for a standard for semantic labeling of "data packets as records". **NOTE:** Both the project 0oo, and the NRV are based on shared ideas, however, while 0oo takes on a monolithic approach to develop a self-sufficient single "Economy as an Ontology and an App", the NRV approach is that of looking back at the systems of the world that exist, and labeling all that while indexing them. "item:destinations": | "item:source-date": "" "item:permalink": "/method/1017/?l=ja" "item:owner": "Mindey" "item:created": "2021-02-22T01:07:38.681480" "item:ownerlink": "/user/147/Mindey" # "item:result:items": - "id": "t-101" "url": "None" "text": | Add v3 version of the NRV. "cost": -1.0 "currency": "HUR" "assets": | - Swapped the 300 with 400, due to ordering the logic in [this](https://0oo.li/method/1041/a-transdisciplinary-lingua-franca#1613904432) idea. - Introduced 600 by separating Locations from 100, as talked in [this](https://0oo.li/method/222/?l=en#a-1082) comment. "owner": "Mindey" "ownerlink": "/user/147/Mindey" "permalink": "/project/1017/?l=ja#t-101" "created": "2021-02-22T01:11:39.367023" "happened": "2021-02-22T01:08:00" "models": "item:result:add": "/admin/hlog/task/add/?parent=1017" "item:transfer:items": "item:transfer:add": "/admin/hlog/operation/add/?parent=1017" "item:comment:add": "/projects/addnote?parent=1017" "item:comment:add:csrf_token": "d60ck0jJDSK1ZSJQ8dhJo6QI4hMiz1MRWijmd3om2bzwgfmfSmsjKkEVbr1T85QY" "item:comment:form": |
  • コメントが新しい問題を挙げるとマークする。
  • コメントが潜在的な解決を提供するとマークする。
  • コメントが推論に役に立つの事実があるとマークする。
  • コメントがすべきのタスクがあるとマークする。
  • ログインしてください。 # "comments": - "id": "c-68001" "mtrans": | プロジェクトの詳細は圧倒的であるため、プロジェクトに関するコメントは、電報のメインディスカッションストリームに送られるべきではありません。プロジェクトの詳細は、アイデアや質問よりも「共通」ではなく、広く一般の注目を集める価値があります。プロジェクトのコメントは通常、グループのローカルな注目に値するものであり、コンテキスト(公開されて共有され、発見可能な)コメントは公開されます(ただし、通知を叫ぶことはありません)。 "text": | Comments on projects should not go to the main discussion stream on telegram regarding interests and ideas, because the project details are overwhelming, -- they are less of "commons" than ideas and questions, that really are worthy the broad public attention. The project comments usually are worthy the local attention of the group, and contextual (publicly shared, discoverable) comments for public (but without screaming notifications). "owner": "Mindey" "ownerlink": "/user/147/Mindey" "permalink": "/method/1017/?l=ja#c-68001" "created": "" "base:js": "/static/js/base.c7357c06cc89.js"